Success! Subscription added.
Success! Subscription removed.
Sorry, you must verify to complete this action. Please click the verification link in your email. You may re-send via your profile.
This page has been created to assist users that prefer to use logic for controlling the Remote System Update (RSU) feature using Cyclone III and Cyclone IV FPGAs. The example was verified using the BeMicro SDK evaluation board.
The example designs are based upon the following wiki page:
https://forums.intel.com/s/ics-frm-article/a3g0P0000005RSTQA2/remote-update-for-cyclone-v
However, the ALTREMOTE_UPDATE command structure for Cyclone III and Cyclone IV is significantly different than Cyclone V, so the system console tcl scripts were written to match Cyclone III and Cyclone IV. The command structure for addressing the ALTREMOTE_UPDATE function for Cyclone III and Cyclone IV can be found in the System Console tcl scripts within the FI project directory. The factory image (FI) and application image (AI) projects can be found in the download section below.
The example RSU test system consists of:
File:CycloneIV RSU BeMicroSDK System Console.zip
Note: it is also necessary to download the Qsys IP core below for the example design to operate properly. The Qsys IP core can then be applied to your specific application.
To use this core, download from the link below, unzip, and place into your project ip directory. Open Qsys. You may need to add the new ip/rsu_cyclone4 directory in the Qsys IP search path. This core MUST run at a a clock lower or equal to 40 MHz.
This core can also be used for Cyclone III.
Special thanks to Cal and Shawn.
Community support is provided Monday to Friday. Other contact methods are available here.
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
For more complete information about compiler optimizations, see our Optimization Notice.