Hello.
I am seing an interesting behavior difference in my custom board from the EK-TM4c129XL, after erasing the entire flash.
I have written a function that, after receiving a command via the UART0, it erases the full flash memory of the device using ROM_FlashErase calls. This function is executed from SRAM to avoid any issue with the calls.
Then, the function completes and the memory is empty in the devices (both Evaluation board and Custom board). However, when I try to reprogram the chip using the Uart0, even with LM Flash programmer, the reprogramming only works on the Evaluation board. I am assuming this should be the standard operation for a erased device (we are used to do that with our 123x devices with no issues). It happens the same if the flash is erased from the LM flash programmer (using a ICDI device as JTAG).
Moreover, if I use a stellaris board to Unlock both boards, then I can reprogram our custom board only if I uncheck the "DISABLE AUTO BAUD SUPPORT" option from the menu, and set the baud rate to 115200. The Evaluation board can be reprogrammed with the auto baud support option ON.
We have tried all this methods with our custom boards using different versions of the silicon as XM4c129ENCPDTI1 or TM4c1292NCPDTI3. We haven't seen any issue with the UART0 port when the program is running even at high speeds (even at 8Mbps). To communicate we are using a original FTDI USB 2.0 Hi-Speed to UART cable which C232HD ic.
Have you experienced the same issues at some point?
Regards
