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

    I'm having a similar error. Have you found a solution yet? I'll keep looking.

  • 0 in reply to Former Member

    Although the kernel is not functional yet, I did manage to get past this point by entering a different compatible string in the devicetree root node.

    At the point of my previous post the devicetree appears to have been ignored or something (not found any reason for this) but according to documentation found in the linux-xlnx tree the actual ID (r1) does not matter, it loads the machine information from the device tree.
    So this message seems to mean that the devicetree is not found/loaded. I could be mistaken but it seems this way.

    Instead of the xlnx,zynq-zed you can also find in the xilinx-linux devicetree, I entered xlnx,zynq-zc702 which it accepted as a compatible machine.
    This is pretty odd because I cloned a BSP for this project and the xlnx,zynq-zed is listed as a compatible machine in the kernel...

    Nontheless, I think it is worth the try for you as well, just to see if it responds. just adjust the devicetree root node compatible strign to something else the kernel should be compatible with.

    Btw, I use a uImage and boot my kernel with bootm <kernel address> - <devicetree address>
    The seccond argument is the ramdisk which is the seccond partition of the SD card. it is listed in the devicetree so it should work this way according to windriver documentation.

Reply
  • 0 in reply to Former Member

    Although the kernel is not functional yet, I did manage to get past this point by entering a different compatible string in the devicetree root node.

    At the point of my previous post the devicetree appears to have been ignored or something (not found any reason for this) but according to documentation found in the linux-xlnx tree the actual ID (r1) does not matter, it loads the machine information from the device tree.
    So this message seems to mean that the devicetree is not found/loaded. I could be mistaken but it seems this way.

    Instead of the xlnx,zynq-zed you can also find in the xilinx-linux devicetree, I entered xlnx,zynq-zc702 which it accepted as a compatible machine.
    This is pretty odd because I cloned a BSP for this project and the xlnx,zynq-zed is listed as a compatible machine in the kernel...

    Nontheless, I think it is worth the try for you as well, just to see if it responds. just adjust the devicetree root node compatible strign to something else the kernel should be compatible with.

    Btw, I use a uImage and boot my kernel with bootm <kernel address> - <devicetree address>
    The seccond argument is the ramdisk which is the seccond partition of the SD card. it is listed in the devicetree so it should work this way according to windriver documentation.

Children
No Data