Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[New Variant][on way] Heltec LoRa Node L151 #983

Closed
fthiebolt opened this issue Mar 11, 2020 · 5 comments
Closed

[New Variant][on way] Heltec LoRa Node L151 #983

fthiebolt opened this issue Mar 11, 2020 · 5 comments
Labels
new variant Add support of new bard waiting feedback Further information is required

Comments

@fthiebolt
Copy link

Heltec LoRa Node L151

  • features a STM32L151CCU6 + SX1276

==> initial support at https://github.com/fthiebolt/LoRa-boards-stm32duino

Bonjour Frederic,
After having added support to BSFrance LORAM3 L151 board for my university :), I started the same with Heltec LoRa Node L151: i then noticed a weird GPIO behaviour when applying proper product_line: STM32L151xC ... but this wrong behaviour disappear when setting STM32L151xB product line for this STM32L1R1CC device ?!?!
Thanks.
François

Note that user can add a STM32 based board following this wiki

Any contribution is welcome, so do not hesitate to submit a PR.

@fthiebolt fthiebolt added the new variant Add support of new bard label Mar 11, 2020
@fpistm
Copy link
Member

fpistm commented Mar 12, 2020

Hi,

You used the one generated from from STM32L151C(6-8-B)Tx.xml instead this one generated from STM32L151CCUx.xml:
https://github.com/stm32duino/Arduino_Tools/blob/master/src/genpinmap/Arduino/STM32L1/STM32L151CCUx/PeripheralPins.c

Anyway, as you use the macro to define the FLASH and RAM size it should be correct.

@fpistm fpistm added the waiting feedback Further information is required label Mar 12, 2020
@fthiebolt
Copy link
Author

Hello Frederic,

Ok, in branch 'development' from https://github.com/fthiebolt/LoRa-boards-stm32duino, i corrected things according to your message and i switch back product_line to STM32L151xC (because of STM32L151CCU6 onboard).
This way, you create a simple led_blink app and you'll discover that whenever you set a GPIO as an output, once set to HIGH, it's impossible to set it to LOW (pin level stuck HIGH ---verified with a scope).

F

@fpistm
Copy link
Member

fpistm commented Mar 12, 2020

I will not be able to test as I don't have a board with this chip.

@fpistm
Copy link
Member

fpistm commented Mar 13, 2020

@fthiebolt
Could you generate a basic example with STM32CubeMX and test to Toggle a GPIO (Blink)?
The if this is the same issue then open an issue in the STM32CubeL1 repo:
https://github.com/STMicroelectronics/STM32CubeL1

@fpistm
Copy link
Member

fpistm commented Mar 18, 2020

Do not hesitate to provide a PR.
I've added it to the request list to track.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new variant Add support of new bard waiting feedback Further information is required
Projects
None yet
Development

No branches or pull requests

2 participants