|
Hello, I am new at this petalinux development, coming from the FPGA
side of things, and I seemed to be confused. I managed to get the linux 2.4 kernel going by copying the
auto-config.in, file (from a Windows EDK project with petalinux OS installed),
to petalinux in VMware in: linux-2.4.x/arch/microblaze/platform/microblaze-auto
(after doing dos2unix auto-config.in auto-config.in) and running the resulting
image.bin in XMD from the Windows EDK. Now I want to run u-boot and I couldn’t compile a
successful u-boot image while just selecting the u-boot build option in the
xconfig settings. So I ended up re-reading the “Petalinux Platform From
Scratch” and creating a petalinux-new-platform
and copied the auto-config.in to the respective linux-2.4.x/arch/microblaze/platform
directory. Then I was
able to successfully build u-boot and the kernel. This new kernel doesn’t
work (doesn’t echo back to the console at all). The
u-boot.srec generated is sent via TeraTerm in Windows via “send
file” (because the Kermit send didn’t respond) which just sends the
raw stream but there is no complaint when FS-Boot is in non-debug mode, only in
debug mode where it said the file was not SREC. In any case after investigating
the FS-Boot seems to be booting from an address that has no hardware devices
mapped. Sorry for the long-winded story, but I believe that I have
some configuration step missing, any guidance is greatly appreciated. Thanks, -A Bose |