tools/cpy2remed: Addition of new programmer for nucleo boards #17550
Conversation
github-actions
bot
added
Area: boards
makefiles/boards/stm32.inc.mk
Outdated
| @@ -1,5 +1,5 @@ | |||
| PROGRAMMER ?= openocd | |||
| PROGRAMMERS_SUPPORTED += bmp dfu-util openocd stm32flash | |||
| PROGRAMMERS_SUPPORTED += bmp dfu-util openocd stm32flash cpy2remed | |||
There was a problem hiding this comment.
This is not supported by all stm32 boards, so far only nucleo-l552ze-q provides the needed configuration
There was a problem hiding this comment.
Unfortunately yes. I do not have access to other Nucleo boards and I cannot check this. Moreover, I suspect that each board have different removable media name (directory in Linux). Due to this fact I introduce DIR_NAME_AT_REMED variable.
There was a problem hiding this comment.
Yea so let's just add this for nucleo-l552ze-q for now.
boards/nucleo-l552ze-q/doc.txt
Outdated
| make BOARD=nucleo-l552ze-q PROGRAMMER=cpy2remed flash | ||
| ``` | ||
|
|
||
|
|
There was a problem hiding this comment.
Note that all Nucelos support this, provided the firmware of the ST-Link is up to date. Maybe add a line to point out that updating the ST-Link firmware could be required? (ST actually provides a .jar file to perform the update, and surprisingly Java actually lived up to the "write once run everywhere" and it does actually work also on Linux.) Maybe the link to that website can be added here?
There was a problem hiding this comment.
even older boards? I'll give it try!
There was a problem hiding this comment.
I could add appropriate text to the documentation page (doc.txt file) but I have only one Nucleo board. My board have such firmware:
Version: V2J37M26
Build: May 13 2020 17:07:43
Which probably states that this is version 2.37.26. Looking at the STM update page this is third most recent firmware.
Do you think about note. "This PROGRAMMER was tested using 2.37.26 version of the ST-LINK firmware. You could find firmware update at STM webpage."
There was a problem hiding this comment.
I added note to the doc.txt concerning ST-LINK firmware and fix small issue with } in cpy2remed.sh script.
krzysztof-cabaj
force-pushed
the
add-cpy2remed
branch
from
0a0b70e
to
5dc9557
Compare
|
|
|
Do you think about such change - remove cpy2remed programmer from all stm32 and include only in l552ze-q? |
|
Please squash |
krzysztof-cabaj
force-pushed
the
add-cpy2remed
branch
from
46102ed
to
1fe199e
Compare
|
Squashed! There are some problems with doc.txt - description of flashing procedure using cpy2remed for git probably is in this same place which section Accessing shell from PR #17639. |
|
You have a merge conflict now - please do a |
krzysztof-cabaj
force-pushed
the
add-cpy2remed
branch
from
1fe199e
to
d417e95
Compare
krzysztof-cabaj
force-pushed
the
add-cpy2remed
branch
from
d417e95
to
4bb5487
Compare
|
Fixed! |
|
Thanks! |
|
Are there same problems with Murdock? I have just looked at ci.riot - there are no queued jobs ... and my PR still have "Expected — Waiting for status to be reported ". Moreover some PR that are accepted later than my has been already processed. |
benpicco
added
the
CI: ready for build
|
Oops, sorry forgot to add the label |
Contribution description
This PR adds a new programmer to the Nucleo boards with an on-board ST-LINK debugger. On-board ST-LINK provides removable media to which program image file in HEX format could be copied for programing. Introduced cpy2remed (copy two removable media) script automates programming process.
OpenOCD programmer could utilize ST-LINK, but in my opinion, more straightforward method without installing additional software could be beneficial for users not familiar with micro-controllers.
Testing procedure
Currently, programmer was tested on STM Nucleo-L552ZE-Q board; however, all Nucleo boards with ST-LINK should work after a minor enhancement - add DIR_NAME_AT_REMED variable to the Makefile.include file.
Go to RIOT/examples/blinky and run command:
After a while, the green LED (LD1) should start blinking.
Changes in documentation can be observed using commands:
Issues/PRs references
N/A