PDA

View Full Version : hangs during boot



orlandov
11-08-10, 12:30 AM
one of our Warp devices hangs during boot.
plug in a usb with version 2.2.5.6 file
I hooked up a serial connect to see where it was hanging

Does anyone have any suggestions?

Here is the snip of the boot information until the point where it hangs, fan going full speed and stays there


:::::

U-Boot 1.3.0-95 (Oct 22 2010 - 11:48:23)

CPU: AMCC PowerPC 440EP Rev. C at 533.333 MHz (PLB=133, OPB=66, EBC=66 MHz)
I2C boot EEPROM enabled
Bootstrap Option H - Boot ROM Location I2C (Addr 0x52)
, PCI async ext clock used 32 kB I-Cache 32 kB D-Cache


Board: PIKA Embedded Appliance
I2C: ready
DRAM: 256 MB
### Press 'p' to enter POST ###: 0
RAM Offset: 0x0ff34000
NOR Offset: 0xfff80000
DIF Offset: 0xf004c000
FLASH: 4 MB
NAND: 256 MiB
In: serial
Out: serial
Err: serial
FPGA: 3.0.1.4
MMC: PIKA SD: 0
Net: ppc_4xx_eth0
.ENET Speed is 100 Mbps - FULL duplex connection (EMAC0)

USB: No USB storage devices found
Persistent Version: 2.2.7-3:1287762494
Hit any key to stop autoboot: -1

NAND read: device 0 offset 0x0, size 0x180000

reading NAND page at offset 0x0 failed
1572864 bytes read: ERROR
## Booting image at 02000000 ...
ERROR: Magic number was not found in image header. Aborting boot

mrecoskie
11-08-10, 09:55 AM
Hi orlandov,

In this case the loadable kernel size is too small. Using your serial cable enter uboot by pressing a key at the following prompt - 'Hit any key to stop autoboot: '

And then enter the following two commands exactly:

setenv load_nand_kernel nand read.jffs2 0x02000000 0x00000000 0x00200000
saveenv

This should resolve the issue.

\Mark

orlandov
11-08-10, 10:33 AM
Thanks Mark
I tried several times but the error is almost the same:

=> setenv load_nand_kernel nand read.jffs2 0x02000000 0x00000000 0x00200000
=> saveenv
Saving Environment to Flash...
Saving environment variables to flash ...
.. done
=> reset


Resetting board...Goodbye.


U-Boot 1.3.0-95 (Oct 22 2010 - 11:48:23)

CPU: AMCC PowerPC 440EP Rev. C at 533.333 MHz (PLB=133, OPB=66, EBC=66 MHz)
I2C boot EEPROM enabled
Bootstrap Option H - Boot ROM Location I2C (Addr 0x52)
, PCI async ext clock used 32 kB I-Cache 32 kB D-Cache


Board: PIKA Embedded Appliance
I2C: ready
DRAM: 256 MB
### Press 'p' to enter POST ###: 0
RAM Offset: 0x0ff34000
NOR Offset: 0xfff80000
DIF Offset: 0xf004c000
FLASH: 4 MB
NAND: 256 MiB
In: serial
Out: serial
Err: serial
FPGA: 3.0.1.4
MMC: PIKA SD: 0
Net: ppc_4xx_eth0
.ENET Speed is 100 Mbps - FULL duplex connection (EMAC0)

USB: No USB storage devices found
Persistent Version: 2.2.7-3:1287762494
Hit any key to stop autoboot: -1

NAND read: device 0 offset 0x0, size 0x200000

reading NAND page at offset 0x0 failed
2097152 bytes read: ERROR
## Booting image at 02000000 ...
ERROR: Magic number was not found in image header. Aborting boot

awayte
11-08-10, 11:01 AM
Hi orlandov,

Make sure to also re-burn the Kernel image after you alter the kernel size. Probably best to re-burn most of what is in the 2.2.7 package (http://outgoingftp.pikatech.com/appliance/2.2/images_2.2.7.3.tgz).

To do so:

1. Copy all of the new images to your tftp server.

2. Burn the fpga:

update fpga fpga3014.wrp -d tftp

3. With your serial cable connected reboot the warp and again halt the boot process when prompted.

4. Enter the following commands as follows. Select yes when prompted for confirmation. No need to reset after each image is burned and reboot at the end:

update kernel kernel-2.6.31.7-7.wrp -d tftp
update persistent persistent-2.2.7-3.wrp -d tftp
update persistent1 persistent1-2.2.7-3.wrp -d tftp
update persistent2 persistent2-2.2.7-3.wrp -d tftp
update ramdisk ramdisk-2.2.7-3.wrp -d tftp

5. Reboot the Warp and you should be ready to go!

/Adam

mrecoskie
11-08-10, 11:29 AM
I should have caught this before - specifically the following lines:

...
USB: No USB storage devices found
Persistent Version: 2.2.7-3:1287762494
...

From this I believe only a persistent image is burnt to your Warp. This would imply the kernel, ramdisk and persistent 1&2 images are all missing. The suggestions given by awayte should resolve the problem however I don't believe the step to burn a new FPGA image is necessary. From your output you are already using 3.0.1.4.

orlandov
11-08-10, 11:45 PM
thanks, worked perfectly