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.

TMS320F28035: Firmware update through RS-232 Port without using Boot- loader tool.

Part Number: TMS320F28035
Other Parts Discussed in Thread: C2000WARE

Hi Everyone,
        We want to update the firmware of controller (TMS320F28035) through Modem using RS-232 port. Instead of doing manually using C2-Prog Boot- loader tool. We want to develop that in our source code. What exactly Hex file we want to update is able to fetch that file from server. Just need to be transfer that file to controller using RS-232 port. Before writing that file to UART port.
        What are the necessary things need to be send to controller and what are the check point and functionality we should have to implement in our source code. so as simple as how C2-Prog backgroundly doing that we want to develop. Need the help from your side.
Thanks,
Solar Rnd.
  • Hello, 

    Please refer to the App note sprabv4, which explains how to use SCI Flash kernels and a PC side host tool to update firmware. You can find the F2803x SCI Flash Kernel in C2000Ware at the following path:

    C2000Ware_x_xx_xx_xx > device_support > f2803x > examples > c28 > f2803x_flash_kernel

    Thanks,

    Sira

  • Hi Sira,

                 what you want say is that need to be change source code from controlling side. Actually we do not want to change anything from controlling side. Exactly what we are looking for is we have that standard bootable hex file in our Modem flash. That file we want to load in to the controller using SCI mode.

                 My question is what data need to be send before loading that file to controller so that controller firmware will update successfully. Please refer this link https://www.ti.com/lit/ug/spru513u/spru513u.pdf?ts=1606183428392  In that " Figure 12-8 " so like that we need to be send before loading that file.

    Thanks,

    Solar RND

  • I still am having trouble understand your request, but my interpretation is that you don't want to manually update firmware in SCI boot mode, instead you want to have the firmware update capability inbuilt into the application. To support this, we have support for what is called LFU (Live Firmware Update, either with or without device reset). Here, the system will only boot in Flash boot mode (i.e. no need to switch boot mode to SCI boot, no need to download the SCI Flash kernel to RAM). However, the SCI Flash Kernel will have to statically reside in Flash. Then, when the host sends a firmware update command, the application will transfer control to the SCI Flash kernel, which will receive the new firmware image from the host, and program the Flash. Then a device reset occurs, and the new application runs. So the SCI ROM bootloader is not invoked at all in this process.

    Please refer to SPRUIU8 (LFU with device reset), SPRUIU9 (LFU without device reset).

    Thanks,

    Sira