Actions
Forum Thread Details
  • State Not Answered
  • Replies 8 replies
  • Subscribers 361 subscribers
  • Views 702 views
  • Users 0 members are here
Related

Zedboard booting up issue

Former Member

Hi,

Working with xillinux linux distribution to boot the zedboard I have a problem.

1.The board boots fine works well but hangs up frequently.

2. On re-boot the boot loader displays a message that there is an error while decompressing the kernel image and stops booting.

3. Each and every time even after properly shutting down the board this error happens and the board boots up fine if the boot partition is formatted and freshly created again.

Can any one please suggest why this is happening with the board
working with Z7000 APSoC 

Parents
  • 0

    Hi,

    Even though it's good to know that Xillinux-1.1 solves your issue, it's not such good news for Xillinux-1.3, which was released about a month ago.

    The thing is that the root filesystems are almost the same. The differences are mainly in the kernel version and Uboot, which have both been upgraded (the latter based upon another initialization routine, which is supplied by a newer version of XPS).

    So question #1 is: Which revision of Zedboard do you have? Maybe it's an issue with some specific revision.

    The v1.3 bundle for Zedboard has been downloaded >200 times by now, so it's safe to assume that the vast majority of users haven't seen any problem (or there would have been more complaints).

    As I mentioned earlier, the immediate suspects are poor signal integrity on the wires going to the DDR memories and SD card, which can be a result of inadequate initialization of their registers on the processor.

    If you'd like to help me investigate this, could you please try running the C program that is listed on this post on Xillinux-1.3?

    http://billauer.co.il/blog/?p=3932

    Just copy it somehow into the SD card's file system (say, as memtest.c) and then go (on the board's shell propmt):

    gcc -O3 memtest.c -o memtest

    and then run it as shown on the post. At least for a few hours.

    Don't bother starting an X session.

    Thanks in advance,
       Eli

  • 0 in reply to Former Member

    As you suggested I did the test for over 6 hours and it did not return any errors. I am e-mailing you the snap-shot of the result.

    Please suggest me if I have to re-run the test again. It ran for over 6 hours but did not return the time of run. I paced the program in the background and brought it back again.

    Harsha

Reply Children
No Data