2018-09-20 10:57 PM
Hello,
I'm following this guide (https://mcuoneclipse.com/2015/08/22/debugging-stm32f103rb-nucleo-board-with-with-segger-j-link/)
The board I am using is NUCLEO-L4R5ZI. I've connected the following pins to the 10-pin ARM connector:
I've also tied the VDD_Target/VTref pin to 3.3V.
When I launch Keil uVision5, I go to Project options and select the debugger. I am getting a "RDDI-DAP Error".
Please do not suggest I use the built in ST-LinkV2 debugger as a solution.
Thank you for your help!
Solved! Go to Solution.
2018-09-21 12:12 PM
@Community member No, I think it is correct. Anyhow, I also swapped them and no luck. Here is a cleaner pinout and connections.
Is there a problem with CMSIS-DAP compatibility? I am curious why this won't work :(
2018-09-20 11:43 PM
> Please do not suggest I use the built in ST-LinkV2 debugger as a solution.
Why not ...?
Have you verified that all SWD connections from the target to the ST-Link are really separated ?
How long are the cables ?
And using the internal ST-Link, have you verified the target works fine ?
2018-09-21 12:30 AM
Don't use that connection for SWDIO and SWCLK, go in via the target side of the jumper pins.
2018-09-21 08:25 AM
Thanks. I have already checked that the Target is working well with the built in ST Link.
@Clive Two.Zero : I will try this out and report back!
2018-09-21 08:40 AM
Specifically CN4, the lower pin on each pair connects to Target SWCLK (NORTH), SWDIO (SOUTH)
2018-09-21 11:00 AM
I just connected the SWDIO and SWCLK to the target side through CN4 with the rest of the stuff still in the CN5 connector.
I also have another board NUCLEO-F030R8 with the Stlink portion of the board snapped off. Perhaps I should try connecting directly without the STlink MCU messing up the signals?
Still no luck :( here is the pic:
2018-09-21 11:21 AM
You seem to have 2 and 4 switched in your picture vs your chart 2=SWCLK, 4=SWDIO, would me easier if you'd draw them in numeric/pin order
2018-09-21 12:12 PM
@Community member No, I think it is correct. Anyhow, I also swapped them and no luck. Here is a cleaner pinout and connections.
Is there a problem with CMSIS-DAP compatibility? I am curious why this won't work :(
2018-09-21 12:27 PM
Looks like I might have found the problem. The 10-pin fanout cable's pin 1 (Red wire) is not on the same side as the 10-pin socket on the ARM UlinkPlus debugger.
Here is a picture of how the cable connects to the socket.
2018-09-21 01:11 PM
Yep, that was indeed the problem. I am now able to connect.
Anyone who is reading this thread in the future, please use the diagram above to connect to your STM32 Nucleo board and Ulink/Ulink2 or UlinkPlus debuggers from ARM Keil.
Everything is working great. Thanks for the help from @Community member and @Community member .
FYI - The reason why I'd like to use the ARM UlinkPlus debugger is first of all, I paid $700 for this so I might as well use it for faster flashing and debugging. It had trace functionality as well as power metrics, discrete IO for production testing. It is a great little ******!
Closing this thread, thanks.