• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 811 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.

CCS4.1 F28035 Flash programming problem

JosefMieslinger
Intellectual 2170 points


Hi,

my customer wants to use the CCS4.1 IDE to program the flash of his F28035 device in the Experimenters Kit.

Unfortunately the On-chip Flash Dialog in CCS4.1 for F28035 allows only to set the OSCCLK in the Clock configuration section and not to set the PLLCR and the CLKINDV as as shown in the guide on the TI Embedded Processing Wiki.

He tried to set the OSCCLK to 10MHz (internal oscillator frequency of F28035), but this does not work with the tool and generates the following error message:
"C28xx: Flash Programmer: Error erasing flash memory. Sysclk (5) is not within the valid range [15,100]. Adjust the OSCCLK and PLLCR value accordingly."

Setting OSCCLK to 60MHz is accepted by the tool, but flashing the device a few times leads to the effect that CCS can no longer connect to the F28035 device via JTAG.

A recommendation of the "right" settings for the On-chip Flash tool in CCS4.1 would be highly appreciated.

Thanks for your help!

Best regards,
-Joe

 

  • 0
    TI__Guru* 92780 points

    Joe,

    I also recieved an email with regards to this (I think it is the same customer).  I'll respond in both places.

    A system clock calculation bug has been identified by the Code Composer folks for the flash plug-in.  They are working towards a fix.  More details in the email thread.

    If the device is truly locked then it will need to be replaced.  Can some checks be done to double check this (if not done already).

    - put the device in “WAIT” boot mode (SCI mode should also work).   This should allow connection without the eCSL kicking the JTAG off.

    - Try to connect CCS.

    - If you can connect then open a memory window to the password locations.  On piccolo this is at 0x3F 7FF8 - 0x3F 7FFF

    - If the password reads all 0x0000 then refresh the window a couple of times.

    - After a refresh if the password still reads all 0x0000 then it is most likely locked.  If it reads 0xFFFF then it has unlocked and something else is going on.

    Regards,

    Lori