On 01/12/2012 02:04 PM, Andrei Gherzan wrote:
I used linux-yocto kernel for beagleboard and got over my last problem:
KMACHINE_qemuarmv7 = "yocto/standard/beagleboard"
SRCREV_machine_qemuarmv7 ?= "6b4bf6173b0bd2d1619a8218bac66ebc4681dd35"
COMPATIBLE_MACHINE_qemuarmv7 = "qemuarmv7"

Now my boot process is looping in:

omap_i2c_write: Bad register 0x00000214

Any ideas?

@g

This was because i used beaglexm and not beagle as -M. Now my whole thing can boot successfully with one down point: cannot see kernel boot messages... i can review them with dmesg.

#qemu-system-arm -M beagle -m 256 -sd sd.img -clock unix -serial stdio

U-Boot 2011.06 (Jan 12 2012 - 15:21:35)

OMAP35XX-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 600 mHz
OMAP3 Beagle board + LPDDR/NAND
I2C:   ready
DRAM:  256 MiB
NAND:  256 MiB
MMC:   OMAP SD/MMC: 0
*** Warning - bad CRC, using default environment

ERROR : Unsupport USB mode
Check that mini-B USB cable is attached to the device
In:    serial
Out:   serial
Err:   serial
Beagle Rev C4
No EEPROM on expansion board
Die ID #51454d5551454d555400000051454d55
Hit any key to stop autoboot:  0
SD/MMC found on device 0
reading uEnv.txt

** Unable to read "uEnv.txt" from mmc 0:1 **
reading uImage

3106596 bytes read
Booting from mmc ...
## Booting kernel from Legacy Image at 82000000 ...
   Image Name:   Linux-3.0.12-yocto-standard+
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3106532 Bytes = 3 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
omap2_inth_read: Bad register 0x00000020

Yocto (Built by Poky 6.0) 1.1+snapshot-20120112 beagleboard ttyO2

beagleboard login:

-----------------------------------------------

Does anybody know why these boot messages are not printed on serial in qemu?

@g

_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

Reply via email to