Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

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.

Debug problem F2837XD

Other Parts Discussed in Thread: TMS320F28379D

Dear All,

I have a massive problem. I am working with a microcontroller F28377D. It was OK. I almost finished my application, but suddenly I got an error message when I try to debug the device. I did not change anything in my code and I don't have any breakpoints. As I said it was compiling and working fine. The error message is the end of this post.  I am using the FLASH memory because my application is quite large and RAM memory is not enough. I tried to compile another project into the RAM memory and it worked ok, so I think is something about the FLASH memory. I hope somebody could help me with this issue because I am not an expert and I felt myself completely lost about this problem. Many thanks for your help.

C28xx_CPU1: 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_CPU1: GEL Output:
Memory Map Initialization Complete
C28xx_CPU1: Trouble Removing Breakpoint with the Action "Remain Halted" at 0x1988f: (Error -1066 @ 0x1988F) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 5.1.450.0)
C28xx_CPU1: Error during Flash verification (Flash algorithm returned error condition). Operation cancelled.
C28xx_CPU1: Flash verification returned error condition. Operation cancelled.
C28xx_CPU1: Error during Flash verification (Flash algorithm returned error condition). Operation cancelled.
C28xx_CPU1: Flash verification returned error condition. Operation cancelled.
C28xx_CPU1: Please make sure the memory location you are programming have not already been programmed.
C28xx_CPU1: Error during Flash programming (Flash algorithm returned error code). Operation cancelled.
C28xx_CPU1: Please make sure the memory location you are programming have not already been programmed.
C28xx_CPU1: Error during Flash programming (Flash algorithm returned error code). Operation cancelled.
C28xx_CPU1: Please make sure the memory location you are programming have not already been programmed.
C28xx_CPU1: Error during Flash verification (Flash algorithm returned error condition). Operation cancelled.
C28xx_CPU1: Flash verification returned error condition. Operation cancelled.
C28xx_CPU1: Please make sure the memory location you are programming have not already been programmed.

  • Danilo,

    There are a few things I can recommend:

    1. Try to perform a standalone mass erase on Flash. This is to confirm that the Flash is still working as expected.

    To perform a mass erase, launch a debug session for your configuration, go to `Tools -. On-Chip Flash` and look for the erase button.

    2. If erase is successful, try loading a smaller example program. This is to determine if the problem is specific to the program you are loading.

    3. Turn on verbose mode. This option is in the On-Chip Flash view as well (very bottom). This will give you more information on what the program loader is doing during Flash Programming.

    4. Try turning off the Auto ECC Generation option in the On-Chip Flash view. Since the error is a verification error, there might be a problem with verifying the ECC.

    5. If it turns out to be a problem with the program you are loading, please let me know if you can send me this program for debugging purposes.

    6. Also, please let me know which version of CCS you are using.

    Thanks,

    Ricky

  • Hello there,

    I had a similar problem with the "TMS320F28379D controlCARD R1.3", while trying to program the flash I was getting the following error messages:

    C28xx_CPU1: GEL Output:
    Memory Map Initialization Complete
    C28xx_CPU1: 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_CPU1: Trouble Removing Breakpoint with the Action "Remain Halted" at 0xc15f: (Error -1066 @ 0xC15F) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 6.0.83.0)
    C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0xc591: (Error -1066 @ 0xC591) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 6.0.83.0)
    C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint
    C28xx_CPU1: Error occurred during flash operation: Timed out waiting for target to halt while executing erasew.alg
    C28xx_CPU1: Error occurred during flash operation: Cannot disable hardware breakpoint while the target is halted. Halt the target and try again
    C28xx_CPU1: Flash Programmer: Error erasing Sector A. Operation Cancelled.
    C28xx_CPU1: File Loader: Memory write failed: Unknown error
    C28xx_CPU1: GEL: File: C:\work\xwpro\Software\projects\xwpro_core\Debug\Bin\XWPro.out: Load failed.
    C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0xc0e3: (Error -1066 @ 0xC0E3) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 6.0.83.0)
    C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint

    It seems that in my case the issue was due to fact that I was powering up the card with a USB cable plugged in the J17 USB connector on the docking board and maybe the USB port was not able to supply enough power. I then used an external power supply plugged in the J1 connector of the docking board and the issues disappeared. In my setup I noticed that the docking board and the control card would use about 250 mA.

    Hope that this will help other who encounter similar weird issues.

    Best regards,

    Doru

  • Thank you for sharing your experience. I am sure this will be useful for other.