Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ST-Link V2-1 and Windows 10
#51
(08-03-2018, 11:21 AM)vargham Wrote: "At the moment I have a Nucleo ST-Link snapped off from the main board and converted to J-Link - seems to program stand alone STM32 projects"
It should progam any device. The onboard (Nucleo, Discovery) ST-Link does not know anything about the target. It is a generic programmer.
But it is illegal: "The firmware is for use with evaluation boards only. It is not for use with custom hardware."
https://www.segger.com/products/debug-pr...-on-board/

Yeah I wondered whether the J-Link ST-Link firmware was restricted to mcu's that had discovery boards (specific model matches). Curious though - can the standalone ST-Link V2 be reprogrammed as a J-link? I'll have to try it I guess.
Reply
#52
"can the standalone ST-Link V2 be reprogrammed as a J-link?"
No.
Reply
#53
Hi,
I have a STM32F746G-DISC0 board and Windows-10
Debugging did not work, because STLinkGDB can not connect with on-board ST-Link V2-1 device.

I downloaded the latest stlink version from  https://github.com/texane/stlink/releases ,
compiled it and now I use this as debugger. It's working :-)

If anyone would like to try - I have uploaded it to    http://www.gadgetpool.de/nuke/downloads/..._1_5_0.zip
and also attached it to this posting.

- Get the zip file.
- Unzip it
- Copy the files st-util.exe and libusb-1.0.dll to your  EmBitz  .../share/contrib  folder.
- in EmBitz->Debug->Interfaces->GdbServer   select   st-util.exe


Attached Files
.zip   st-util_1_5_0.zip (Size: 295.66 KB / Downloads: 138)
Reply
#54
Thank you FrankW!
Reply
#55
Thank you, it's working for me too (Nucleo f103).
However, the copy of libusb-1.0.dll to the contrib folder was not worked, I had to select libusb using Zadig.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)