Code composer 5.1.1.- Helloworld problem

Edvard,

These should not be hard errors.  There is a known issue with the new toolchain packaging such that the x86 libraries get put into the search path, which leads to this message as they are checked and discarded because they are not ARM libraries.  But functionality should not be impacted.  Are you seeing a functionality failure?

Chase

Chase,

thank you for response.

I have 7 files in Debug directory (helloworld, helloworld.d, helloworld.o, makefile,  objects.mk, sources.mk, subdir.mk).

helloworld file should be excecutable - am I right?

Is it possible to remove x86 libraries from the search path (to get rid error reporting)?

Where can I see known issuses of the latest Sitara tool chain - I could not find any issue related to x86 libraries put into the search path?

Regards, Edo

Edo,

Yes, the helloworld should be the executable.

removing the x86 libraries is something we are looking at but don't have a solution for right now.

Thank you Chase,

helloworld works fine, remote terminal also works fine (It is possible to run excecutable file helloworld on remote system).

Now I have a problem with debugger - It reports an error:

'Launching helloworld Debug' has encountered a problem. Error during file upload.

Details: Error file upload. Operation failed. File system input or output error

Any ideas - what should I check?

Edo

Edo,

This usually is a permission issue on the target board.  I would delete the existing helloworld from your file system because when the debugger launches it first wants to copy the new executable over, then debug.  If the existing file has incompatible permissions you get this error.

Chase

Chase,

I have deleted the file "helloworld" from AM335x Starter Kits's (destination) file system but after debugger relaunch I got the message in Console:

When Remote Shell icon is selected:

root@am335x-evm:~# echo $PWD'>'
/home/root>
root@am335x-evm:~# gdbserver :2345 /home/root/helloworld;exit
Process /home/root/helloworld created; pid = 1845
Listening on port 2345

Wnen <terminated, exit value: 127>gdb icon is selected:

"<terminated> helloworld Debug [C/C++ Remote Application] gdb

I have checked - helloworld is successfully transferred to the destination file system but debugger doesn't work.

What else should I check?

Regards

Edo

I'm having exactly the same issue - did you resolve this issue?

I am still waiting for help.

Some more data: OS: 64-bit Ubuntu 12.04 LTS, 32-bit transitional libs are installed (to support 32-bit applications), latest SDK  for AM335x Starter Kit (AM335xSDK 05_06_00_00).

Regards,

Edo

I am using 32-bit Ubuntu LTS, latest SDK (AM335xsdk 05_06_00_00) as well. I'm sure it's something silly, but it's kicking my butt right now :(

Please, can somebody confirm if gdb debugger works correctly in Code Composer 5.1.1. with the latest SDK for AM335x Starter kit (AM335xsdk 05_06_00_00).

I am working on development system for AM335x Starter kit for more than 14 days but I am still not able to debug simple helloworld application!!!

If gdb debugger works, please, give me information - how to debug helloworld application. I strictly followed documentation http://processors.wiki.ti.com/index.php/Sitara_Linux_Training:_Hands_on_with_the_SDK -> Debugging with CCS and GDB but after step 8 (click Debug to compile the project and start the debug. You system should be halted at the first line of the mainfunction) the system is not haltet at the first line of the main function - debugger reports <terminated, exit value: 127>gdb <terminated> helloworld Debug [C/C++ Remote Application] gdb.

Copying of the file helloworld to the destination file system works - the problem is debugger.

I also have one question related to GDB configuration file ( .gdbinit). What is a valid content of this file (case1: destination file system is located on SD flash card, case2: destination file system is located on my computer).

!!!Guys from TI - please, check the latest two comments from the following llink:

http://processors.wiki.ti.com/index.php/Sitara_Linux_Training:_Hands_on_with_the_SDK

DjordjeZ said ...

Jeffberryhill said ...

I am having the same issue and need to have the debugger working.

Please help!

Hi,

to make GDB work, change this file:

arm-arago-linux-gnueabi-gdb

from: #!/bin/sh to #!/bin/bash

More about this solution: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/247783/874203.aspx#874203

Regards, Edo

Thanks a lot!  Tested it works now.

Hi,
i am new to gdb debugging and i face the same problem. what do you mean with change arm-arago-linux-gnueabi-gdb from: #!/bin/sh to #!/bin/bash? arm-arago-linux-gnueabi-gdb is a binary file, how can i update it?

thank you,
regards
Andrea

Hi,

you should change content of the file "arm-arago-linux-gnueabi-gdb" (this file is a script, not a binary).

Simply replace text with another text and save file with the same name. Do not change other lines.

I found out Embedded Linux is NOT suitable for my project (os for the main CPU of Fire control panel). This operating system is to complex, documentation is poor, support sucks - to much problems, ...

Now I am switching to Keil MDK, which provides RTOS, drivers, TCP/IP stack, file system, good support and good documentation for ARM microcontrolles.

Yes, it is expensive - It costs 7kEur but I lost  even more money by "playing" with "free" Embedded Linux.

Please, note - nothing is free - free stuff can be clumsy an very, very expensive at the end of day!

Regards,

Edo

Hi Edo,
thank you for the reply. Maybe i would have to say before that i'm debugging with a DaVinci DM8127 and the file arm-arago-linux-gnueabi-gdb provided with RDK is a binary file. I have thought your debugging problem was the same i'm facing but evidently it isn't.

Thank you anyway, maybe i'll open a new thread to solve my gdb remote debugging problem
regards

Andrea