- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Hi,
a customer using TMS320F28234 for many years suddenly faces the following.
We have had problems with the bootloader on 2 boards with the TMS320F28234 at the same time.
The application (safety critical) was no longer functional after the failed software update.
The bootloader is 7 years old (also the design of the pcb board) and we have programmed hundreds of boards with it without any problems.
The TMS320 is programmed via an application processor using the UART interface.
First an autobaud detect is performed, then a flash API is transferred to the TMS320 via the UART interface, followed by the command to erase the flash memory.
This erasing of the flash memory is done sector by sector. In the processor a timeout period of 10 s per sector is programmed. In this case the time was not sufficient (see picture).
Usually the necessary time is about 2...3 s per sector.
It should be noted that both before the bootloader was executed and after (with extended timeout time and successful programming of the flash memory), the controller worked without any problems.
The last current case is with a TMS320F28234PGFA G4A-97C7PJW (G4) processor.
To our question: how can it come to such an extension of the "normal" time for erasing the flash memory? (approx. factor 3-5)
