• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 82 subscribers
  • Views 1178 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.

CCS/TMS320F28379D: Debug: Get the following error on CPU 2

Anil Singhal
Intellectual 810 points
Part Number: TMS320F28379D

Tool/software: Code Composer Studio

C28xx_CPU2: If erase/program (E/P) operation is being done on one core, the other core should not execute from shared-RAM (SR) as they are used for the E/P code. Also, CPU1 will be halted to determine SR ownership for the CPU which will run the Flash Plugin code, after which CPU1 will be set to run its application. User code execution from SR could commence after both flash banks are programmed.
C28xx_CPU2: Trouble Removing Breakpoint with the Action "Remain Halted" at 0xc0eb: (Error -1066 @ 0xC0EB) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 8.0.27.9)
C28xx_CPU2: Error executing PLL configuration algorithm. Operation cancelled. (0x0)
C28xx_CPU2: File Loader: Memory write failed: Unknown error
C28xx_CPU2: GEL: File: Y:\Software\Digital\IMPACT_FW\Series400\Firmware\Trunk\SecondaryCore\Bootloader\SantaCruzBootloader_LAN9252\Debug\SantaCruzBootloader_LAN9252.out: Load failed.
C28xx_CPU2: Trouble Setting Breakpoint with the Action "Remain Halted" at 0xc056: (Error -1066 @ 0xC056) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 8.0.27.9)
C28xx_CPU2: Breakpoint Manager: Retrying with a AET breakpoint

  • 0
    TI__Guru** 113165 points

    Anil,

    Please make sure you have CPU1 also connected to CCS and halted.

    Error is for address 0xC056 which GS0 RAM. Are you using that RAM for CPU2 code? If yes then please note that by default this RAM is assigned to CPU1 hence CPU2 can not execute code from GS0 unless CPU1 code (or Gel file) assign it to CPU2.

    Regards,

    Vivek Singh 

  • 0 in reply to Vivek Singh
    Intellectual 810 points

    I can connect to CPU1. I checked the map file for CPU 2 and there is nothing assigned at that address.

    I also get the following errors after the initial errors

    C28xx_CPU2: Breakpoint Manager: Retrying with a AET breakpoint
    C28xx_CPU2: Error occurred during flash operation: Timed out waiting for target to halt while executing pwrite_en.alg
    C28xx_CPU2: Flash operation timed out waiting for the algorithm to complete. Operation cancelled.
    C28xx_CPU2: Perform a debugger reset and execute the Boot-ROM code (click on the RESUME button in CCS debug window) before erasing/loading the Flash. If that does not help to perform a successful Flash erase/load, check the Reset cause (RESC) register, NMI shadow flag (NMISHDFLG) register and the Boot-ROM status register for further debug.
    C28xx_CPU2: Breakpoint Manager: Unable to remove requested AET job
    C28xx_CPU2: Trouble Setting Breakpoint with the Action "Remain Halted" at 0xc056: (Error -1066 @ 0xC056) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 8.0.27.9)
    C28xx_CPU2: Breakpoint Manager: Retrying with a AET breakpoint
    C28xx_CPU2: Error occurred during flash operation: Timed out waiting for target to halt while executing pwrite_dis.alg
    C28xx_CPU2: Flash operation timed out waiting for the algorithm to complete. Operation cancelled.
    C28xx_CPU2: Perform a debugger reset and execute the Boot-ROM code (click on the RESUME button in CCS debug window) before erasing/loading the Flash. If that does not help to perform a successful Flash erase/load, check the Reset cause (RESC) register, NMI shadow flag (NMISHDFLG) register and the Boot-ROM status register for further debug.
    C28xx_CPU2: Breakpoint Manager: Unable to remove requested AET job

  • 0 in reply to Anil Singhal
    TI__Guru** 113165 points

    Anil,

    What is the BOOTMODE (GPIO72/GPIO84) setting you have on board? If it is BOOT to FLASH (1/1) then please change it to Wait BOOT (1/0) and see if that helps. after changing the BOOTMODE pin setting please make sure to reset (or power cycle) the board.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    TI__Guru** 113165 points

    Anil,

    Is this issue resolved?

    Vivek Singh

  • 0 in reply to Vivek Singh
    Intellectual 810 points

    The error is gone.. but I still don't know why.  However, we can move on.