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.

Programming error

Other Parts Discussed in Thread: CONTROLSUITE

I'm using CCS v5 , TMSF28035, and Blackhawk XDS560v2. Here is my question.

At the beginning, I got error message like this when programming flash.

After looking for solutions from the Internet, I found that that I might accidentally locked the device. By checking the .out file (using hex2000.exe), it does show 0xffffff... at address 0x3f7ff8. Tried to unlock the device with on-chip programmer. Even though it showed the device was successfully unlocked, I got another error when erasing Flash memory. Failed to erase sector A. Meanwhile, I found that the "DSP2803x_CSMPasswords.asm" was included in my project. I got rid of it, and the .out file also showed there is nothing in CSM_PWL area. I thought I probably solved my problem despite the fact that I already ruined four devices by far (or failed to unlock any of them.)

Got another device with new chip on board. I successfully programmed the new .out file into the device. Just for another few minutes did I realize that I was (or might be) wrong for everything I just mentioned. That same error message showed. I am unable to program my fifth device anymore.

Does anyone have idea what might went wrong here? Besides, is there any method to get my five might-be-locked devices back?

Thanks for all your help.

  • Oliver,

    What is the exact version of CCS you are using? And which target board - is it an experimenters kit or a custom board?
    Do you see this error when programming any of the examples provided in ControlSuite?

    Have you tried some of the 3rd party flash programmers to see if they generate the same error as well? If so, that probably means that the device is locked but at least it will take CCS out of the picture and you can try to erase/program to Flash directly. Some flash programmers to consider are Blackhawk Flashburn and Codeskin programmer.

  • Thanks, Arti.

    It seems the problem is a little bit random now. My CCS version is 5.1.0.9., and I'm using a custom board. Per your suggestion, I downloaded Blackhawk Flashburn. It still failed to unlock the locked MCU. What's weird was that I successfully programmed two other devices using exact .out file that locked my previous MCUs. Everything was normal as usual. I could erase, program, and verify the Flash. My problem started from a new version of my program. At the beginning, I suspected that my newer program was to be blamed until I removed the CSM_passwords file from my project, and the problem remained. Now I have no idea what went wrong here.

    The following is the error message I got when using Blackhawk Flashburn to erase my locked MCUs.

    ==========

    C:\Program Files (x86)\Blackhawk\BHFlashburn_v4.0\bin\BhFlashBurn.exe -p 0 -n 0 -d "tixds560c28x.dvr" -f "LF28XX_BHXDS560V2-USB.dat" -q- -r -c 20x6/2 -u FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF -e:ff "C:\Program Files (x86)\Blackhawk\BHFlashburn_v4.0\bin\Flash28xx\Algorithms\2803x\FlashAPIInterface2803xV1_00.out"
    Opening driver 'tixds560c28x.dvr', dat-file 'LF28XX_BHXDS560V2-USB.dat', port 0, target 0
    Connecting to DSP
    Target 'c28xx', type B, word/char/int 16/16/16 bits, big-endian 0
    Resetting DSP
    Unlocking F28035 CSM (PWL at 0x3F7FF8)
    Password FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF
    Loading 'C:\Program Files (x86)\Blackhawk\BHFlashburn_v4.0\bin\Flash28xx\Algorithms\2803x\FlashAPIInterface2803xV1_00.out'
    Loading section .cinit(2) at 0x00008AA7, size 0x00000022
    Loading section .text(3) at 0x00008848, size 0x0000025F
    Running Target Agent (type 1), press ESC to stop
    Task 'PRG_init'
    Task complete
    Clock Config: OSCCLK 20MHz, CLKINDIV /2, PLLCR x6, SYSCLKOUT 60MHz
    Erasing, options FF
    Task 'PRG_erase'
    Error: Task 'PRG_erase' failed, status 65535
    Running DSP

    Process exited with code: 65535

  • If other programmers are not able to unlock the device either, then the device may be permanently locked. I am not an expert on the device details itself and if you wish you could post to the C2000 device forum to see if they have other suggestions, but unfortunately it may just be that the device cannot be recovered.