• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 1687 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

On Gauss c6657 EVM with CCS 5.2 I get this error when I connect USB and go to debugger environment.

Harikrishna Vuppaladhadiam
Expert 1855 points

On Gauss c6657 EVM with CCS 5.2 I get this error when I connect USB and go to debugger environment.

Trouble Writing Memory Block at 0x1845028 on Page 0 of Length 0x4:
(Error -1202 @ 0x1845028)
Device core is hung. The debugger will attempt to force the device to a ready state to recover debug control. Your application's state will be corrupt. You should have limited access to memory and registers, but you may need to reset the device to debug further.
(Emulation package 5.0.791.0)

C66xx_0: GEL Output: Setup_Memory_Map...
C66xx_0: GEL Output: Setup_Memory_Map... Done.
C66xx_1: GEL Output: Setup_Memory_Map...
C66xx_1: GEL Output: Setup_Memory_Map... Done.
C66xx_0: GEL Output:
Connecting Target...
C66xx_0: GEL Output: DSP core #0
C66xx_0: GEL Output: No initialization performed since bootmode = 0x00000005
C66xx_0: GEL Output: force initialize with GlobalDefaultSetup
C66xx_0: GEL Output: C6657L GEL file Ver is 1.0
C66xx_0: GEL Output: Global Default Setup...
C66xx_0: GEL Output: Setup Cache...
C66xx_0: GEL Output: L1P = 32K
C66xx_0: GEL Output: L1D = 32K
C66xx_0: GEL Output: L2 = ALL SRAM
C66xx_0: GEL Output: Setup Cache... Done.
C66xx_0: GEL Output: Main PLL (PLL1) Setup ...
C66xx_0: GEL Output: PLL1 Setup for DSP @ 1000.0 MHz.
C66xx_0: GEL Output: SYSCLK2 = 333.3333 MHz, SYSCLK5 = 200.0 MHz.
C66xx_0: GEL Output: SYSCLK8 = 15.625 MHz.
C66xx_0: GEL Output: PLL1 Setup... Done.
C66xx_0: GEL Output: Power on all PSC modules and DSP domains...
C66xx_0: Trouble Writing Memory Block at 0x2350300 on Page 0 of Length 0x4: (Error -1060 @ 0x2350300) Device is not responding to the request. 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.0.791.0)
C66xx_0: GEL: Error while executing OnTargetConnect(): target access failed at *(pdctl)=(*(pdctl)|0x00000001) [evmc6657l.gel:1212] at Set_PSC_State(0, 3, 0x3) [evmc6657l.gel:1648] at Set_Psc_All_On() [evmc6657l.gel:777] at Global_Default_Setup_Silent() [evmc6657l.gel:505] at OnTargetConnect() .
C66xx_0: Trouble Reading Register ControlRegisters_CSR: (Error -1060 @ 0x41) Device is not responding to the request. 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.0.791.0)
C66xx_0: GEL Output: Invalidate All Cache...
C66xx_0: Trouble Writing Memory Block at 0x1845028 on Page 0 of Length 0x4: (Error -1060 @ 0x1845028) Device is not responding to the request. 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.0.791.0)
C66xx_0: GEL: Error calling OnPreFileLoaded(): target access failed
C66xx_0: Trouble Writing Memory Block at 0x800000 on Page 0 of Length 0x7ff0: (Error -1060 @ 0x64) Device is not responding to the request. 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.0.791.0)
C66xx_0: GEL: File: C:\Documents and Settings\hvuppaladhadiam\Desktop\user\baker\bakerdsp\current_silabs_dsp\edmaspi\Debug\edmaspi.out: Load failed.



  • 0
    TI__Guru**** 169874 points

    Hi,

    This error is coming from the GEL file itself and not CCS, therefore it is possible this is being caused by:

    - A GEL file unsuitable for your board - in this case you should try to obtain an updated GEL file from the board manufacturer;

    - A damaged board - in this case you will have to try a different board;

    Another possibility is if the device is already running some code that is preventing the emulator from accessing the core - this is a more common scenario with ARM cores, though, but is a possibility.

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Expert 1855 points

    It is not clear what is the problem. On the board Blue LED near Ethernet port does not glow. If I set the DIP Switch setting to Big Endian mode, then it connects. I converted the project to Big Endian for now. Not sure what happened to the board. This board is a Gauss EVB c6657. eInfochips.

  • 0 in reply to Harikrishna Vuppaladhadiam
    TI__Guru**** 169874 points

    Hi,

    Very interesting; per your description it seems that your board already has code pre-loaded and the ill-configured endianess was preventing it from accessing some memory regions (the GEL errors indicate it can't access certain memory or registers). I can't tell for sure this is the root cause of this problem as it is heavily tied to the pre-loaded application and the device configuration.

    Another idea is the GEL file provided by the board manufacturer is at fault; maybe it was only tested with the processor operating in big endian? Not sure, but I strongly suggest contacting the manufacturer to clarify this, or even checking the device forum (maybe someone there got a similar scenario).

    In any case, thank you for reporting back your findings. This may help others in the future.

    Regards,

    Rafael

  • 0 in reply to desouza
    Expert 1855 points

    Rafael,

      Thanks. The Gauss c6657 EVB is from TI (manufactured by eInfoChips). Anyway I have now my code working on Big Endian mode. For now I am OK till I get any other problem with the board. 

    Regards,

    Hari