• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 485 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Preassembled image hangs during boot on Beagleboard xM

Jan Vachun
Prodigy 40 points

As suggested on http://processors.wiki.ti.com/index.php/Qt_on_BeagleBoard, I have downlaoded preassembled image http://beagle.s3.amazonaws.com/beagle_qt_certification_files.zip

I put it on sd card, but Beagleboard doesn't start at all - on serial console I'have seen 60 when trying user+reset buttons

So I have replaced contents of first partition with contents of first partition of working Beagleboard xM image.

Now Beagleboard starts but hangs after 'Uncompressing Linux .. done, booting the kernel.'.

Thank you for help to solve my problem.

Regards,

  Jan

Below is contents of uEnv.txt and boot log on serial console

--------------- uEnv.txt -----------------------------

mpurate=1000

dvimode="hd720 omapfb.vram=0:8M,1:4M,2:4M"
vram=16M
optargs="consoleblank=0"
console="tty0 console=ttyS2,115200n8"

--------------- boot log -----------------------------

Texas Instruments X-Loader 1.5.0 (Mar 27 2011 - 17:37:56)
Beagle xM
Reading boot sector
Loading u-boot.bin from mmc


U-Boot 2011.03-rc1-00000-g9a3cc57-dirty (Apr 01 2011 - 17:41:42)

OMAP36XX/37XX-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 512 MiB
NAND: 0 MiB
MMC: OMAP SD/MMC: 0
*** Warning - readenv() failed, using default environment

In: serial
Out: serial
Err: serial
Beagle xM Rev C
No EEPROM on expansion board
Die ID #622000029ff800000168432d16027028
Hit any key to stop autoboot: 0
The user button is currently NOT pressed.
SD/MMC found on device 0
reading uEnv.txt

134 bytes read
Loaded environment from uEnv.txt
Importing environment from mmc ...
Loading file "/boot/uImage" from mmc device 0:2 (xxa2)
3001004 bytes read
Booting from mmc ...
## Booting kernel from Legacy Image at 80200000 ...
Image Name: Angstrom/2.6.29/beagleboard
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3000940 Bytes = 2.9 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux.................................................................................................................................................................................................. done, booting the kernel.

  • 0
    TI__Prodigy 120 points

    Hi,

    Can you try using console ttyO2.

    Regards,

    Deepti Vaidya

  • 0 in reply to Deepti Vaidya
    Prodigy 40 points

    Hi,

    I'm not sure, if I have understand correctly.

    I have replaced last line of uEnv.txt 

    console="tty0 console=ttyS2,115200n8"

    with

    console="tty0 console=ttyO2,115200n8"

    but the result is the same. 

    Serial console stops after 'Uncompressing Linux .. done, booting the kernel.' and no other activity can be observed ( onboard LEDs , HDMI output etc. ).

    Can I try something else to solve this problem ?

    Regards,

      Jan

  • 0 in reply to Jan Vachun
    Prodigy 40 points

    Hi,

    just for curiosity I have replaced uImage in root of first partition and also in /boot in second partition and now beagleboard boots O.K.

    Obviously I'm unable to do much in this way, because kernel modules are for different version and couldn't be loaded.

    So it seems that kernel shipped in http://beagle.s3.amazonaws.com/beagle_qt_certification_files.zip ( linked from  http://processors.wiki.ti.com/index.php/Qt_on_BeagleBoard ) doesn't work on Beagleboard xM (rev.C).

    Is there another image ready for testing Qt with OpenGL ES 2.0 ?

    Thank you.

  • 0 in reply to Jan Vachun
    Genius 4090 points

    Jan Vachun said:
    Obviously I'm unable to do much in this way, because kernel modules are for different version and couldn't be loaded.

    What exactly do you mean by this?

  • 0 in reply to chethu gowda
    Prodigy 40 points

    Hi,

    original uImage delivered with preassembled image is kernel 2.6.29 and uImage that I 'borrowed' from working image is kernel 2.6.36 so modules on preassembled image doesn't match running kernel.

    I need that modules for gles hw support.

    I'm now trying an image build by narcissus but I'm having problems to get Qt+GLES working. For this reason I have seeked for preassembled, ready to test image.

    Regards,

       Jan