Forum Discussion
New ContributorMAX 10 RSU
Hi SDevaux,
Thank you for your response.
We solved our problem, which in short was: We had two CFM images and we wanted that each image to work with it's own/different software image (in the UFM). We solved this by having the NIOS processors, from the two CFM images, boot at different address (different boot vectors). The boot vector for the second CFM image should point to an UFM address that is > address space necessary for the first software image. Then we took the two ufm.rpd files, trim them, and stitched them together: 1st software image: 0x0000 _ 0xNNNN and 2nd software image: (0xNNNN + 1) _ end of UFM.
New Contributorhi,
you can update your UFM with the same process than CFMx.
But you can't use UFM and update it at the same time, you need to run the update software/firmware on external memory or onchip memory, especially if you want a backup image if update fails.
SCroi1Hi SDevaux,
Thank you for your response.
We solved our problem, which in short was: We had two CFM images and we wanted that each image to work with it's own/different software image (in the UFM). We solved this by having the NIOS processors, from the two CFM images, boot at different address (different boot vectors). The boot vector for the second CFM image should point to an UFM address that is > address space necessary for the first software image. Then we took the two ufm.rpd files, trim them, and stitched them together: 1st software image: 0x0000 _ 0xNNNN and 2nd software image: (0xNNNN + 1) _ end of UFM.
