主题 : mini6410 sd卡烧写后启动,停在android不动了,串口反复输出如下信息: 复制链接 | 浏览器收藏 | 打印
级别: 新手上路
UID: 3689
精华: 0
发帖: 41
金钱: 250 两
威望: 104 点
综合积分: 82 分
注册时间: 2009-02-02
最后登录: 2014-05-27
楼主  发表于: 2012-06-05 11:48

 mini6410 sd卡烧写后启动,停在android不动了,串口反复输出如下信息:



s3c64xx_d
usbcore: registered new interface driver s2255                                        
PL080
s3c-fimc: controller 0 registered successfully
S3C6410: Initialising architecture          
s3c-fimc: controller 1 registered successfully> at 0                            
SCSI subsy
FIMC Driver, 2010 ported by FriendlyARM http://www.arm9.neted new interface driver usbfs                              
ov965x: probe  
usbcore: r
s3c-fimc: i2c transfer errorr hub                      
s3c-fimc: i2c transfer e                      
[CAM]RESET CAM.e Driver Versio
S3C PostProcessor Driver v3.12, (c) 2009 Samsung Electronics    
Bluetooth: Core ver 2.15                        
NET: R
S3C6410 TV encoder Driver, (c) 2008 Samsung Electronics      
Bluetooth: HCI device and connection manager ini
S3C6410 TV encoder Driver init OK.                            
Blueto
S3C6410 TV scaler Driver, (c) 2008 Samsung Electronics                
Switching to clocksource clock_sourc
S3C6410 TV scaler Driver init OK.                
NET: Registered
S3C JPEG Driver, (c) 2007 Samsung Electronics    
IP route cache hash table entries: 1024
one_wire_status: 4                  
Bluetooth: HCI UART driver ver 2.2                              
NE
Bluetooth: HCI H4 protocol initialized                        
RPC: Registe
Bluetooth: HCILL protocol initialized                        
RPC: Registe
Bluetooth: Generic Bluetooth USB driver ver 0.6              
RPC: Registered tcp NFSv4.1 back
one_wire_status: 2odule.            
usbcore: registered new interface driver btusbshmem: initialized                  
        
s3c-sdhci s3c-sdhci.0: clock source 2: mmc_bus (84666666 Hz)   FB1: map_video_memory: dma=52b00000 cpu=ff600000 size=000
mmc0: SDHCI controller on samsung-hsmmc [s3c-sdhci.0] using ADMA              
Window[0] - FB2: map_video_memory: clear ff63fc00
s3c-sdhci s3c-sdhci.1: clock source 0: hsmmc (133000000 Hz)      
            FB2: map_video_memory: dma=52b3fc00 cpu
s3c-sdhci s3c-sdhci.1: clock source 1: hsmmc (133000000 Hz)                                    
Console: switching to
s3c-sdhci s3c-sdhci.1: clock source 2: mmc_                                        
usbhid: USB HID core driver                          
logger: created 64K log 'log_main'video_memory: dma=52bbfc00 cpu=ff7
logger: created 256K log 'log_events'                                    
logger: created 64K log 'log_radio'buffer device                      
logger: created 64K log 'log_system'                          
leds    i
asoc: AC97 HiFi <-> s3c-ac97 mapping okitialized                  
adc     in
s3c6400_setup_sdhci_cfg_card: CTRL 2=c0004120, 3=00008080l0 at MMIO 0x7f005000 (irq = 16) is a S3C6400/10        
mmc0: new high speed SDHC card at address 0001                    
                        
ALSA device list:4) is a S3C6400/1
  #0: MINI6410 (WM9713)                      
TCP cubic registered          
s3c6400-u
NET: Registered protocol family 17005c00 (irq = 28) is a S3C6400/10
Bluetooth: L2CAP ver 2.15                        
Bluetooth: L2CAP socket layer initializedded                  
pmem: 1 init      
Bluetooth: SCO (Voice Link) ver 0.6    
pmem_adsp: 0 init            
Bluetooth: SCO socket layer initializedElectronics                            
Bluetooth: RFCOMM TTY layer initializedng hardware ECC.                      
Bluetooth: RFCOMM socket layer initializedD: 0xec, Chip ID: 0xda (Samsung NAND 256Mi
one_wire_status: 2                  
Bluetooth: RFCOMM ver 1.11                          
Bluetooth: BNEP (Ethernet Emulation) ver 1.3MiB 3,3V                                    
s3c-rtc s3c64xx-rtc: setting system clock to 2000-03-25 02:10:17 UTC (953950217)ered                                        
PPP BSD Compression module registe

Freeing init memory: 1396K            
dm9000 Ethern
yaffs: dev is 32505858 name is "mtdblock2" rweth0: dm9000a at c881e000,c8c00004 IRQ 108 MA
yaffs: passed flags ""latform data          
TouchDevice: /dev/touchscreen                            
xres = 480, yres = 272: USB 1.1 'Open' Host
Took 8 samples...Driver          
Top left : X = 1048 Y = 2597              
s3c2410-ohci
Took 9 samples...4XX OHCI        
Top right : X = 3174 Y = 2560
s3c2410-ohci s3c2410-ohci: n
Took 10 samples...ed, assigned bus n
Bot right : X = 3131 Y = 1558                            
usb usb1: New US
467.801270 0.001007 -0.163028ct=2, SerialNumber=1        
init: cannot open '/initlogo.rle'                      
usb usb1:
init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj insteaux 2.6.36-FriendlyARM ohci_hcd                                                  
d.  
enabling adbSerialNumber
adb_open        
/ # Compat-wireless backport release: compat-wireless-2011-06-28-2-FA      
hub 1-0:1.0: 2 ports detected                            
usb
Backport based on linux-next.git next-20110707                                              
cfg80211: Calling CRDA to update world regulatory domain                              
usbcore: registered new i
libertas_sdio: Libertas SDIO driver                                  
option:
usbcore: registered new interface driver rt2800usb                      
USB Serial support register

rtw driver version=v3.0.1590.20110511                  
usbcore: registere
usbcore: registered new interface driver rtl8192cu                            
USB Serial support r
usbcore: registered new interface driver zd1211rw            
usbcore: registered new interface dr
fa_cpu_pfn: module license 'Proprietary' taints kernel.    
ark3116:v0.6:USB ARK3116 serial/IrDA driver      
Disabling lock debugging due to kernel taintal support registered for Belkin / Peracom /
FriendlyARM proprietary driver for mini6410 initialized.                                              
usbcore:
usbcore:
binder: 1222:1229 transaction failed 29189, size 4-0
binder: send failed reply for transaction 1868, target dead
select 1324 (re-initialized>), adj 0, size 2983, to kill
send sigkill to 1324 (re-initialized>), adj 0, size 2983
binder: release 1324:1324 transaction 2044 out, still active
binder: 1222:1228 transaction failed 29189, size 4-0
binder: send failed reply for transaction 2044, target dead
select 1332 (re-initialized>), adj 0, size 2843, to kill
send sigkill to 1332 (re-initialized>), adj 0, size 2843
binder: release 1332:1332 transaction 2051 out, still active
binder: 1222:1229 transaction failed 29189, size 4-0
binder: send failed reply for transaction 2051, target dead
select 1343 (re-initialized>), adj 0, size 2945, to kill
send sigkill to 1343 (re-initialized>), adj 0, size 2945
binder: release 1343:1343 transaction 2190 out, still active
binder: release proc 1343, transaction 2299, not freed
binder: 1222:1342 transaction failed 29189, size 4-0
binder: send failed reply for transaction 2190, target dead
select 1354 (re-initialized>), adj 0, size 2887, to kill
send sigkill to 1354 (re-initialized>), adj 0, size 2887
binder: release 1354:1354 transaction 2381 out, still active
binder: 1222:1229 transaction failed 29189, size 4-0
binder: send failed reply for transaction 2381, target dead


怎么回事?
自由,自强,共享,共创。
级别: 论坛版主
UID: 12573
精华: 27
发帖: 8838
金钱: 46490 两
威望: 9298 点
综合积分: 18216 分
注册时间: 2010-01-09
最后登录: 2019-07-16
1楼  发表于: 2012-06-05 11:59
请把烧写配置文件的内容,和烧写过程的完整信息发来看看,参考我的签名链接
新手如何向我们反馈有效的信息,以便解决问题,见此贴:
http://www.arm9home.net/read.php?tid-14431.html

[注]: 此处签名链接仅为指引方向,而非解答问题本身.
级别: 新手上路
UID: 3689
精华: 0
发帖: 41
金钱: 250 两
威望: 104 点
综合积分: 82 分
注册时间: 2009-02-02
最后登录: 2014-05-27
2楼  发表于: 2012-06-06 11:52
系统信息:
Superboot-6410
Version: 1150
cpu: S3C6410 533Mhz
Ram:128M
Nand: 256(SLC)  ID:ECDA1095
Touch Device: no 1-wire
LCD type: N43


FriendlyArm ini:
CheckOneButton=No
Action=install
OS= Linux

VerifyNandWrite=No

StatusType = Beeper| LED

#################### Linux #####################
Linux-BootLoader = superboot-6410.bin
Linux-Kernel = Linux/zImage_n43
Linux-CommandLine = root=/dev/mtdblock2 rootfstype=yaffs2 init=/linuxrc console=ttySAC0,115200
Linux-RootFs-InstallImage = Linux/rootfs_qtopia_qt4.img
Linux-RootFs-RunImage = Linux/rootfs_qtopia_qt4.ext3

################### Android ####################
Android-BootLoader = superboot-6410.bin
Android-Kernel = Android/azImage_n43
Android-CommandLine = root=/dev/mtdblock2 rootfstype=yaffs2 init=/linuxrc console=ttySAC0,115200 androidboot.console=s3c2410_serial0
Android-RootFs-InstallImage = Android/rootfs_android.img
Android-RootFs-RunImage = Android/rootfs_android.ext3

################### WindowsCE6 #################
WindowsCE6-Bootloader= superboot-6410.bin
WindowsCE6-BootLogo = WindowsCE6\bootlogo.bmp
WindowsCE6-InstallImage = WindowsCE6\NK_n43-i.bin
WindowsCE6-RunImage = WindowsCE6\NK_n43-i.bin

#################### Ubuntu #####################
Ubuntu-BootLoader = superboot-6410.bin
Ubuntu-Kernel = Ubuntu/uzImage_n43
Ubuntu-CommandLine = root=ubi0:FriendlyARM-root ubi.mtd=2 rootfstype=ubifs  init=/linuxrc console=ttySAC0,115200
Ubuntu-RootFs-InstallImage = Ubuntu/rootfs_ubuntu-slc.ubi
Ubuntu-RootFs-RunImage = Ubuntu/rootfs_ubuntu.ext3

############### UserBin #################
UserBin-Image=WindowsCE/NK_n43-i.nb0
userBin-StartAddress=50100000


superboot-6410.bin  是  2011-12-12

azImage_n43                   2011-11-16

rootfs_android.img          2011-11-07

rootfs_android.ext3          2011-11-07    

用sd卡烧写系统,4个系统中只有linux烧写后工作正常,winCE与Andorid烧写启动后死机, Ubuntu干脆烧些失败。  
^很多问题的背后都是简单的原因......
级别: 荣誉会员
UID: 34780
精华: 0
发帖: 1219
金钱: 6230 两
威望: 1246 点
综合积分: 2438 分
注册时间: 2010-12-21
最后登录: 2017-09-18
3楼  发表于: 2012-06-06 12:18
128M内存跑不了Android 2.3.4
Ubuntu肯定烧不了,Flash空间不够
优悦居专业厨卫直销商城 http://www.youyueju.com
级别: 新手上路
UID: 58268
精华: 0
发帖: 8
金钱: 40 两
威望: 8 点
综合积分: 16 分
注册时间: 2011-11-05
最后登录: 2012-06-06
4楼  发表于: 2012-06-06 21:26
Ubuntu肯定烧不,flash空间不足
级别: 新手上路
UID: 3689
精华: 0
发帖: 41
金钱: 250 两
威望: 104 点
综合积分: 82 分
注册时间: 2009-02-02
最后登录: 2014-05-27
5楼  发表于: 2012-06-06 21:40
可否升稼存与flash?可升到多大容量的?型号?