• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 1192 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Compiler/TM4C1294NCPDT: TM4C1294 boot_serial in USB mode, could not make it work

richard payne
Genius 4640 points
Part Number: TM4C1294NCPDT
Other Parts Discussed in Thread: EK-TM4C1294XL, LMFLASHPROGRAMMER

Tool/software: TI C/C++ Compiler

I'm on a learning curve here, I'm familiar with USB where I did some work on LPC1549 device in the past (CDC and other). You short a jumper and then apply reset, the window folder pop up, delete the old firmware and insert new firmware and then applied reset. I assume this is DFU enumeration mode and window 10 handled this for you. 

I have the TMC41294XL Rev D PCB with debug USB on the RHS and Device USB on the LHS.

I found the boot serial code in <.....\products\TivaWare_C_Series-2.1.3.156\examples\boards\ek-tm4c1294xl\boot_serial> and put into CCS 7 and reviewed the <bl_config.h>, see attached, I modified them in accordance to SW-TM4C-BOOTLDR-UG-2.1.3.156.pdf. All CCS software/driver are up to date. 

After installing the firmware into the device, I disconnected the debug USB cable and change jumper from ICDI to OTG on JP1 so MCU is powered by device USB port. I have even isolated CAN and UART from ICDI via jumper JP4/JP5.  

I could not make it work or make sense to me......however I do register USD connection in device list (see picture below, look like there an error) but there no pop up Window under the DFU.

Can you help me to understand what went wrong and check if there is error from my part within the <bl_config.h> file. Is there any other changes in code within <boot_serial> 

Thanks

 

 

0647.bl_config.h

  • 0
    TI__Guru*** 135155 points
    Hello Richard,

    When you check for the DFU being available, are you using LMFlashProgrammer for that? Does it show no device listed under "Manual Configuration", "Interace = USB DFU"?

    That the device shows up as a Stellaris Device Firmware Upgrade usually indicates it is working, though I've never seen that device manager message before.

    Can you flash erase the device and make the connection to see if the ROM USB boot loader has the same messaging? That would be important to understand as it could point to the issue being driver vs boot loader firmware setup.

    Are you using TivaWare version 2.1.3.156 for this? The latest version is 2.1.4.178 and part of our update is a patched USB driver for Windows 10 both of which you can download from: software-dl.ti.com/.../index_FDS.html
  • 0 in reply to Ralph Jacobi
    Genius 4640 points

    Thank for the reply

     

    Yes it did work using LMFlashProgrammer, thank I missed this, sorry. 

     

    I was hoping it pop up window explorer folder like it did on LPC1549 so no 3rd party app is needed. In this case, this programmer app is needed, not ideal, because I need it to work on Android later on.

     

    Do you have C# source code for the programmer so I implement simple programmer code into our app, only for firmware update and verify and that it.

     

    I'm working on TM4C firmware run on CDC (or HID) USB enum, what is the proper procedure to reset the USB and put to DFU mode without powering up and down, do I need to apply POR on a code to put USB to DFU mode?, which approach is best suited?

     

    Best wishes

     

    R.

  • 0 in reply to richard payne
    TI__Guru*** 135155 points
    Hello Richard,

    We do not provide the source code for the LM Flash Programmer. You should reference the commands used for USB DFU covered within our TivaWare Boot Loader user guide (Located at [Install Path]\TivaWare_C_Series-2.1.4.178\docs\SW-TM4C-BOOTLDR-UG-2.1.4.178.pdf)

    As far as your question on USB to DFU mode, it's not uncommon for a boot loader to be invoked via a push button or other trigger without power cycling the hardware. For your application, the key would be ensuring the device recognized as now being recognized as in DFU, so while you wouldn't need to do a full POR, you would need to shut down USB and then restart it so it re-enumerates with the descriptors for DFU.

    If you have further questions about how to make USB DFU work, I'd like to request you make a new post as that is a different topic from the topic presented.