- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Bit of a noob here regarding embedded development, so go easy. I've been developing some firmware for a device using the NIOS II processor and the device is set up to configure and boot from EPCS. I've implemented the ability to backup and overwrite the FPGA and application configuration from within the firmware, which works fine. A new spin of the board however has introduced a much larger EPCS device (2 MiB) which means I have plenty free for general purpose use, which is good. However, when I do a backup of the firmware I really don't want to have to save the whole device, and nor do I want to accidentally store user data over the FPGA config or application binary. So my question is this; is there any way I can programatically determine where the application and FPGA configuration end? Or in other words, how can I tell how much space they consume? On a related note, once I overwrite the FPGA configuration in EPCS, is there any way to force a reconfiguration and reboot from within the application code?Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
--- Quote Start --- So my question is this; is there any way I can programatically determine where the application and FPGA configuration end? Or in other words, how can I tell how much space they consume? --- Quote End --- You get this information from the .sof and .elf files you use to program epcs. For example you may use this manual procedure: 1. Convert fpga configuration .sof file into hex sof2flash --epcs --input=fpga_project.sof --output=fpga_project.flash 2. Convert Nios firmware .elf file into hex right after fpga configuration elf2flash --epcs --after=fpga_project.flash --input=nios_firmware.elf --output=nios_firmware.flash Open the resulting nios_firmware.flash with any text editor, go to the end and read the max used address. Remind that epcs is made of 64KB size blocks, so you must place your user data starting from the beginning of the next block and not right after firmware, otherwise you couldn't erase and change it without erasing the last part of firmware data. --- Quote Start --- On a related note, once I overwrite the FPGA configuration in EPCS, is there any way to force a reconfiguration and reboot from within the application code? --- Quote End --- You should consider using remote_update core. Refer to AN521.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I also think enough of the format of the EPCS image is documented to let you read it to find the code to download - and hence the end of it.
If you want to save other info in the latter blocks, I'd pick a fixed offset that gives some free space beyond the current used part - that way you won't get into trouble when the fpga image grows!
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