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

Does not work with some STM32L1 Medium+ parts #163

Closed
burnsfisher opened this issue Jun 18, 2013 · 6 comments · Fixed by #165
Closed

Does not work with some STM32L1 Medium+ parts #163

burnsfisher opened this issue Jun 18, 2013 · 6 comments · Fixed by #165

Comments

@burnsfisher
Copy link

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.

@burnsfisher
Copy link
Author

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...

@burnsfisher
Copy link
Author

Tested merged version against new STM32L1-DISCO board with 0x427 ID). All ok. Closing this bug report.

@Nightwalker-87
Copy link
Member

Related to #152.

@Nightwalker-87 Nightwalker-87 modified the milestones: v1.6.1, Feedback required Mar 20, 2020
@Nightwalker-87
Copy link
Member

@burnsfisher: I am doing project maintenance. Which PR was that? Can you have a look? Thx.

@burnsfisher
Copy link
Author

Looks like PR #165 which you already got. Thanks for checking!

@Nightwalker-87
Copy link
Member

Thank you so much for your helpful feedback. 👍

@Nightwalker-87 Nightwalker-87 linked a pull request Mar 24, 2020 that will close this issue
@stlink-org stlink-org locked as resolved and limited conversation to collaborators Apr 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants