Hi Nathan, Nathan Hillery wrote:
I lied a little;-) My board has flash, but only enough to program the FPGA. I have fs-boot working from bram (it is selected to initialize block ram) and it works - at least it starts and accepts an s-rec file. However, it doesn't seem to know about the flash in system ace, so it doesn't write the downloaded file correctly. To get around that, I was trying to get u-boot to build with system ace support, but haven't been able to get it to compile successfully. I have found a potential solution in "Software Platform Settings" -> "OS and Libraries" configuration for petalinux. This allows you to select the "Name of Flash Memory Controller" for petalinux, but won't recognize any variation on the name in my design. The core is xps_sysace and my instance is SysACE_CompactFlash.
This is a common misconception. SystemACE presents itself to the MicroBlaze as a block-based, disk-like device, not a typical parallel flash memory interface as is expected by the PetaLinux tools and u-boot default configs etc.
As Michal says, you have a bit of work to do as this is not a default configuration.
To be honest the easiest way to do this would be to just add the u-boot elf file as a payload after the configuration bitstream on the compact flash device, this would just boot u-boot directly after configuration the FPGA.
But, you'll then have to hack on u-boot to get it to interact with the systemACE (as a disk, not flash memory). Then, you should be able to pull a kernel from SystemACE for booting. I think the upstream u-boot sources at denx.de have a SystemACE driver you could backport.
Regards, John ___________________________ microblaze-uclinux mailing list microblaze-uclinux@xxxxxxxxxxxxxx Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/