This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

5505 Boot Signature

For an unsecure boot the first word of the boot image should be 0x09AA.  I don't see this in the output of the hex conversion utility.  Is this the expected behavior?  In other words, is it expected that the flash programmer somehow just knows to stick in this number automatically?  It would be preferable for this to be in the hex conversion utility.  (Maybe it is and I'm using the wrong option!)

I did find one bin file in the software from Spectrum Digital.  The bin file itself has the 0x09AA signature though I couldn't tell if someone hacked that into the file after the fact or if it was generated that way.  

 

  • Brad,

    Looking at some old '5402 code, I see that the hex500 utility adds the boot signature of 0x08AA to the output file. (I ran the hex500 utility and recieved the same results I had in 2001).

    It appears the hex55 utility omits the boot signature from its output.

    Best regards,

    Quentin Aldana

  • When the hex55 -boot option is used you should be getting the required 0x09AA as the first word of the data if you have specified the 5505 boot format by using the -v5505 option.  If you used -v5505 and did not get the 0x09AA that would be a bug.

     

  • Ok, we finally have it figured out.  The hex conversion utility did not introduce 5505 support until version 4.3.3.  We were using the version bundled with CCS 4.1 which is 4.3.2.  Doh!  Part of the issue was also that prior to CGT 4.3.3 the hex conversion utilty would not "complain" that it did not support -v5505.  I'm told that is now fixed.  So when the next device gets introduced and someone uses the wrong version of the hex conversion utility you should get a warning.