• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 81 subscribers
  • Views 534 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

F28027 Device Calibration not complete, check if device is unlocked and recalibrate

CCS/LAUNCHXL-F28069M: "Device Calibration not complete, check if device is unlocked and recalibrate" error for brand new chip

satar fatar
Prodigy 235 points
Part Number: LAUNCHXL-F28069M


Tool/software: Code Composer Studio

I have a LaunchXL-F28069M, whose controller chip was corrupted. Most likely cause was a reset/power glitch during flash programming or my error while using the Flash API. The debugger would give the "Device Cal not complete" error.

I have replaced the chip with a brand new F28062F. However I still get the same error. Suspecting an error in the rest of the board, I have checked core and IO voltages (Vdd,VddIO) and they are all fine.

I downloaded FT_Prog and checked the FTDI EEPROM. It is working fine.

Any help is appreciated.

  • 0
    TI__Mastermind 45456 points

    Hi Satar,

    Are you able to connect to the device OK (i.e. launch target config and connect to CPU1 within CCS)? This error is appearing when trying to load a program?

    After replacing the device did you perform any flash programming/erasing or did you receive the error right off the bat?

    If you're able to connect OK, open a memory browser and check the password values located at 0x3F_7FF8. If they're not programmed they should be all 0xFFFF's, which is good. If they're 0x0000's the device is locked, likely due to a power issue (make sure there are no solder bridges and that the device was soldered on correctly).

    If you're having issues connecting at all try SCI boot mode.

    Best,

    Kevin

  • 0 in reply to Kevin Allen18
    Prodigy 235 points

    Are you able to connect to the device OK (i.e. launch target config and connect to CPU1 within CCS)? This error is appearing when trying to load a program?

    > No I cannot connect to the CPU1. I cannot browse memory/load program. But "Test connection"  works ok (IR,DR scan).

    After replacing the device did you perform any flash programming/erasing or did you receive the error right off the bat?

    > No flash programming/erasing was done. Device was completely fresh and got the error right off the bat.

    open a memory browser and check the password values located at 0x3F_7FF8

    > Unable to do this as I get the error.

    If they're 0x0000's the device is locked, likely due to a power issue (make sure there are no solder bridges and that the device was soldered on correctly).

    >I have other working LaunchXL boards. I'll move the current new chip to these boards and see if the chip works. I'll update if the chip is ok and about any hardware issues on the board. I am fairly confident that the device is soldered correctly. I'll have to check solder bridges more thoroughly.

    If you're having issues connecting at all try SCI boot mode.

    > Tried this but no luck.

  • 0 in reply to satar fatar
    Prodigy 235 points
    I removed F28062F from the defective board and moved it to a working board. It can be erased/programmed without any issues.
    So both the chips (new F28062F and the older F28069M) are ok and the problem is with board hardware.

    Any pointers on which areas to check ?

    FTDI EEPROM has been tested and is working fine.
    JTAG IR DR integrity tests also work fine. Does this imply that data reaches JTAG controller inside the chip successfully ? This would be very helpful as it rules out any hardware issues on JTAG lines, isolation chips and any other components on the debugger.
  • 0 in reply to satar fatar
    TI__Mastermind 45456 points
    Hi Satar,

    I think there might be more to check on the JTAG communication. Could you go through the steps listed in this JTAG debugging Application Report? Figure 3 would be good to look at.

    http://www.ti.com/lit/spracf0

    Best,
    Kevin
  • 0 in reply to Kevin Allen18
    TI__Mastermind 45456 points
    Hi Satar,

    Have you been able to go through the JTAG steps successfully? Have you been able to narrow down the cause of your issue?

    Best,
    Kevin
  • 0 in reply to Kevin Allen18
    Prodigy 235 points

    I have checked till JTAG power part and all is ok. Other things came up at work, soI have yet to get to checking JTAG clock and XRS state. I'll let you know in a couple of days.

  • 0 in reply to satar fatar
    TI__Mastermind 45456 points
    Satar,

    OK, please let me know when you get the chance.

    Thanks,
    Kevin