LS1043A CW_ARMv8 v11.2.0 & v11.1.1 - Remote 'g' packet reply is too long

[Davisg]

I am trying to connect to the LS1043ARDB board using CW_ARMv8 v11.2.0 or v11.1.1 and the CodeWarrior TAP in Ubuntu 14.04. I get the following error:

Error in final launch sequence

Failed to execute MI command:

-interpreter-exec console "source /home/davisg/CW_ARMv8/.metadata/.plugins/com.freescale.debug.tcc/target_init5898642085241188885.gdb"

Error message from debugger back end:

/home/davisg/CW_ARMv8/.metadata/.plugins/com.freescale.debug.tcc/target_init5898642085241188885.gdb:478: Error in sourced command file:\nRemote 'g' packet reply is too long: 310500000000000000000000000000002cdbe77fc0ffffff64ef5900c0ffffff2000000000000000100000000000000000fad8563f00000080e0e77fc0ffffff80ad9400c0ffffff30bd9300c0ffffffccf4ffff0000000004000000000000000000000000000000000000000000000008000000000000000000002827f01a00003a1a00c0ffffffb0d1297d7f00000030fbd3e57f00000000809300c0ffffff8c459400c0ffffff08459400c0ffffff6be39a00c0ffffff010000000000000050398300c0ffffffd0386c00c0ffffff0030a6800000000030120800c0ffffff00000080400000000000000000000000000000000000000000000000000000000000000000000000cd03000070fcd3e57f00000020bf9300c0ffffff00805e774000000064710800c0ffffff848c6b00c0ffffff0cc00800c0ffffff45010060c5000020cd010000000000560000005a0000000213630003001000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000006513010

Not sure how to resolve this. This all works in the Windows version of CW_ARMv8 v11.1.1 but I am trying to switch to Linux version to make u-boot debug easier.

[Davisg]

Fixed. Had to change from "gdb" command (default) to "/opt/Freescale/CW4NET_v2015.08/CW_ARMv8/ARMv8/gdb/bin/aarch64-fsl-gdb.bin" in the debug configuration

[marius_grigoras]

This is strange, the default GDB Command wasn't something like bellow?

[Davisg]

No, the default was "gdb". How do I change the default so i do not have to modify each debug configuration?

[marius_grigoras · Accepted solution]

I think I find out the root cause. Are you using the fsl_eclipse.sh script to open CW on the linux side? I can reproduce this error, only if I'm using the eclipse executable from CW_NetApps_v2016.01_160115/CW_ARMv8/eclipse$ ./eclipse (but this is not correct).

The correct way to open CW is to use the fsl_eclipse.sh -> CW_NetApps_v2016.01_160115/CW_ARMv8$ ./fsl_eclipse.sh

I cannot advise you to update manually the project (can be also and other differences), but if you want to make a try you'll need the update the .launch file from your project:

replace next line

<stringAttribute key="org.eclipse.cdt.dsf.gdb.DEBUG_NAME" value="gdb"/>

with

<stringAttribute key="org.eclipse.cdt.dsf.gdb.DEBUG_NAME" value="&quot;${eclipse_home}../ARMv8/gdb/bin/aarch64-fsl-gdb&quot;"/>

Thank you,

Marius

[marius_grigoras]

Hi,

Please take a look in the TCC readme file (double click on the TCC to open the readme file) and check the DIP SW settings to be the same.

Also, try to run the JTAG Connection Diagnostics (presented only in 11.2.0) - the third button in the TCC View.

Thank you,

Marius