TMS320F280049C: Live firmware upgrade issue

Hi Vishal,

Sorry I was out of office for more than a week.

Are you trying the examples for F28003x now (not F28004x) and it is still not working?

Did you use the example (BOTH LED blinky + Flash kernel) from the DigitalPower SDK (not C2000Ware)?

Thanks,

Sira

Hi Sira, 

No issue!! 

Yes, now i am trying with F28003x LaunchXL.  

As i am referring the document "TIDUEY4D".  So, i am using the example from the DigitalPower SDK "TIDM-02011" ("Buck_F28003x_lfu" + "Flash_kernel_ex3_sci_flash_kernel") [tried with version 4.00.00 and 5.02]. I am using both example with BANK1_TO_BANK0_COPY build configuration. 

Now i am explaining the steps that i have followed:

1. Build Flash_Kernel example with above mentioned build configuration. I was getting JTAG error with " TMS320F280039c.ccxml" so i changed it with "TMS320F280039c_LAUNCHPad.ccxml (taken from blinky example of C2000Ware)". It worked. 

2. Loaded "flash_kernel_ex3_sci_flash_kernel.out" to the F28003x_LAUNCHXL. Selected to "Run".

3.  Build the BANK0_FLASH_BANK10COPY build configuration of the "buck_F28003x_lfu project", with BANK0_V1 predefined symbol. Then, renamed the output .txt file by adding V1 and placed in serial_flash_programmer folder under "DigitalPower_SDK". Same i did with BANK0_V2 predefined symbol. 

4. Downloaded  "buck_F28003x_lfuBANK0FLASH_v1.txt" with windows command prompt  by giving path under "DigitalPower SDK". But not seeing output on board. 

5. I checked with breakpoint on "FLASH_KERNEL" example. It is branching to the BANK0 address. But i don't know why it is not working. Sharing screenshot. 

Regards

Vishal,

Any build configuration should work here, so it is odd that it isn't working in your case. But specifically why are you using the BANK1_TO_BANK0_COPY build configuration (this is more specific to a FOTA like application)? Shouldn't you be trying the BANK0_LDFU/BANK1_LDFU build configurations for LFU? Have you tried those?

Thanks,

Sira

Hi Sira, 

Thanks for your quick support !!

Yes, it is for FOTA application which is going to be used in our exiting product. 

I have tried BANK0_LDFU/BANK1_LDFU, these configuration are working fine. In this case,  LFU is working for both the cases BANK0_LDFU and BANK1_LDFU. But the major concern with this approach, the user needs to be aware of which Flash bank their firmware executable is targeted for. It is difficult to achieve in products installed at field. 

This is the reason i am going with BANK1_TO_BANK0_COPY build configuration. With this build configuration,  seems like flash gets freeze the moment i am downloading the application executable from command prompt. 

STEPS:

1. Loaded the FLASH_KERNEL(BANK1_TO_BANK0_COPY) through CCS Theia. "Run" from CCS Theia.

2. With command prompt, i am giving LFU command then downloading starts. when the application successfully downloaded and i am getting.

               Bit rate /s of transfer was: 7290.536133
                Application load successful!
               Done waiting for application to download and boot...
               What operation do you want to perform? 

At this stage flash gets freeze and FLASH_KERNEL also stops in CCS Theia. But, this is not happening with BANK0_LDFU/BANK1_LDFU build configurations. 

Regards,

Vishal,

Understood.

Did you follow the steps in Section 4 of tiduey4? This specifically discusses running the example like a FOTA example.

Thanks,

Sira

Hi Sira, 

Yes, i am following section#4(FOTA example) of tiduey4.

Since i am new for TI environment. 

One another question : Any project is having two build configuration RAM(Run from RAM) and FLASH(Run from Flash). In example "buck_F28003x_lfu", it is always from FLASH(all build configuration is FLASH based only. So, my question how the build configurations BANK0_FLASH/BANK1_FLASH/BANK2_FLASH are different from BANK0_FLASH_BANK10COPY. What are the changes between these configurations and at what level? 

Why i am asking these question.. Because, I have to prepare my existing running product firmware to LFU compatible firmware. Kindly help me to provide these information also. 

Regards 

Vishal,

All of these are documented in the user guide.

At this point I think it would be good for us to have a meeting to go over your issues and potentially debug.

Can you send me a private message on e2e, so we can take this further?

Thanks,

Sira