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.

xds100v2 recovery

environment: ccs, xds100v2, beaglebone, windows pc

if, during a debug session, the pc returns from sleep, the xds100v2 does not appear to recover very gracefully
in that the debug session is toast. this is sort of unfortunate in that taking a debug break means restarting the
entire session....

  • Hi Jon,

    yes, we have seen that CCS does not like when the debug connection is broken ... by sleep mode, disconnect etc.  During debugging there is constant communication with the chip and associated timesout and issues if this gets cut.  Are you encountering a specific issue? 

    Best Regards,
    Lisa

  • Hi Lisa,

    Well it's just that if I get called away or take a phone call and the pc goes to sleep it kills the debug session.
    Yes I could set the PC up not to go to sleep; but that isn't very environmentally friendly.
    I was hoping there was a "fix" available; or, at least, one in the offing.

    Ciao,
    Jon

  • Hi Jon,

    I am trying to dig further into this for you.  As sleep mode ususally involves shutting the PCI and /or USB bus in many pcs, I am not sure how much can be done to save you from a disconnect.  What might be interesting to see is how CCS handles such a disconnect.  Would you be able to describe the behaviour you are seeing in a bit more detail?  What exactly do you experience recovering from sleep mode?  Do you get a hang?  Do you need to restart the debug session? CCS?  Your workspace?  Are you able to reconnect right after? 

    Best Regards,
    Lisa

  • Lisa,

    Interesting questions. Here is the  entire "Console" after logging back in after waking up.
    The last note is pretty much what it takes to get going again.

    CortxA8: Output: **** AM335x 15x15 EVM Initialization is in progress ..........

    CortxA8: Output: **** AM335x ALL PLL Config for OPP == OPP100 is in progress .........

    CortxA8: Output: Input Clock Read from SYSBOOT[15:14]: 24MHz

    CortxA8: Output: **** Going to Bypass...

    CortxA8: Output: **** Bypassed, changing values...

    CortxA8: Output: **** Locking ARM PLL

    CortxA8: Output: **** Core Bypassed

    CortxA8: Output: **** Now locking Core...

    CortxA8: Output: **** Core locked

    CortxA8: Output: **** DDR DPLL Bypassed

    CortxA8: Output: **** DDR DPLL Locked

    CortxA8: Output: **** PER DPLL Bypassed

    CortxA8: Output: **** PER DPLL Locked

    CortxA8: Output: **** DISP PLL Config is in progress ..........

    CortxA8: Output: **** DISP PLL Config is DONE ..........

    CortxA8: Output: **** AM335x ALL ADPLL Config for OPP == OPP100 is Done .........

    CortxA8: Output: **** AM335x DDR2 EMIF and PHY configuration is in progress.........

    CortxA8: Output: EMIF PRCM is in progress .......

    CortxA8: Output: EMIF PRCM Done

    CortxA8: Output: DDR PHY Configuration in progress

    CortxA8: Output: Waiting for VTP Ready .......

    CortxA8: Output: VTP is Ready!

    CortxA8: Output: DDR PHY CMD0 Register configuration is in progress .......

    CortxA8: Output: DDR PHY CMD1 Register configuration is in progress .......

    CortxA8: Output: DDR PHY CMD2 Register configuration is in progress .......

    CortxA8: Output: DDR PHY DATA0 Register configuration is in progress .......

    CortxA8: Output: DDR PHY DATA1 Register configuration is in progress .......

    CortxA8: Output: EMIF Timing register configuration is in progress .......

    CortxA8: Output: EMIF Timing register configuration is done .......

    CortxA8: Output: PHY is READY!!

    CortxA8: Output: DDR PHY Configuration done

    CortxA8: Output: **** AM335x DDR2 EMIF and PHY configuration is done ****

    CortxA8: Output: **** AM335x 15x15 EVM Initialization is Done ******************

    IcePick_D_0: Error: (Error -150 @ 0x0) One of the FTDI driver functions used during configuration returned a invalid status or an error. (Emulation package 5.0.747.0)

    CS_DAP_DebugSS: Error: (Error -154 @ 0xFFFFFF66) One of the FTDI driver functions used to write data returned bad status or an error. (Emulation package 0.0.0.0)

    CortxA8: JTAG Communication Error

    CortxA8: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging

     

  • Hi Jon,

    what I am going to do is file an enhancment request for CCS to handle sleep mode more gracefully. 

    Best Regards,

    Lisa

  • Lisa,

    Thanks; that will help us all out.

    Jon

  • Hi Jon,

    no problem.

    Best Regards,
    Lisa