Honored Contributor
Honored ContributorHere is the section you are referring to:
--- Quote Start --- Booting From Flash Memory and Running From Volatile Memory If your application image is stored in flash memory, but executes from volatile memory with assistance from a boot loader program, prepare for BSP configuration by following these steps: 1. Nios II processor reset address—Ensure that the Nios II processor's reset address is an address in flash memory. Configure this option using SOPC Builder. 2. Text section linker setting—Ensure that the .text section maps to a volatile region of system memory, and not to the flash memory. 3. Other sections linker setting—Ensure that all of the other sections, with the possible exception of the .rodata section, are mapped to volatile memory regions. The .rodata section can map to a flash-memory region. 4. HAL C run-time configuration settings—Configure the BSP settings as shown in Table 2-3 Table 2–3. BSP Settings to Boot from Flash Memory and Run from Volatile Memory BSP Setting Name Value hal.linker.allow_code_at_reset 0 hal.linker.enable_alt_load 0 hal.linker.enable_alt_load_copy_rwdata 0 hal.linker.enable_alt_load_copy_exceptions 0 hal.linker.enable_alt_load_copy_rodata 0 --- Quote End --- So if you set the linker .text to viotile memory, then how does it store the program code? Do you need to store a copy of it in flash and then dump this into viotile memory at boot-up?
