When I am done developing my code for the LPC1111, I use the uLink programmer to program the board and all is good.
When I try to give the code to the production people to program the part in their realm, it doesn't seem to work right.
here is a portion of the communication that I got from the production facility:
The Keil uVision tool generates the hex file that we use for programming. However, this hex file appears to be missing information in the interrupt vector section. uVision seems to know better, since when you program with uVision and the Ulink dongle, all the interrupt vectors are programmed properly.
Right now, the only way for us to figure out the correct data is to program with the dongle, dump that data, then use the dumped data with MultiWriter. The hex file by itself will not work.
Example:
Line from the hex file provided by PKC
:1000100000000000000000000000000000000000E0
Actual data that the Ulink programs
:100010000000000000000000000000001FF9FFEFDA
I am unsure what to tell them...
Adam,
Thank you soo much for the explanation. It all makes incredible sense once you have the key! I don't think I ever would have found that on my own.
So I ran elfDWT.exe and even put it as a run command in the compilation process. However, I am not sure about how to do the next part "getting it into the hex file" by rerunning the hex file creation process....
When I do this, the hex file is still missing this checksum...
I followed another thread and found out how to create the hex file!!
The trick is to "uncheck" create hex file on the Output page and include a fromelf command as the second run command on the User page:
Run #1: C:\Keil_v5\ARM\BIN\ElfDwT.exe !L
Run #2 C:\Keil_v5\ARM\ARMCC\bin\fromelf.exe --i32combined -o !H !L
and Voila!! the checksum is included!!
Once again, thank you very much for your help!!