Forum Discussion
Altera_Forum
Honored Contributor
14 years agoRemote update controller issue
Hi everyone,
I'm using the remote update controller (cyclone III) on my Cyclone IV GX dev board with a EPCS128 flash memory. I wish to have two firmwares in my EPCS (factory and application). Actually, I placed the firmware like this in the EPCS: 0x000000 Factory image (hw0 + sw0) 0x440000 Application image (hw1 + sw1) (I'm not using the flash programmer to load the image in flash memory) The nios II boots correctly on the factory image when I start the board. But when I try to reconfig the FPGA with the application image using the remote update controller, the Factory image is loaded... I write 0x110000 to the remote update controller, then start the reconfig for loading the application image. Is this address correct? I think my problem comes when I'm creating the application image. Here is my script to create the .flash: --- Quote Start --- java -jar C:\altera\11.0\nios2eds\bin\sof2flash.jar --epcs --input="..\..\2Dcam.sof" --output="2Dcam_sof.flash" --verbose java -jar C:\altera\11.0\nios2eds\bin\elf2flash.jar --epcs --after="2Dcam_sof.flash" --input="..\2DCam\2DCam.elf" --output="2DCam_elf.flash" --offset 0 rem merge the two files copy /b /y 2Dcam_sof.flash+2DCam_elf.flash 2DCam.flash --- Quote End --- I create factory and application image (.flash) with this script. And load the factory image at address 0x000000 and the application at address 0x440000 in EPCS. Do I have to make something different for the application image, because her address is not 0x000000? Has anyone the same problem? Best regards37 Replies
- Altera_Forum
Honored Contributor
Yes, the bootloader of QSYS works fine.
If I place my firmware at address 0, I can boot without problem. But if I load my firmware at address 0x600000 (with the custom bootloader). When I try to reboot on, only the hardware is loading. - Altera_Forum
Honored Contributor
Thank you st_f for the help. I too am seeing the same issue.
Greg - Altera_Forum
Honored Contributor
Thank you st_f for the help. I too am seeing the same issue and your post has really helped me.
I am having an issue though. When I try to generate the hex file with the command line you've given above, I get all 0's in the data field of the hex file. If you have any idea what's wrong please let me know. Thanks PS: Please disregard, I didn't see the whole thread where others have the 0's problem. Answer should be in here somewhere. thanks. - Altera_Forum
Honored Contributor
Hello,
I've tried to implement the new bootloader on a Cyclone IV and I found a bug in "boot_loader_epcs_bits_sii_siii_ciii.S" writed by hallodu. To have a full compatibility with all address you must write this code before "fp_short_circuit:" label: movhi r24, %hi(IMAGE_START) add r_flash_ptr, r_flash_ptr, r24 //orhi r_flash_ptr, r_flash_ptr, %hi(IMAGE_START) best regards - Altera_Forum
Honored Contributor
Thanks to all..i got resolved Bootloader issue @CycloneIII..
- Altera_Forum
Honored Contributor
--- Quote Start --- Hi, The source code for the default bootloader is included in the Quartus distribution (C:\altera\11.1\ip\altera\nios2_ip\altera_nios2\boot_loader_sources) and must be modified for the application image. First you change the assembly file boot_loader_epcs_bits_sii_siii_ciii.S so that the bootloader for the application image jumps to the Nios code for the application image (which is just after the FPGA configuration for EPCS). Here is one way to change to this code: 1) Add a define to the offset to the application image: # define IMAGE_START 0x00440000 2) Replace all occurencs of the following code : (several places in the code) movi r_flash_ptr, xx with: movhi r_flash_ptr, %hi(IMAGE_START) ori r_flash_ptr, r_flash_ptr, xx 3) Add the following statement before fp_short_circuit: orhi r_flash_ptr, r_flash_ptr, %hi(IMAGE_START) This should work if the 16 lower bits of IMAGE_START are 0. Then run make (Last time I tried it I only got it working with the gcc3 quartus 10.0, not with gcc4). Then go to the obj directory and run: elf2hex --input="boot_loader_epcs_sii_siii_ciii.elf" --output="epcs_controller_boot_rom.hex" --base=0 --width=32 --end=1023 --record=4 --lower You must then replace the boot rom file in your design with this file. In Quartus 11.1 the file name may be changed to epcs_flash_controller_boot_rom_synth.hex. Note that you do not have to recompile the whole design, you just select 'Update Memory Iniialization File' in Quartus and run the asssembler after changing the bootloader. I have tested this for Stratix II,III,IV and Cyclone IV. --- Quote End --- Will this method works for EPCQ 256?? I'm trying to implement dual boot on ArriaV, with Factory Image @0x00 and Application Image @0x800000. I have modified the default bootloader boot_"loader_epcq256_cv" in the same manner as above. But not working !!! Thanks in advance for your suggestions and reply. - Altera_Forum
Honored Contributor
If you are using a recent quartos, try using the newer boot code that converts avalon reads directly into epcq accesses.
You then point the nios reset vector directly at the flash address (which takes up 32MB of address space foe an EPCQ256). Note that I've not used that logic, we load the nios over pcie.