Hi Hong, [quote userid="542779" url="~/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1495866/tm4c129encpdt-jtag-programming-tm4c-failed-with-corrupted-flash-image/5748199#5748199"] UNDI code segment, data segment UNDI physical device KB free base memory after llation failed - can not continu [/quote] These are legible English. What is stored in the ROM memory is just binary. I cannot relate why you think these are in the ROM bootloader. I have a couple of questions and suggestions. - Are you seeing these English " PXENV+ at . !PXI.. entry point at .. UND.. I code segemtn, data segment. (.kb)...." on every device you have tested? - You mentioned you are using tftp boot mode. Is this your custom Ethernet bootloader or you are using TivaWare bootloader? - Can you repeat the same problem using TivaWare Ethernet bootloader example? - The readable ASCII are at address locations between 0x3D0 and 0x440 as shown on your screenshot. The ROM does not locate at this address, The ROM starts at 0x20000000. First of all, I don't know where these texts come from. Let's suppose these are part of the ROM which shouldn't happen in the first place, the programmer must have read the ROM (starting at 0x20000000) and program to the flash at 0x3D0 to 0x440. This is the reason I asked which programmer did you use? - One question to ask is you the tftp boot is reading from a .out file or a .bin file. A .out file will contain debug symbols. Can you check if you are reading really a binary file and not other formats? - As part of the debug, is it possible for you to print out what is received on TFTP to a UART COM port and also print out what you are going to program to the flash on the UART COM port. For example, you may be reading a data stream of 0x12345678 from TFTP. The 0x12345678 is supposed to be the data you are going to program to the flash. If you are programming anything other than 0x12345678 then it is a problem with the programmer.
↧