Hi all,
I am fairly new to the group and have gotten some great info so far, now I am stuck.
I am using CCS 6 to write code and generate the *.bin files. A boot loader is involved and I am using the code given with TivaWare 2.1.0.12573. A bootloader BIN is generated using the included example. My custom application has an offset of 0x4000 (the example given with TivaWare is basically being used) and has the code necessary to recognize an update request. "SoftwareUpdateBegin" gets called when LM FLASH Programmer 1613 requests it and the program is downloaded with no errors. My custom code does not start. I can keep sending successful program requests to no avail. A hard reboot does not even bring my program up, but LM Flash is still able to successfully send it code. The same behavior happens when using the given TivaWare examples. Under normal behavior my application boots up just fine when a bootloader is present. Hard resets work properly. Only when I try an program with LM Flash does it enter this state. What am I missing? Here is my procedure.
1) generate bootloader and application BINS with proper offsets
2) use LM FLASH (ICDI) to download bootloader to offset 0x0000 (erase entire flash, verify and reset are selected)
3) use LM FLASH (ICDI) to download application to offset 0x4000 (erase necessary pages, verify and reset are selected, application starts after this)
4) test that the application comes up properly, reset multiple times
5) use LM FLASH (Ethernet) to download same application - it appears successful, but application never starts, but I can successfully download repeatedly
The end result should be the customer only needing LM Flash Programmer, Ethernet and an application BIN. This is being tested on the DEV kit but will eventually be moved to a custom board.
Any ideas?
TIA
Draper
As a quick follow up, I uploaded the entire BIN contents of the device to a file after step 4. Then programmed it back into the dev board.. The application runs but when I use LM FLASH ethernet to download program it gives the error "error starting the BOOTP server." Is this a clue?
Ok, the issue is resolved, I should have done more research .. My DK-TM4C129X is the RAO version which DOES NOT support a ROM bootloader. Verified by checking the register and the markings on the chip. Lesson learned, hopefully it will be useful to others..