Actions
Forum Thread Details
  • State Not Answered
  • Replies 7 replies
  • Subscribers 338 subscribers
  • Views 1282 views
  • Users 0 members are here
Related

U-boot machine ID

Former Member

Currently I am testing the zedboard's zynq chip for its potential use in future products.
One of its requirements is to run Windriver Linux, this is giving quite the problems.


After creating a new linux kernel, devicetree and rootfs, I use the xilinx U-Boot to launch this new kernel.


I can launch the original linuz that came with the board using this U-Boot. With my own kernel it gets stuck after 'booting the kernel'.


Now this isnt the most uncommon error and using low-level debugging I managed to extract the following onformation:
<6>Booting Linux on physical CPU 0
<6>Initializing cgroup subsys cpuset
<6>Initializing cgroup subsys cpu
<5>Linux version 3.4.34-rt40-WR5.0.1.0_preempt-rt (gcc version 4.6.3 (Wind River Linux Sourcery CodeBench 4.6a-99) ) #1 SMP PREEMPT RT Tue May 7 10:05:01 CEST 2013
<4>CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
<4>CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
<4>
<4>Error: unrecognized/unsupported machine ID (r1 = 0x1fb56824).
<4>
<4>Available machine support:
<4>
<4>ID (hex)tNAME
<4>fffffffftXilinx Zynq Platform
<4>
<4>Please check your kernel config and/or bootloader.



after a long struggle to find out the problem, it appears that U-Boot is not giving a correct machine ID (the r1) to the kernel.


So the zedlinux does not require this check? is that some sort of config that I can set in my own kernel as well?
I checked the machine ID that the U-Boot creates/finds using dbinfo.
This machine id is identical to the r1 of the error message.


In the xilinx U-boot repository the correct machine ID can be found in mach-types.h but this does not appear to be used by the zynq config. Is this perhaps the problem? Or can I create a new U-Boot that does contain the correct ID?

Parents
  • 0

    Maybe this may not work for you but i'll post my solution.

    I use a uImage instead of a zImage that allows me to use the bootm command.
    (if you use Digilent linux or Xilinux you need to have the 'fixed_devtree' configuration in .config disabled. if this option is set, you start with 'go')

    you can use mkimage to convert the zImage to a uImage
    if you add "UIMAGE_LOADADDR=0x8000 uImage" to the make command.

    Besides making a uImage you need to load the uImage one a different address than the zImage because you will get more error if you do.

    instead of loading it at 0x8000, you load it 64 bytes before it at 0x79c0. so im my case (i use a NFS):

    tftp 0x79c0 uImage
    tftp 0x1000000 devicetree.dtb
    bootm 0x79c0 - 0x1000000

    this option works for me, feel free to try it yourself.

Reply
  • 0

    Maybe this may not work for you but i'll post my solution.

    I use a uImage instead of a zImage that allows me to use the bootm command.
    (if you use Digilent linux or Xilinux you need to have the 'fixed_devtree' configuration in .config disabled. if this option is set, you start with 'go')

    you can use mkimage to convert the zImage to a uImage
    if you add "UIMAGE_LOADADDR=0x8000 uImage" to the make command.

    Besides making a uImage you need to load the uImage one a different address than the zImage because you will get more error if you do.

    instead of loading it at 0x8000, you load it 64 bytes before it at 0x79c0. so im my case (i use a NFS):

    tftp 0x79c0 uImage
    tftp 0x1000000 devicetree.dtb
    bootm 0x79c0 - 0x1000000

    this option works for me, feel free to try it yourself.

Children
No Data