Other Parts Discussed in Thread: SEGGER,
Hello,
I have a SEGGER J-Link EDU that I am attempting to connect to program/debug a TMS570LS0432 with. I am using this microcontroller on my own custom board, and have gotten the debugger to work with a development board for the microcontroller (TMS57004 Launchpad). When attempting to connect to the microcontroller, I receive the following error:
I'm sort of at a loss as to what the hold up could be. Some things of note that I've noticed/tried so far are:
1.) I've tried putting a 2.7k pullup from nRST to VCC on the JTAG header to ensure that the device is in reset when attempting to program, as per this thread, but it doesn't seem to fix the issue.
2.) The connections from the debugger to my board aren't using the 20 pin ribbon cable that came with the J-Link, as my board doesn't follow any standard pinout. I'm only connecting one of the ground pins on the debugger to the board, and although I'm sure it would be ideal if I connected more, I can't imagine this being my issue (I'm not trying to connect at a high speed).
3.) I've referenced the schematic for the TMS57004 and there's nothing different between my debugging circuit and the one on the Launchpad. I don't have any pullups on TMS, TDI, or the clock lines, but these are marked as DNP on the schematic (which seems off to me, but I'll trust it).
4.) The light on the J-Link turns orange after I attempt to connect and stays that way until I close J-Link Commander.
I'm running a little thin on ideas as to what could possibly be wrong with my setup. It's certainly possible that there's an issue with my board, but as far as I understand, the only thing that could cause a problem would be an issue with power supply, and that all seems to be in order, so I'm kind of at the end of what I can check without actually connecting the debug probe. Does anybody happen to know why I can't connect the J-Link EDU to a custom board? Are there any hardware/design considerations I may have missed? Is there any way to check if the microcontroller is even working if it's never been programmed and I can't connect to it with my debug probe?
Thank you for your time,
Thomas Meier