cancel
Showing results for 
Search instead for 
Did you mean: 

PC Processors

DanielZimmermann
Journeyman III

FPGA Program checksum

I am programming an old board that contains an XCF01SV020C, 1M Flash and Xilinx XC3S200-4TQG144C FPGA.  We produced new boards that contain an XCF04SVO20C, 4M Flash and the same XC3S200-4TQG144C FPGA.  I am using Xilinx iMpact to program the board with an .mcs file.  The board programs successfully but the checksum is different from the board with a 1M Flash.  I presume this is because the checksum algorithm takes into account the unused memory, which is different between the 1M and 4M versions.  Before I take the time to install the board in the system that uses it, I would like input regarding whether it will work or if there's a way to configure iMpact to calculate the same checksum with the 1M and 4M Flash.  

Thanks for your time.  This may be a better question for a Xilinx forum but thought I'd try here because the Flash is an AMD part.

Dan

0 Likes
4 Replies

This is a basic, mostly 'user to user' forum.

Probably better to try the xilinx support forum.

 

My PC- Ryzen 5 5600x, B550 aorus pro ac, Hyper 212 black, 2 x 16gb F4-3600c16dgtzn kit, NM790 2TB, Nitro+RX6900XT, RM850, Win.10 Pro., LC27G55T.
0 Likes
avritch
Journeyman III

Hi Dan,

We are running into the same issue.  Did you ever find a work around (other than coming up with a new load file that zero's out all new memory or changing your expected checksum?).  i.e. can you instruct the IMPACT tool to calculate a checksum over a user specified range?   I looked in the IMPACT users guide and don't see anything like that 

0 Likes

Hi,

 

I couldn't find a way to configure iMPACT to calculate the same checksum and our board didn't work in the system with a 4M Flash.   I believe that the data was stored in a different region in Flash and the boot program didn't configure the FPGA properly.  Fortunately we were able to source 1M Flash from a surplus supplier and never had to find a solution to the checksum or programming issue.  Your idea to write 0 to all unused memory locations might work, but it depends on how the checksum is calculated.  I would think that the algorithm takes into account the number of 0s and you might not get the same checksum as with the smaller memory.  You might also have to make sure that the data is written to the correct addresses in Flash.  Your best bet is to try to find the legacy Flash at a surplus dealer.  Good luck with your project, and sorry I can't help more.

 

Dan

0 Likes

I just noticed that AMD has a new Forum for Xlinx hardware/software here at AMD Forums:

https://adaptivesupport.amd.com/s/?language=en_US

 

Screenshot 2024-09-23 194754.png

0 Likes