The question about install linux (mini2440)

Hi...

I am a ARM beginner.
When i step by step to install linux(reference：Mini2440
Manual(2010-02-04))
get the blow error message：

----------------------------------------------------------------
.
.
.
block 436 is bad
block 437 is bad
block 438 is bad
block 439 is bad
block 440 is bad
block 441 is bad
block 442 is bad
block 443 is bad
block 444 is bad
block 445 is bad
block 446 is bad
block 447 is bad
block 448 is bad
block 449 is bad
block 450 is bad
block 451 is bad
block 452 is bad
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.
----------------------------------------------------------------

who could tell me Where I was going wrong ?

is Mini2440 Manual or CD file(comes with product) has problem ?

thanks a lot.

Bad blocks are a fact of life, but you seem to have a lot of them! I assume
there were many more of them before 536

You'll need to tell us a bit more about what you are doing.  Have you
managed to restore the factory default software and got it working as per
original and now you are trying to . . .

oops 436

Hi...

I did the following things
---------------------------
Supervivi
  1.[v]Download vivi  ----------------> supervivi-64M
  2.[k]Download kernel  --------------> zImage_T35
  3.[y]Download root_yaffs image  ----> root_qtopia-64M.img
  4.USB disconnect
  5.[b]Boot the system
---------------------------

and i have not change any default,
error message just happened as above,

I'll assume you are trying to restore the factory distro.

Did you do the first step in DNW where the NAND is partitioned?

[x]

Hi

Yes, i am try to restore the factory distro,

and, i am also try to use [x] to format NAND Flash for Linux before step
[v][k][y][b]

I am using Super terminal(Win XP) to send operation [v][k][y][b],
and send data from CD to NAND Flash using DNW.

I would like know which version could to achieve my purpose,
include supervivi[v],linux kernel[k],root_yaffs image[y],

my hardware as below
------------------------
-ARM9 mini2440
-64M SDRAM on board
-64M Nand Flash
-3.5" LCD (Toppoly)
------------------------

Operation system Windows XP

As long as you are using supervivi, zImage and root_qtopia from the same
distro everything should be OK.  It looks like you are doing the right
thing.

Cut and paste the whole message, there might be a clue before all your bad
blocks.

Supervivi>param set linux_cmd_line "noinitrd root=/dev/mtdblock3
init=/linuxrc console=ttySAC0"

max,

I noticed you mentioned the above in this posting as well:
http://www.friendlyarm.net/forum/topic/689?lang=en

Could you explain why this line has to be added?

How's it going John W.?

Thanks,
Dave

Your error is :
Failed to execute /linuxrc.  Attempting defaults...

The system can't find boot file, I don't remenber my old command line but
it should not match, after this correction my board boot ok. 
I don't try to understand more, and enjoy

there is no need for init=/linuxrc . linuxrc shell script  is used by the
initrd (ram disk) before the boot cycle completes to execute the linuxrc.


--fatbrain

Hi everyone.

The initial value of "linux_cmd_line" in mini2440 just like  
"noinitrd root=/dev/mtdblock3 init=/linuxrc console=ttySAC0"

and i also try to change "linux_cmd_line" to below
"noinitrd root=/dev/mtdblock3 console=ttySAC0" 
but, it still did not succeed 


error message as below
please give me some suggestions 
thanks a lot.

-----------------------------------------------------------------
.
.
.
block 387 is bads detected053063
block 388 is badi2c s3
Initializ
block 389 is badage driver... Se
block 390 is badBad eraseblock 2
block 391 is badstered new inter
block 392 is badtoragenered for 
block 393 is bad/ Palm OS0m     
block 394 is bads Storage suppor
block 395 is badat 
USB Serial s
block 396 is badusbcore: registe
block 397 is bad driver ums-alau
block 398 is badUSB Serial suppo
block 404 is bad
block 405 is bad
block 406 is bad
block 407 is bad
block 408 is bad
block 409 is bad
yaffs_read_super: isCheckpointed 0
VFS: Mounted root (yaffs filesystem) on device 31:3.
Freeing init memory: 160K
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.
Backtrace:
[<c0035270>] (dump_backtrace+0x0/0x10c) from [<c03958f0>]
(dump_stack+0x18/0x1c)

 r7:00000000 r6:c0503ed0 r5:c0503660 r4:c04c61a0
[<c03958d8>] (dump_stack+0x0/0x1c) from [<c0395940>] (panic+0x4c/0x134)
[<c03958f4>] (panic+0x0/0x134) from [<c00305a4>] (init_post+0xec/0x178)
 r3:00000000 r2:c393c200 r1:c0539000 r0:c045348c
[<c00304b8>] (init_post+0x0/0x178) from [<c00084c4>]
(kernel_init+0xf4/0x124)
 r5:c00205d4 r4:c00205d4
[<c00083d0>] (kernel_init+0x0/0x124) from [<c004d1a4>] (do_exit+0x0/0x62c)
 r7:00000000 r6:00000000 r5:00000000 r4:00000000
-----------------------------------------------------------------

You do one thing for sure 
either follow mini2440 step by step tutorial or at least do as below :

Turn the boot selection switch to NOR flash on the board. Connect mini2440
with PC using minicom via RS232. Power on the board and you shall see this
boot-up menu:
##### FriendlyARM BIOS for 2440 #####
[x] bon part 0 320k 2368k
[v] Download vivi 
[k] Download linux kernel 
[y] Download root_yaffs image 
[c] Download root_cramfs image 
[a] Absolute User Application
[n] Download Nboot 
[e] Download Eboot 
[i] Download WinCE NK.nb0 
[w] Download WinCE NK.bin 
[d] Download & Run 
[f] Format the nand flash 
[p] Partition for Linux 
[b] Boot the system 
[s] Set the boot parameters 
[t] Print the TOC struct of wince 
[u] Backup NAND Flash to HOST through USB(upload) 
[r] Restore NAND Flash from HOST through USB 
[q] Goto shell of vivi 
Enter your selection: q
--------------------------------------------------------------------------------
-
Press q and Enter at the prompt and switch to vivi promp. 
Now connect PC with mini2440's USB device port, via a USB cable.
 Tell vivi that you need 239616 Bytes space in the RAM to load 
something from the USB, starting at 0x31000000
--------------------------------------------------------------------------------
-
-
Supervivi> load ram 0x31000000 239616 u     //here, 239616 is size of
u-boot file.
USB host is connected. Waiting a download.
--------------------------------------------------------------------------------
-
-
On another shell window, use following command to download 
u-boot into the RAM of mini2440
[using linux to configure mini2440]
--------------------------------------------------------------------------------
-
-
desktop:~/s3c2410_boot_usb$ sudo ./s3c2410_boot_usb u-boot.bin
--------------------------------------------------------------------------------
-
-
Enter root password when prompted, and you shall see this output on the
shell
--------------------------------------------------------------------------------
-
-
csum = 0xd542
send_file: addr = 0x33f80000, len = 0x0003a5a8
Error downloading  program    
--------------------------------------------------------------------------------
-
-
Please ignore the error. 
Now go back to vivi. You shall see follows 
--------------------------------------------------------------------------------
-
-
Now, Downloading [ADDRESS:31000000h,TOTAL:239026]
RECEIVED FILE SIZE:  239026 (233KB/S, 1S)
Downloaded file at 0x31000000, size = 239016 bytes
--------------------------------------------------------------------------------
-
-
Now we are ready to write u-boot from the RAM to NAND flash. 
Execute the code starting at RAM location 0x31000000:
--------------------------------------------------------------------------------
-
-
Supervivi> go 0x31000000
go to 0x31000000
  argument 0 = 0x00000000
  argument 1 = 0x00000000
  argument 2 = 0x00000000
  argument 3 = 0x00000000

U-Boot 1.3.2-dirty-moko12 (Apr 16 2009 - 18:14:52)

I2C:   ready
DRAM:  64 MB
Flash:  2 MB
NAND:  Bad block table not found for chip 0
Bad block table not found for chip 0
64 MiB
Found Environment offset in OOB..
USB:   S3C2410 USB Deviced
In:    serial
Out:   serial
Err:   serial
MAC: 08:08:11:18:12:27
Hit any key to stop autoboot:  0 
--------------------------------------------------------------------------------
-
-
When seeing "Hit any key to stop autoboot," press any key on the keyboard.
The prompt shall change from Supervivi> to MINI2440 #.
 Get the information about the NAND flash: 
--------------------------------------------------------------------------------
-
-
MINI2440 # nand info

Device 0: NAND 64MiB 3,3V 8-bit, page size 512, sector size 16 KiB
--------------------------------------------------------------------------------
-
-
Erase everything on the NAND flash: 
--------------------------------------------------------------------------------
-
-
MINI2440 # nand scrub

NAND scrub: device 0 whole chip
Warning: scrub option will erase all factory set bad blocks!
         There is no reliable way to recover them.
         Use this command only for testing purposes if you
         are sure of what you are doing!

Really scrub this NAND flash? <y/N>
Erasing at 0x3ffc000 -- 100% complete.
Bad block table not found for chip 0
Bad block table not found for chip 0
OK
--------------------------------------------------------------------------------
-
-
Please enter a lower case y and press Enter when prompted. 
Now create a new partition table
--------------------------------------------------------------------------------
-
-
MINI2440 # nand createbbt
--------------------------------------------------------------------------------
-

Now you will get the the bad block list and a bad block table will be
created in NAND, to avoid storing data on it, then you can proceed to work
as per tutorial : 
<a
href="http://code.google.com/p/mini2440/wiki/MiniBringup">http://code....
</a>

today i made the install and i have this problem too, but the solucion its
downloading another package, the source its this page you have to look very
well, download the same package but with diferent bit, if you try with 16
do it again but with the 32, good luck



forgive my english im from colombia but i hope this could help you

Hi John W

Your problem may be that you are using 128 MB NAND and using 64 MB
supervivi-64 and image. 

I had the same problem and saw some 128MiB in the output and checked the
NAND it was 128 MB (but the manual came with that said it is 64 MB).

Hope this helps.

Ya.. Thats right..even i had the same problem and i tried loading the files
for 128 MB NAND instead and it worked.

first do the file sytem(root_yaffs) 
then do the bootloader and then load the kernel....

hmm I also have these problems after I have changed the configuration that
worked before. Sometimes that are little things in the kernel configuration
(make menuconfig) that breaks the filesystem on working.

Maybe you should try this: http://www.usr.cc/html/15/n-715.html

I also faced the same problem.

Kernel panic - not syncing: No init found.  Try passing init= option to
kernel.

I am using qemu for mini2440 board. I also get one more message 
"NOR flash not found"

can anybody help?

Does this also happen with my customized kernel at
http://git.programmers-projects.de/?p=mini2440-dev.git;a=tree;f=kernel-2...
?

I didn't try it.
Let me give it a try.

Hi, i also have problem with lot of bad blocks. I use factory images,
u-boot version is 1.1.6 and it doesn't have command nand createbbt. Another
problem is that when i try to download rootfs (55 MB) using dnw.exe process
stop on 47 MB, so i make new rootfs image (i don't touch valuable files
from /bin or /libs). I download new image of rootfs to nand, boot the
device and get same big list of errors. I wrote this letter to techsupport
(no answer yet):

I buy EM2440-III 64MB device without LCD. I'm trying to install Linux to
device using images from original DVD, because Linux on device (factory
settings) does not work. I made all steps following manuals, but there is
problem: Linux crashes in kernel panic because it can't mount rootfs. There
was error messages when i format NAND (using u-boot form DVD). I suggest
that problem is in writing or reading rootfs on NAND.
 
##### Boot for Nor Flash Main Menu #####

[1] Download u-boot or STEPLDR.nb1 or other bootloader to Nand Flash

[2] Download Eboot to Nand Flash

[3] Download Linux Kernel to Nand Flash

[5] Download CRAMFS image to Nand Flash

[6] Download YAFFS image to Nand Flash

[7] Download Program (uCOS-II or EM2440_Test) to SDRAM and Run it

[8] Boot the system

[9] Format the Nand Flash

[0] Set the boot parameters

[a] Download User Program (eg: uCOS-II or EM2440_Test)

[b] Download LOGO Picture (.bin) to Nand Flash

[l] Set LCD Parameters

[o] Download u-boot to Nor Flash

[r] Reboot u-boot

[q] quit from menu

Enter your selection: 9



##### Erase Nand Menu #####

[1] Nand scrub - really clean NAND erasing bad blocks (UNSAFE)

[2] Nand earse - clean NAND eraseing

[q] Return main Menu

Enter your selection: 1


NAND scrub: device 0 whole chip

Warning: scrub option will erase all factory set bad blocks!

There is no reliable way to recover them.

Use this command only for testing purposes if you

are sure of what you are doing!


Really scrub this NAND flash? <y/N> :
 
Erasing at 0x0 -- 0
Erasing at 0xa0000 -- 1
Erasing at 0x144000 -- 2
Erasing at 0x1e8000 -- 3
Erasing at 0x28c000 -- 4
Erasing at 0x330000 -- 5
...
Erasing at 0x1708000 -- 36
Erasing at 0x17ac000 -- 37
Erasing at 0x1850000 -- 384MiB 3,3V 8-bit: MTD Erase failure: -5


Erasing at 0x18f4000 -- 39
Erasing at 0x1998000 -- 40
...
Erasing at 0x3eb8000 -- 98
Erasing at 0x3f5c000 -- 99
Erasing at 0x3ffc000 -- 100OK
 
After format i burn U-boot (u-boot_W35.bin) to NAND. that's ok
Then i burn linux kernel (zImage_64MB_W35). that's ok too
This steps was in NOR-boot mode
 
Then i tried to burn rootfs using dnw.exe (v0.50A as in manual) tool
 
##### Boot for Nand Flash Main Menu #####

[1] Download u-boot or STEPLDR.nb1 or other bootloader to Nand Flash

[2] Download Eboot to Nand Flash

[3] Download Linux Kernel to Nand Flash

[5] Download CRAMFS image to Nand Flash

[6] Download YAFFS image to Nand Flash

[7] Download Program (uCOS-II or EM2440_Test) to SDRAM and Run it

[8] Boot the system

[9] Format the Nand Flash

[0] Set the boot parameters

[a] Download User Program (eg: uCOS-II or EM2440_Test)

[b] Download LOGO Picture (.bin) to Nand Flash

[l] Set LCD Parameters

[r] Reboot u-boot

[q] quit from menu

Enter your selection: 6

USB host is connected. Waiting a download.


Now, Downloading [ADDRESS:30000000h,TOTAL:55892506]

RECEIVED FILE SIZE:47251464
 
but maximum size for image is 47MB and size of image that i tried to burn
is 55 MB
when counter of progress goes to 47 MB all process freezes
 
To defeat this i make own rootfs that is less than 47 MB following by user
manual (guide for Linux developers),
 
Booting Linux ...

Copy linux kernel from 0x00200000 to 0x30008000, size = 0x00200000 ... Copy
Kernel to SDRAM done,NOW, Booting Linux......

Uncompressing
Linux...........................................................................
.............................................
done, booting the kernel.
Linux version 2.6.30.4-EmbedSky (feng@feng-desktop) (gcc version 4.3.3
(Sourcery G++ Lite 2009q1-203) ) #19 Mon Jan 4 22:41:07 CST 2010
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
CPU: VIVT data cache, VIVT instruction cache
Machine: TQ2440
ATAG_INITRD is deprecated; please update your bootloader.
Memory policy: ECC disabled, Data cache writeback
CPU S3C2440A (id 0x32440001)
S3C24XX Clocks, (c) 2004 Simtec Electronics
S3C244X: core 400.000 MHz, memory 100.000 MHz, peripheral 50.000 MHz
CLOCK: Slow mode (1.500 MHz), fast, MPLL on, UPLL on
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
Kernel command line: noinitrd root=/dev/mtdblock2 init=/linuxrc
console=ttySAC0
NR_IRQS:85
irq: clearing pending ext status 00080000
irq: clearing subpending status 00000003
irq: clearing subpending status 00000002
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
console [ttySAC0] enabled
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 60956KB available (3428K code, 373K data, 112K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Calibrating delay loop... 199.47 BogoMIPS (lpj=498688)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 296 bytes
NET: Registered protocol family 16
S3C2440: Initialising architecture
S3C2440: IRQ Support
S3C24XX DMA Driver, (c) 2003-2004,2006 Simtec Electronics
DMA channel 0 at c4808000, irq 33
DMA channel 1 at c4808040, irq 34
DMA channel 2 at c4808080, irq 35
DMA channel 3 at c48080c0, irq 36
S3C244X: Clock Support, DVS off
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
s3c2440-i2c s3c2440-i2c: slave address 0x10
s3c2440-i2c s3c2440-i2c: bus frequency set to 97 KHz
s3c2440-i2c s3c2440-i2c: i2c-0: S3C I2C adapter
cfg80211: Calling CRDA to update world regulatory domain
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NET: Registered protocol family 1
yaffs Jan 4 2010 22:38:10 Installing.
msgmni has been set to 119
alg: No test for stdrng (krng)
io scheduler noop registered (default)
Console: switching to colour frame buffer device 40x15
fb0: s3c2410fb frame buffer device
backlight initialized
GPIO-Control initialized
PWM-Test initialized
adc initialized
s3c2440-uart.0: tq2440_serial0 at MMIO 0x50000000 (irq = 70) is a S3C2440
s3c2440-uart.1: tq2440_serial1 at MMIO 0x50004000 (irq = 73) is a S3C2440
s3c2440-uart.2: tq2440_serial2 at MMIO 0x50008000 (irq = 76) is a S3C2440
loop: module loaded
Driver 'sd' needs updating - please use bus_type methods
dm9000 Ethernet Driver, V1.31
Now use the default MAC address: 10:23:45:67:89:ab
eth0 (dm9000): not using net_device_ops yet
eth0: dm9000e at c4814000,c4818004 IRQ 51 MAC: 10:23:45:67:89:ab (EmbedSky)
S3C24XX NAND Driver, (c) 2004 Simtec Electronics
s3c2440-nand s3c2440-nand: Tacls=3, 30ns Twrph0=7 70ns, Twrph1=3 30ns
NAND device: Manufacturer ID: 0xec, Chip ID: 0x76 (Samsung NAND 64MiB 3,3V
8-bit)
Scanning device for bad blocks
Bad eraseblock 257 at 0x000000404000
Bad eraseblock 258 at 0x000000408000
Bad eraseblock 259 at 0x00000040c000
Bad eraseblock 260 at 0x000000410000
Bad eraseblock 261 at 0x000000414000
Bad eraseblock 262 at 0x000000418000
Bad eraseblock 263 at 0x00000041c000
Bad eraseblock 264 at 0x000000420000
Bad eraseblock 265 at 0x000000424000
 
 
and many many messages Bad eraseblock XXX at 0xXXXXXXXXXX
 
 
Bad eraseblock 1244 at 0x000001370000
Bad eraseblock 1245 at 0x000001374000
Bad eraseblock 1246 at 0x000001378000
Bad eraseblock 1247 at 0x00000137c000
Bad eraseblock 1248 at 0x000001380000
Bad eraseblock 1249 at 0x000001384000
Bad eraseblock 1568 at 0x000001880000
Creating 3 MTD partitions on "NAND 64MiB 3,3V 8-bit":
0x000000000000-0x000000040000 : "EmbedSky_Board_uboot"
0x000000200000-0x000000400000 : "EmbedSky_Board_kernel"
0x000000400000-0x00000ff80000 : "EmbedSky_Board_yaffs2"
mtd: partition "EmbedSky_Board_yaffs2" extends beyond the end of device
"NAND 64MiB 3,3V 8-bit" -- size truncated to 0x3c00000
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Initial EmbedSky TWO USB HOST Driver!
s3c2410-ohci s3c2410-ohci: S3C24XX OHCI
s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1
s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x49000000
usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: S3C24XX OHCI
usb usb1: Manufacturer: Linux 2.6.30.4-EmbedSky ohci_hcd
usb usb1: SerialNumber: s3c24xx
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbserial
usbserial: USB Serial Driver core
USB Serial support registered for pl2303
usbcore: registered new interface driver pl2303
pl2303: Prolific PL2303 USB to serial adaptor driver
mice: PS/2 mouse device common for all mice
TQ2440 TouchScreen successfully loaded
input: TQ2440 TouchScreen as /devices/virtual/input/input0
S3C24XX RTC, (c) 2004,2006 Simtec Electronics
s3c2410-rtc s3c2410-rtc: rtc disabled, re-enabling
s3c2410-rtc s3c2410-rtc: rtc ...stripped-down

i2c /dev entries driver
Linux video capture interface: v2.00
zc0301: V4L2 driver for ZC0301[P] Image Processor and Control Chip v1:1.10
usbcore: registered new interface driver zc0301
gspca: main v2.5.0 registered
usbcore: registered new interface driver zc3xx
zc3xx: registered
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v0.1.0)
S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
s3c2410-wdt s3c2410-wdt: watchdog inactive, reset disabled, irq enabled
mapped channel 0 to 0
s3c2440-sdi s3c2440-sdi: powered down.
s3c2440-sdi s3c2440-sdi: initialisation done.
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.18a.
No device for DAI UDA134X
No device for DAI s3c24xx-i2s
S3C24XX_UDA134X SoC Audio driver
UDA134X SoC Audio Codec
s3c2440-sdi s3c2440-sdi: powered down.
mmc0: error -110 whilst initialising SD card
s3c2440-sdi s3c2440-sdi: powered down.
asoc: UDA134X <-> s3c24xx-i2s mapping ok
ALSA device list:
#0: S3C24XX_UDA134X (UDA134X)
TCP cubic registered
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
lib80211: common routines for IEEE802.11 drivers
s3c2410-rtc s3c2410-rtc: hctosys: invalid date/time
yaffs: dev is 32505858 name is "mtdblock2"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.2, "mtdblock2"
yaffs: block 1 is marked bad
block 2 is bad
yaffs: block 2 is marked bad
block 3 is bad
yaffs: block 3 is marked bad
block 4 is bad
yaffs: block 4 is marked bad
block 5 is bad
yaffs: block 5 is marked bad
block 6 is bad
yaffs: block 6 is marked bad
block 7 is bad
 
 
and many many messages
"yaffs: block X is marked bad
block X is bad"
 
 
yaffs: block 991 is marked bad
block 992 is bad
yaffs: block 992 is marked bad
block 993 is bad
yaffs: block 993 is marked bad
block 994 is bad
yaffs: block 1312 is marked bad
block 1313 is bad
yaffs_read_super: isCheckpointed 0
VFS: Mounted root (yaffs filesystem) on device 31:2.
Freeing init memory: 112K
Kernel panic - not syncing: Attempted to kill init!
Backtrace:
[<c0028fd4>] (dump_backtrace+0x0/0x10c) from [<c029e794>]
(dump_stack+0x18/0x1c)
r7:c381a000 r6:c03a9be0 r5:0000000b r4:0000000b
[<c029e77c>] (dump_stack+0x0/0x1c) from [<c029e7e4>] (panic+0x4c/0x124)
[<c029e798>] (panic+0x0/0x124) from [<c003a450>] (do_exit+0x520/0x620)
r3:c0386798 r2:c381de10 r1:c381dce4 r0:c032f2dc
[<c0039f30>] (do_exit+0x0/0x620) from [<c003a594>]
(do_group_exit+0x44/0xc4)
[<c003a550>] (do_group_exit+0x0/0xc4) from [<c0044a4c>]
(get_signal_to_deliver+0x198/0x350)
 r5:0000000b r4:c381c000
[<c00448b4>] (get_signal_to_deliver+0x0/0x350) from [<c0027788>]
(do_signal+0x5c/0x4b0)
[<c002772c>] (do_signal+0x0/0x4b0) from [<c0027c0c>]
(do_notify_resume+0x30/0x34)
[<c0027bdc>] (do_notify_resume+0x0/0x34) from [<c0024eac>]
(work_pending+0x1c/0x20)
 
This is big PROBLEM. What can you advise to me? And maybe you have another
images
of kernel and rootfs or even u-boot? (this u-boot is v1.1.6 and it hasn't
function to create bad blocks table)
 
I hope you help me.

I'm also trying u-boot 1.3.2 and follow instructions to use nand create bbt
and so on (i don't remember use i dynenv or not), i make uImage from zImage
and convert yaffs2 to jffs2, but when i bott system i have message:
Uncompressing Linux ...................... ... .......................
done, booting the kernel. and process stops.

And question to davef: you say in another thread that u-boot load only
uImages, but there are only u-boot, zImage and root_qt2...64MB in my DVD
and in user manual they use u-boot to load zImage. How it can be? Or is
there nedd to convert zImage to uImage?

No Supervivi on the DVD?

Where in the user manual do they say to use u-boot to load zImages?

mkimage is used to convert zImage to uImage.

I did read a thread where some guy was trying to "up-grade" u-boot to load
zImages. I emailed him and he never got back to me.

If u-boot can load zImages, I would be happy to be corrected.

Dave

HI.

I Installed Wince to NorFlash and Now I can`t Installed Again.

I can`t see boot menu in hyper terminal or DNW.

i don`t know how can i format the norflash.

please help me.

my device is EM2440-III

Sajad,

You will possibly get a better response putting this in the WinCE part of
the forum.

Err...  EM2440-III is not the same as Mini2440...

FYI,

We had the kernel panic issue too, we were trying to use 64M images on a
128M device.

Works like a charm now!!

Caps Lock it ON some different process betwent "x", "X"

Hello,

I am new to Linux porting and am facing the same problem as stated
above(Kernel Panic).
I am using prebuilt images both kernel and qt-rootfilesystem from the DVD
that came along with the board and also from the download section.

My board has 1GB Nand flash and I was wondering if I am using either 64 MB
or 128 MB flash images of the RFS.
http://www.friendlyarm.net/forum/topic/700#16277 like Brian as suggested.



By the way I have flashed uboot and kernel and flash have been put on my SD
card. The kernel is booting fine but says ""Kernel panic - not syncing:
Attempted to kill init"" and sometimes ""Kernel panic - not syncing: No
init found.  Try passing init= opt""

Would someone **kind** enough to point me where I can get Rootfs image of
QT which can be used on the 1GB nand.

First, you do have determine what size of RAM you have. Read the part
number on the RAM chip(s).

Second, the pre-built images are for downloading with Supervivi not u-boot.

Supervivi = zImage = rootfs.yaffs2
U-boot = uImage = rootfs.jffs2

Search for <mini2440vietnam> for instructions on how to make your own Qt
rootfs.

Dropping your error messages into search will provide hours of reading
material.

Good luck!

Hello Denn.

The Mini2440 all have 64M RAM. The vivi-128 will work on everything bigger
than 64M NAND. It is good for 128M, 256M, and 1024M/1G NAND. The NAND chips
contain in the part number 1G, 2G or 8G (for number of bits).

(If there is ever a 2G NAND then it will probably need an SLC version of
vivi).

Sorry, I was thinking of flash erase size!

Thanks for correcting it.

Hello TheRegnirps, davef,

I understand that uboot cant flash yaffs2 image to the NAND flash. But I am
looking to boot the RFS from my MMC-SD card. Isnt that possible? I have
created a ext3 partition and copied the prebuilt rootfs.yaffs2 and qt based
rfs images. But it won't boot stating the above said errors.

Is it possible to load a qt based RFS from SD card?

Thanks,

Have a look around this site:

http://billforums.station51.net/

> Isnt that possible?

I would expect that one could, but I was solidly into using u-boot by the
time I learnt how to load stuff off a SDcard.