T56 software bug found.... OOPS!!!!

fordav1

I loaded a PIC16F57 binary. Checksum shows 0007c0c9.
I did nothing to the data and saved it as a different .bin file.
I zipped the original file and the saved file and the CRC32 is DIFFERENT!!I re-loaded the saved file and the checksum is the same 0007c0c9!
Checksum in the XGecu software is the same since checksum is inaccurate way to calculate data.
PLEASE USE CRC32 as a minimum for checksum display.

I saved the file 10 times more and only a few are the same CRC32, most have different CRC32 and different data when compared.
I assume this is a joke and the programmers are having fun with us. Very funny!!

I repeated the test but saved as .HEX and in 10 saves all HEX files have the same CRC32 when zipped/compared.

THIS IS A BUG. PLEASE FIX BINARY SAVING OF PIC16F57 (and probably many other chips also have same bug) so that binary file is not corrupted.
Thankyou!

Igor

compare both files via fc /b file1.bin file2.bin > txt.txt

fordav1

I did the fc compare. There are 647 differences listed. WOW!This is a REAL problem.
I am now using different software to save binary PIC files. I load the hex into different software and save it there as bin because XGecu software can't be trusted.

txt.zip (2.82 KB)

下载次数: 5785

2023-11-11 20:19