Identification of programmed FPGA images
ozpropdev
Posts: 2,792
Hi All,
A few times early on I have been "caught out" by Quartus not loading the FPGA image I thought into my board.
This happens when you make a copy of a project folder to preserve the original and don't update the path in the
create programming files dialog. One simple way to help identify your image is to change the propeller
version number which is stored @ $FFFF in the hub_rom_high.v file. The default is "1" as expected.
To change it to 4 for example the following changes were made.
This makes it easy to identify the correct image was programmed into the FPGA.
A simple "Identify Hardware" from PropTool tells the story.
Hope this helps, it certainly helped me.
Cheers
Brian
A few times early on I have been "caught out" by Quartus not loading the FPGA image I thought into my board.
This happens when you make a copy of a project folder to preserve the original and don't update the path in the
create programming files dialog. One simple way to help identify your image is to change the propeller
version number which is stored @ $FFFF in the hub_rom_high.v file. The default is "1" as expected.
To change it to 4 for example the following changes were made.
:200FF800F03934B13F873F04A53F3488A63F1E37A73F16370000AE3F21893F000171FF046A change to ::200FF800F03934B13F873F04A53F3488A63F1E37A73F16370000AE3F21893F000471FF0467The last byte is the checksum which is the 2's complement of the sum of all the bytes.
This makes it easy to identify the correct image was programmed into the FPGA.
A simple "Identify Hardware" from PropTool tells the story.
Hope this helps, it certainly helped me.
Cheers
Brian
396 x 223 - 18K
Comments