• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 1232 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS5 omap3530 debugging fail with Target must be connected before calling the function

Marek Belisko
Intellectual 330 points


Hi,

I follow : http://processors.wiki.ti.com/index.php/Linux_Debug_in_CCSv5 (part Creating A Source-code Project for the Kernel).4

I successfully create configuration (following steps). Basically I need debug why kernel doesn't boot up.

Alway when try to debug (press debug button) I got:  Cortex_A8_0: GEL: Target must be connected before calling the function

Target is connected (stopped manually at u-boot countdown).

Also verify connection with Connect target  (I can connect so chain must be OK).

When connected try to load vmlinux automatically but it also fails with:

Cortex_A8_0: File Loader: Data verification failed at address 0x00000000 Please verify target memory and memory map.

Cortex_A8_0: Unable to terminate memory download: NULL buffer pointer at 0x3a9f

Cortex_A8_0: GEL: File: /home/open-nandra/kernels/linux-2.6/vmlinux: a data verification error occurred, file load failed.

Any ideas?

CCS5: Version: N201102161400 
Thanks,
Marek

 

  • 0
    TI__Guru**** 171224 points

    Marek,

    Although many other details may be blocking the ability to debug your target, one thing that strikes me in your question is the use of a GEL file.

    Keep in mind the u-boot routine already performs several device initialization routines and therefore the GEL will get in its way. The page mentions:

    "When creating a target configuration in the configuration editor, it is best to bypass all unused targets. You would also remove the GEL file for the ARM you are going to debug. The GEL file will not work when an OS is present on the target."

    Try to remove the GEL file from your target configuration and try to connect.

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Intellectual 330 points

    Hello,

    thanks for reply. I try remove all GEL files but behavior is same. According wiki you just setup target configuration, then hit debug button and you can debug.

    Anyway maybe just not correctly remove GEL files. Is there any screen shoot how to do it?

    thanks,

    marek