• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 82 subscribers
  • Views 235 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.

TMS320F280049C: serial_flash_programmer problem (VQFN 56-pin device)

Sh.Sasaki
Guru 13625 points

Part Number: TMS320F280049C
Other Parts Discussed in Thread: C2000WARE

Hi experts,

My customer is testing a firmware update on SCI using serial_flash_programmer. The customer has successfully updated the firmware using F280049C LaunchPad.

The kernel and application used are as follows.

  • C:\ti\c2000\C2000Ware_3_04_00_00\utilities\flash_programmers\serial_flash_programmer\f28004x_fw_upgrade_example\flashapi_ex2_sci_kernel.txt
  • C:\ti\c2000\C2000Ware_3_04_00_00\utilities\flash_programmers\serial_flash_programmer\f28004x_fw_upgrade_example\led_ex1_blinky.txt

The customer then tried SCI programming with the customer's original board(F280049C VQFN 56-pin). The kernel and app are the same as before.

The kernel download is successful, but the device loops at the autobaudlock() of the app download.

Do you know why such a problem occurs? autobaudlock() at kernel download was successful.

Best regards,
Sasaki

  • +1
    TI__Expert 5630 points

    Hi Sasaki, 

    What clock source is the customer using? If it is different from the clock source used in the launchpad, the example's clock configuration needs to be modified accordingly in Device_init. 

    Thanks, 

    Anu

  • 0 in reply to Anu Biradar
    Guru 13625 points

    Hi Anu-san,

    Thank you for the information.

    I I have confirmed that the BOOTROM uses INTOSC and the kernel uses an external crystal.
    The customer's board has a different clock source, so I ask the customer to modify the kernel program.

    Best regards,
    Sasaki