Booboo succesfully boots Linux Kernel on Dingoo!

I've just received some very good news from Booboo:

"Hi,

I just got a linux kernel booting in the dingoo. Please note that this
is a quick shot and it is configured for the Dingoo PAVO reference
design and thus a lot of things fail miserably.

One step closer to running linux in the Dingoo...



U-Boot 1.1.6 (May 4 2009 - 04:13:34)

Board: Dingoo A320 (CPU Speed 336 MHz)
DRAM: 32 MB
Flash: 0 kB
NAND: 4096GiB
*** Warning - bad CRC or NAND, using default environment

In: serial
Out: serial
Err: serial
Hit any key to stop autoboot: 3 0
A320 # bootm 0x81100000
## Booting image at 81100000 ...
Image Name: Linux-2.6.24.3
Image Type: MIPS Linux Kernel Image (gzip compressed)
Data Size: 1857876 Bytes = 1.8 MB
Load Address: 80010000
Entry Point: 80332440
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK

Starting kernel ...

Linux version 2.6.24.3 (booboo@inspiron) (gcc version 4.1.2) #3
PREEMPT Mon May 4 04:13:56 CEST 2009
CPU revision is: 0ad0024f (Ingenic JZRISC)
CPU clock: 336MHz, System clock: 84MHz, Peripheral clock: 84MHz,
Memory clock: 84MHz
JZ4740 PAVO board setup
Determined physical RAM map:
memory: 04000000 @ 00000000 (usable)
User-defined physical RAM map:
memory: 02000000 @ 00000000 (usable)
Zone PFN ranges:
Normal 0 -> 8192
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0 -> 8192
Built 1 zonelists in Zone order, mobility grouping off. Total pages: 8128
Kernel command line: mem=32M console=ttyS0,57600n8
Primary instruction cache 16kB, VIPT, 4-way, linesize 32 bytes.
Primary data cache 16kB, 4-way, VIPT, no aliases, linesize 32 bytes
Synthesized clear page handler (25 instructions).
Synthesized copy page handler (44 instructions).
Synthesized TLB refill handler (20 instructions).
Synthesized TLB load handler fastpath (32 instructions).
Synthesized TLB store handler fastpath (32 instructions).
Synthesized TLB modify handler fastpath (31 instructions).
PID hash table entries: 128 (order: 7, 512 bytes)
Console: colour dummy device 80x25
console [ttyS0] enabled
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 27968k/32768k available (3230k kernel code, 4800k reserved,
790k data, 176k init, 0k highmem)
Mount-cache hash table entries: 512
net_namespace: 64 bytes
NET: Registered protocol family 16
Linux Plug and Play Support v0.97 (c) Adam Belay
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
Time: jz_clocksource clocksource has been installed.
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
Total 4MB memory at 0x1400000 was reserved for IPU
Power Management for JZ
yaffs May 4 2009 04:10:24 Installing.
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
jzlcd use 1 framebuffer:
jzlcd fb[0] phys addr =0x00480000
LCDC: PixClock:9333333 LcdClock:12923076
Console: switching to colour frame buffer device 60x34
fb0: jz-lcd frame buffer device, using 512K of video memory
JzSOC onchip RTC installed !!!
JzSOC: char device family.
Jz generic touch screen driver registered
JZ4740 SAR-ADC driver registered
UDC starting pnp monitor thread
JZ UDC hotplug driver registered
Serial: 8250/16550 driver $Revision: 1.5 $ 2 ports, IRQ sharing disabled
o•Ă‰¥…±Ă¡250: ttyS0 at MMIO 0x0 (irq = 9) is a 16550A
serial8250: ttyS1 at MMIO 0x0 (irq = 8) is a 16550A
RAMDISK driver initialized: 2 RAM disks of 4096K size 1024 blocksize
loop: module loaded
Jz CS8900A driver for Linux (V0.02)
eth%d: CS8900A rev ; detected
Linux video capture interface: v2.00
JzSOC Camera Interface Module (CIM) driver registered
Ingenic CMOS camera sensor driver registered
Driver 'sd' needs updating - please use bus_type methods
Nand DMA request channel 0.
NAND device: Manufacturer ID: 0xec, Chip ID: 0xd7 (Samsung NAND 4GiB
3,3V 8-bit) planenum:4
Nand using two-plane mode, and resized to writesize:8192 oobsize:256
blocksize:0x100000
Scanning device for bad blocks
Bad eraseblock 5 at 0x0002ff000
Bad eraseblock 6 at 0x00037f000
Bad eraseblock 7 at 0x0003ff000
Bad eraseblock 8 at 0x00047f000
Bad eraseblock 10 at 0x00057f000
Bad eraseblock 11 at 0x0005ff000
Bad eraseblock 12 at 0x00067f000
Bad eraseblock 13 at 0x0006ff000
Bad eraseblock 14 at 0x00077f000
Bad eraseblock 16 at 0x00087f000
Bad eraseblock 17 at 0x0008ff000
Bad eraseblock 19 at 0x0009ff000
Bad eraseblock 20 at 0x000a7f000
Bad eraseblock 21 at 0x000aff000
Bad eraseblock 22 at 0x000b7f000
Bad eraseblock 23 at 0x000bff000
Bad eraseblock 24 at 0x000c7f000
Bad eraseblock 25 at 0x000cff000
Bad eraseblock 26 at 0x000d7f000
Bad eraseblock 27 at 0x000dff000
Bad eraseblock 30 at 0x000f7f000
Bad eraseblock 31 at 0x000fff000
Bad eraseblock 32 at 0x00107f000
Bad eraseblock 33 at 0x0010ff000
Bad eraseblock 34 at 0x00117f000
Bad eraseblock 35 at 0x0011ff000
Bad eraseblock 36 at 0x00127f000
Bad eraseblock 37 at 0x0012ff000
Bad eraseblock 38 at 0x00137f000
Bad eraseblock 39 at 0x0013ff000
Bad eraseblock 40 at 0x00147f000
Bad eraseblock 41 at 0x0014ff000
Bad eraseblock 43 at 0x0015ff000
Bad eraseblock 44 at 0x00167f000
Bad eraseblock 47 at 0x0017ff000
Bad eraseblock 48 at 0x00187f000
Bad eraseblock 49 at 0x0018ff000
Bad eraseblock 50 at 0x00197f000
Bad eraseblock 53 at 0x001aff000
Bad eraseblock 54 at 0x001b7f000
Bad eraseblock 55 at 0x001bff000
Bad eraseblock 56 at 0x001c7f000
Bad eraseblock 58 at 0x001d7f000
Bad eraseblock 59 at 0x001dff000
Bad eraseblock 64 at 0x00207f000
Bad eraseblock 65 at 0x0020ff000
Bad eraseblock 66 at 0x00217f000
Bad eraseblock 67 at 0x0021ff000
Bad eraseblock 68 at 0x00227f000
Bad eraseblock 69 at 0x0022ff000
Bad eraseblock 70 at 0x00237f000
Bad eraseblock 73 at 0x0024ff000
Bad eraseblock 76 at 0x00267f000
Bad eraseblock 77 at 0x0026ff000
Bad eraseblock 80 at 0x00287f000
Bad eraseblock 81 at 0x0028ff000
Bad eraseblock 84 at 0x002a7f000
Bad eraseblock 85 at 0x002aff000
Bad eraseblock 86 at 0x002b7f000
Bad eraseblock 87 at 0x002bff000
Bad eraseblock 88 at 0x002c7f000
Bad eraseblock 91 at 0x002dff000
Bad eraseblock 98 at 0x00317f000
Bad eraseblock 99 at 0x0031ff000
Bad eraseblock 100 at 0x00327f000
Bad eraseblock 101 at 0x0032ff000
Bad eraseblock 102 at 0x00337f000
Bad eraseblock 103 at 0x0033ff000
Bad eraseblock 104 at 0x00347f000
Bad eraseblock 105 at 0x0034ff000
Bad eraseblock 106 at 0x00357f000
Bad eraseblock 107 at 0x0035ff000
Bad eraseblock 108 at 0x00367f000
power cable insert!
Bad eraseblock 109 at 0x0036ff000
Bad eraseblock 110 at 0x00377f000
Bad eraseblock 111 at 0x0037ff000
Bad eraseblock 112 at 0x00387f000
Bad eraseblock 113 at 0x0038ff000
Bad eraseblock 114 at 0x00397f000
Bad eraseblock 115 at 0x0039ff000
Bad eraseblock 116 at 0x003a7f000
Bad eraseblock 117 at 0x003aff000
Bad eraseblock 118 at 0x003b7f000
Bad eraseblock 119 at 0x003bff000
Bad eraseblock 120 at 0x003c7f000
Bad eraseblock 121 at 0x003cff000
Bad eraseblock 122 at 0x003d7f000
Bad eraseblock 123 at 0x003dff000
Bad eraseblock 124 at 0x003e7f000
Bad eraseblock 125 at 0x003eff000
Bad eraseblock 127 at 0x003fff000
Bad eraseblock 128 at 0x00407f000
Bad eraseblock 129 at 0x0040ff000
Bad eraseblock 130 at 0x00417f000
Bad eraseblock 131 at 0x0041ff000
Bad eraseblock 132 at 0x00427f000
Bad eraseblock 133 at 0x0042ff000
Bad eraseblock 134 at 0x00437f000
Bad eraseblock 136 at 0x00447f000
Bad eraseblock 137 at 0x0044ff000
Bad eraseblock 139 at 0x0045ff000
Bad eraseblock 207 at 0x0067ff000
Bad eraseblock 208 at 0x00687f000
Bad eraseblock 209 at 0x0068ff000
Bad eraseblock 225 at 0x0070ff000
Bad eraseblock 4096 at 0x08007f000
Bad eraseblock 4097 at 0x0800ff000
Bad eraseblock 4098 at 0x08017f000
Bad eraseblock 4099 at 0x0801ff000
Bad eraseblock 4100 at 0x08027f000
Bad eraseblock 4101 at 0x0802ff000
Bad eraseblock 4103 at 0x0803ff000
Bad eraseblock 4117 at 0x080aff000
Bad eraseblock 4118 at 0x080b7f000
Bad eraseblock 4239 at 0x0847ff000
Bad eraseblock 4240 at 0x08487f000
Bad eraseblock 4242 at 0x08497f000
Creating 6 MTD partitions on "NAND 4GiB 3,3V 8-bit":
0x000000000-0x000400000 : "NAND BOOT partition"
0x000400000-0x000800000 : "NAND KERNEL partition"
0x000800000-0x008000000 : "NAND ROOTFS partition"
0x008000000-0x010000000 : "NAND DATA1 partition"
0x010000000-0x020000000 : "NAND DATA2 partition"
0x020000000-0x040000000 : "NAND VFAT partition"
jz-ohci jz-ohci.0: JZ OHCI
jz-ohci jz-ohci.0: new USB bus registered, assigned bus number 1
jz-ohci jz-ohci.0: irq 3, io mem 0x13030000
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...
usb 1-1: new low speed USB device using jz-ohci and address 2
usb 1-1: device descriptor read/64, error -62
usb 1-1: device descriptor read/64, error -62
usb 1-1: new low speed USB device using jz-ohci and address 3
usb 1-1: device descriptor read/64, error -62
usb 1-1: device descriptor read/64, error -62
usb 1-1: new low speed USB device using jz-ohci and address 4
usb 1-1: device not accepting address 4, error -62
usb 1-1: new low speed USB device using jz-ohci and address 5
usb 1-1: device not accepting address 5, error -62
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
JzSOC Watchdog Timer: timer margin 60 sec
JZ SD/MMC card driver registered
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
JzSOC On-Chip I2S controller registered (DAC: DMA(play):4/IRQ36,
ADC: DMA(record):3/IRQ35)
JZ I2S OSS audio driver initialized
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00 3072 mtdblock0 (driver?)
1f01 3072 mtdblock1 (driver?)
1f02 117760 mtdblock2 (driver?)
1f03 120832 mtdblock3 (driver?)
1f04 241664 mtdblock4 (driver?)
1f05 503808 mtdblock5 (driver?)"

Comments

  1. Got quite a way through the boot sequence, top notch stuff!

    ReplyDelete
  2. Stuff's pretty awesome! Not long till we boot up a full OS.

    ReplyDelete
  3. fuuuuxxxx yessssss!!!! This aughta jump-start the scene nicely! =D

    ReplyDelete

Post a Comment

Popular posts from this blog

Dingoo A380 Review

Mancala for Dingux released (Mandingoo was released in 1975)

Idiot’s Guide to installing Dingux using Windows released

An interview with the creator of the Tauon PC-1, Volodymyr Mishin

How to show all your 17,083 c64 games from the c64 romset (archive.org) on the C64 Mini or C64 Maxi loader

Tauon PC-1 review

The Dingoo-Scene JXD S7800B (Rockchip 3188 SoC) Android Gaming Console Review

Dingoo representative at a320.freeforums.org !