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.

TPLD2001: Checksum problems with .hex file

Part Number: TPLD2001
Other Parts Discussed in Thread: TPLD-PROGRAM

Hi,

I'm working on a I2C temporary programmer for the TPLD2001 and have the following issue:

the .hex file generated by Interconnect Studio 1.7.3+1363 has e.g. as the first line:

:10020000327f2b7f457f002a00002a2a507f000084

It seems that the Checksum is wrong..

Address: 020016 = 51210
Byte count: 1016 = 1610
Record type: 0016 = Data
Checksum: 8416
Calculated checksum: 8216

 

  • Hi Moritz,

    Can you rephrase your question for me? I'm not sure I understand the question.

    Are you receiving errors that are preventing you from programming the TPLD correctly? How are you determining what the checksum should be, and how are you determining what the incorrect checksum is?

    Regards,

    Nikki

  • Hi Nikki,

    I'm programming the device successfully using I2C from a microcontroller and also with the TPLD-PROGRAM tool on the EVM. While implementing the I2C hex file parsing code I tried to check the data using the checksum and couldn't get it to work. I expected the checksum to be 0x82 for the example line posted above. I used  https://www.fischl.de/hex_checksum_calculator/ to calculate the checksum, that's how I got the 0x82. I also wrote my own code and got the same result.

    However, the Interconnect Studio calculated a checksum of 0x84 (last 2 digits). This happens in each line. I tried different lines and different hex files. I think it is a bug in Interconnect Studio or a deviation from the standard way to calculate the checksum.  

    Best Regards,

    Moritz

  • Hi Moritz,

    I've looked into this and have found that you are correct. The checksum is not being calculated correctly. I will report this to the team so that it can be fixed. Thanks for catching it.

    However, this is a bug with InterConenct Studio that does not actually affect the functionality of the TPLD. The TPLD can be successfully programmed with an incorrect checksum without any problems. The TPLD itself never actually used the checksum to do anything, so it does not affect the functionality of the device.

    Regards,

    Nikki