TM4C1294KCPDT: LM Flash programmer does not show USB option and does not load required drivers on Windows 10 systems with no previous TI tools/software

Hello Steve,

I don't see this issue come up often but it has popped up a couple times. One user reported this process working well to set LM Flash to be in Windows 7 Compatibility mode. Is that a solution that you have tried before?

• Right Click - > Properties
• Compatibility -> Check Compatibility Mode
• Select Windows 7, Hit Ok.
• Launch Program (Or simply plug into USB if no firmware is loaded)
• DFU should now be an option

For the drivers, there are two possible issues there.

1. Needing the latest TivaWare drivers for Win 10, which you found with the patch file
2. The USB DFU firmware has a small error that sometimes causes issues with enumeration on Windows 10 machines - we did not catch this bug before TivaWare 2.2.0.295 was released. Details can be found here: https://e2e.ti.com/support/microcontrollers/other-microcontrollers-group/other/f/other-microcontrollers-forum/917631/tm4c1294ncpdt-tiva-usb-bootloader-windows-driver/3390384#3390384

Let me know how much these help with your situation, I want to see how these known solutions help first and then if there are still issues we can dive in further.

Hi Ralph,

We haven't tried running LM FLASH Programmer in Win 7 Compatibility mode as yet, but we will do some tests to check if this solves the USB DFU menu issue, and report back asap.

I'm still not clear on item 2 details you provided and how to utilize it.  Let me add some additional info on our implementation to help with context:

Our implementation does not normally boot with a DFU device enumerated.  It boots up as a generic CDC 2 port serial device using WINUSB (i.e. PID and VIDs at 0xFFFF). based on TIVAWare 2.1.2.111.  We do this to avoid having to provide custom ..inf files with our product and it has worked quite well to date.  For FW updating, we utilize the serial USB connection to send a command to place the device into DFU mode. That command instructs the TIVA to execute this code:

void enterDFUmode (void){
// Terminate the USB device and detach from the bus.
//
USBDCDTerm(0);

//
// Disable all interrupts.
//
ROM_IntMasterDisable();

//
// Disable SysTick and its interrupt.
//
ROM_SysTickIntDisable();
ROM_SysTickDisable();

//
// Disable all processor interrupts. Instead of disabling them one at a
// time, a direct write to NVIC is done to disable all peripheral
// interrupts.
//
HWREG(NVIC_DIS0) = 0xffffffff;
HWREG(NVIC_DIS1) = 0xffffffff;
HWREG(NVIC_DIS2) = 0xffffffff;
HWREG(NVIC_DIS3) = 0xffffffff;
HWREG(NVIC_DIS4) = 0xffffffff;

//
// Enable and reset the USB peripheral.
//
ROM_SysCtlPeripheralEnable(SYSCTL_PERIPH_USB0);
ROM_SysCtlPeripheralReset(SYSCTL_PERIPH_USB0);
ROM_USBClockEnable(USB0_BASE, 8, USB_CLOCK_INTERNAL); //Ver 2.1.2.111 needs an 8, Ver 2.1.4.178 needs a 4

//
// Wait for about a second.
//
ROM_SysCtlDelay(g_ui32SysClock / 3);
//
// Re-enable interrupts at the NVIC level.
//
ROM_IntMasterEnable();

//
// Call the USB boot loader.
//
ROM_UpdateUSB(0);
//ROM_UpdateEMAC(g_ui32SysClock);

//
// Should never get here, but just in case.
//
while(1)
{
}

}

This is using ROM library calls.  Do I need to change this to MAP_ library calls from a newer TIVAWare library?  

In the past, we have manually loaded the .dll and .lib files from ...PATCH-1.0.zip into the /windows32 and /syswow64 directories,  in most cases after a PC reboot, the DFU device enumerated properly, and we are good (a rather messy way to setup customers with DFU capability);  However in a recent case with a customer's Win10 laptop, this did not work, and DFU still did not enumerate properly.

Thanks for your expertise Ralph!

Best,

Steve

Hello Steve,

For the ROM USB boot loader you shouldn't need to worry about the code updates. That's only for Flash based USB boot loaders with Windows 10.

I have not tried doing the method you described for installing the device drivers. Our recommended method is to go into Device Manager and find the device that is not enumerating correctly in the list, and then after confirming that, updating the driver via Manual Search and pointing to the TivaWare driver folder or the PATCH folder.

Can you see if the customer can try and manual installation on their laptop? I've not really had anyone raise this issue in the context of needing to resolve an issue for a customer though so I can understand if that is difficult. I don't know if we really have many or any other customers using our exact TivaWare drivers like that, if that is common, it's not something I am aware of and so I don't really have a more customer friendly idea to offer right now.