Actions
Forum Thread Details
  • State Not Answered
  • Replies 2 replies
  • Subscribers 173 subscribers
  • Views 127 views
  • Users 0 members are here
Related

Building Open Source Linux from the linux-xlnx, hangs when booting.

Former Member

Hello.

After extensive testing and google/(xilinx forum)/(microzed) searching, I decided to post this question here.


I'm trying to cross-compile the linux kernel (Open Source Linux from Xilinx) in an OpenSUSE computer and boot it in a MicroZed board. I downloaded the Vivado Web Pack and the linux kernel (what I think is "Open Source Linux") from the xilinx's linux-xlnx git repository. I build the kernel, and it generates the image. For this, I had to generate build the mkimage utility found in the "u-boot-xlnx" file that also comes in the repository, as outlined in the Xilinx's guide.


For the cross-compilation process, I use the cross-compilation toolchain that are available after installing Vivado and sourcing the settings64.sh file. I copy the uImage to an SD card. In this card, there are also the other booting files and images from the MicroZed SD image. That is, I use the same boot.bin, the ramdisk, etc., and I only replace the uImage that I just cross-compiled.


The kernel is able to boot, but it hangs, in the line that says:


"Starting Kernel ...."



The checksums and everything prior to that is ok.



It simply hangs there, and no further action is performed. One reason may be that it is not decompressing the uImage properly because I might be using the wrong mkimage utility.



Any thoughts on what could it be and how to procceed?



Good day.

  • 0

    I haven't done anything with SuSe, but I know there are differences in the way the development environment is set up between CentOS and Ubuntu.  Although my first thought is that there may be something missing in your SuSe setup, I would expect to see some kind of error in the compilation process.  Assuming the compilation is clean, here are some things I can think of to try to track this down:

    1. SuSe development environment issue.  Have you tried replicating the kernel build using a CentOS or Ubuntu development environment?  Just as a sanity check to verify all the procedures you are using are correct?  See the Ubuntu tutorial on Zedboard.org for information on creating a development environment based on either distribution.

    2. Mismatch between u-boot in boot.bin and the kernel version in the uImage.  This seems unlikely, but the boot is hanging at a very early stage in the kernel boot.  You may want to try rebuilding the corresponding version of u-boot for the tag you are using for the kernel, then substitute that in the boot.bin file to see if there is any change.

    2. Configuration error in the Linux kernel.  If you are unable to complete 1 above to verify your process, then this may be relevant. 

    3. Error in the compiled device tree.  Unlikely to be the problem at this stage of the boot, but anything is possible. 

    I know there are quite a few developers out there, particularly in Europe, using SuSe, so if anyone has some actual similar experience, please feel free to jump in here.

    Let me know the results if you try any of the suggestions above.  We may need additional information to get to the bottom of this.

    Ron

  • 0

    Hello.

    I will go to through your proposals in the same number you enumerated them.

    1. I have tried building the linux kernel that I downloaded from the Xilinx's git, and compile it inside a Vbox virtual machine running Ubuntu. I download the image, and put it on the SD Card, together with the image files that come with the MicroZed's SD image. It hangs as previously described.

    2. I try to build the boot.bin image. The compilation succeded with the source code downloaded from the Xilinx's git. The behavior is even worse, because u-boot does not even starts up when turning the system on.

    2. (you listed "2" twice) I have followed the tutorial as outlined by Xilinx's build process. I set up the environment variables, and pass the config and make variables when doing the compiltion (ARCH=arm zynq_xxx_defconfig).

    3. This could an issue. I haven't tried to generate a device tree yet. I am in the process of trying to do this.

    It seems that there are many issues related to SUSE, starting from Xilinx's tools themselves.

    In any case, the linux kernel build should work as specified in the Xilinx's tutorial. In principle, modifications to the boot.bin and the device tree should not be necessary when building the xilinx-linux kernel from the Xilinx's git. However, it seems that it doesn't. I wonder if this assumption is correct all.

    If the assumption is not right, I am starting to think that the inclusion of the .bsp files during the build process is necessary.

    Any further comments will be appreciated.

    Good day.