Forum Discussion

Dennis_Nedry's avatar
Dennis_Nedry
Icon for New Contributor rankNew Contributor
1 month ago

Manual checksum verification of CFM0

I am working on some post-build scripting for generating firmware update programming files for the Max 10 series FPGA.  My goal is to generate 2 separate files: POF file, for use with USB Blaster. ...
Configuration
Farabi's avatar
Farabi
Icon for Regular Contributor rankRegular Contributor
7 days ago

Hello, 

 

There might be some confusion here: 

Checksum : configuration data checksum, reflect the contents that actually downloaded/configured into CFM. Any changes to the bitstream will change checksum. Usage to detect corruption or mismatch in configuration data.

 

Usercode : it is NOT the checksum of the POF file. Quartus may default it to something static or left constant. Usercode remains identical is expected behavior. Usage to version tagging/design identification/JTAG bases system identification. 

 

regards,
Farabi

 

 

 

Dennis_Nedry's avatar
Dennis_Nedry
Icon for New Contributor rankNew Contributor
4 days ago

Cool, that sounds right to me.  Do you have any ideas about the method that those checksums are calculated?  My guess is that they seem like simple sums of a range of data, but I don't know the correct ranges or word sizes to add up.

  • Farabi's avatar
    Farabi
    Icon for Regular Contributor rankRegular Contributor
    22 hours ago

    Hello, 

     

    I am soryy, this information is treated as confidential. This is built-in inside the Quartus Programmer engine. 

    Quartus Programmer calculates the checksum by performing a simple byte-wise summation of the binary configuration data programmed to the device, excluding metadata. You can confirm this number by refer to the generated map file. 

     

     

    regards,
    Farabi