- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We do our remote FPGA update using the ASMI (Active Serial Memory Interface) and the .rpd file. We have had cases when the wrong rpd file was chosen and programmed into the FPGA. The folks using the ASMI do not have programming cables, so this in effect causes the board to be dead.
We would like to add a header to the binary rpd file that software can read before the FPGA is programmed to match against the current board type. If the types don't match the programming would be aborted. If there is a match the header would be stripped off and the rpd file would then be programmed into the FPGA. We could manually add this identifier, but would like a more robust method. Is there a way to change the rpd generation to add a unique identifier inside the file? If this is not possible are there any side effects from manually editing the rpd file? RegardsLink Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Could this be solved by writing a TCL script to add the identifier to the .rpd and then add the TCL script to the Quartus toolbar?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Create intel hex file as unique identifier
Then use Create programming file and add hex
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page