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.

TMS320F280025C: The time for programming the firmware into device

Part Number: TMS320F280025C

Hi Champ,

I am asking for my customer.

They are ready for production, and the factory is asking the approximate time for programming the FW to MCU.

Is the time gotten from how many flash memories are been erased and programmed ? How could we calculate the approximate time for programming the FW to MCU ?

Does the time have anything to do with the size of the generated output file(.out) or the programming tool been used ?

Thanks and regards,

Johnny

  • Hi Johnny,

    Below is from the datasheet.  This assumes that the flash API and the application image are available in the device.  

    Exact time depends on the boot peripheral used to stream the image in to the device.  

    Thanks and regards,
    Vamsi

  • Hi Vamsi,

    Thanks for the screenshot for the datasheet, I am clear about this.

    Exact time depends on the boot peripheral used to stream the image in to the device

    Would you kindly clarify more what do you refer to the boot peripheral ? Do you mean the way to boot (i.e. boot to flash) ?

    Also, would the exact time be calculated accurately ? And how ?

    Thanks and regards,

    Johnny.

  • Johnny,

    I mean to say, it depends on how the application flash image is loaded in to the device: Say, via JTAG, via SCI bootloader etc.  

    Exact time depends on different parameters.  Example: If SCI based loading is chosen, exact time depends on the baud rate, image size, hand shake etc.

    For more details, please contact the developer of the flash programming tool that the customer is going to use for the production. 

    Thanks and regards,
    Vamsi