• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 55 subscribers
  • Views 1239 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.

CCS/AM5716: Can the launch be simplified?

ChristianF
Intellectual 340 points
Part Number: AM5716


Tool/software: Code Composer Studio

Hi,

With the help of the forum I was able to port the TI SBL project into the CCS environment.

If I want to debug, I have to proceed as follows:

1. compile/link

2. launch

After a few lines the system stops: Texas Instruments XDS100v2 USB Debug Probe/CortexA15_0 : Target must be connected before loading program.

3. I have to connect the target: the launch will continue...

4. Wenn the core is initialized: CortexA15_0: GEL Output: --->>> AM571x Target Connect Sequence DONE !!!!!  <<<---

I have the following output: No source available for "0x3808c"

5. Then I have to load the sbl.out (Run->Load->Load Program)

6. Finally I can press the resume button and debug.

How can I simplify the launch process? Other projects (such as the TI UART Basic Example) can be started in two steps (compile/link + launch).

I'm using SDK RTOS v04.01.00.06, PDK v1.0.8, on Windows, CCS 7.2.0.00013

Best Regards,

Christian

  • 0
    TI__Guru**** 473401 points
    Hello,
    When using the "Debug" button to start a debug session for a project, much of those steps should be automated. It should auto-connect to the target so I don't know why you are prompted to manually connect. It looks like something goes wrong during step 2, which messes up the automation. Can I see a screenshot at this stage? I'd like to see any GEL output in the debug console. Also provide the A15 GEL file you are using.

    Thanks
    ki
  • 0 in reply to Ki
    Intellectual 340 points

    Hi ki,

    Console and Debug tabs after stop, see

    The GEL file is the original one, see

    AM571x_cortexa15_cpu0_startup.gel

    Best Regards,

    Christian

  • 0 in reply to ChristianF
    Intellectual 340 points
    Hi,

    It seems like the screenshots have not been taken ...

    All console output after stop (step 2):

    Cortex_M4_IPU1_C0: GEL Output: --->>> AM571x Cortex M4 Startup Sequence In Progress... <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> AM571x Cortex M4 Startup Sequence DONE! <<<---
    Cortex_M4_IPU1_C1: GEL Output: --->>> AM571x Cortex M4 Startup Sequence In Progress... <<<---
    Cortex_M4_IPU1_C1: GEL Output: --->>> AM571x Cortex M4 Startup Sequence DONE! <<<---
    C66xx_DSP: GEL Output: --->>> AM571x C66x DSP Startup Sequence In Progress... <<<---
    C66xx_DSP: GEL Output: --->>> AM571x C66x DSP Startup Sequence DONE! <<<---
    CortexA15_0: GEL Output: --->>> AM571x Cortex A15 Startup Sequence In Progress... <<<---
    CortexA15_0: GEL Output: --->>> AM571x Cortex A15 Startup Sequence DONE! <<<---
    Texas Instruments XDS100v2 USB Debug Probe/CortexA15_0 : Target must be connected before loading program.

    Best Regards,
    Christian
  • 0 in reply to ChristianF
    Guru 92251 points

    ChristianF said:
    Texas Instruments XDS100v2 USB Debug Probe/CortexA15_0 : Target must be connected before loading program.

    If you right-click on the project properties in the CCS Project Explorer, and under Debug -> Auto Run and Launch Options with "CortexA15_0" selected as the device check if the "Connect to the target on debugger startup" option is ticked:

    If the "Connect to the target on debugger startup" option is not ticked, that could be the cause of the problem with the GEL script stopping with an error and requiring a manual load of the program.

  • 0 in reply to ChristianF
    TI__Guru**** 473401 points
    Christian - nothing stands out in the GEL file that would interrupt the default behavior of the automatic launch. Please check the setting that Chester describes to see if somehow that auto-connect option was disabled

    Thanks
    ki
  • 0 in reply to Chester Gillon
    Intellectual 340 points

    Hi Chester,

    In fact, the option "Connect to the target on debugger startup" was not activated. However, this configuration did not change the boot process.

    But I discovered the following (in Debug Configurations/Main):

    If the Target Configuration points to: C:\Develop\TC_CTR_V5\Workspace_CCS_V7\idkAM571x_SBL\targetConfigs\IDK_AM571X.ccxml (which is [Active])

    ... is not the same like: ${target_config_active_default:idkAM571x_SBL}

    In the second case, the process works as desired.

    Have I misunderstood something or is this a bug?

    Regards,

    Christian