Mailinglist Archive: opensuse-arm (80 mails)

< Previous Next >
[opensuse-arm] Factory images broken!
  • From: Guillaume Gardet <guillaume.gardet@xxxxxxx>
  • Date: Mon, 05 Aug 2013 16:35:09 +0200
  • Message-id: <51FFB81D.4070004@free.fr>
Hi,

I tested beagle image from factory (but this problem should occur on all other
boards) and it does not boot at all, with this message:
************************************************************
U-Boot SPL 2013.04 (May 28 2013 - 14:13:22)
OMAP SD/MMC: 0
spl: error reading image u-boot.bin, err - -1
### ERROR ### Please RESET the board ###
************************************************************

First problem is in BOOT partition, all available files are under a boot/
folder and nothing at the root of the partition.

Then u-boot starts but I get this error:
********************************************************************************
U-Boot SPL 2013.04 (May 28 2013 - 14:13:22)
OMAP SD/MMC: 0


U-Boot 2013.04 (May 28 2013 - 14:13:22)

OMAP3630/3730-GP ES1.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 A
No EEPROM on expansion board
Die ID #5e3c00011ff00000015739eb0a01c005
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO
Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 1.800
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 480ab000 using PIO, IRQ 0
Net: usb_ether
Hit any key to stop autoboot: 0
mmc0 is current device
gpio: pin 173 (gpio 173) value is 0
gpio: pin 4 (gpio 4) value is 0
SD/MMC found on device 0
** File not found uEnv.txt **
1576 bytes read in 5 ms (307.6 KiB/s)
Running bootscript from mmc0 ...
## Executing script at 80200000
kerneladdr=0x80200000
ramdiskaddr=0x81000000
mmc0 is current device
4338904 bytes read in 385 ms (10.7 MiB/s)
65842548 bytes read in 5656 ms (11.1 MiB/s)
Unknown command '1' - try 'help'
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Booting from nand ...

no devices available
Wrong Image Format for bootm command
ERROR: can't get kernel image!
OMAP3 beagleboard.org #
********************************************************************************

I guess the "unknown command" problem comes from the u-boot script:
**********
if itest 1${loadfdt} == 11; then
setenv load_fdt 'ext2load ${bootdev} ${bootpart} ${fdt_addr} ${fdt}'
else
setenv load_fdt '1'
fi
**********

When u-boot want to run load_fdt for non device tree board, it tries to run 1.
Which is wrong but should not be fatal.

If (under uboot) I run:
setenv boottype bootz
and then:
run doit
the kernel starts but it crashed after 10/12 seconds.

"file linux.vmx" returns:
linux.vmx: Linux kernel ARM boot executable zImage (little-endian)

Have we switched to zImage for all boards? at least the ones supported by
default kernel?

The kernel crash is maybe only a kernel problem and not related to the rest of
this e-mail.


Guillaume

--
To unsubscribe, e-mail: opensuse-arm+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-arm+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups