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.

LAUNCHXL-F28379D: USB bootloader issues with the F28379D launchpad

Part Number: LAUNCHXL-F28379D
Other Parts Discussed in Thread: C2000WARE

Hello,

I'm working with the F28379D launchpad, and I've been having trouble getting the USB bootloader to work. I've read up on all the information about bootloading in the TRM, as well as the information in sprabv4c document about serial flash programming. I've also been following the steps to emulate the USB bootloader found in C2000ware (setting memory location 0x0D00 to 0x0C5A and whatnot, however I am not seeing the bootloader in my device manager and thus am unable to install the driver like the instructions say).

The end application is to program firmware on the F28379D via USB without using JTAG; the final uC will be on a custom PCB and we don't want to include a debugger. As of right now, I only have the launchpad to experiment with.

1) Is it even possible to use the USB bootloader on the launchpad? I know the SCI pins aren't accessible on the launchpad so I though this could be the case, despite having a USB port.

2) If the launchpad USB port is unable to utilize the USB bootloader, then is there a set of UART pins accessible on the launchpad that can? I have a couple FTDI breakouts I can use for other pins.

3) I noticed that the options for using the two boot pins are parallel IO (00), SCI (01), wait (10) and get/flash (11). I also know that in order to use the USB bootloader in the design without emulation, I would need to alter BOOTCTRL register in the OTP section. Does this mean that once I alter that register to allow for USB bootloading, I will be unable to boot from flash? The goal is to update the firmware with USB, then have that firmware run from flash.

Thank you for your help!

Regards,

Colin

  • Hi Colin,

    Can you provide the steps that you did after writing 0x0C5A to 0x0D00 memory location? Did you run from the reset vector to start the USB boot loader.

    What is the output of the following command, usb_flash_programmer.exe -l

    Response to your other questions

    1) USB Boot loader uses pins GPIO42 and GPIO43. Looking at the schematic , these pins are not connected any jumpers. Hence it is not possible to get the USB boot loader working on the Launchpad. It was developed and tested on the Control Card ()

    2) As mentioned, GPIO42  and GPIO43 need to be used

    3)  Will get back to you regarding this query.

    Best Regards

    Siddharth

  • Hi Siddharth,

    I started a program using the debugger, then I entered 0x0C5A in address 0xD00 in the memory viewer, then did a CPU reset (run -> reset -> cpu reset). Afterward, I should see bootloader under "other devices" in my device manager, and then I should install the included driver, however I don't see the bootloader in my device manager. Running the command usb_flash_programmer.exe -l doesn't show any connected devices.

    I believe we can accomplish what we want to do without using a bootloader, so we should be good to go.

    Thanks for your support!

    Best,

    Colin