[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [microblaze-uclinux] Booting design from flash then FS-Boot, U-Boot, Kernel
Hi Ulrich,
Thanks for giving input. But I have one problem. I build hardware
project for Spartum 3A on window machine with os option as petalinux. After
building hardware I pick Kconfig file from there and copy manually on
Spartum3E500_REVC platform code.
After all this I build my kernel as steps mention in you document.
Is these step ok ?
Thanks
Deepak
-----Original Message-----
From: owner-microblaze-uclinux@xxxxxxxxxxxxxx
[mailto:owner-microblaze-uclinux@xxxxxxxxxxxxxx] On Behalf Of Ulrich
Hoffmann
Sent: Tuesday, February 03, 2009 4:01 PM
To: microblaze-uclinux@xxxxxxxxxxxxxx
Subject: Re: [microblaze-uclinux] Booting design from flash then FS-Boot,
U-Boot, Kernel
Hi Deepak,
good to know, that you try to do the same thing :-)
I currently do not work with XMD, but given my problem I probably
will :-)
I currently use the petalinux-v0.30-rc1 - file from the web page.
I very closely followed the description in
http://developer.petalogix.com/wiki/BoardGuides/Custom/Tutorial
I ran petalinux-new-platform - Script, to create a new hardware platform
directory for the Xilinx Spartan 3A Starter Kit Rev D board that I have
and for a Linux 2.6 kernel.
Then I also built a specific Microblaze design for the Spartan 3A
Start Kit with UARTLite, parallel Flash support and EthernetLite
using the BSB (Base System Builder) and I included FS-Boot
in BRAM in this design. So, when I download the bitstream of
this design it runs FS-Boot and shows its messages on the serial
console. As the Spartan 3A starter kit has a smaller FPGA, I hat to
reduce the cache size from 8K as proposed in the tutorial to 2K
(for both ICache and DCache).
To build Petalinux (and U-Boot) I first ran the script
peta-linux-autoconfig and then went through all the options that
are mentioned in the tutorial. The 2.6 Kernel options are
at different places than described in the tutorial, so you have to
do some searching....
"make all" then creates a kernel/filesystem-image and u-boot.
To boot Petalinux, I download the bitstream, this starts FS-Boot
as it is part of the design.
At the SREC-prompt I upload the file u-boot.srec.
This then boots into u-boot.
Now I flashed u-boot and the image similar to the procedure
described in the tutorial:
I loaded the U-Boot configuration:
U-Boot> loadb $(clobstart)
I upload ub.config.img using Kermit protocol.
U-Boot> autoscr $(clobstart)
Then the U-Boot-Image:
U-Boot> loadb $(clobstart)
upload uboot-s.bin using Kermit protocol
U-Boot> protect off $(bootstart) +$(bootsize)
U-Boot> erase $(bootstart) +$(bootsize)
U-Boot> cp.b $(clobstart) $(bootstart) $(bootsize)
U-Boot> protect on $(bootstart) +$(bootsize)
At this time I can download the bitstream and the system
boots into u-boot.
I flash the kernel image. I also used serial upload as I
did not want to mess around with ethernet and tftp at that time.
Be warned however that the kernel upload via serial line takes
about 25 minutes.
U-Boot> loadb $(clobstart)
upload image.ub using Kermit protocol (wait 25 min)
U-Boot> protect off $(kernstart) +$(kernsize)
U-Boot> erase $(kernstart) +$(kernsize)
U-Boot> cp.b $(clobstart) $(kernstart) $(kernsize)
U-Boot> protect on $(kernstart) +$(kernsize)
At this time I can download the bitstream and the system
boots into u-boot and then boots the Petalinux kernel
as described in my previous post.
However putting the design in SPI flash, let the FPGA
configure from there and boot linux does not work for me
in the moment. I guess I have to learn a bit of XMD to do
the low level debugging...
Regards,
Ulrich
BTW: Do you have the Base System Builder running under Linux?
I have CentOS here but BSB refuses to start;
ERROR:MDT - Unable to run BsbWiz!
So - currently I use BSB under Windows and copy files :-(
Am 03.02.2009 um 07:50 schrieb Deepak Yadav:
> Hi Ulrich,
> I am also try to port Petalinux on Spartan 3A Starter Kit .But
> unable to find any linux prints on terminal except FS_Boot prints.
> Can you
> tell me the steps which you follows.
>
> I am following these steps
>
> 1.Take spartum 3E-500 REVC linux kernel code.
>
> 2.Generate Kconfig for Spartum 3A board.
>
> 3.Copy this Kconfig in spartum 3E-500 REVC code.
>
> 4.Build Kernel.
>
> 5.Boot FS boot from RAM.
>
> 6.Copy kernel image(image.bin) in ram start address by using dow
> command.
>
> 7.Con at start address.
>
> Thanks
> Deepak
>
> -----Original Message-----
> From: owner-microblaze-uclinux@xxxxxxxxxxxxxx
> [mailto:owner-microblaze-uclinux@xxxxxxxxxxxxxx] On Behalf Of Ulrich
> Hoffmann
> Sent: Monday, February 02, 2009 9:17 PM
> To: microblaze-uclinux@xxxxxxxxxxxxxx
> Subject: [microblaze-uclinux] Booting design from flash then FS-Boot,
> U-Boot, Kernel
>
> Hi,
> I'm about to port Petalinux to the Spartan 3A Starter Kit (Rev D)
> Board.
>
> I followed the Petalinux documentation closely and created a
> Microblaze design with
> fs-boot and also flashed u-boot and the kernel image fine. I can now
> boot
> Petalinux when I freshly download the Microblaze design via the JTAG
> interface (USB-Cable).
>
> What I would like to have is a Microblaze configuration that loads
> into the
> FPGA from SPI flash at reset time.
>
> I used IMPACT to put the bitstream in the ATMEL AT45DB161D serial
> flash. On reset it indeeds downloads Microblaze and fs-boot so that I
> can
> see its boot message:
>
> =================================================
> FS-BOOT First Stage Bootloader (c) 2006 PetaLogix
> =================================================
> FS-BOOT: System initialisation completed.
> FS-BOOT: Booting from FLASH. Press 's' for image download.
> FS-BOOT: Booting image...
>
> then nothing happens.
>
> If I interrupt the boot process and press 's'. I can download
> the u-boot.srec-file, but this hangs as soon as u-boot is trying to
> display the flash statistics and then resets strangely into fs-boot
> again:
>
> =================================================
> FS-BOOT First Stage Bootloader (c) 2006 PetaLogix
> =================================================
> FS-BOOT: System initialisation completed.
> FS-BOOT: Booting from FLASH. Press 's' for image download.
> FS-BOOT: Waiting for SREC image....
> FS-BOOT: Image download successful.
> FS-BOOT: Warning image location differ from default boot location.
> Image will no
> t boot automatically after POR.
> FS-BOOT: Press 'n' to boot old image.
> FS-BOOT: Use new image.
> FS-BOOT: Booting image...
> SDRAM :
> Enabling caches :
> Icache:OK
> Dcache:OK
> U-Boot Start:0x8ffa0000
> Malloc Start:0x8ff60000
> Board Info Start:0x8ff5ffd0
> =================================================
> FS-BOOT First Stage Bootloader (c) 2006 PetaLogix
> =================================================
> FS-BOOT: System initialisation completed.
> FS-BOOT: No existing ima
>
>
> Maybe the parallel flash is not available when loading the
> configuration via SPI flash?
>
> Any hints are very welcome.
>
> Regards,
> Ulrich
>
> Here is a successful boot, when downloading the bitstream via JTAG:
>
> =================================================
> FS-BOOT First Stage Bootloader (c) 2006 PetaLogix
> =================================================
> FS-BOOT: System initialisation completed.
> FS-BOOT: Booting from FLASH. Press 's' for image download.
> FS-BOOT: Booting image...
> SDRAM :
> Enabling caches :
> Icache:OK
> Dcache:OK
> U-Boot Start:0x8ffa0000
> Malloc Start:0x8ff60000
> Board Info Start:0x8ff5ffd0
> Boot Parameters Start:0x8ff4ffd0
> FLASH: 4 MB
> ETHERNET: MAC:00:0a:35:00:22:01
>
> Hit any key to stop autoboot: 0
> ## Booting image at 884a0000 ...
> Image Name: PetaLinux Kernel 2.6
> Image Type: Microblaze Linux Kernel Image (uncompressed)
> Data Size: 2687018 Bytes = 2.6 MB
> Load Address: 8c000000
> Entry Point: 8c000000
> Verifying Checksum ... OK
> OK
> Linux version 2.6.20-uc0 (root@xxxxxxxxxxxxxxxxxxxxx) (gcc version
> 3.4.1 ( PetaL
> inux 0.20 Build -rc1 050607 )) #0 Sun Feb 1 23:21:12 CET 2009
> setup_cpuinfo: initialising
> setup_cpuinfo: No PVR support in CPU. Using static compile-time info
> set_cpuinfo_static: Using static CPU info.
> setup_memory: max_mapnr: 0x8ffff
> setup_memory: min_low_pfn: 0x8c000
> setup_memory: max_low_pfn: 0xMounting proc:
> Mounting var:
> Populating /var:
> Running local start scripts.
> Mounting /etc/config:
> Populating /etc/config:
> flatfsd: Nonexistent or bad flatfs (-48), creating new one...
> flatfsd: Failed to write flatfs (-48): No such device
> flatfsd: Created 5 configuration files (185 bytes)
> Mounting sysfs:
> Setting hostname:
> Setting up interface lo:
> Setting up interface eth0:
> Starting thttpd:
>
> spartan login:
>
>
> ___________________________
> 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/
>
> ___________________________
> 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/
>
___________________________
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/
___________________________
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/