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.

ADC Calibration not complete, check if device is unlocked and recalibrate.

Other Parts Discussed in Thread: TMS320F28335, UNIFLASH

Hi,

   Hi i am using TMS320F28335 with ccsv5 and xds100V3 from olimex.

   I successfully loaded a toggling  program into Flash memory GPIO pins were toggled.

   Boot mode was “jump to flash”, all the boot mode pins were high.

   Then I was trying to load the same program into Flash memory. But i got an error.

   So I erased the flash sectors using  uniflash, with boot mode branch to SARAM.

   Now no program are loaded  in flash.

  Then again I loaded the same program into flash successfully, Boot mode was “jump to flash” all the boot mode

   pins were high.   And GPIO pins were toggled.

 

 Then i was trying to load a program into RAM memory boot mode was branch to SARAM. Suddenly I got the below error, and I could not erase OR unlock the flash sectors.

 

  While loading into RAM I got the below error

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 

C28xx: Flash Programmer: Warning: The configured device (TMS320F28335), does not match the detected device (). Flash Programming operations could be affected. Please consider modifying your target configuration file.

C28xx: GEL Output:

ADC Calibration not complete, check if device is unlocked and recalibrate.C28xx: GEL Output:

ADC Calibration not complete, check if device is unlocked and recalibrate.C28xx: GEL Output:

ADC Calibration not complete, check if device is unlocked and recalibrate.C28xx: GEL Output:

ADC Calibration not complete, check if device is unlocked and recalibrate.C28xx: Breakpoint Manager: Retrying with a AET breakpoint

C28xx: Trouble Setting Breakpoint with the Action "Finish Auto Run" at 0x9409: (Error -1066 @ 0x9409) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 5.1.232.0)

C28xx: Can't Run Target CPU: (Error -1156 @ 0x0) Device may be operating in low-power mode. Do you want to bring it out of this mode? (Emulation package 5.1.232.0)

C28xx: Trouble Halting Target CPU: (Error -1135 @ 0x0) The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Emulation package 5.1.232.0)

C28xx: Error: (Error -1135 @ 0x0) The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Emulation package 5.1.232.0)

C28xx: Unable to determine target status after 20 attempts

C28xx: 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

 ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 

Now I could not load the program into flash or ram.

 

This shows that my devise is locked.

I didn’t interrupt any erasing process, or I didn’t write zero to CSM section.

 

 I read data from password locations using uniflash. 0x33 FFF8 - 0x33 FFFF  these locations were zeros.

I have attached the CCS error which I got when I am loading program into ram 

How can I solve this issue?

What is the reason for this?

is this this related to boot mode?

how can i avoid this error?

I have one more processor,  have the same issue.

 

 

 

Thanks in Advance

AKHIL FARNCIS

 

 

  • Hi Akhil,

    If you are reading 0x0 from password locations in flash then it's very likely that device is LOCK. If you have not programmed the password locations then either it happened due to some mistake in .out or due to interruption during flash operation. To find out issue in .out file, please check your map file to see if there is anything mapped at password locations in flash.  If you find something then it's good news because you should be able to find the value at those location from hex file and use that to unlock the device. If not then device can not be recovered and it need to be replaced. Since you already have another locked device, it'll be good to find the cause of program disruption specially power supply or any external reset which could reset the device.

    You have another post open here which look  similar. Are both issues related?

    Regards,

    Vivek Singh

  • HI Vivek,

    Thanks for your reply.

    I could not find anything wrong in mt .out file.

    Means i could not find anything which is capable to lock the device or unlock the device.

    I am attaching the .OUT file.

    Please check.

    I have some doubt on my boot mode circuit also.

    I am attaching my boot mode circuit also please check both and give me a solution

    boot_mode.docx

    F28335_example_nonBIOS_flash.rar

    Thanks in Advance

    Akhil Francis

  • There may be additional information here: e2e.ti.com/.../552007
  • Akhil,

    I checked your COFF file provided. It doesn't seem have any valid password. So, I suspect the device got locked because of some interruption during flash erase / programming process.

    You seem to have a very weak up on your boot mode pins. 2.2k is enough, So you don't need 22k.

    Regards,
    Manoj