How to calculate this crc16

Requan · Joined: 11 May 2008 Posts: 74

I trigger my bootloader by sending rs232 command, so I have to write my own program on PC instead of siow function: "download software". I listened what siow program send by rs232 and i saw that before last row (hex file): "00000001FF" program send CRC (for hex file below is "FEE7").

asmboy · Joined: 20 Nov 2007 Posts: 2128 Location: albany ny

try a SEARCH of this forum ???

also nice solutions in the code forum.
cmon don't be lazy......

here is a great one with c code

[url]
http://www.ccsinfo.com/forum/viewtopic.php?t=24977&highlight=crc16 [/url]

FvM · Joined: 27 Aug 2008 Posts: 2337 Location: Germany

You didn't tell why you want to calculate the CCS-private CRC? It's not checked anywhere as far as I'm aware of.

Requan · Joined: 11 May 2008 Posts: 74

asmboy
I am not lazy, i checked it also.

FvM
I would like to use bootloader in modbus line, so i have to create my own software to upload firmware(switch between rx and tx)
CCS told me that it is crc16 so i thought that is ordinary CRC16, but as You wrote i was wrong Crying or Very sad

I dont know what for is this crc because each row of hex contains crc and in loader.c after receiving each row, program calulate crc. I didn't see if in ccs bootloader example this crc is checking

FvM · Joined: 27 Aug 2008 Posts: 2337 Location: Germany

Sounds like you are confusing two points:
- Hex files have a 8-Bit checksum at the end of each line. It's checked e.g. by the bootloader
- CCS hex files have a CRC16 in the last comment line. It's generation method is undocumented, but I assume you can get the information from CCS. It's not checked by the bootloader.

Ttelmah · Joined: 11 Mar 2010 Posts: 19497

and, seriously, a bootloader, really can't use it.
Problem is that a PIC has a lot less RAM than ROM. So the bootloader has to have already written most of the memory, by the time it reaches the the CRC. If it's bad, what has been written is screwed.
It almost certainly is standard CRC16. Have you read the Intel Hex format definitions?. They specify a CRC _option_ for the format, and quite a few programs can generate this. It check-sums the memory block, _not_ the transmitted data. So the block of memory represented by the file, has a checksum calculated on it using standard CRC16, and this is then appended as a 'comment' line to the end of the file. If you are trying to checksum the 'file', then it won't work.

Best Wsihes