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

*.flash targets don't work with current openocd and miss references #34

Closed
karlp opened this issue Dec 20, 2013 · 8 comments
Closed

*.flash targets don't work with current openocd and miss references #34

karlp opened this issue Dec 20, 2013 · 8 comments
Labels

Comments

@karlp
Copy link
Member

karlp commented Dec 20, 2013

There's references to SCRIPT_DIR and stlink_flash.scr and so on, it's duplicated in the different stm32 directories, and some of the flash erase commands aren't correct for recent/current openocd releases

@BuFran
Copy link
Member

BuFran commented Jan 2, 2014

Hi @karlp, is there any documentation of oocd, where i can find which flash erase command is needed for particular architecture ? I am adressing it on #37 but I have problem with doc.

@karlp
Copy link
Member Author

karlp commented Jan 2, 2014

Just drop the mass erase bit altogether... here's what I use for flashing via oocd on the command line

openocd -f board/stm32ldiscovery.cfg \
                    -c "init" -c "reset init" \
                    -c "flash write_image erase ${ELFY}" \
                    -c "reset" \
                    -c "shutdown"

@BuFran
Copy link
Member

BuFran commented Jan 2, 2014

hmmm nice, the "stm32l1x mass_erase 0" isn't needed ?

If I understood You correctly, the "erase" option will select appropriate stm32x mass_erase for specified arch automatically, right ?

@BuFran
Copy link
Member

BuFran commented Jan 15, 2014

Probably solved with #37, pushed in master in 1b98ef8

@enikulenkov
Copy link

Just want to remember, that there are still references to $(SCRIPT_DIR)/stlink_flash.scr in Makefile.rules. But this file is missed in libopencm3 repository.

@BuFran
Copy link
Member

BuFran commented Jan 23, 2014

Yeah, someone who created the rule should put the file to the right place.

Blame reveals author: @karlp:

SHA-1: f1f1aa84f30d9496dbaaff1bb252ddb5a0a77660 (from original libopencm3 tree) so maybe karlp have this file on his harddrive :-)

@quitte
Copy link

quitte commented Feb 12, 2016

The flash helping snippets in the examples would be a nice addition to the mk directory

karlp added a commit that referenced this issue Dec 29, 2016
Likely to be insufficient, but perhaps a start.

See #34
@karlp
Copy link
Member Author

karlp commented Aug 29, 2018

This appears to be mostly implemented now.

@karlp karlp closed this as completed Aug 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants