• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 51 subscribers
  • Views 531 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.

CCSv4 4.0.1.0.01001 Debug session startup errors

Eugene K
Expert 1685 points

Target: Aries EVM, Emulator: SD XDS510USB

I have CCXML set up with separate initialization GEL scripts for R4 and M3. Each script contains StartUp() for setting memory map file ans some initial CTI configuration. Debug properties are set to 'Connect to the target on debugger start up' and connect only to R4. Each time I start debug session I receive following errors in console window:

CortexR4_0: GEL: Error while executing StartUp(): target is not connected.
CortexM_0: GEL: Error while executing StartUp(): target is not connected.
CortexR4_0: GEL: Error while executing OnHalt(): target is not connected.

They disappear after few seconds and replaced by the other one:

CortexM_0: GEL: Error while executing OnHalt(): target is not connected.

While debugging the issue I removed the code in R4 StartUp() which accesses CTI and 'CortexR4_0: GEL: Error while executing StartUp(): target is not connected.' went away but OnHalt() errors are still present.

The original GEL with CTI access in StartUp() works fine in CCSv3.

Did the GEL callback sequence change from CCSv3?

Why OnHalt() is called on non connected target?

Where do I place CTI set up code in CCSv4 GEL?

Eugene

  • 0
    TI__Guru**** 463481 points

    Hi Eugene,

    I'm surprised that your CTI access actions in StartUp() did not raise any error messages in 3.3. We discourage any target access calls in StartUp() (as mentioned in page 3 of SPRAA74).

    However, you should not have had any issues with having you CTI access calls in the OnHalt() callback function. The OnHalt() is getting called during the target connect phase of your debug session startup (since the target is halted when connection is established). But that OnHalt() callback should be getting called after the target has been connected. But the errors you are getting indicate that it is being called before the target connection has been completed. I spoke with a CCSv4 engineer and we agreed that it looks like this may be a bug and that you should be able to have any target access call in your OnHalt() function. I will file a bug for this issue. In the meantime what I would suggest is to ignore the errors that first time as the target is being connected and also to explicitly call OnHalt() somewhere in your OnTargetConnect() call. This will guarantee that your CTI access calls will be made after the target is connected that first time.

    Thanks

    ki

  • 0 in reply to Ki
    Expert 1685 points

    Ki,

    Is there a way in GEL or JS to determine if target is connected?

    Eugene

  • 0 in reply to Eugene K
    TI__Guru**** 463481 points

    Not via GEL but with JS (via DSS) you can ( target.isConnected() API )