This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM2434: Debug Configuration Boot Error only on some hardware

Part Number: AM2434


Support,

I have this weird issue where my debug configuration works on my AM2434 Launchpad, but will not work on two other launchpad boards. The other two boards were previously running another project and I'm out of the loop on it's history, but I'm told that they never had this problem. This doesn't make any sense to me because the bootloader should be performing a mass erase on the boards so it should be hardware independent. Note that my project is running all four R5 cores and both PRU_0 and PRU_1.

The issue is that when the debug session gets to the PRU_0 core, I get a brief "WAITINGTOCONNECT" status before the session ends unexpectedly. Then, looking at the debug output I get this error in the logs:

"ICSS_G0_PRU_0: GEL: Target must be connected before calling the function."

What could be causing this to happen on the other two launchpad boards and not my launchpad board?

Here is a video of the behavior I’m seeing on the other two launchpad boards as described above.

https://inlbox.box.com/s/lhhs6jwjr3zdv0j0d2ewv2cyr6uvoprp

Thanks!

Marshall