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

STM32F217: Problem flashing #278

Closed
bebork opened this issue Oct 23, 2014 · 2 comments
Closed

STM32F217: Problem flashing #278

bebork opened this issue Oct 23, 2014 · 2 comments

Comments

@bebork
Copy link

bebork commented Oct 23, 2014

Currently I am playing around with a development board holding a STM32F217. The chip can be connected via an external STLink V2 adapter. I want use the fruits of the great work, which was done here, to flash the chip on my linux box. However it does not work. If I do ...

bebork@bubuwork ~/work/sandbox/stm32/test/stlink.git $ ./st-flash write Xynergy.bin 0x0800000
2014-10-23T22:50:14 INFO src/stlink-common.c: Loading device parameters....
2014-10-23T22:50:14 INFO src/stlink-common.c: Device connected is: F2 device, id 0x20016411
2014-10-23T22:50:14 INFO src/stlink-common.c: SRAM size: 0x20000 bytes (128 KiB), Flash: 0x100000 bytes (1024 KiB) in pages of 131072 bytes
bebork@bubuwork ~/work/sandbox/stm32/test/stlink.git $

So <st-flash> stops workink after determining SRAM and Flash size. Any suggestions to that?

By the way erasing the chip works properly ...

bebork@bubuwork ~/work/sandbox/stm32/test/stlink.git $ ./st-flash erase
2014-10-23T22:58:42 INFO src/stlink-common.c: Loading device parameters....
2014-10-23T22:58:42 INFO src/stlink-common.c: Device connected is: F2 device, id 0x20016411
2014-10-23T22:58:42 INFO src/stlink-common.c: SRAM size: 0x20000 bytes (128 KiB), Flash: 0x100000 bytes (1024 KiB) in pages of 131072 bytes
Mass erasing..............
bebork@bubuwork ~/work/sandbox/stm32/test/stlink.git $
@xor-gate
Copy link
Member

xor-gate commented May 5, 2016

Could you test with latest master and latest stlink programmer firmware (2.27)?

@Nightwalker-87
Copy link
Member

Here we can not precisely determine which version was used, only that this was v1.0.0 or even a commit prior to that (taken from the old stlink-common.c sourcefile name and the opening date).

I believe though that even a commit prior to 2e6ba20 was in use when this appeared. The latter corrected a typo in the flash size register address for the STM32F2 series that would explain the observed behaviour, where simply nothing happened. As no further investigation is possible, I'll close this now as resolved.

@Nightwalker-87 Nightwalker-87 removed this from the Old issues milestone Apr 9, 2020
@Nightwalker-87 Nightwalker-87 added this to the v1.2.0 and older milestone Apr 9, 2020
@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

No branches or pull requests

3 participants