Honored Contributor
Honored Contributor
> so just to clear on this, the .elf data comes immediately after the .sof data.
...snip...
regards,
--scott
<div align='right'><{post_snapback}> (index.php?act=findpost&pid=10806)
--- quote end ---
--- Quote End --- This is all well and fine, but what if you want to control where the ELF is loaded? Let's say you want to reserve some portion of the EPCS device for HW, and then have the SW start at the next sector past that - certainly, so that the beginning of the ELF (software) isn't in the same sector as the HW (configuration). How do you... a ) Control the offset in the EPCS (or any flash) where the software is placed. This is different from where it's going to be located once it's loaded into RAM - we don't care about that - we need to specify PUT THE SOFTWARE IN THE EPCS AT OFFSET BLAH. b ) Tell the bootloader this offset. c ) Be able to tell where in the EPCS the code is loaded from - from the application itself. If this is not possible, we could use the hard coded value from step "a", but it would be really nice to figure that out for step "a" and then have everything else just configure automagically. This stuff is "cake factor infinite (facile)" for a traditional microcontroller based design, but seems quite obtuse in the Nios environment. I've looked for stuff on EPCS, flash in general, etc., and I completely grok how to write stuff to specific addresses in flash, how to get information about a flash device, etc., but finding ANYTHING that documents how to get the build process to put stuff at specific addresses in the EPCS. Also, our rep tells us that for the part we have, there is some finite limit as to how big the hardware configuration can be, and that's not the same thing as the number of LEs, etc. This could be helpful in determining where we want to start putting code (like the sector after that). How do we find that out? Thanks Greg
