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.

Compiler/AM3352: Loading debug configurations and get error messages

Part Number: AM3352
Other Parts Discussed in Thread: AM3358

Tool/software: TI C/C++ Compiler

When I load a debug configuration, the Console shows these messages.

The complete message:

CortxA8: Trouble Writing Memory Block at 0x4900478c on Page 0 of Length 0x4: (Error -2130 @ 0x4900478C) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.0.27.9)


CortxA8: GEL: Error while executing OnTargetConnect(): Target failed to write 0x4900478C
at *((unsigned int *) (dma+(j*4)))=(unsigned int) 0 [AM335x_600.gel:294]
at disable_dma_access() [AM335x_600.gel:454]
at ARM_OPP120_Config() [AM335x_600.gel:384]
at AM3358_SK_Initialization() [AM335x_600.gel:368]
at OnTargetConnect()


CortxA8: Trouble Reading Register REG_ENDIAN: (Error -1044 @ 0xFFFFFF0E) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.0.27.9) 

CortxA8: Trouble Reading Register CP15_Registers.CP15_CONTROL_REGISTER: (Error -2131 @ 0x20013F00) Unable to access device register. 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 8.0.27.9)


CortxA8: Error: (Error -1170 @ 0x0) 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 8.0.27.9)


CortxA8: Unable to determine target status after 20 attempts


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

This message happens once in a while.

The reason that I click "Ask a related question" rather than "Ask a new question" is a suspicion in my mind that this with linker command file.

UPDATE:

It's loaded successfully after:

1. restart CCS

2. clean project

3. build project

4. load debug configuration

  • Hi Andy,

    Glad to hear you resolved the issue and thank you for the update!

    For some clarification:

    Andy Lin94 said:
    a suspicion in my mind that this with linker command file.

    This issue is unlikely a linker command file issue. The errors appear to be occurring when executing the actions in the OnTargetConnect() GEL callback function. These actions would be occurring before the program load (and hence unrelated to any potential linker command file issues). Those types of errors usually occur when the device is not in a good state. Often times, a target power cycle will help - along with restarting the debug session.

    Thanks

    ki