-
Notifications
You must be signed in to change notification settings - Fork 29
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
Programming via ST-LinkV2 #13
Comments
What type of STLink board do you have? Can you attach a picture? When / Where did you get the board from? After you make that change does the programming actually work? (IE The board goes into the bootloader fine?) |
Yes, this ultimately works. I've got the tomu running the blinky example now. I got it off of you at LCA2017. I'm using some old knock-off ST-LINK-V2 $8 programmer from e-Bay or somewhere. It is running the most recent firmware. It looks something like this. |
@rdpowers Would you mind writing up some documentation on using that board with the tomu? |
Sure mate, I'll see what I can do. |
@mithro I just did more or less the same thing with the ST-Link that comes with STM Discovery Boards. If you're interested, I can document the necessary steps! |
That would be awesome!
…On 8 Feb. 2018 12:22 pm, "jadeaffenjaeger" ***@***.***> wrote:
@mithro <https://github.com/mithro> I just did more or less the same
thing with the ST-Link that comes with STM Discovery Boards. If you're
interested, I can document the necessary steps!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#13 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABS3HhwNVuUwukpinJQI1dCXksui5bSks5tS1eMgaJpZM4M2Zmg>
.
|
Oh, wow. Sorry @mithro , this completely fell off my radar!! If something isn't together in the next week, I'll promise to pick it back up then. |
Hi! Here's what I did to use a $8 ST-Link V2 to program Tomu via SWD |
I was able to flash the bootloader with an STLinkV2, but encountered some issues. I'm exceptionally new to OpenOCD, so it may just be inexperience on my part.
Using OpenOCD and an ST-LinkV2 gives a chip ID error:
It seems that the efm32hg309 is not defined and falls through to default (0x2ba01477)
From (tcl/target/efm32.cfg):
Using a very recent build of OpenOCD
Workaround - Q&D Modify openocd/tomu.conf to define CPUTAPID
Then this works:
openocd -f interface/stlink-v2.cfg -f ./tomu.conf
Some questions, maybe more OpenOCD related than tomu-bootloader related:
Am I building OpenOCD wrong or is the efm32hg309 just not properly supported?
Perhaps you were doing development with one of the Cortex M3 or M4 which has the chip ID of 0x2ba01477?
Or does
transport select swd
on the RPi config get the ID right while hla_swd transport supported by STLink somehow get it wrong?The text was updated successfully, but these errors were encountered: