Other Parts Discussed in Thread: CC3235SF, TM4C1294NCPDT, , EK-TM4C1294XL
Hi. We have custom boards using the TM4C129CNCPDT connected to a CC3235SF. We normally flash the XDS110 bootloader and firmware using xdsdfu.exe, and the device shows up as a Ti XDS110 in Windows device manager. On our last build, we were using a slightly different model, the TM4C1294NCPDT, and the process worked fine. But we just got our new revision boards in with the TM4C129CNCPDT and the firmware seems like it's getting stuck somewhere.
I am able to connect with xdsdfu -e, flash the updated bootloader (I've tried files from ccs1011, ccs1040, and ccs1120 but all have the same failure), and flash the firmware. But after the firmware flash is done, the chip does not respond, the LEDs do not come on, and there are no drivers populated in Windows device manager.
Luckily we have a SWD connection to the chip, so I've tested using J-Flash to verify the contents of the flash, they look fine. I've even loaded up some example project for the EK-TM4C1294XL in Code Composer Studio to prove that the LEDs will light up (our LEDs are on PD2 and PD3). Power, clocking, GPIO, LEDs all seem to work, but the XDS110 firmware will not.
Is there any known issue with TM4C129CNCPDT in relation to TM4C1294NCPDT? Or should I keep looking at our board layout for errors?