USB host is not connected after flashing vivi throught JTAG

Hi Guys,

I have a EM2440-III board which is exactly same as mini2440 except it has
only 4 buttons instead of 8 as on mini2440. 2 of them are also connected to
different IRQ's. 

By mistake i corrupted U-boot and the kernel on the board hence I
programmed vivi from friendly arm website into the NOR flash using H-Jtag
software. Now the boards boots with vivi from NOR flash. 

I am trying to dowload u-boot as per the following links.
http://narnia.cs.ttu.edu/drupal/node/131
http://bill.station51.net/index.php?post/2010/01/16/U-Boot-on-Mini2440

After I run "load ram 0x32000000 <uboot size> u-boot" command in vivi
shell.

I get an error message "USB host is not connected yet". I also tried 
./s3c2410_boot_usb  but this gave me an error "Cannot find QT2410 device in
bootloader mode"

I tried installing the same thing with dnw software in windows 7 64bit but
there also I get the same usb error. Even tried installing
usb-downloaddr-setup but no luck.

The board doesnt boot at all 
--------------------------------------------------------------------------
Enter your selection: b

Copy linux kernel from 0x00060000 to 0x30008000, size = 0x00500000 ... done

Warning: this binary is not compressed linux kernel image

zImage magic = 0xffffffff

Setup linux parameters at 0x30000100

linux command line is: "noinitrd root=/dev/mtdblock3 init=/linuxrc
console=ttySAC0"

MACH_TYPE = 1999

NOW, Booting Linux......
--------------------------------------------------------------------------

Nothing happens after this. 
Can some one please give some pointers to solve this issue. Is there any
way to program u-boot by some other means? 

Cheers
Tama

> After I run "load ram 0x32000000 <uboot size> u-boot" command in vivi
> shell.

But, the command is "load ram 0x31000000 <uboot size> u"

Is it a 64M machine?  Are you using his u-boot.bin ?

Hi Davef,

The board has got 64MB Nand Flash (K9F1208UDC), 2KB or NOR Flash and 64MB
SDRAM. 

Today I tried to flash MINI2440 U-boot "u-boot-v132.bin" directly onto NOR
Flash and U-boot from EM2440III SDK cd onto NAND Flash.

When I boot from Nor flash with Mini2440 U-boot the board dosent gets
recognized by windows on USB port. So I issue usb start command, but then
also it is not detected by windows.

If I boot from NAND flash with U-boot(from EM2440SDK) the board gets
recognized as SEC S3C2410X TEST B/D. I dont have the drivers for this hence
I cannot communicate with the board.


Has any one experience similar situation. Could some one please give some
pointers.

Cheers
Tama

Ah, you have two boards with two different problems.

I have never heard of or tried putting u-boot in NOR.  Following that
tutorial in your first link and all the work I have done using the
Pengutronix BSP ... Supervivi remains in NOR and then you put the
bootloader in NAND.

What instructions or tutorial are you following to place u-boot in NOR?

And you have read all relevant threads here:

http://billforums.station51.net/viewforum.php?f=1&sid=6e7c3ad3afdccb...

Hi Davef,

I have only one board (EM2440III). As mentioned earlier this board is
exactly same as Mini2440. Hence I want to flash this board with uboot,
linux kernel and root fs from mini2440. 

Today I programmed NOR flash on the board with supervivi 2010-08-18 from
friendly arm download link. Then I boot the board from nor flash. I can see
##### FriendlyARM BIOS for 2440 ##### from super vivi. 
Then i pressed q to switch to vivi prompt. 
load ram 0x31000000 239016 u

Then I get an error message saying USH host not connected. 
As per the link http://narnia.cs.ttu.edu/drupal/node/131

It says USB host is connected. But In my case it is saying usb not
connected. 

I tried all these steps on xp machine. I couldnt even see a unknow usb
device in windows device manager. 

Looks vivi dosent have usb drivers.  


So I programmed uboot 2010-07-01(friendly) on to NAND flash using Hjtag
tool. After I boot from NAND flash I boot can see 
---------------------------------
USB:   S3C2410 USB Deviced
In:    serial
Out:   serial
Err:   serial
MAC: 08:08:11:18:12:27
Hit any key to stop autoboot:  0
---------------------------------

In this case also no USB activity on the PC. 


Apart from sdcard can download the kernel and file system through USB when
I boot from NAND flash to uboot.

Cheers
tama

There are some drivers for DNW, have you got those?

On the downloads page:

Software
Mini2440 / Micro2440

    USB download driver setup
    USB download driver (inf)
    DNW download tool (Windows)

I recall that I had to get the sequence right, ie start DNW then plug USB
cable to the mini2440 in OR the other way around.

I assume your board has a USB host connector?

I will try the sequence as you mentioned. My board does have usb host
connector of type b.

The 64M NAND boards require the supervivi-64 version and the 64M version of
u-boot (latest u-boot versions auto-detect I think). The block read and
write sizes are different for 64M versus all larger NAND.

I programmed NOR flash again with supervivi-64 through jtag. Then after I
boot from Nor flash and try to dowload u-boot, I get the same error USB
host not connected. I even tried xmodem but that is also not working. 

I dont understand what is causing this error. I even tried on a linux
machine. My biggest problem is that after I program nor flash with
supervivi I am not able to go the next step of dowloading uboot. 

Any other means to load u-boot.

Are you using DNW?

Did you install USB drivers for DNW?

Yes I tried with DNW and even with supervivi full download tool. I though
there was something worng with my board. Hence I borrowed my colleagues
mini2440 with 3.5 inch lcd and tried the same steps on it.

Even with mini2440(3.5lcd) i was getting same results. Supervivi which is
on the board doesnt connect on USB. I tried this on a xp machine and
reinstalled all the usb drivers also. But still no luck.

I have attached circuit diagram for my board em2440.

usb schematic

So, now you have two non-functional boards?

Has your colleague ever been able to use Supervivi on his host system?
Did he ever JTAG in Supervivi to get his board working again?

Are you following the guide called "Mini2440 Downloader Instructions"?

I just found another description of the "proper" sequence I used:

- run DNW
- switch to NOR
- power on the mini2440
- you should see the user menu in DNW and
- THEN plug in the USB cable from FriendlyArm to the PC

Don't think the schematics are going to tell anyone what is wrong.  

Get the mini2440 working again and then maybe you have go to a forum which
is deals with the em2440 or the manufacturer.

Good luck.

The board which I borrowed from my colleague (mini2440 3.5inhc LCD) is
working. The board boots as it has factory bootload and other images. 

I just got that board to test whether after booting from nor flash into
supervivi usb is detected. But apparently when i hit q in super vivi and
say load ram <addr> <file size> u. It says USB host not connected. 

This is exactly the same thing happening on my board. 

I check the usb schematic everything is identical.

One more question, when the procedure says USB host its the Mini2440 -> USB
Type A connector on the board -> Type A-A cable -> PC. 

or is it mini2440 type B - Type B- Type A cable -> PC

I just found a link to similar thread in WindowsCE section. This guy is
also facing the same problem as I am. 

http://www.friendlyarm.net/forum/topic/2257

You could try both ways!  The square cable goes into the mini2440 and the
flatter rectangular end goes into the PC.

The square cable END . . .

Finally after trying for so many days I could get supervivi to talk 
through USB. 

There is something wrong with supervivi_64MB USB. After reading the thread
"http://www.friendlyarm.net/forum/topic/2257";, I downloaded supervivi_128MB
onto NOR flash. After booting USB started working and I could download
U-boot. 

I might change the NAND chip on the board. 

Any idea what is the 128MB/256MB/1GB nand chips number which is being used
on mini2440 boards.

Cheers

But, you said early in the thread that it was a 64M flash.

Why change the NAND chip?  If it REALLY is a 128M flash why not keep it?

Read the number off the NAND chip and go and download the datasheet off the
downloads page!

The existing flash which came along with the board is 64Mb.

Initially I downloaded supervivi_64mb but the USB didn't work. Then after
reading the other thread which I mentioned earlier. That guy has same board
as I have with 64mb nand + 64mb sdram. So i tried uploading
supervivi_128mb. After booting from NOR with supervivi_128mb USB started
working. Hence i mentioned I can change that NAND flash from 64MB to 128MB.

> Hence i mentioned I can change that NAND flash from 64MB to 128MB.

You mean in some menu selection, not actually physically replacing it ...
right?  I thought you were saying you were going to physically replace the
chip :)

Well, if everything else works properly you have managed to solve it.  

Good luck.

No I was planing to change the physical 64MB nand chip to 128MB nand chip.

Does it make any difference if I download superviv_128MB, but physically
nand chip is only 64MB.


I have been trying different methods to upload kernel and rootfs on the
board but no success. 

I could manage to compile kernel and convert zimage to uimage. But when no
success with building a rootfs. I even followed 
http://code.google.com/p/friendlyarm/wiki/Linux_Tutorial 

but the links what are there for copying etc from existing rootjffs2 dosent
work. 

I even read your thread about uploading files via tftp. 

Could you please give some inputs on this.

cheers

Hi Davef,

Could you please give some inputs on compiling rootfs and uploading the
roofts + kernel to the board.

I downloaded busybox1.13.4 and followed this link to compile rootfs
"http://wiki.iface.ch/index.php/Basic_rootfs_for_Mini2440";. There were no
errors with compiling the rootfs apart from a warning. 
--------------------------------------------------
You will probably need to make your busybox binary
setuid root to ensure all configured applets will
work properly.
--------------------------------------------------

After that I created all the folders and files as per the link
"http://wiki.iface.ch/index.php/Basic_rootfs_for_Mini2440";. But How do i
tar/mount this file system. What kind of file system is this.

I am able to compile kernel and then convert it into uImage. then I
followed this thread to upload via tftp

http://billforums.station51.net/viewtopic.php?f=1&t=205

"tftp 30008000 uImage.bin" then issue "bootm 0x30008000"
-------------------------------------------------------------

U-Boot 1.3.2-mini2440 (May 25 2010 - 19:15:21)

I2C:   ready

DRAM:  64 MB

Flash:  2 MB

NAND:  64 MiB

Found Environment offset in OOB..

USB:   S3C2410 USB Deviced

In:    serial

Out:   serial

Err11:18:12:27

MINI2440 #    

MINI2440 # printenv

bootdelay=3

baudrate=115200

ethaddr=08:08:11:18:12:27

netmask=255.255.255.0

usbtty=cdc_acm

mini2440=mini2440=0tb

bootargs_base=console=ttySAC0,115200 noinitrd

bootargs_init=init=/sbin/init

root_nand=root=/dev/mtdblock3 rootfstype=jffs2

root_mmc=root=/dev/mmcblk0p2 rootdelay=2

root_nfs=/mnt/nfs

set_root_nfs=setenv root_nfs root=/dev/nfs rw
nfsroot=${serverip}:${root_nfs}

ifconfig_static=run setenv ifconfig
ip=${ipaddr}:${serverip}::${netmask}:mini2440:eth0

ifconfig_dhcp=run setenv ifconfig ip=dhcp

ifconfig=ip=dhcp

set_bootargs_mmc=setenv bootargs ${bootargs_base} ${bootargs_init}
${mini2440} ${root_mmc}

set_bootargs_nand=setenv bootargs ${bootargs_base} ${bootargs_init}
${mini2440} ${root_nand}

set_bootargs_nfs=run set_root_nfs; setenv bootargs ${bootargs_base}
${bootargs_init} ${mini2440} ${root_nfs} ${ifconfig}

mtdids=nand0=mini2440-nand

mtdparts=mtdparts=mini2440-nand:0x00040000(u-boot),0x00020000(u-boot_env),0x0050
0000(kernel),0x03aa0000(r.4

serverip=192.168.1.6

partition=nand0,0

mtddevnum=0

mtddevname=u-boot



Environment size: 1051/131068 bytes

MINI2440 # tftp 0x32000000 uImage

dm9000 i/o: 0x20000300, id: 0x90000a46 

DM9000: running in 16 bit mode

MAC: 08:08:11:18:12:27

TFTP from server 192.168.1.6; our IP address is 192.168.1.4

Filename 'uImage'.

Load address: 0x32000000

Loading: *T ###################################T
##############################

   #################################################################

   #################################################################

   #################################################################

   #################################################################

   #################################################################

   #####################################################

done

Bytes transferred = 2266656 (229620 hex)
-------------------------------------------------------------------------

then I write the kernel to nand flash using following 
command "nand write 0x32000000 kernel"

NAND write: device 0 offset 0x60000, size 0x500000

 5242880 bytes written: OK

Set the bootarg as follows:=
"setenv bootargs  console=ttySAC0,115200 root=dev/nfs
nfsroot=192.168.1.6:/home/uid/friendlyarm/target init=helloworld"

then I set saveenv and reset the board
-------------------------------------------------------------------------


Loading from NAND 64MiB 3,3V 8-bit, offset 0x60000

reading NAND page at offset 0x60000 failed

** Read error

## Booting kernel from Legacy Image at 32000000 ...

   Image Name:   

   Created:      2012-02-19   9:03:06 UTC

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    2266592 Bytes =  2.2 MB

   Load Address: 30008000

   Entry Point:  30008000

   Verifying Checksum ... OK

   Loading Kernel Image ... OK

OK



Starting kernel ...



Uncompressing
Linux...........................................................................
........................................................................
done, booting the kernel.

Linux version 2.6.32.2-FriendlyARM (pritam@pritam-desktop) (gcc version
4.4.3 (ctng-1.6.1) ) #2 Sun Feb 19 16:50:18 WST 2012

CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177

CPU: VIVT data cache, VIVT instruction cache

Machine: FriendlyARM Mini2440 development board

Memory policy: ECC disabled, Data cache writeback

CPU S3C2440A (id 0x32440001)

S3C24XX Clocks, (c) 2004 Simtec Electronics

S3C244X: core 405.000 MHz, memory 101.250 MHz, peripheral 50.625 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: console=ttySAC0,115200 root=dev/nfs
nfsroot=192.168.1.6:/home/pritam/friendlyarm/target init=helloworld

PID hash table entries: 256 (order: -2, 1024 bytes)

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: 60084KB available (4176K code, 451K data, 156K init, 0K highmem)

SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1

Hierarchical RCU implementation.

NR_IRQS:85

irq: clearing pending status 02000000

irq: clearing subpending status 00000002

Console: colour dummy device 80x30

console [ttySAC0] enabled

Calibrating delay loop... 201.93 BogoMIPS (lpj=504832)

Mount-cache hash table entries: 512

CPU: Testing write buffer coherency: ok

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

s3c-i2c s3c2440-i2c: slave address 0x10

s3c-i2c s3c2440-i2c: bus frequency set to 98 KHz

s3c-i2c s3c2440-i2c: i2c-0: S3C I2C adapter

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

RPC: Registered udp transport module.

RPC: Registered tcp transport module.

RPC: Registered tcp NFSv4.1 backchannel transport module.

NetWinder Floating Point Emulator V0.97 (double precision)

yaffs Feb 19 2012 16:45:03 Installing. 

msgmni has been set to 117

alg: No test for stdrng (krng)

io scheduler noop registered (default)

Console: switching to colour frame buffer device 100x30

fb0: s3c2410fb frame buffer device

backlight  initialized

leds  initialized

buttons  initialized

pwm  initialized

adc  initialized

s3c2440-uart.0: s3c2410_serial0 at MMIO 0x50000000 (irq = 70) is a S3C2440

s3c2440-uart.1: s3c2410_serial1 at MMIO 0x50004000 (irq = 73) is a S3C2440

s3c2440-uart.2: s3c2410_serial2 at MMIO 0x50008000 (irq = 76) is a S3C2440

loop: module loaded

S3C24XX NAND Driver, (c) 2004 Simtec Electronics

s3c24xx-nand s3c2440-nand: Tacls=3, 29ns Twrph0=7 69ns, Twrph1=3 29ns

s3c24xx-nand s3c2440-nand: NAND soft ECC

NAND device: Manufacturer ID: 0xec, Chip ID: 0x76 (Samsung NAND 64MiB 3,3V
8-bit)

Scanning device for bad blocks

Creating 5 MTD partitions on "NAND 64MiB 3,3V 8-bit":

0x000000000000-0x000000040000 : "supervivi"

0x000000040000-0x000000060000 : "param"

0x000000060000-0x000000560000 : "Kernel"

0x000000560000-0x000040560000 : "root"

mtd: partition "root" extends beyond the end of device "NAND 64MiB 3,3V
8-bit" -- size truncated to 0x3aa0000

0x000000000000-0x000040000000 : "nand"

mtd: partition "nand" extends beyond the end of device "NAND 64MiB 3,3V
8-bit" -- size truncated to 0x4000000

dm9000 Ethernet Driver, V1.31

eth0: dm9000e at c4814300,c4818304 IRQ 51 MAC: 08:90:90:90:90:90 (chip)

ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) 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.32.2-FriendlyARM 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 ums-alauda

usbcore: registered new interface driver ums-cypress

usbcore: registered new interface driver ums-datafab

usbcore: registered new interface driver ums-freecom

usbcore: registered new interface driver ums-isd200

usbcore: registered new interface driver ums-jumpshot

usbcore: regis...stripped-down

usbcore: registered new interface driver ums-karma

usbcore: registered new interface driver ums-onetouch

usbcore: registered new interface driver ums-sddr09

usbcore: registered new interface driver ums-sddr55

usbcore: registered new interface driver ums-usbat

usbcore: registered new interface driver usbserial

USB Serial support registered for generic

usbcore: registered new interface driver usbserial_generic

usbserial: USB Serial Driver core

USB Serial support registered for aircable

usbcore: registered new interface driver aircable

USB Serial support registered for ark3116

usbcore: registered new interface driver ark3116

USB Serial support registered for Belkin / Peracom / GoHubs USB Serial
Adapter

usbcore: registered new interface driver belkin

belkin_sa: v1.2:USB Belkin Serial converter driver

USB Serial support registered for ch341-uart

usbcore: registered new interface driver ch341

USB Serial support registered for cp210x

usbcore: registered new interface driver cp210x

cp210x: v0.09:Silicon Labs CP210x RS232 serial adaptor driver

USB Serial support registered for Reiner SCT Cyberjack USB card reader

usbcore: registered new interface driver cyberjack

cyberjack: v1.01 Matthias Bruestle

cyberjack: REINER SCT cyberJack pinpad/e-com USB Chipcard Reader Driver

USB Serial support registered for DeLorme Earthmate USB

USB Serial support registered for HID->COM RS232 Adapter

USB Serial support registered for Nokia CA-42 V2 Adapter

usbcore: registered new interface driver cypress

cypress_m8: v1.09:Cypress USB to Serial Driver

USB Serial support registered for Digi 2 port USB adapter

USB Serial support registered for Digi 4 port USB adapter

usbcore: registered new interface driver digi_acceleport

digi_acceleport: v1.80.1.2:Digi AccelePort USB-2/USB-4 Serial Converter
driver

USB Serial support registered for Edgeport 2 port adapter

USB Serial support registered for Edgeport 4 port adapter

USB Serial support registered for Edgeport 8 port adapter

USB Serial support registered for EPiC device

usbcore: registered new interface driver io_edgeport

io_edgeport: v2.7:Edgeport USB Serial Driver

USB Serial support registered for Edgeport TI 1 port adapter

USB Serial support registered for Edgeport TI 2 port adapter

usbcore: registered new interface driver io_ti

io_ti: v0.7mode043006:Edgeport USB Serial Driver

USB Serial support registered for empeg

usbcore: registered new interface driver empeg

empeg: v1.2:USB Empeg Mark I/II Driver

USB Serial support registered for FTDI USB Serial Device

usbcore: registered new interface driver ftdi_sio

ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver

USB Serial support registered for funsoft

usbcore: registered new interface driver funsoft

USB Serial support registered for Garmin GPS usb/tty

usbcore: registered new interface driver garmin_gps

garmin_gps: v0.33:garmin gps driver

USB Serial support registered for hp4X

usbcore: registered new interface driver hp4X

hp4x: v1.00:HP4x (48/49) Generic Serial driver

USB Serial support registered for PocketPC PDA

usbcore: registered new interface driver ipaq

ipaq: v0.5:USB PocketPC PDA driver

USB Serial support registered for IPWireless converter

usbcore: registered new interface driver ipwtty

ipw: v0.3:IPWireless tty driver

USB Serial support registered for IR Dongle

usbcore: registered new interface driver ir-usb

ir_usb: v0.4:USB IR Dongle driver

USB Serial support registered for iuu_phoenix

usbcore: registered new interface driver iuu_phoenix

iuu_phoenix: v0.11:Infinity USB Unlimited Phoenix driver

USB Serial support registered for Keyspan - (without firmware)

USB Serial support registered for Keyspan 1 port adapter

USB Serial support registered for Keyspan 2 port adapter

USB Serial support registered for Keyspan 4 port adapter

usbcore: registered new interface driver keyspan

keyspan: v1.1.5:Keyspan USB to Serial Converter Driver

USB Serial support registered for Keyspan PDA

USB Serial support registered for Keyspan PDA - (prerenumeration)

USB Serial support registered for Xircom / Entregra PGS - (prerenumeration)

usbcore: registered new interface driver keyspan_pda

keyspan_pda: v1.1:USB Keyspan PDA Converter driver

USB Serial support registered for KL5KUSB105D / PalmConnect

usbcore: registered new interface driver kl5kusb105d

kl5kusb105: v0.3a:KLSI KL5KUSB105 chipset USB->Serial Converter driver

USB Serial support registered for KOBIL USB smart card terminal

usbcore: registered new interface driver kobil

kobil_sct: 21/05/2004:KOBIL USB Smart Card Terminal Driver (experimental)

USB Serial support registered for MCT U232

usbcore: registered new interface driver mct_u232

mct_u232: z2.1:Magic Control Technology USB-RS232 converter driver

USB Serial support registered for Moschip 2 port adapter

mos7720: 1.0.0.4F:Moschip USB Serial Driver

usbcore: registered new interface driver moschip7720

USB Serial support registered for Moschip 7840/7820 USB Serial Driver

mos7840: 1.3.2:Moschip 7840/7820 USB Serial Driver

usbcore: registered new interface driver mos7840

USB Serial support registered for moto-modem

usbcore: registered new interface driver moto-modem

USB Serial support registered for navman

usbcore: registered new interface driver navman

USB Serial support registered for ZyXEL - omni.net lcd plus usb

usbcore: registered new interface driver omninet

omninet: v1.1:USB ZyXEL omni.net LCD PLUS Driver

USB Serial support registered for opticon

usbcore: registered new interface driver opticon

USB Serial support registered for GSM modem (1-port)

usbcore: registered new interface driver option

option: v0.7.2:USB Driver for GSM modems

USB Serial support registered for oti6858

usbcore: registered new interface driver oti6858

USB Serial support registered for pl2303

usbcore: registered new interface driver pl2303

pl2303: Prolific PL2303 USB to serial adaptor driver

USB Serial support registered for Qualcomm USB modem

usbcore: registered new interface driver qcserial

safe_serial: v0.0b:USB Safe Encapsulated Serial

USB Serial support registered for safe_serial

usbcore: registered new interface driver safe_serial

USB Serial support registered for siemens_mpi

usbcore: registered new interface driver siemens_mpi

Driver for Siemens USB/MPI adapter

Version 0.1 09/26/2005 Thomas Hergenhahn@web.de http://libnodave.sf.net

USB Serial support registered for Sierra USB modem

usbcore: registered new interface driver sierra

sierra: v.1.3.8:USB Driver for Sierra Wireless USB modems

USB Serial support registered for SPCP8x5

usbcore: registered new interface driver spcp8x5

spcp8x5: v0.04:SPCP8x5 USB to serial adaptor driver

USB Serial support registered for symbol

usbcore: registered new interface driver symbol

USB Serial support registered for TI USB 3410 1 port adapter

USB Serial support registered for TI USB 5052 2 port adapter

usbcore: registered new interface driver ti_usb_3410_5052

ti_usb_3410_5052: v0.9:TI USB 3410/5052 Serial Driver

USB Serial support registered for Handspring Visor / Palm OS

USB Serial support registered for Sony Clie 3.5

USB Serial support registered for Sony Clie 5.0

usbcore: registered new interface driver visor

visor: USB HandSpring Visor / Palm OS driver

USB Serial support registered for Connect Tech - WhiteHEAT -
(prerenumeration)

USB Serial support registered for Connect Tech - WhiteHEAT

usbcore: registered new interface driver whiteheat

whiteheat: v2.0:USB ConnectTech WhiteHEAT driver

mice: PS/2 mouse device common for all mice

s3c2410 TouchScreen successfully loaded

input: s3c2410 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 core: registered s3c as rtc0

i2c /dev entries driver

Linux video capture interface: v2.00

gspca: main v2.7.0 registered

usbcore: registered new interface driver conex

conex: registered

usbcore: registered new interface driver etoms

etoms: registered

usbcore: registered new interface driver finepix

finepix: registered

usbcore: registered new interface driver jeilinj

jeilinj: registered

usbcore: registered new interface driver mars

mars: registered

usbcore: registered new interface driver mr97310a

mr97310a: registered

usbcore: registered new interface driver ov519

ov519: registered

usbcore: registered new interface driver ov534

ov534: registered

usbcore: registered new interface driver pac207

pac207: registered

usbcore: registered new interface driver pac7311

pac7311: registered

usbcore: registered new interface driver sn9c20x

sn9c20x: registered

usbcore: registered new interface driver sonixb

sonixb: registered

usbcore: registered new interface driver sonixj

sonixj: registered

usbcore: registered new interface driver spca500

spca500: registered

usbcore: registered new interface driver spca501

spca501: registered

usbcore: registered new interface driver spca505

spca505: registered

usbcore: registered new interface driver spca506

spca506: registered

usbcore: registered new interface driver spca508

spca508: registered

usbcore: registered new interface driver spca561

spca561: registered

usbcore: registered new interface driver sq905

sq905: registered

usbcore: registered new interface driver sq905c

sq905c: registered

usbcore: registered new interface driver sunplus

sunplus: registered

usbcore: registered new interface driver stk014

stk014: registered

usbcore: registered new interface driver t613

t613: registere...stripped-down

usbcore: registered new interface driver tv8532

tv8532: registered

usbcore: registered new interface driver vc032x

vc032x: registered

usbcore: registered new interface driver zc3xx

zc3xx: registered

usbcore: registered new interface driver ALi m5602

ALi m5602: registered

usbcore: registered new interface driver STV06xx

STV06xx: registered

gspca_gl860: driver startup - version 0.9d10

usbcore: registered new interface driver gspca_gl860

gspca_gl860: driver registered

usbcore: registered new interface driver uvcvideo

USB Video Class driver (v0.1.0)

initializing s3c2440 camera interface......

s3c2440 camif init done

Loading OV9650 driver.........

SCCB address 0x60, manufacture ID 0xFFFF, expect 0x7FA2

SCCB address 0x60, manufacture ID 0xFFFF, expect 0x7FA2

No OV9650 found!!!

S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics

s3c2410-wdt s3c2410-wdt: watchdog inactive, reset disabled, irq enabled

s3c-sdi s3c2440-sdi: powered down.

s3c-sdi s3c2440-sdi: mmc0 - using pio, sw SDIO IRQ

usbcore: registered new interface driver usbhid

usbhid: v2.6:USB HID core driver

Advanced Linux Sound Architecture Driver Version 1.0.21.

No device for DAI UDA134X

No device for DAI s3c24xx-i2s

S3C24XX_UDA134X SoC Audio driver

UDA134X SoC Audio Codec

asoc: UDA134X <-> s3c24xx-i2s mapping ok

ALSA device list:

  #0: S3C24XX_UDA134X (UDA134X)

TCP cubic registered

NET: Registered protocol family 17

s3c2410-rtc s3c2410-rtc: setting system clock to 2142-02-22 22:10:22 UTC
(1137426126)

Looking up port of RPC 100003/2 on 192.168.1.6

rpcbind: server 192.168.1.6 not responding, timed out

Root-NFS: Unable to get nfsd port number from server, using default

Looking up port of RPC 100005/1 on 192.168.1.6

rpcbind: server 192.168.1.6 not responding, timed out

Root-NFS: Unable to get mountd port number from server, using default

Can some one please give some inputs on how to create a image of rootfs and
then program it into the nand.