Boot problems

Hi all,


there seems to a problem with my Mini2440. Downloading the kernel and the
qtopia image is no problem but I can't boot the systems afterwards. The
systems reports lots of bad blocks and bad erase blocks and ends with 

yaffs_read_super: isCheckpointed 0
VFS: Mounted root (yaffs filesystem) on device 31:3.
Freeing init memory: 128K
Warning: unable to open an initial console.
Failed to execute /linuxrc.  Attempting defaults...
Kernel panic - not syncing: No init found.  Try passing init= option to
kernel.

What is wrong? 


Regards

Peter

What power supply do you use?

Regards,
Andreas

Hi Andreas,

thanks for your reply.

I use a 3.8 A switching power supply. My board did well with this power
supply. Then I tried to load some other operating systems ......


Regards,


Peter

Correct image? The mini2440 is avaiable with different flash sizes (64M,
128M, 256M, 1GB).

Yes, at least I hope so. I used zImage_T35 and
root_qtopia-64M_20090429.img. Correct?


Regards,

Peter

This is a image for mini2440 with 64MB NAND Flash.

My 2440 has 64MB, but I have tried with the 128 MB versions of the software
as well and without success.

I have done the following:

- Format NAND flash for Linux

- Download Linux Kernel (using file zImage_T35, no extension like bin)

- Download root_yaffs image (using file root_qtopia-64M_20090429.img)

- Boot the system

All I get is a Tasmanian Devil on the LCD and (beneath lots of other
messages) 

.
.
.
Bad eraseblock 419 at 0x000003460000
Bad eraseblock 420 at 0x000003480000
Bad eraseblock 421 at 0x0000034a0000
Bad eraseblock 422 at 0x0000034c0000
Bad eraseblock 423 at 0x0000034e0000
Bad eraseblock 424 at 0x000003500000
Bad eraseblock 425 at 0x000003520000
Creating 4 MTD partitions on "NAND 256MiB 3,3V 8-bit":
0x000000000000-0x000000060000 : "supervivi"
0x000000060000-0x000000260000 : "Kernel"
0x000000260000-0x000040260000 : "root"
mtd: partition "root" extends beyond the end of device "NAND 256MiB 3,3V
8-bit" -- size truncated to 0xfda0000
0x000000000000-0x000040000000 : "nand"
mtd: partition "nand" extends beyond the end of device "NAND 256MiB 3,3V
8-bit" -- size truncated to 0x10000000


and


.
.
.

block 424 is bad
block 425 is bad
block 426 is bad
Partially written block 152 detected
Partially written block 152 detected
Partially written block 152 detected
Partially written block 152 detected
Partially written block 152 detected
Partially written block 152 detected
yaffs_read_super: isCheckpointed 0
VFS: Mounted root (yaffs filesystem) on device 31:3.
Freeing init memory: 128K
Warning: unable to open an initial console.
Failed to execute /linuxrc.  Attempting defaults...
Kernel panic - not syncing: No init found.  Try passing init= option to
kernel.

NAND is reported as 256 MB by the system.


What could be wrong? Should I provide the complete log of the booting
process?


Regards


Peter

If the system reports 256M NAND I would suspect that either it really was
256M or there is another problem.

How old is the dev board?  Was it sold as 64M? Can you read the part number
on the flash chip?

The board is brand new, at least I have bought it a few days ago. 

I thought it is a 64 MB NAND board, but in fact it was sold as a 256 MB
NAND board. The NAND is a Samsung K9F2G08U0B.

Peter

Sure looks like a 256M part.

Thanks for this information. Having 256 MB NAND is fine, if the board will
boot again.

And now? There seem to be no 256 MB images/versions. Is creating a partions
with a total capacity of 128 MB a solution?


Peter

The files for the new boards (256MB, 1GB) are currently only available at:
http://arm9.net/download.asp
We will upload them to this site this weekend.

Regards,
Andreas

Hi Andreas,

thanks for your reply.

Using the new files did the trick.


Regards


Peter

Well, it almost did the trick.

I can load and start Qtiopia and Android now, but both OS don't start by
themselves. I have to boot them via the boot command in DNW or vivi. Do I
have to set a boot flag or something like it?

Peter