This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DS5 debug on nvidia TX1 board

Hello

I have some problem to connect DS5 (v5.26.2) debugger to nvidia TX1 board. First, I used the "platform configuration" wizard in eclipse for creating TX1 which seems ok except few warnings about devices that does not have any connections (CSTFunnel / CSETM). Then, I created debug configuration (baremetal debug with connect only option). When I try to debug, I have a
"connection Failed" popup with the following message: "Unable to connect to... Reason: Unable to connect to USB:XXXXXX Unable to connect to device APB_0 No connection to target.".

Does somebody successfully connect DS5 debugger to RX1? Any tips would be greatly appreciate!

Thanks in advance!

Vincent

Top replies

Stuart Hirons over 7 years ago in reply to vdupre +1 verified

Hi Vincent, My guess is that the other cores are powered down, but that the board has some proprietary reset/power controller that DS-5 is not aware of. Consequently, the tool is trying to to connect to...

+1 vdupre over 7 years ago

Finally I found a solution to my problem. Instead of using eclipse platform configuration wizard, I used dbghwconfig and cdbimporter script (located in DS-5 bin folder). With dbghwconfig, a platform file (*.rvc) is generated by connecting the DS5 debugger to TX1 board ("connect" button then "auto-configure" button). With the saved rvc file, the script cdbimporter generates TX1 database. In eclipse (window - preferences - DS-5 - Configuration Database), TX1 database need to be added and rebuilt ("Rebuild database" button). Finally, the TX1 platform should be found in the connection tab when creating a new DS-5 debugger configuration.
Cancel
Up 0 Down

Cancel
0 Stuart Hirons over 7 years ago in reply to vdupre

Hi,
It is interesting that dbghwconfig got you a configuration whereas PCE didn't. But please bear in mind that dbghwconfig is no longer shipped with DS-5.
It would be interesting to see/know why PCE was unable to create a config that seemingly didn't work, it should have done, but I don't have access to a board to test this myself I am afraid. If you have any logs then they would be much appreciated.

Thanks,
Stuart
Cancel
Up 0 Down

Cancel
0 vdupre over 7 years ago in reply to Stuart Hirons

Thanks for the comment! Currently, debugging is ok on the booting core but for the secondary cores, DS5 can't connect to TX1 board and throw "Unable to connect to device ... unknown error" (when debugging with H/W configured with dbghw tool)...
I will check for the logs and post it this week when using platform configuration tool in eclipse.

Vincent
Cancel
Up 0 Down

Cancel
+1 Stuart Hirons over 7 years ago in reply to vdupre

Hi Vincent,

My guess is that the other cores are powered down, but that the board has some proprietary reset/power controller that DS-5 is not aware of.

Consequently, the tool is trying to to connect to the cores that are powered down, expecting at least some of the debug logic to be powered up but finding that in fact the whole core is powered down, including the debug power domain on that core.

Assuming you have access to a TRM/Programmers Reference Guide for the SoC, have a look at the sections relating to reset and/or power and see if there are any specific registers that need to be written in order to power up the core.

This assumes that you are developing bare-metal. If you have Linux running then of course Linux is performing the power management and can be quite aggressive in order to keep power consumption down (this can include such policies as disabling clocks and/or power to cores that are not running/used, disabling debug clock and so forth).

The Linux kernel code might have the answer, if you don't have a TRM for the SoC.

I hope that helps ?

Regards,
Stuart
Cancel
Up +1 Down

Cancel
0 vdupre over 7 years ago in reply to Stuart Hirons

Hello Stuart,

You were right, the secondary cores weren't power on. I thought that u-boot did the power-up but it wasn't the case! Also, secondary cores booting on TX1 is done via PSCI interface, way easier than the power-up routine described in TX1 board TRM!

Thanks again for the help

Vincent
Cancel
Up 0 Down

Cancel