This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

what file should a production programmer use to program a chip after development is done? It seems that the .hex file isn't quite enough...

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...

0