I am attempting to flash a custom PCB using Atollic TrueStudio and a Nucleo board. I have the PCB connected to the SWD header on the Nucleo. In TrueStudio I have set the target device and am using ST-LINK as the debug probe with the GDB Connection Settings set to "Autostart local GDB server", and the Interface set to JTAG. When I click debug, it builds the project, but then gives me an error:

Target unknown MCU target

Error in initializing ST-Link device.
Reason: Unknown MCU found on target.

What does this error mean?

I have also tried debugging using the SWD interface, but when I use that I get the error:

Target no device found

Error in initializing ST-Link device.
Reason: No device found on target.

I have searched for explanations of these errors, but have not been able to find anything helpful. I have also looked through tutorials on using TrueStudio, but I have not been able to figure out why this fails to flash my board or what is going wrong.

Also, I am new to TrueStudio, so please explain. Thanks!

  • \$\begingroup\$ What does Atollic support say? \$\endgroup\$ – Leon Heller Dec 6 '17 at 19:48
  • \$\begingroup\$ I am using the free version of TrueStudio and have not paid for Atollic's support. \$\endgroup\$ – L. MacKenzie Dec 6 '17 at 19:57
  • 1
    \$\begingroup\$ You need to figure out what chip id it is detecting. If something implausible like all 0's, you have a wiring issue with SWD or a design issue in the board or an assembly issue. If something valid (try a web search on the value), perhaps you have a chip variant unknown to (potentially outdated versions of) the tools you are trying to use. Do make sure you removed the jumpers that connect the on-board target to the Nucleo's SWD adapter, and make sure your target is connected to the correct header on the Nucleo, not where the jumpers were. \$\endgroup\$ – Chris Stratton Dec 6 '17 at 20:05
  • \$\begingroup\$ @ChrisStratton thanks for the comment. I have the ST-LINK jumpers removed and the target board is connected to the SWD header and I checked the wiring. Can you explain how I can find the chip id that it is detecting? \$\endgroup\$ – L. MacKenzie Dec 6 '17 at 20:14
  • \$\begingroup\$ No idea for atollic, maybe some kind of verbose mode? Or you could try ST's flashing tool for windows and see if it detects anything. If you used openocd it would be printed to the console. \$\endgroup\$ – Chris Stratton Dec 6 '17 at 20:17

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.