[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [microblaze-uclinux] Kernel boot problem ( Michael Simek Wiki )
first of all just Michal - no worries about and please do not apology.
some my comments below.
Mohammad Sadegh Sadri wrote:
> Hi all,
> according to this reference from Michael : "Mainline linux kernel for
> Microblaze" available at http://www.monstr.eu/wiki/doku.php?id=fdt:fdt i
> have built the linux kernel.
I'll have to update my page.
> I have downloaded the latest version of code for all of the packages
> from Michael's web based git repository.
I think you are not able to use latest our master branch because you have older toolchain
If you want to use our master branch at
please do not use microblaze: futex support patch - you can revert it or use older version.
> I have done all of the specified steps in the Wiki carefully.
> Unfortunately the kernel stops working completely at initial step.
> Base system is built using EDK 11.2, SP2
> Microblaze version is 7.20.b :
> - barrel shifter : active
> - floating point unit : disabled
> - Integer multiplier : 32 bits
> - integer devider : active
> - machine status register instructions : acitve
> - Pattern comperator : active
> - cache : 8kbytes data and instruction , cache line length : 4
> - MMU : active , mode 3 (VIRTUAL)
> - processor version registers (PVR) : FULL
> microblaze is running at 50MHz and DRAM controller at 100MHz, and
> hardware is working properly.
> Boot process : fsboot ----> U-BOOT ----> Linux kernel
> Linux version : latest available version from Michael Simek's gir
> u-boot required config files and device tree generated with latest
> available BSPs by Michael. using DTC I make system.dtb according to
> Michaels documents.
> Linux kernel configuration: ( note : when i download the kernel source
> code from gir repository i see that there is no default config )
There are two defconfigs in arch/microblaze/configs/
> I do the steps specified in the Wiki exactly : just i mention the
> differences with what Michael says
> - CONFIG_KERNEL_BASE_ADDR = 0x44800000 ( because my DDR SDRAM
> Controller base address is 0x44000000 )
> - CONFIG_XILINX_MICROBLAZE_FAMILY = "spartan3" ( instead of "virtex5"
> which is the default )
> - CONFIG_XILINX_MICROBLAZE_USE_HW_MUL=1 ( instead of 2 because i use a
> 32bits multiplier )
> - CONFIG_XILINX_MICROBLAZE_USE_FPU = 0 ( because i dont have any FPU )
> - CONFIG_XILINX_MICROBLAZE_HW_VER = "7.20.b" ( my microblaze version )
> - I also enable MMU in kernel configuration
> - i do not enter any commands to be passed to kernel
> - I enable the xilinx uart lite driver to be added to the kernel
> - I say that the console should come up on uart lite ( ttyUL0 )
make menuconfig -> Platform option -> setup your parameters
(It should work any kernel base addr but I am using/testing ddr base addr)
copy your platform.dts file to arch/microblaze/boot/dts/
touch rootfs.cpio -> just fake cpio image
and run make simpleImage.platform
then you find in arch/microblaze/boot folder some files
ad 1. load bitstream to your board , run this xmd.ini
connect mb mdm
You should be able to see output on console -> then you can fight with rootfs.
ad 2. load that ub image via u-boot and run
tftp XXXXXXXXX simpleImage.platform.ub
then you should be able to see the same output as for previous image
If not- read log buffer to see what wrong is.
> Making the u-boot image for kernel:
> I use exactly the same command as what michael has specified in his Wiki.
> fs-boot brings up u-boot at memory location 0x47fc0000
> using u-boot i do the following:
> - tftp 0x44780000 system.dtb
> - tftp 0x44800000 image.ub
> - bootm 0x44800000 - 0x44780000
> what happens is as follows:
> U-Boot-mONStR> bootm 0x44800000 - 0x447800000
> ## Booting kernel from Legacy Image at 44800000 ...
> Image Name: ICTI LInux kernel
> Image Type: MicroBlaze Linux Kernel Image (uncompressed)
> Data Size: 1593860 Bytes = 1.5 MB
> Load Address: 44800000
> Entry Point: 44800000
> Verifying Checksum ... OK
> XIP Kernel Image ... OK
From log I see that you don't have support for booting multiple images.
That's why your kernel not work.
> and the system stops working completely!!!
> would you please provide me with some guesses through your previous
> experiments that what can be the cause of this phenomenan?
> Less clicking: Hotmail access on the new MSN homepage.
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663
microblaze-uclinux mailing list
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/