• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 83 subscribers
  • Views 499 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.

TMS320F28027: Flash programming : error when writing to flash memory

Royston Calder Dsouza
Prodigy 10 points
Part Number: TMS320F28027


Hi,

The controller was working perfectly fine, then I disabled the PLL oscillator using PLL_disableOsc() function and flashed the controller, then later when I tried to change code and enable the oscillator using PLL_enableOsc(), after building while flashing, I started getting this error. as shown in the picture below.

Later I tried running it on a different system , Then I started getting issue that Processor is in low power mode and once I pressed the reset button it runs , but then the flash programmer error comes again.

I tried running it on the RAM as well; in that case, I keep getting issue cant find pll.c source file

I am note able to figure out how to solve this issue, would be very grateful if I could get some help,

Regards
Royston

  • 0
    TI__Mastermind 27736 points

    Hi Royston, 

    Our subject matter expert will be able to get to you tomorrow, sorry for this delay.

    Best,

    Ryan Ma

  • 0 in reply to Ryan Ma
    TI__Guru* 81970 points

    Royston,

    Can you comment on how you flashed the device?  Was it just via load of an .out file in CCS, or did you use the flash API to program code inside your own code?

    If the flash programming didn't finish properly we may have activated the CSM(unless you know you intentionally wrote a password).  If the device is executing code from a secure region and JTAG connection tried to establish itself, it will fail.  One way to prevent this is to boot in Wait Boot mode(shown below), which will hold the code in the BROM which is unsecure after a reset or power cycle.  After you connect, you can unlock the device and debug as normal if this was intentional, or at least determine if the device is locked. 

    Let me know if this fixes the connection and we can debug more from there.

    Best,

    Matthew