• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 4190 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.

Update to CCS 5 Emulation package causes "Unable to access the DAP" on 2nd attempt to connect to AM3358 Cortex A8

Chester Gillon
Guru 92251 points
Other Parts Discussed in Thread: AM3358

Using CCS 5.5.0.00077 on Windows XP SP3 32-bit with AM335x Starter Kit connected via built in XDS100v2, to debug the Cortex A8.

The 1st attempt to debug after powering-on the AM335x Starter Kit is successfull, is that can download and debug a program on the Cortex A8. If terminate the debug session, when attempt to restart the debug session fails with the following error message:

CortxA8: Error connecting to the target: (Error -1203 @ 0x3D5B) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.340.0)
Once this error has occured, the only way to clear it is to power-cycle the AM335x Starter Kit.

 

Ruled out the program being debugged from causing the problem since:
a) Power cycle
b) Launch the selected target configuration without a project
c) Connect to the Cortex A8 (without loading a program) which works
d) Disconnect from the Cortex A8
e) Attempt to connect to the Cortex A8. Fails with:

CortxA8: Error connecting to the target: (Error -1203 @ 0x3D5B) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.340.0)
f) have to power-cycle to be able to connect to the Cortex A8 again

 

The last time debugged programs on the AM335x Starter Kit with CCS 5.5, don't recall having this problem, but have since performed CCS 5.5 updates. Therefore, installed CCS 5.5.0.00077 in a clean directory but didn't install any updates. The clean install of CCS 5.5.0.00077, which uses TI Emulators 5.1.232.0 doesn't suffer the problem. i.e. can perform multiple debug sessions without having to power-cycle the AM335x Starter Kit between each debug session.

Whereas using the same workspace/project/target configuration with a CCS 5.5.0.00077 installation with the "latest" updates, which uses TI Emulators 5.1.340.0 have to power-cycle the AM335x Starter Kit after each debug session to avoid getting the "Unable to access the DAP" error.

Therefore, it appears that an update has caused the problem. While CCS maintains a Installation History, I can't get the Eclipse revert function to work. i.e. can't back-out the updates one at a time to see which update introduced the problem.

  • 0
    Guru 92251 points

    Another test which points at the update of the TI Emulators package as being the cause of the problem is that a CCS 6.0.0.00091 installation using TI Emulators 5.1.275.0 was able to perform multiple debug sessions without having to power-cycle the AM335x Starter Kit between each debug session.

    However, when the CCS 6 installation was updated to TI Emulators 5.1.340.0 had to then power-cycle the AM335x Starter Kit after each debug session to avoid getting the following error:

    CortxA8: Error connecting to the target: (Error -1203 @ 0x3D5B) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.340.0)
  • 0 in reply to Chester Gillon
    Prodigy 240 points

    I'm experiencing the same issue with a Blackhawk USB560 v2 System Trace talking to an XAM3359 ES1.0 PG1

    After power cycle debugger initialization works as expected. In CCS, disconnecting (recompiling or not) and reconnecting the debugger results in a "(Error -1203 @ 0x3D5B) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.340.0)" error. 

    Choosing "System Reset" from the resets dropdown prior to disconnecting (in an attempt to reach the good state without a power cycle) does not resolve the issue, even though the SoC does exhibit a reset signature. Selecting "Reset Emulator" does not appear to help either.

    The previous version of CCS did not exhibit this issue.

  • 0 in reply to Chester Gillon
    Guru 92251 points

    Today after updating CCS 5.5 with TI Emulators 5.1.402.0 the behavior changed.

    On the first download of a program after power-cycling the AM335x Starter Kit the GEL script runs and the program is downloaded without error.

    On the second and subsequent downloads the GEL script encounters an error and aborts, but the program appear to get downloaded without error. Capture of the GEL script error:

    CortxA8: Output: **** AM3358_SK Initialization is in progress ..........
    CortxA8: Output: **** AM335x ALL PLL Config for OPP == OPP100 is in progress .........
    CortxA8: GEL: Error while executing OnTargetConnect(): Target failed to read 0x44E10040 at (*((unsigned int *) (0x44E10000+0x40))>>22) [AM3358_StarterKit.gel:379] at GetInputClockFrequency() [AM3358_StarterKit.gel:450] at ARM_OPP100_Config() [AM3358_StarterKit.gel:370] at AM3358_SK_Initialization() [AM3358_StarterKit.gel:356] at OnTargetConnect() .
    Will investigate if debugging now stable...

    Edit: Corrected to say "... downloaded without error"

  • 0 in reply to Chester Gillon
    Guru 92251 points

    Chester Gillon said:
    On the second and subsequent downloads the GEL script encounters an error and aborts, but the program appear to get downloaded without error. Capture of the GEL script error

    On further investigation the GEL script error was due to running a SYS/BIOS example. SYS/BIOS is changing something in the AM335x configuration such that the control register at address 0x44E10040 isn't readable by a GEL script (or the debugger).

    After downloading a SYS/BIOS program, executing a system reset before stopping the debug session then allows the GEL script to run without error on the next debug attempt.

    After installing the TI Emulators 5.1.402.0 update in both CCS5.5 and CCS6 beta 3 have seen no more "Unable to access the DAP" errors.