JTAG on the NUCLEO-G474RE, No device found on target.

seppeltronics_v · ‎2021-06-09

Hello,

I have an issue with the Nucleo-G474RE, I can't get the JTAG to work, I tried JTAG in 4-pin and 5-Pin-Mode, the IDE reports "No device found on target". With SWD it works in ST-Link-GDB-Server-Mode, but not JTAG. I checked JTAG is connected to the onboard StLinkV3 in 5 Pin JTAG-Mode, seems to be fine.

Does someone know the problem, or may can give me some hints on how to solve that issue?

Thank's a lot in advance.

Best Regards, Seppel

Solder-Bridges still in factory Setting:

SB40 - Set(closed)

SB41 - Set(closed)

SB15 -Set(closed)

SB9 - Set (closed)

SB1 - Set(closed) 100nF from NRST to GND

JP3 -Set(closed)

Console:

STMicroelectronics ST-LINK GDB server. Version 5.8.0

Starting server with the following options:

Persistent Mode : Disabled

Logging Level : 1

Listen Port Number : 61234

Status Refresh Delay : 15s

Verbose Mode : Disabled

InitWhile : Enabled

Target no device found

Error in initializing ST-LINK device.

Reason: No device found on target.

Message:

Error in final launch sequence:

Failed to start GDB server

Error in initializing ST-LINK device.

Reason: (4) No device found on target.

seppeltronics_v · ‎2021-06-09

In the Meantime I tried my older STM32F103 Board with a ST-Link-V2, the ST-LINK GDB server works in 5-Pin-JTAG Mode, that works fine.

Does anyone use the JTAG on a Nucleo with 5-Pin JTAG?

Thanks a lot.

Best Regards, Seppel

Console, all good:

STMicroelectronics ST-LINK GDB server. Version 5.8.0

Starting server with the following options:

Persistent Mode : Disabled

Logging Level : 1

Listen Port Number : 61234

Status Refresh Delay : 15s

Verbose Mode : Disabled

InitWhile : Enabled

Waiting for debugger connection...

Debugger connected

-------------------------------------------------------------------

STM32CubeProgrammer v2.7.0-RC1

-------------------------------------------------------------------

ST-LINK SN : (confidential)

ST-LINK FW : V2J37S7

Board : --

Voltage : 3.28V

JTAG freq : 1125 KHz

Connect mode: Under Reset

Reset mode : Hardware reset

Device ID : 0x410

Revision ID : Rev X

Device name : STM32F101/F102/F103 Medium-density

Flash size : 128 KBytes

Device type : MCU

Device CPU : Cortex-M3

Memory Programming ...

Opening and parsing file: ST-LINK_GDB_server_a21596.srec

File : ST-LINK_GDB_server_a21596.srec

Size : 25060 Bytes

Address : 0x08000000

Erasing memory corresponding to segment 0:

Erasing internal memory sectors [0 24]

Download in Progress:

File download complete

Time elapsed during download operation: 00:00:01.855

Verifying ...

Download verified successfully

waclawek.jan · ‎2021-06-09

Hi Seppel,

The 4-wire JTAG may not be viable, see Full JTAG configuration without NJTRST pin cannot be used erratum.

However, your problem is different. I don't think many users here use JTAG these days, so don't be surprised if there's no relevant response. Maybe try a known-good JTAG interface which provides better feedback/diagnostics than STLink. Heck, maybe even try the STLINKv2, why not.

JW

seppeltronics_v · ‎2021-06-09

Hello Jan,

thanks for the reply, I may have to do a breakout-Board, I'll keep the "on-Board" ST-Link as it is. I do not gain anything if I use JTAG, but I'm new to the STM32G474, so I thought, ok, I'll give it a try. For the STM32F103 I used 5-Pin-JTAG, I checked the Pinout for the Nucleo-G474RE and set all the Pin's,... surprise, didn't work.

If I have news I'll post it.

Best regards, Seppel

seppeltronics_v · ‎2021-06-29

Hello Jan,

it's trivial, only SWD is supported, UM2505 User manual - Rev 4 - February 2021; STM32G4 Nucleo-64 boards (MB1367); Chapter "6.3 Embedded STLINK-V3E"; Page 11/44:

Best Regards, Seppel