• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 813 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.

RTOS/AM6548: CCS8.2 cannot debug the AM6 Temp project?

Rio Chan
Genius 14655 points
Part Number: AM6548

Tool/software: TI-RTOS

Hi.

#1. Please see the attached picture.

#2. My CCS8.2 can use the  GEL for initializing the DMSC / R5F / A53.

#3. I have built the temp project and the .bin file is output.

#4. After DMSC -> R5F -> A53 are initialized by sequence, I load the .out file.

     My problem is:

     Why the CCS8.2 shows me this: CortexA53_0_0: AutoRun: Target not run as the symbol "main" is not defined?

     I have built my project as "debug" version.

BR Rio

  • 0
    TI__Guru** 116170 points

    RioChan,

     This is a known issue that is currently being tracked using bug ID PRSDK-4654 and is being discussed with the CCS IDE and compiler team. There are several other PDK driver examples for A53 that are using same compiler options but the Template project that uses projspecs is the only one where this is been reported. This is not a functional issue as the demo is functioning and you do see the drivers running based on the UART output. However from debug perspective this does pose a challenge.

    We will get back to you when we root cause the issue and let you know if there is quick fix. The issue has been reproduced with CCSv8.1 as well as CCSv8.0. At the moment the only thing that we have been doing is to read the map file to find the main symbol and set a hardware break point. Also it is unclear why the CCS loader halts at that address given Auto Run doesn`t find main but this is on out radar to resolve prior to next update.

    Regards,

    Rahul

    PS: Since the thread is locked, I am posting a response for anyone who finds this thread. Work around is documented here:

    https://e2e.ti.com/support/tools/ccs/f/81/p/790751/2949094#2949094