-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Does not work with some STM32L1 Medium+ parts #163
Comments
I've fixed the problem in a fork, and have figured out how to do the pull request and have made it. Sorry for lots of messages, anyone watching... |
Tested merged version against new STM32L1-DISCO board with 0x427 ID). All ok. Closing this bug report. |
Related to #152. |
@burnsfisher: I am doing project maintenance. Which PR was that? Can you have a look? Thx. |
Looks like PR #165 which you already got. Thanks for checking! |
Thank you so much for your helpful feedback. 👍 |
The code has only STM32L1 device IDs 0x416 and 0x437. The device on the new Discovery board (STM32L1-DISCO) has ID 0x427.
I do have a patch for this problem. It shuffles the device names a bit (0x437 is now HIGH, 427 is MEDIUM_PLUS). I also added a longer timeout for the loader since I kept getting timeout messages despite everything working.
I'm new to working in this environment, so I'll provide the patch when I figure out how it is expected. Comments welcome, of course.
The text was updated successfully, but these errors were encountered: