64MQQ2440烧写MINI2440光盘中的内容同样可以跑起来
生活随笔
收集整理的這篇文章主要介紹了
64MQQ2440烧写MINI2440光盘中的内容同样可以跑起来
小編覺得挺不錯的,現(xiàn)在分享給大家,幫大家做個參考.
?2008年購買了QQ2440,后來出去工作了,2440壓箱子底壓了兩年,現(xiàn)在拿出來想弄弄qtopia,可是一查友善的資料已經(jīng)出到了ARM11的板子了,內(nèi)核以及qtopia的支持根文件映像也不知升級了多少次了,在此先恭喜友善能做的這么快。后來在友善網(wǎng)上下得了MINI2440的整個光盤內(nèi)容,希望通過將mini2440光盤中的kernel2.6.32和root下載到QQ2440上使使。不過一路上遇到了超級多的問題,最后總算是可以將kernel和root下載進(jìn)去了,可是剛開始開啟QQ2440時程序跑不起來,后來得到了版主和一些熱心朋友的幫助,最終通過一些修改終于可以以NOFLASH啟動方式跑起來了。不過還存在幾個驅(qū)動不匹配的問題。我用的是N35的屏,2008年QQ2440光盤中的supervivi,最近剛發(fā)布的MINI2440光盤中的kernel?(linux2.6.32)以及最新的root。??
下面將我一步一步的過程記錄如下,希望給同樣使用著QQ240板子的初級學(xué)者一點幫助,高手就莫笑話我了,另外網(wǎng)絡(luò)驅(qū)動和USB驅(qū)動的問題請高手看出什么問題后給點幫助和建議。?
步驟一 直接利用QQ2440中的supervivi(2008年的版本)燒寫MINI2440光盤中的內(nèi)核和根文件系統(tǒng)到QQ2440nandflash?
?????????????? 1.1 出現(xiàn)問題 : 在燒寫zimageN35時出現(xiàn)了被燒寫的文件大小大于分區(qū)大小,不讓燒寫?
??????????????? 1.2 解決思路 :我猜想應(yīng)該是老版本的supervivi中對于內(nèi)核的分區(qū)太小了,于是我決定先升級SUPERVIVI到最新版本
步驟二 利用H-JTAG升級supervivi64M到norflash,按照mini2440光盤中的介紹升級supervivi?
?????????????? 2.1 出現(xiàn)問題 :supervivi燒寫進(jìn)入了K9F1208芯片(由于我是筆記菜的菜鳥,此時還不知道該芯片是NANDFLASH),?
???????????????????? 但是以NOFLASH方式啟動QQ2440時串口輸出的還是以前的信息。?
?????????????? 2.2 解決思路 :我猜測是不是燒寫的地方不對(因為H-JTAG的燒寫過程是對的,表示程序確實被燒到某個地方了),?
????????????????????? 然后經(jīng)過SEA大哥一點播發(fā)現(xiàn)K9F1208為nandflash芯片, 我說難怪會看到有64M的空間的,后來選擇對了?
?????????????????????? 芯片(QQ2440為AM29LV160DB),燒寫進(jìn)去后串口輸出果然跟mini2440資料上一樣了。?
?????????????? 2.3 打印信息:##### FriendlyARM BIOS for 2440 #####?
[x] bon part 0 320k 2368k?
[v] Download vivi?
[k] Download linux kernel?
[y] Download root_yaffs image?
[a] Absolute User Application?
[n] Download Nboot?
[l] Download WinCE boot-logo?
[w] Download WinCE NK.bin?
[d] Download & Run?
[z] Download zImage into RAM?
[g] Boot linux from RAM?
[f] Format the nand flash?
Boot the system?
[s] Set the boot parameters?
Backup NAND Flash to HOST through USB(upload)?
[r] Restore NAND Flash from HOST through USB?
[q] Goto shell of vivi?
Version: 0945-12?
步驟三 利用新的supervivi64M開始下載zimageN35?
????????????? 3.1 出現(xiàn)問題:按照MINI2440光盤上的方法(noflash方式啟動然后按“F”)進(jìn)行分區(qū),可是打印出的信息一直為失敗?
???????????????????? 并且USB好像出了問題,DNW不能正常下載東東了,安裝驅(qū)動后提示沒找到USB設(shè)備,重新拔插也沒?
??????????????????? 讓我安裝驅(qū)動,windows也沒有噔噔、噔噔的硬件拔插呻吟聲了。??
???????????????3.2 解決思路:這個我還沒有什么解決思路,只好先放在一邊了。?
??????????????? 3.3 打印信息:?
???????????????????? q] Goto shell of vivi?
???????????????????????? Version: 0945-12?
???????????????????????? Enter your selection: f?
????????????????????????? ...................................................................................................................................................?
????????????????????????? ......................................................................................................................................................?
????????????????????????? .................................................................................................................... ... failed?
?????????????? 3.4 我利用part show看了看硬件分區(qū),不知道為什么,確實是改變了,分區(qū)如下:?
??????????????? Enter your selection: q?
???????????????? Supervivi> part show?
???????????????? Number of partitions: 4?
???????????????? name : offset size flag?
?????????????????? ------------------------------------------------------------?
???????????????? vivi :??????? 0x00000000??? 0x00040000 0?
????????????????? param : 0x00040000?? ?0x00020000 0?
????????????????? kernel : 0x00060000??? 0x00500000 0?
????????????????? root :???? 0x00560000??? 0x03a9c000 0?
????????????????? Supervivi>?
????????????????????????? 以前的vivi分區(qū)只有0X00020000的,現(xiàn)在變?yōu)榱?x00040000,看來確實是變大了。但是DNW用不了了?
?????????????????????????? 沒辦法下載,只好考慮把以前的VIVI換回來。?
步驟四 重新把2008年的supervivi燒寫到noflash中,USB好了?
?????????????? 4.1 重新又把08的VIVI燒了進(jìn)去,然后利用part add 和part del手動分區(qū),將分區(qū)分的跟上面一摸一樣。??
???????????????4.2 出現(xiàn)問題 :燒寫kernel以及root確實沒什么問題了,可以燒成功了,nandflash中的vivi下載為新的supervivi64M?
????????????????????????????????????????kernel燒寫的是mini2440光盤中的?
???????????????????? zimageN35,root燒寫的是mini2440光盤中的root_qtopia-64M.img。不過啟動是跑不過kernel。?
??
??????????????? 4.打印信息如下:?
Enter your selection: b?
Copy linux kernel from 0x00060000 to 0x30008000, size = 0x00500000 ... done?
zImage magic = 0x016f2818?
Setup linux parameters at 0x30000100?
linux command line is: "noinitrd root=/dev/mtdblock2 init=/linuxrc console=ttySAC0"?
MACH_TYPE = 782?
NOW, Booting Linux......?
Uncompressing Linux..........................................................................?
......................................................................................... done, booting the kernel.?
????????????? 4.4 解決思路 : 到了MACH_TYPE這就過去了,估計是MACH_TYPE的問題了,于是找了找資料,發(fā)現(xiàn)MINI2440的mach_type?
??????????????????? 為1999?
步驟五 改寫了mach_type為1999 ,確實跑過了kernel,大喜?
???????????? 5.1 出現(xiàn)問題 : 跑到了根文件系統(tǒng)那過不去了?
???????????? 5.2 打印信息 :?
Enter your selection: b?
Copy linux kernel from 0x00060000 to 0x30008000, size = 0x00500000 ... done?
zImage magic = 0x016f2818?
Setup linux parameters at 0x30000100?
linux command line is: "noinitrd root=/dev/mtdblock2 init=/linuxrc console=ttySAC0"?
MACH_TYPE = 1999?
NOW, Booting Linux......?
Uncompressing Linux................................................................................................................................................................... done, booting the kernel.?
Linux version 2.6.32.2-FriendlyARM ([url=mailto:root@tom]root@tom[/url]) (gcc version 4.3.2 (Sourcery G++ Lite 2008q3-72) ) #2 Fri Jan 8 15:32:06 CST 2010?
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177?
CPU: VIVT data cache, VIVT instruction cache?
Machine: FriendlyARM Mini2440 development board?
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 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: noinitrd root=/dev/mtdblock2 init=/linuxrc console=ttySAC0?
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: 59560KB available (4676K code, 469K data, 160K 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 ext status 00000200?
irq: clearing subpending status 00000003?
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?
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?
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 Jan? 8 2010 12:48:07 Installing.?
msgmni has been set to 116?
alg: No test for stdrng (krng)?
io scheduler noop registered (default)?
Console: switching to colour frame buffer device 30x20?
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?
Bad eraseblock 412 at 0x000000670000?
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?
dm9000 dm9000: read wrong id 0x043429b2?
dm9000 dm9000: read wrong id 0x2b2a0000?
dm9000 dm9000: read wrong id 0x002a2906?
dm9000 dm9000: read wrong id 0x2b2a2900?
dm9000 dm9000: read wrong id 0x2b2a2928?
dm9000 dm9000: read wrong id 0x002a2928?
dm9000 dm9000: read wrong id 0x2b2a2928?
dm9000 dm9000: read wrong id 0x00ff2928?
dm9000 dm9000: wrong id: 0x00ff2928?
dm9000 dm9000: not found (-19).?
Atmel at76x USB Wireless LAN Driver 0.17 loading?
usbcore: registered new interface driver at76c50x-usb?
usbcore: registered new interface driver zd1211rw?
usbcore: registered new interface driver rtl8187?
usbcore: registered new interface driver zd1201?
usbcore: registered new interface driver rt2500usb?
usbcore: registered new interface driver rt73usb?
usbcore: registered new interface driver rt2800usb?
usbcore: registered new interface driver ar9170usb?
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: 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 [url=mailto:Hergenhahn@web.de]Hergenhahn@web.de[/url]?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: registered?
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?
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_read_super: isCheckpointed 0?
VFS: Mounted root (yaffs filesystem) on device 31:2.?
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:c3887f00 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?
???????????????????? 5.3 解決思路:是不是 ROOT下載的地址和vivi啟動的地址沒對上產(chǎn)生的這個問題,不過由于小弟比較菜?
?????????????????????????? 這個問題實在不知道怎么解決了。?
步驟六 ?根據(jù)樓主的提示,的確是vivi中的分區(qū)表與kernel中啟動地址沒對上,更改啟動配置的地方?
?????????????????????????6.1??????? 更改方法? noflash方式啟動 ,按鍵“q”?
????????????????????????????????????? 然后在命令輸入行鍵入> param set linux_cmd_line "console=ttySAC0 root=/dev/mtdblock3"?
????????????????????????????????????????????????????????????????????????????? > boot?
???????????????????????????????????????? 可以啟動了,跑起來了。?
????????????????????????? 6.2?? 遇到問題 :雖然root跑了起來,但是可以發(fā)現(xiàn)網(wǎng)絡(luò)以及USB都不能正常使用了,并且不能以NANDFLASH的方式跑,因為沒有supervivi的源碼,?
???????????????????????????????????????????????????????? 只能通過norflash方式修改啟動時的root對應(yīng)分區(qū)才能跑起來。?
??????
?????????????????????????? 6.3? 解決思路 :修改內(nèi)核,自己做一個適合QQ2440的linux-2.6.32?
步驟7??? 制作適合QQ2440的內(nèi)核linux-2.6.32,為了讓QQ2440以nandflash方式啟動是跑起以yaff2方式的ROOT,必須修改內(nèi)核的兩處地方然后重新編譯(還沒解決驅(qū)動的問題),第一處是在內(nèi)核配置文件中修改nandflash的分區(qū)數(shù)組中的root所在的位置,第二處是加入對yaff2文件系統(tǒng)的支持。?
????????????????7.1 在內(nèi)核配置文件中修改nandflash的分區(qū)數(shù)組中的root所在的位置:?
?????????????????????? a將mini2440光盤中的linux文件夾中的linux-2.6.32.2-mini2440-20100609.tar.gz文件拷貝到linux系統(tǒng)中?
?????????????????????? b 解壓縮linux-2.6.32.2-mini2440-20100609.tar.gz,shell命令行# tar xzvf linux-2.6.32.2-mini2440-?????????????????????????20100609.tar.gz -C /opt/FriendlyARM/QQ2440/kernel?
??????????????????????c # cd /opt/FriendlyARM/QQ2440/kernel/linux2.6.32/arch/arm/mach-s3c2440/?
??????????????????????d#gedit mach-mini2440.c?
????????????????????? e 將其中分區(qū)數(shù)組改成如下情況?
static struct mtd_partition friendly_arm_default_nand_part[] = {?
?[0] = {?
??.name?= "supervivi",?
??.size?= 0x00040000,?
??.offset?= 0,?
?},?
?[1] = {?
??.name?= "param",?
??.offset = 0x00040000,?
??.size?= 0x00020000,?
?},?
?[3]?= {?
??????????? .name?= "Kernel",?
??.offset = 0x00060000,?
??.size?= 0x00500000,?
?},?
?[2] = {?
??????????? .name = "root",?
??.offset = 0x00560000,?
??.size?= 1024 * 1024 * 1024, //?
?},?
?[4] = {?
??.name?= "nand",?
??.offset = 0x00000000,?
??.size?= 1024 * 1024 * 1024, //?
?}?
};?
????????????????????? f 保存退出?
????????????? 7.2 修改menuconfig中的項目,使得kernel支持yaff2文件系統(tǒng)?
??????????????????? a?進(jìn)入剛才加壓縮的內(nèi)核的根目錄,也就是linux2.6.32下,使用?make mini2440-defconfig?
??????????????????? b?#make?menuconfig?
????????????????????c進(jìn)入file systems->?miscellaneous filesystems?
???????????????????? d 找到y(tǒng)aff2該項,并按空格建選住?
??????????????????????e 退出并保存?
???????????????7.3 產(chǎn)生內(nèi)核?
?????????????? a a?進(jìn)入剛才加壓縮的內(nèi)核的根目錄,也就是linux2.6.32下,使用?make mini2440-defconfig?
????????????????? b # make zImage?
??????????????? 等待一會會在/arch/arm/boot中生成zImage。將該zImage拷貝到windows下。?
?????????????? 7.4 利用supervivi將該內(nèi)核文件燒寫到nandflash中,根文件系統(tǒng)還是燒寫mini2440光盤中的最新文件系統(tǒng)。?
??????????????? 7.5 nandflash方式啟動QQ2440,QQ2440可以跑起來了,不過現(xiàn)在觸摸屏什么的都不能用了,驅(qū)動沒加入。??
??
步驟8?? 制作適合QQ2440的內(nèi)核驅(qū)動(一)--------借助友善的配置文件修改
?????????????8.1??直接使用友善做好的內(nèi)核配置config_mini2440_n35(因為我的QQ2440是N35的屏幕)
???????????????????? a 按照7.1 先修改好MACH-MINI2440,C文件
??????????????????????b?#cp config_mini2440_n35??? .config
????????????????????? c make menucofig 先進(jìn)去逛逛,看看能否開啟該編譯選擇框
????????????????????? d make zImage
????????????????????? e 拷貝。。/arch/arm/boot中的zImage到windows下,然后燒寫到QQ2440
???????????? 8.2? 以noflash方式啟動,直接按b,可以看到啟動正常了,并且之前的驅(qū)動都還在里頭(觸摸屏可以用
??????????????????????,音樂可以聽,串口也是好的等)
???????????? 8.3 以nandflash方式啟動,同樣可以啟動的了。
步驟九?? 制作適合QQ2440的內(nèi)核驅(qū)動(二)-------移植網(wǎng)卡驅(qū)動
總結(jié):碰到了主要兩個問題:1新的supervivi燒寫到QQ24440后,QQ2440的USB下載功能沒了?
???????????????????????????????????????????????????? 2,利用舊的supervivi手動分區(qū)后下載新的內(nèi)核以及ROOT,可以跑起來了,?
???????????????????????????????????????????????????????? 不過網(wǎng)絡(luò)功能和USB功能沒有。??
?????????????????????????????????????????????????????對該文章有興趣的朋友可以郵箱聯(lián)系,共同探討。本人郵箱:[url=mailto:litie86222@163.com]litie86222@163.com[/url] [ 此帖被yjbcnmdb在2010-09-05 23:04重新編輯 ]
下面將我一步一步的過程記錄如下,希望給同樣使用著QQ240板子的初級學(xué)者一點幫助,高手就莫笑話我了,另外網(wǎng)絡(luò)驅(qū)動和USB驅(qū)動的問題請高手看出什么問題后給點幫助和建議。?
步驟一 直接利用QQ2440中的supervivi(2008年的版本)燒寫MINI2440光盤中的內(nèi)核和根文件系統(tǒng)到QQ2440nandflash?
?????????????? 1.1 出現(xiàn)問題 : 在燒寫zimageN35時出現(xiàn)了被燒寫的文件大小大于分區(qū)大小,不讓燒寫?
??????????????? 1.2 解決思路 :我猜想應(yīng)該是老版本的supervivi中對于內(nèi)核的分區(qū)太小了,于是我決定先升級SUPERVIVI到最新版本
步驟二 利用H-JTAG升級supervivi64M到norflash,按照mini2440光盤中的介紹升級supervivi?
?????????????? 2.1 出現(xiàn)問題 :supervivi燒寫進(jìn)入了K9F1208芯片(由于我是筆記菜的菜鳥,此時還不知道該芯片是NANDFLASH),?
???????????????????? 但是以NOFLASH方式啟動QQ2440時串口輸出的還是以前的信息。?
?????????????? 2.2 解決思路 :我猜測是不是燒寫的地方不對(因為H-JTAG的燒寫過程是對的,表示程序確實被燒到某個地方了),?
????????????????????? 然后經(jīng)過SEA大哥一點播發(fā)現(xiàn)K9F1208為nandflash芯片, 我說難怪會看到有64M的空間的,后來選擇對了?
?????????????????????? 芯片(QQ2440為AM29LV160DB),燒寫進(jìn)去后串口輸出果然跟mini2440資料上一樣了。?
?????????????? 2.3 打印信息:##### FriendlyARM BIOS for 2440 #####?
[x] bon part 0 320k 2368k?
[v] Download vivi?
[k] Download linux kernel?
[y] Download root_yaffs image?
[a] Absolute User Application?
[n] Download Nboot?
[l] Download WinCE boot-logo?
[w] Download WinCE NK.bin?
[d] Download & Run?
[z] Download zImage into RAM?
[g] Boot linux from RAM?
[f] Format the nand flash?
Boot the system?
[s] Set the boot parameters?
Backup NAND Flash to HOST through USB(upload)?
[r] Restore NAND Flash from HOST through USB?
[q] Goto shell of vivi?
Version: 0945-12?
步驟三 利用新的supervivi64M開始下載zimageN35?
????????????? 3.1 出現(xiàn)問題:按照MINI2440光盤上的方法(noflash方式啟動然后按“F”)進(jìn)行分區(qū),可是打印出的信息一直為失敗?
???????????????????? 并且USB好像出了問題,DNW不能正常下載東東了,安裝驅(qū)動后提示沒找到USB設(shè)備,重新拔插也沒?
??????????????????? 讓我安裝驅(qū)動,windows也沒有噔噔、噔噔的硬件拔插呻吟聲了。??
???????????????3.2 解決思路:這個我還沒有什么解決思路,只好先放在一邊了。?
??????????????? 3.3 打印信息:?
???????????????????? q] Goto shell of vivi?
???????????????????????? Version: 0945-12?
???????????????????????? Enter your selection: f?
????????????????????????? ...................................................................................................................................................?
????????????????????????? ......................................................................................................................................................?
????????????????????????? .................................................................................................................... ... failed?
?????????????? 3.4 我利用part show看了看硬件分區(qū),不知道為什么,確實是改變了,分區(qū)如下:?
??????????????? Enter your selection: q?
???????????????? Supervivi> part show?
???????????????? Number of partitions: 4?
???????????????? name : offset size flag?
?????????????????? ------------------------------------------------------------?
???????????????? vivi :??????? 0x00000000??? 0x00040000 0?
????????????????? param : 0x00040000?? ?0x00020000 0?
????????????????? kernel : 0x00060000??? 0x00500000 0?
????????????????? root :???? 0x00560000??? 0x03a9c000 0?
????????????????? Supervivi>?
????????????????????????? 以前的vivi分區(qū)只有0X00020000的,現(xiàn)在變?yōu)榱?x00040000,看來確實是變大了。但是DNW用不了了?
?????????????????????????? 沒辦法下載,只好考慮把以前的VIVI換回來。?
步驟四 重新把2008年的supervivi燒寫到noflash中,USB好了?
?????????????? 4.1 重新又把08的VIVI燒了進(jìn)去,然后利用part add 和part del手動分區(qū),將分區(qū)分的跟上面一摸一樣。??
???????????????4.2 出現(xiàn)問題 :燒寫kernel以及root確實沒什么問題了,可以燒成功了,nandflash中的vivi下載為新的supervivi64M?
????????????????????????????????????????kernel燒寫的是mini2440光盤中的?
???????????????????? zimageN35,root燒寫的是mini2440光盤中的root_qtopia-64M.img。不過啟動是跑不過kernel。?
??
??????????????? 4.打印信息如下:?
Enter your selection: b?
Copy linux kernel from 0x00060000 to 0x30008000, size = 0x00500000 ... done?
zImage magic = 0x016f2818?
Setup linux parameters at 0x30000100?
linux command line is: "noinitrd root=/dev/mtdblock2 init=/linuxrc console=ttySAC0"?
MACH_TYPE = 782?
NOW, Booting Linux......?
Uncompressing Linux..........................................................................?
......................................................................................... done, booting the kernel.?
????????????? 4.4 解決思路 : 到了MACH_TYPE這就過去了,估計是MACH_TYPE的問題了,于是找了找資料,發(fā)現(xiàn)MINI2440的mach_type?
??????????????????? 為1999?
步驟五 改寫了mach_type為1999 ,確實跑過了kernel,大喜?
???????????? 5.1 出現(xiàn)問題 : 跑到了根文件系統(tǒng)那過不去了?
???????????? 5.2 打印信息 :?
Enter your selection: b?
Copy linux kernel from 0x00060000 to 0x30008000, size = 0x00500000 ... done?
zImage magic = 0x016f2818?
Setup linux parameters at 0x30000100?
linux command line is: "noinitrd root=/dev/mtdblock2 init=/linuxrc console=ttySAC0"?
MACH_TYPE = 1999?
NOW, Booting Linux......?
Uncompressing Linux................................................................................................................................................................... done, booting the kernel.?
Linux version 2.6.32.2-FriendlyARM ([url=mailto:root@tom]root@tom[/url]) (gcc version 4.3.2 (Sourcery G++ Lite 2008q3-72) ) #2 Fri Jan 8 15:32:06 CST 2010?
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177?
CPU: VIVT data cache, VIVT instruction cache?
Machine: FriendlyARM Mini2440 development board?
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 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: noinitrd root=/dev/mtdblock2 init=/linuxrc console=ttySAC0?
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: 59560KB available (4676K code, 469K data, 160K 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 ext status 00000200?
irq: clearing subpending status 00000003?
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?
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?
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 Jan? 8 2010 12:48:07 Installing.?
msgmni has been set to 116?
alg: No test for stdrng (krng)?
io scheduler noop registered (default)?
Console: switching to colour frame buffer device 30x20?
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?
Bad eraseblock 412 at 0x000000670000?
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?
dm9000 dm9000: read wrong id 0x043429b2?
dm9000 dm9000: read wrong id 0x2b2a0000?
dm9000 dm9000: read wrong id 0x002a2906?
dm9000 dm9000: read wrong id 0x2b2a2900?
dm9000 dm9000: read wrong id 0x2b2a2928?
dm9000 dm9000: read wrong id 0x002a2928?
dm9000 dm9000: read wrong id 0x2b2a2928?
dm9000 dm9000: read wrong id 0x00ff2928?
dm9000 dm9000: wrong id: 0x00ff2928?
dm9000 dm9000: not found (-19).?
Atmel at76x USB Wireless LAN Driver 0.17 loading?
usbcore: registered new interface driver at76c50x-usb?
usbcore: registered new interface driver zd1211rw?
usbcore: registered new interface driver rtl8187?
usbcore: registered new interface driver zd1201?
usbcore: registered new interface driver rt2500usb?
usbcore: registered new interface driver rt73usb?
usbcore: registered new interface driver rt2800usb?
usbcore: registered new interface driver ar9170usb?
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: 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 [url=mailto:Hergenhahn@web.de]Hergenhahn@web.de[/url]?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: registered?
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?
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_read_super: isCheckpointed 0?
VFS: Mounted root (yaffs filesystem) on device 31:2.?
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:c3887f00 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?
???????????????????? 5.3 解決思路:是不是 ROOT下載的地址和vivi啟動的地址沒對上產(chǎn)生的這個問題,不過由于小弟比較菜?
?????????????????????????? 這個問題實在不知道怎么解決了。?
步驟六 ?根據(jù)樓主的提示,的確是vivi中的分區(qū)表與kernel中啟動地址沒對上,更改啟動配置的地方?
?????????????????????????6.1??????? 更改方法? noflash方式啟動 ,按鍵“q”?
????????????????????????????????????? 然后在命令輸入行鍵入> param set linux_cmd_line "console=ttySAC0 root=/dev/mtdblock3"?
????????????????????????????????????????????????????????????????????????????? > boot?
???????????????????????????????????????? 可以啟動了,跑起來了。?
????????????????????????? 6.2?? 遇到問題 :雖然root跑了起來,但是可以發(fā)現(xiàn)網(wǎng)絡(luò)以及USB都不能正常使用了,并且不能以NANDFLASH的方式跑,因為沒有supervivi的源碼,?
???????????????????????????????????????????????????????? 只能通過norflash方式修改啟動時的root對應(yīng)分區(qū)才能跑起來。?
??????
?????????????????????????? 6.3? 解決思路 :修改內(nèi)核,自己做一個適合QQ2440的linux-2.6.32?
步驟7??? 制作適合QQ2440的內(nèi)核linux-2.6.32,為了讓QQ2440以nandflash方式啟動是跑起以yaff2方式的ROOT,必須修改內(nèi)核的兩處地方然后重新編譯(還沒解決驅(qū)動的問題),第一處是在內(nèi)核配置文件中修改nandflash的分區(qū)數(shù)組中的root所在的位置,第二處是加入對yaff2文件系統(tǒng)的支持。?
????????????????7.1 在內(nèi)核配置文件中修改nandflash的分區(qū)數(shù)組中的root所在的位置:?
?????????????????????? a將mini2440光盤中的linux文件夾中的linux-2.6.32.2-mini2440-20100609.tar.gz文件拷貝到linux系統(tǒng)中?
?????????????????????? b 解壓縮linux-2.6.32.2-mini2440-20100609.tar.gz,shell命令行# tar xzvf linux-2.6.32.2-mini2440-?????????????????????????20100609.tar.gz -C /opt/FriendlyARM/QQ2440/kernel?
??????????????????????c # cd /opt/FriendlyARM/QQ2440/kernel/linux2.6.32/arch/arm/mach-s3c2440/?
??????????????????????d#gedit mach-mini2440.c?
????????????????????? e 將其中分區(qū)數(shù)組改成如下情況?
static struct mtd_partition friendly_arm_default_nand_part[] = {?
?[0] = {?
??.name?= "supervivi",?
??.size?= 0x00040000,?
??.offset?= 0,?
?},?
?[1] = {?
??.name?= "param",?
??.offset = 0x00040000,?
??.size?= 0x00020000,?
?},?
?[3]?= {?
??????????? .name?= "Kernel",?
??.offset = 0x00060000,?
??.size?= 0x00500000,?
?},?
?[2] = {?
??????????? .name = "root",?
??.offset = 0x00560000,?
??.size?= 1024 * 1024 * 1024, //?
?},?
?[4] = {?
??.name?= "nand",?
??.offset = 0x00000000,?
??.size?= 1024 * 1024 * 1024, //?
?}?
};?
????????????????????? f 保存退出?
????????????? 7.2 修改menuconfig中的項目,使得kernel支持yaff2文件系統(tǒng)?
??????????????????? a?進(jìn)入剛才加壓縮的內(nèi)核的根目錄,也就是linux2.6.32下,使用?make mini2440-defconfig?
??????????????????? b?#make?menuconfig?
????????????????????c進(jìn)入file systems->?miscellaneous filesystems?
???????????????????? d 找到y(tǒng)aff2該項,并按空格建選住?
??????????????????????e 退出并保存?
???????????????7.3 產(chǎn)生內(nèi)核?
?????????????? a a?進(jìn)入剛才加壓縮的內(nèi)核的根目錄,也就是linux2.6.32下,使用?make mini2440-defconfig?
????????????????? b # make zImage?
??????????????? 等待一會會在/arch/arm/boot中生成zImage。將該zImage拷貝到windows下。?
?????????????? 7.4 利用supervivi將該內(nèi)核文件燒寫到nandflash中,根文件系統(tǒng)還是燒寫mini2440光盤中的最新文件系統(tǒng)。?
??????????????? 7.5 nandflash方式啟動QQ2440,QQ2440可以跑起來了,不過現(xiàn)在觸摸屏什么的都不能用了,驅(qū)動沒加入。??
??
步驟8?? 制作適合QQ2440的內(nèi)核驅(qū)動(一)--------借助友善的配置文件修改
?????????????8.1??直接使用友善做好的內(nèi)核配置config_mini2440_n35(因為我的QQ2440是N35的屏幕)
???????????????????? a 按照7.1 先修改好MACH-MINI2440,C文件
??????????????????????b?#cp config_mini2440_n35??? .config
????????????????????? c make menucofig 先進(jìn)去逛逛,看看能否開啟該編譯選擇框
????????????????????? d make zImage
????????????????????? e 拷貝。。/arch/arm/boot中的zImage到windows下,然后燒寫到QQ2440
???????????? 8.2? 以noflash方式啟動,直接按b,可以看到啟動正常了,并且之前的驅(qū)動都還在里頭(觸摸屏可以用
??????????????????????,音樂可以聽,串口也是好的等)
???????????? 8.3 以nandflash方式啟動,同樣可以啟動的了。
步驟九?? 制作適合QQ2440的內(nèi)核驅(qū)動(二)-------移植網(wǎng)卡驅(qū)動
總結(jié):碰到了主要兩個問題:1新的supervivi燒寫到QQ24440后,QQ2440的USB下載功能沒了?
???????????????????????????????????????????????????? 2,利用舊的supervivi手動分區(qū)后下載新的內(nèi)核以及ROOT,可以跑起來了,?
???????????????????????????????????????????????????????? 不過網(wǎng)絡(luò)功能和USB功能沒有。??
?????????????????????????????????????????????????????對該文章有興趣的朋友可以郵箱聯(lián)系,共同探討。本人郵箱:[url=mailto:litie86222@163.com]litie86222@163.com[/url] [ 此帖被yjbcnmdb在2010-09-05 23:04重新編輯 ]
總結(jié)
以上是生活随笔為你收集整理的64MQQ2440烧写MINI2440光盘中的内容同样可以跑起来的全部內(nèi)容,希望文章能夠幫你解決所遇到的問題。
- 上一篇: qq2440 cs8900移植
- 下一篇: 用telnet 测试Http协议