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

Fix for programming STM32L152 #138

Merged
merged 1 commit into from
Mar 22, 2013
Merged

Fix for programming STM32L152 #138

merged 1 commit into from
Mar 22, 2013

Conversation

6thimage
Copy link
Contributor

Commit 0ed3907 added the clearing of DMA registers that was preventing programming (see issue #74), however it uses hardcoded addresses of the DMA registers on the STM32F4. This seems to prevent the flashing and verification on STM32L1, as the registers only partly cover the range zeroed. So the DMA clearing has been limited to the STM32F4
microcontroller.

Additionally, sometimes, typically directly after erases, a 'flash loader run error' will occur that terminates the writing. This is not necessary, as the writing is successfully performed by page writing (line 1581 onwards of stlink-common.c), and so has been returned to a error message (see issue #112). There is a comment on line 1574 (added by Uwe Bonnes in commit 0164043) that this may happen on blank devices, and so the fatal error message is the incorrect response.

Commit 0ed3907 added the clearing of DMA registers that was preventing
programming (see issue stlink-org#74), however it uses hardcoded addresses of the
DMA registers on the STM32F4. This seems to prevent the flashing and
verification on STM32L1, as the registers only partly cover the range
zeroed. So the DMA clearing has been limited to the STM32F4
microcontroller.

Additionally, sometimes, typically directly after erases, a 'flash
loader run error' will occur that terminates the writing. This is not
necessary, as the writing is successfully performed by page writing
(line 1581 onwards of stlink-common.c), and so has been returned to a
error message (see issue stlink-org#112). There is a comment on line 1574 (added by
Uwe Bonnes in commit 0164043) that this may happen on blank devices,
and so the fatal error message is the incorrect response.
texane added a commit that referenced this pull request Mar 22, 2013
Fix for programming STM32L152
@texane texane merged commit d1635e8 into stlink-org:master Mar 22, 2013
@Nightwalker-87 Nightwalker-87 added this to the v1.2.0 and older milestone Feb 25, 2020
@stlink-org stlink-org locked as resolved and limited conversation to collaborators Apr 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants