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.

PROCESSOR-SDK-AM64X: GDB Debug configurations question Automatic Remote Debugging Launcher

Part Number: PROCESSOR-SDK-AM64X

Hi:

So I have one of the example applications building and running on the A53, as well as using manual remote debugging launcher working. 

Presumably this is the correct version of GDB to use ... since it seems to work with manual launch.

ti-processor-sdk-linux-am64xx-evm-08.00.00.21/linux-devkit/sysroots/x86_64-arago-linux/usr/bin/aarch64-none-linux-gnu-gdb

Getting the automatic stuff to work always seems to change, and can be fickle. 

Was wondering if there is an example set of steps to get automatic remote debug launching working on the PSDK for AM64x?

I'm created an ssh connection using user/password authentication.   However I get Error during file upload: Algorithm negotiation fail errors.

Actually a sample .gdbinit file would be kinda cool too.

Thanks

Howard

  • Hi Howard,

    Can you ssh to the target via command line?

    Thanks.

  • One more bit of info, I stumbled onto the Remote Systems perspective (never messed with that perspective before), and I basically get the same error after setting up an ssh connection in the remote systems perspective.


    This is sort of a related question. Is there any reason to install a vanilla Eclipse CDT instance?  I just assumed for basic linux app development targeting the A53 using the installed CCS should be fine.  It looks fine, since it is Eclipse, but just wondered if there was something I was not aware of.

    Seems to work so long as I point the compiler directory and prefixes properly.   Just can't seem to make SSH or automatic remote debugging work.  Not a total disaster, but would be nice if it worked.


  • I was about to just try running the latest generic Eclipse CDT to see if it behaved better, but for some reason remembered I had wanted to try CLion.  Downloaded the trial and it works great for building and debugging Linux apps on the A53. 

    You can hardly tell you are debugging the app remotely.  So problem solved I guess. Just press the debug button and it builds, downloads, auto starts gdbserver etc.

    I guess in theory that also means I can have a CLion session up for debugging A53 app, and a CCS session up connected to the R5F for debugging that app (which I already know works).