TMS320F28379D: Configuring OTP BOOTCTRL Register

Hi Varada,

1. Please refer to the C2000™ Software Controlled Firmware Update Process for more details : http://www.ti.com/lit/an/spracn1/spracn1.pdf

2. As mentioned in the Technical Reference Manual "By default, Get boot mode executes flash boot when in standalone mode or wait boot when an emulator is connected to the device." So I think what you wrote is correct.

Thanks and Regards

Hi Sal,

Thanks for the input.

So what you are saying is that if we configure the BOOT_CTRL register with USB boot we cannot come back to Flash boot mode.

I cannot make out clearly from your Statement "If you want the option to boot to flash or USB, then you should configure your device to always boot to flash and then have your flash application determine whether or not it should call into the USB Bootloader from boot ROM." Could you please elaborate further/make it clear.

Your statement says that "call USB boot-loader from boot ROM". How to do this? could you please suggest?

Thanks,

varada pavani.

Hi Sal,

1. We can able to identify the GPIO status for USB connection from the application.

2. I have included Boot Rom symbols in to my project as follows is this right?

properties-->Include options>/home/ti/C2000Ware_2_00_00_02_Software/libraries/boot_rom/f2837xd/revB/rom_symbol_libs 

3. Can you please provide me any document or any thread for function call to boot rom and usb bootloader from my application?

Thanks and regards,

varada pavani.

Hi Sal,

We are calling USB Boot loader from application as follows.

EntryAddr = USB_Boot(USB_BOOT);

But unable to start the USB Boot loader. While debugging using CCS we noticed that USB_Boot() Function was returning FLASH_ENTRY_POINT, Because USB Module is not enabled. Below is the code snippet from USB_Boot function.

//If the USB module is not enabled, bypass the bootloader

if (DevCfgRegs.DC12.bit.USB_A == 0)
return FLASH_ENTRY_POINT;

Here my query is that how to enable the USB module before calling the USB_Boot() from the application?

Thanks,

Varada pavani.

Hi Sal,

After calling USB_BOOT from my application we can able to see usb device(F28x7x USB Boot Loader) in device manager.

DevCfgRegs.DC12.bit.USB_A = 1;
uint32_t EntryAddr = USB_Boot(USB_BOOT);
return EntryAddr;

But we are unable to flash our new firmware using usb_flash_programmer.exe

usb_flash_programmer.exe F2837xD_usb_flash_kernels_cpu01.dat blinky_cpu01.dat.

Are we missing anything here?

Please find the below screenshots and the error messages.

Have you been able to get it to work booting to USB bootloader?

I recommend you get that working first, and then start creating your solution. This will help you debug your issues.

sal

Hi Sal,

Device is  able to enter in to USB Boot loader.And on host PC detected as F28x7x USB Boot Loader in device manager after calling USB_Boot() from the application.

Enumeration was successful using command line usb_flash_programmer.exe -l .

Performing device check only

Manufacturer: Texas Instruments

Product ID: TMS320F28X7X USB Boot Loader

Serial number: 2

To Flash the firmware usb_flash_programmer.exe is used as below, During this transferring F2837xD_usb_flash_kernels_cpu01.dat was successful But flashing new_image.dat was failing. Please check the below logs.

usb_flash_programmer.exe F2837xD_usb_flash_kernels_cpu01.dat  new_image.dat

Manufacturer: Texas Instruments

Product ID: TMS320F28X7X USB Boot Loader

Serial number: 2

Sending 14206 bytes of data from the file F2837xD_usb_flash_kernels_cpu01.dat ... Done!

14206 out of 14206 bytes sent

success!

Error enumerating device interface: 0x0103
This may mean that the device is not attached or the driver is not installed
Error: Couldn't open the USB device

Are we missing anything from application side? Other than USB_Boot() do we need to initialise  anything?

Hi,

I do not believe there is anything different you need to do?

Can you confirm that the kernel is entirely linked to load and run from RAM?

Can you confirm that your flash application is entirely linked to load and run from flash?

Have you gotten the solution working by using EMU boot to boot to USB bootloader? I am asking if you have gotten the DFU solution working before trying to get it working when booting to flash and then the USB bootloader from your applicaiton.

sal

HI,

Also, please try loading the kernel via CCS and running it on its own and connecting with the PC application and only loading the flash application .dat file.

Let me know if this works.

sal

Hi Sal,

Can you confirm that the kernel is entirely linked to load and run from RAM?
Yes, but is this about F2837xD_usb_flash_kernels_cpu01.dat ?

Can you confirm that your flash application is entirely linked to load and run from flash?
Can you please elaborate little more on this?

Have you gotten the solution working by using EMU boot to boot to USB bootloader? I am asking if you have gotten the DFU solution working before trying to get it working when booting to flash and then the USB bootloader from your applicaiton.
Yes, below is the procedure we followed for EMU Boot to boot to USB Bootloader.

1. Connect the target with switch settings 11

2. Open Memory Browser and update the Memory Location 0xD00 with 0x0C5A.

3. Then connect USB from PC to the Micro USB Port on top of F2837xD Control Card.

4. Press CPU Reset and run button on CCS.

5. On Host PC Control card detected as "F28x7x USB bootloader" in device manager.

6. Executed the following command in host PC as below and able to flash the new firmware.
"usb_flash_programmer.exe F2837xD_usb_flash_kernels_cpu01.dat new_image.dat"

Also, please try loading the kernel via CCS and running it on its own and connecting with the PC application and only loading the flash application .dat file.

We have tried loading the kernel (F2837xD_usb_flash_kernels_cpu01) via CCS and it is running, but on host PC it is showing as "unknown USB Device" .

Thanks,

varada pavani.

Hi Sal,

Yes, it seems that something is wrong with the entry point returned by USB_Boot. 

We have modified blinky_cpu01 firmware and below is the code snippet.

uint32_t gpio46_value = GPIO_readPin(46);
if(gpio46_value == 1) //Checking whether USB is connected or not.
{
            //USB is connected with HOST PC.
            DevCfgRegs.DC12.bit.USB_A = 1;
            EntryAddr = USB_Boot(USB_BOOT); //Calling USB_Boot function.
            return EntryAddr;
}

Is the above function call is enough or need to call anyother function to branch to Entry point?

We have included the rom symbols to the project.

added the following lib path “ti/C2000Ware_2_00_00_02_Software/libraries/boot_rom/f2837xd/revB/rom_symbol_libs/c1_ROM_API/F2837xRevB_c1bootROM_BootROMSymbols_fpu32.lib” in “Project properties -->Build-->C2000 Linker --> File Search Path”.

Added the following files to project.
Shared_Boot.c
USB_Boot_Funcs.c
USB_Boot.c
USB_Structs.c
from the below location “/ti/C2000Ware_2_00_00_02_Software/libraries/boot_rom/f2837xd/revB/rom_sources/F2837x_bootROM/cpu01-bootROM/source”

During debug I have noticed that EntryAddr returned by USB_Boot fucntion is 0x00000000. Is this correct?

Am I doing anything wrong?

Hi Sal, Please check my response in-line.

I thought you were calling USB_Boot from your application. Here are the steps you should take.

Yes we are calling USB_Boot function from the application.

1a - device) Call USB_Boot from your application.

Device : Checking the USB connection with HOST and Calling USB_Boot function in application.

1b - host) Use the usb flash programmer to load the kernel to the device.

Host: using the usb flash programmer to load the kernel as below. Here I have included the log of usb flash programmer.

“usb_flash_programmer.exe F2837xD_usb_flash_kernels_cpu01.dat new_image.dat"

usb_flash_programmer.exe F2837xD_usb_flash_kernels_cpu01.dat  new_image.dat

Manufacturer: Texas Instruments

Product ID: TMS320F28X7X USB Boot Loader

Serial number: 2

Sending 14206 bytes of data from the file F2837xD_usb_flash_kernels_cpu01.dat ... Done!

14206 out of 14206 bytes sent

success!

Error enumerating device interface: 0x0103
This may mean that the device is not attached or the driver is not installed
Error: Couldn't open the USB device

From the above log it looks like that “F2837xD_usb_flash_kernels_cpu01.dat” was loading to the device, after that USB was getting removed from the device and flashing of the application was failing.

2a - device) branch to the entry point. This will branch to the kernel you just loaded to RAM. The entry point is likely 0x00000000. This will execute the flash kernel.

After USB_Boot function call, is it required to call any function to branch to entry point?

2b - host) Use the usb flash programmer to load the flash application.

3 - device) The kernel will branch to the entry point of the flash application upon completion.

Since the USB device is removed from the host after Kernel is loaded, loading flash application was failing.

Thanks,

Pavani,

Yes, it is required to branch to the entry point after loading the kernel. You are not doing 2a.

sal

Hi Sal,

Thanks for the support. We are able to do firmware up-gradation over USB on CPU1 Flash.

Now we are trying to update both CPU1 and CPU2 flash through USB.  We have referred one of the thread related to  usb firmware upgrade for both the CPU Flash. Here is the link .

Here i have mentioned build configuration of all images.

F2837xD_usb_flash_kernels_cpu01.dat-- DUAL

F2837xD_usb_flash_kernels_cpu02.dat --RAM

blink_dc_cpu1.dat--CPU1_FLASH_STANDALONE

blink_dc_cpu2.dat--CPU2_FLASH.

With the above binaries we tried to update the firmware as shown in the below command.But it failed.Please check the log.

from  the above thread we have downloaded dual2.zip and we used binaries from this and it worked.So here my query is that do we need to add anything in the project properties in usb_flash_kernels ? or Are we missing anything?

Thanks,

pavani.

Hi Pavani,

I will be unable to debug this for you specifically. If you provide more details and start the debug process and provide me updates, then I will be better able to assist you.

To help with debug, you can try to load the cpu2 kernel and run it with CCS and then load the CPU2 flash application to it using the PC tool. Then you can see what the device is doing.

However, you are unable to flash the CPU1 image, so you need to start debugging there. Start with this, and then you can post here again with what you find.

sal