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/TMS320F28069: Error encountered when writing to flash memory

Part Number: TMS320F28069
Other Parts Discussed in Thread: UNIFLASH

Tool/software: Code Composer Studio

I am trying to load the software  using Uniflash v4)( in my custom board using the XDS100-V3 JTAG USB   emulator. I have all the time this kind of errors:
[ERROR] C28xx: Error occurred during flash operation: Timed out waiting for target to halt while executing FlashAPIInterface2806xV1_00.out
[ERROR] C28xx: Flash Programmer: Error erasing flash memory. Flash operation timed out waiting for the algorithm to complete. Operation cancelled.
I tested successfully  the JTAG communication used the test provided in CCS6  
I cant erase or load the program
any idea will be appreciated 
Thanks
Hamid
  • just wondering :
    before I used the TMS320F28069PZPS – with Success

    Now I try to program the TMS320F28069UPZPS – but I do not succeed

    any differences between theses 2 versions that don't allow me to use the XDS100?

    your answer is very appreciated
    Thanks
    Hamid
  • Hamid, both device should be same from CCS connection and code loading point of view. Please check if you have installed all the CCS updates. You can check the same by clicking on "Help" -> "Check for Updates" and install any update available for C2000.

    Regards,

    Vivek Singh
  • Thank you Vivek for your fast answer
    I figured out that TMS320F28069UPZPS has USB andd TMS320F28069PZPS not and that has nothing to do with my problem.
    Regarding the update I downloaded the last version of the UNIFLASH and I can't even erase the flash memory or calculate the checksum but I can read
    Hamid
  • I also install all the updates available for c2000 but I still having the same problem:
    [ERROR] C28xx: Error occurred during flash operation: Timed out waiting for target to halt while executing FlashAPIInterface2806xV1_00.out
    [ERROR] C28xx: Flash Programmer: Error erasing flash memory. Flash operation timed out waiting for the algorithm to complete. Operation cancelled.

    Hamid
  • Instead of Uniflash, can you try CCS?

    Vivek Singh
  • I tried first with CCS and is the same behave

    Hamid
  • Hi Vivek,
    I just found that the xrs pin goes low every 13.4ms milliseconds when I launch the erase or program tools and stays high after. Is that normal ?
    is it important to add a capacitor (100nf) at this pin ?
    Thanks
    Hamid
  • Hamid,

    You should follow the guidelines provide in device manual. Toggling XRSn is not good and could cause issue with connection. It may be because of BOOT MODE pin setting. Please check of BOOT MODE pin setting is same on working and non-working boards.

    Regards,

    Vivek Singh
  • Hi Viivek,

    Yes I am following the guidelines provided in the manual. The pin XRS is tied to vdd through 2.2k   but I didn't put any capacitor   and I did the same thing for another board athat I was able to load the program on it.

    regarding the boot mode   , when the emulator is connected the pin TRST is set to high level  so  the selected mode is "Emulation Boot"    regardless of the  state of  other pins.

    when I connect the emulator  the pin XRS  doesn't toggle.  Only when I start the erasing or  the programming   functions   XRS start toggling  and stop when the functions end with error.

    any idea what can cause this problem ?

    Thanks

    Hamid

  • Hi Viivek,

    I configured GPIO34 and GPiO37  to work in wait mode at power up , I am no able to erase flash , to read memory  but I still not able to load the program 

    ERROR] C28xx: Flash Programmer: Error encountered when writing to flash memory
    [ERROR] C28xx: File Loader: Memory write failed: Unknown error
    when I start loading the pin XRS start pulsing (reseting the device every 13ms)  
    I tried many things (different emulator, update the software,....)
    is the wdtimer the source of this problem ?  any idea will be appreciated ?
    Thank you 
    Hamid