Honored Contributor
Honored ContributorThere are a lot of posts in the forum about how to do this.
The basics: 1 - Application code is unpacked before storing in the flash (not in S-record format). So you can safely convert the application file to binary and deploy that. 2 - Application code is typically located immediately following the FPGA configuration data. This is simply because the default EPCS bootloader will search for the end of the config data and begin boot loading from there. The algorithm for finding the end of the fpga config data can be discovered by looking at the current EPCS bootloader found in: C:\altera\91\nios2eds\components\altera_nios2\boot_loader_sources\boot_loader_epcs_bits_<device_family>.S Now some things to consider about remote update ... 1 - What happens if you corrupt the application code while you're downloading new code? Usually you provide a safe boot app and a user boot app. You never touch the safe boot app so that you can default back to it if remotely updating your user application fails. Jake
