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

Get compiled linux running

Former Member

Hey there,

I'm now trying for one week to get get a linux running which i compiled myself. Basically I followed the Embedded Linux Hands-on Tutorial provided by Digilent.

I'm using the latest Vivado and SDK versions.

My last try now was to just create a basic design with only the zynq in it, synthesize it and generate a bitstream. After exporting it to the SDK I created the FSBL with the default settings.

After creating a BOOT.BIN and copying all necessary files to the SD-Card, at least I should see the blue LED turning on some time, or am I wrong?
Because that's not happening.


Apart from that I compiled my own uBoot and kernel 3.6 from github.com/digilent. I didn't use the arm-xilinx-linux-gnueabi, instead I used the free arm-linux-gnueabi tools.
With an FSBL I got somewhere I was able to boot the linux to a point where it said: "mousedev: PS/2 mouse device common for all mice", then it hang there. Could this be a problem with the compiler? If yes, I already downloaded different ISE versions and SDKs but I didn't find the thin in there. Is there a painless way to install them on linux?

This makes me think, that the first problem is the FSBL (and then something further down the road). Any Ideas?

Thank you in advance for your help. I'm really starting to loose it here ...

EDIT: Now I tried to use the fsbl, bitfile and uBoot provided by Digilent and create a BOOT.BIN. But again, no blue LED. Why isn't this working? The provided BOOT.BIN works, but if I compile my own one it breaks?

Parents
  • 0

    For the love of god, it's finally running. Linux on one core and baremetal one the other.
    For future googlers and people struggling:
    1. Use the FSBL_DEBUG and FSBL_DEBUG_INFO flags for your FSBL to get some more information if it's not working
    2. Connect the damn sd0 ping in the blockdesign of vivado
    3. The latest u-boot and linux (tag: xilinx-v14.7) from the xilinx git repository works. Be careful to make the zedboard target of course
    4. Don't forget to set the number of CPUs to 1 in the kernel boot line

Reply
  • 0

    For the love of god, it's finally running. Linux on one core and baremetal one the other.
    For future googlers and people struggling:
    1. Use the FSBL_DEBUG and FSBL_DEBUG_INFO flags for your FSBL to get some more information if it's not working
    2. Connect the damn sd0 ping in the blockdesign of vivado
    3. The latest u-boot and linux (tag: xilinx-v14.7) from the xilinx git repository works. Be careful to make the zedboard target of course
    4. Don't forget to set the number of CPUs to 1 in the kernel boot line

Children
No Data