[已解决]嵌入式板子控制台丢失!(页 1) - 嵌入式系统 - linux论坛 - powered by discuz! archiver.htm

S3C44B0X下的LCD （framebuffer）驱动资料与相关代码

space unaligned access handling in the kernel (for simple config)<BR>echo 2 &gt; 
/proc/cpu/alignment<BR><BR># loads the NPE ethernet modules into the 
kernel.<BR><BR>insmod&nbsp;&nbsp;/lib/modules/2.6.13.2/intel/ixp400.ko<BR><BR># 
Firmware code for NPE Engine.<BR><BR>cat&nbsp;&nbsp;/etc/IxNpeMicrocode.dat &gt; 
/dev/ixNpe<BR><BR>insmod /lib/modules/2.6.13.2/intel/ixp400_eth.ko 
npe_learning=0 netdev_max_backlog=6000<BR><BR>echo "Reconfiguring 
NPE-B(ixp0-LAN) with `flash_mac -i ixp0`&nbsp;&nbsp;MAC address"<BR>echo 
"Reconfiguring NPE-C(ixp1-WAN) with `flash_mac -i ixp1`&nbsp;&nbsp;MAC 
address"<BR><BR><BR>后面省略.<BR>第一行rdS 
start都显示不出来.但是一些信息估计是加载模块里面的printk出来的.</DIV></DIV><BR>
<DIV class="simpletable smalltxt" style="WIDTH: 98%">
<DIV class="subtable altbg1"><SPAN class=right>2007-6-14 18:00</SPAN> 
<B>augustusqing</B></DIV>
<DIV class="subtable altbg2 t_msg" style="WIDTH: auto; HEIGHT: auto"><B>回复 #2 
smalloc 的帖子</B><BR><BR>你不是怀疑<B 
style="COLOR: black; BACKGROUND-COLOR: #ffff66">busybox</B>编译时配置的不对吗？所以我指的<B 
style="COLOR: black; BACKGROUND-COLOR: #ffff66">busybox</B>盘就是指用<B 
style="COLOR: black; BACKGROUND-COLOR: #ffff66">busybox</B>编译出来的文件系统<BR><BR>先请你把你启动信息详细贴出来<BR><BR>先不用关注inittab，rc$<B 
style="COLOR: black; BACKGROUND-COLOR: #99ff99">脚本</B>，文件系统中没有这些东东，照样启动，如果能run_init_process("/sbin/init")成功，系统就进去了，关键看你的init程序有没有<B 
style="COLOR: black; BACKGROUND-COLOR: #a0ffff">执行</B>，<B 
style="COLOR: black; BACKGROUND-COLOR: #a0ffff">执行</B>到哪一步了，我的建议是你找到你的<B 
style="COLOR: black; BACKGROUND-COLOR: #ffff66">busybox</B>中init的源代码，在各个部分添加打印信息(如开始部分，打开控制口前，<B 
style="COLOR: black; BACKGROUND-COLOR: #a0ffff">执行</B>inittab前等等)，重新编译<B 
style="COLOR: black; BACKGROUND-COLOR: #ffff66">busybox</B>制作文件系统，加载<B 
style="COLOR: black; BACKGROUND-COLOR: #a0ffff">执行</B>，再贴出详细信息</DIV></DIV><BR>
<DIV class="simpletable smalltxt" style="WIDTH: 98%">
<DIV class="subtable altbg1"><SPAN class=right>2007-6-14 20:15</SPAN> 
<B>smalloc</B></DIV>
<DIV class="subtable altbg2 t_msg" style="WIDTH: auto; HEIGHT: auto">[quote]原帖由 
[i]augustusqing[/i] 于 2007-6-14 18:00 发表于 7楼&nbsp;&nbsp;<BR>你不是怀疑<B 
style="COLOR: black; BACKGROUND-COLOR: #ffff66">busybox</B>编译时配置的不对吗？所以我指的<B 
style="COLOR: black; BACKGROUND-COLOR: #ffff66">busybox</B>盘就是指用<B 
style="COLOR: black; BACKGROUND-COLOR: #ffff66">busybox</B>编译出来的文件系统<BR><BR>先请你把你启动信息详细贴出来<BR><BR>先不用关注inittab，rc$<B 
style="COLOR: black; BACKGROUND-COLOR: #99ff99">脚本</B>，文件系统中没有这些东东，照样启动，如果能ru 
... 
[/quote]<BR><BR><BR>run_init_process("/sbin/init")已经成功启动了，在板子上"/sbin/init"是<B 
style="COLOR: black; BACKGROUND-COLOR: #ffff66">busybox</B>的一个连接，他确实启动了，而且我认为是它解析的inittab，inittab里的初试化<B 
style="COLOR: black; BACKGROUND-COLOR: #99ff99">脚本</B>也启动了，（所以我断定是run_init_process("/sbin/init")已经成功启动，并且想你说的就是“系统进去了”）但是<B 
style="COLOR: black; BACKGROUND-COLOR: #ffff66">busybox</B>里的printf()开始是显示不出来的，我看了原代码，在<B 
style="COLOR: black; BACKGROUND-COLOR: #ffff66">busybox</B>的init_main他关掉了0,1,2文件描述符，又重新打开，注意这个时候是没控制台提示符的，打印不出任何信息，我不知道inittab里的getty 
ttyS1是不是成功运行了。反正在内核init的main里可以打开/dev/ttyS1。<BR>系统进去了，运行了，但是没有提示符，也不能printf(输出)。我没有成功的这个板子上成功运行过的<B 
style="COLOR: black; BACKGROUND-COLOR: #ffff66">busybox</B>盘。<BR><BR>打印输出现在也没法贴，明天贴，请帮我看看。<BR>大概是到了VFS：mount 
root (后面的记不得)<BR>free init memary:315K<BR>如果不启动<B 
style="COLOR: black; BACKGROUND-COLOR: #99ff99">脚本</B>后面就什么也没有（没有提示符，也不能输入什么象挡机一样），如果初始<B 
style="COLOR: black; BACKGROUND-COLOR: #99ff99">脚本</B>里有加载模块，模块里printk可以显示<BR>还有2个串口我也都试过，getty 
ttyS0,getty ttyS1都不行(问题可能就在这里，ttyS0,1在内核中确实可以被打开)，也许是 
getty要加路径？明天试一下<BR>实在想不出什么好办法，连调试的办法都没有了<BR><BR>[[i] 本帖最后由 smalloc 于 2007-6-14 
20:49 编辑 [/i]]</DIV></DIV><BR>
<DIV class="simpletable smalltxt" style="WIDTH: 98%">
<DIV class="subtable altbg1"><SPAN class=right>2007-6-15 14:24</SPAN> 
<B>smalloc</B></DIV>
<DIV class="subtable altbg2 t_msg" 
style="WIDTH: auto; HEIGHT: auto">控制台信息如下,请帮忙分析一下,或提点建议谢谢<BR><BR><BR>Using base 
address 0x00029800 and length 0x00111c38<BR>Uncompressing 
Linux............................................................................ 
done, booting the kernel.<BR><BR>Linux version 2.6.13.2 
([email][e-mail][/email]ldomain) (gcc version 3.4.3) #136 Thu Jun 14 
14:57:23 CST 2007<BR><BR>CPU: XScale-IXP42x Family [690541f1] revision 1 
(ARMv5TE)<BR><BR>Machine: Intel IXDP425 Development Platform<BR><BR>Memory 
policy: ECC disabled, Data cache writeback<BR><BR>CPU0: D VIVT undefined 5 
cache<BR><BR>CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 
sets<BR><BR>CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 
sets<BR><BR>Built 1 zonelists<BR><BR>Kernel command line: console=ttyS1,115200 
root=/dev/mtdblock2 noinitrd rootfstype=jffs2 mem=32M@0x00000000 
init=/sbin/init<BR><BR>PID hash table entries: 256 (order: 8, 4096 
bytes)<BR><BR>Dentry cache hash table entries: 8192 (order: 3, 32768 
bytes)<BR><BR>Inode-cache hash table entries: 4096 (order: 2, 16384 
bytes)<BR><BR>Memory: 32MB = 32MB total<BR><BR>Memory: 29952KB available (1678K 
code, 401K data, 316K init)<BR><BR>Mount-cache hash table entries: 
512<BR><BR>CPU: Testing write buffer coherency: ok<BR><BR>NET: Registered 
protocol family 16<BR><BR>PCI: IXP4xx is host<BR><BR>PCI: IXP4xx Using direct 
access for memory space<BR><BR>PCI: bus0: Fast back to back transfers 
enabled<BR><BR>dmabounce: registered device 0000:00:08.0 on pci 
bus<BR><BR>NetWinder Floating Point Emulator V0.97 (double 
precision)<BR><BR>JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, 
Inc.<BR><BR>Initializing Cryptographic API<BR><BR>IXP4xx Watchdog Timer: 
heartbeat 60 sec<BR><BR>Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ 
sharing disabled<BR><BR>ttyS0 at MMIO 0xc8000000 (irq = 15) is a 
XScale<BR><BR>ttyS1 at MMIO 0xc8001000 (irq = 15) is a XScale<BR><BR>io 
scheduler noop registered<BR><BR>io scheduler cfq registered<BR><BR>Intel(R) 
PRO/1000 Network Driver - version 6.0.60-k2-NAPI<BR><BR>Copyright (c) 1999-2005 
Intel Corporation.<BR><BR>ixp_flash_probe<BR><BR>STARAT ADDR IS 
:50000000<BR><BR>end addr is :50ffffff<BR><BR>windows size is 1000000,windows 
addr is c2880000&lt;3&gt;PLAT NAME IS 
cfi_probe<BR><BR>mtd_do_chip_probe<BR><BR>Search for id:(9f f0) interleave(1) 
type(1)<BR><BR>Search for id:(9f f0) interleave(1) type(1)<BR><BR>Search for 
id:(9f f0) interleave(1) type(1)<BR><BR>Search for id:(b0 00) interleave(1) 
type(1)<BR><BR>Search for id:(b0 00) interleave(1) type(1)<BR><BR>Search for 
id:(b0 e3) interleave(1) type(2)<BR><BR>jedec match ok!<BR><BR>Found: winbond 
w28j320bt90l<BR><BR>cfi setup ok<BR><BR>IXP4XX-Flash.0: Found 1 x16 devices at 
0x0 in 16-bit bank<BR><BR>setcmd 0001<BR><BR>cfi_fixup 
jedec_fixup_table<BR><BR>using fwh lock/unlock 
method<BR><BR>cfi_intelext_chipdrv<BR><BR>number of CFI chips: 1<BR><BR>cfi 
interleave is 1<BR><BR>devsize is 4194304<BR><BR>cfi-&gt;devsize is 
22<BR><BR>mtd size is 400000<BR><BR><BR>FLASH PROBE PASS!<BR><BR>type is 
3<BR><BR>FLAGS IS 5<BR><BR>size is 400000<BR><BR>erasesize is 
10000<BR><BR>numeraseregions is 1<BR><BR>PARSE_MTD_Partitions<BR><BR>redboot 
test start!<BR><BR>offset is 3e0000&nbsp; &nbsp; ,master size is 400000 is&nbsp; 
&nbsp;&nbsp; &nbsp; ,erasersize is 10000 is&lt;3&gt;Searching for RedBoot 
partition table in IXP4XX-Flash.0 at offset 0x3e0000<BR><BR>5 RedBoot partitions 
found on MTD device IXP4XX-Flash.0<BR><BR>parse_mtd_partitions end<BR><BR>ERR IS 
5&lt;3&gt;add_mtd_pa start<BR><BR>Creating 5 MTD partitions on 
"IXP4XX-Flash.0":<BR><BR>0x00000000-0x00050000 : "RedBoot"<BR><BR>ADD_MTD_DEVICE 
OK!!!OHYE!!<BR><BR>0x00050000-0x00170000 : "zImage"<BR><BR>ADD_MTD_DEVICE 
OK!!!OHYE!!<BR><BR>0x00170000-0x003e0000 : "filesystem"<BR><BR>ADD_MTD_DEVICE 
OK!!!OHYE!!<BR><BR>0x003e0000-0x003ef000 : "FIS directory"<BR><BR>mtd: partition 
"FIS directory" doesn't end on an erase block -- force 
read-only<BR><BR>ADD_MTD_DEVICE OK!!!OHYE!!<BR><BR>0x003ef000-0x003f0000 : 
"RedBoot config"<BR><BR>mtd: partition "RedBoot config" doesn't start on an 
erase block boundary -- force read-only<BR><BR>ADD_MTD_DEVICE 
OK!!!OHYE!!<BR><BR>ADD PARTITIONS OK<BR><BR>NET: Registered protocol family 
2<BR><BR>IP route cache hash table entries: 512 (order: -1, 2048 
bytes)<BR><BR>TCP established hash table entries: 2048 (order: 2, 16384 
bytes)<BR><BR>TCP bind hash table entries: 2048 (order: 1, 8192 
bytes)<BR><BR>TCP: Hash tables configured (established 2048 bind 
2048)<BR><BR>TCP reno registered<BR><BR>TCP bic registered<BR><BR>NET: 
Registered protocol family 1<BR><BR>NET: Registered protocol family 
17<BR><BR>802.1Q VLAN Support v1.8 Ben Greear 
&lt;[email][e-mail][/email]&gt;<BR><BR>All bugs added by David S. 
Miller &lt;[email][e-mail][/email]&gt;<BR><BR>sector_size is 
10000,blocks is27,flash size is270000<BR><BR>VFS: Mounted root (jffs2 
filesystem).<BR><BR>Freeing init memory: 316K<BR><BR>execute 
command<BR><BR>run_init_process ok</DIV></DIV><BR>
<DIV class="simpletable smalltxt" style="WIDTH: 98%">
<DIV class="subtable altbg1"><SPAN class=right>2007-6-15 14:33</SPAN> 
<B>augustusqing</B></DIV>
<DIV class="subtable altbg2 t_msg" style="WIDTH: auto; HEIGHT: auto">[quote]原帖由 
[i]smalloc[/i] 于 2007-6-14 16:44 发表于 6楼&nbsp;&nbsp;<BR><BR><BR>第一行rdS 
start都显示不出来.但是一些信息估计是加载模块里面的printk出来的.<BR>[/quote]<BR><BR>这里说的有你的加载模块的printk信息也贴出来<BR><BR>系统停住后，能够敲入字符回显吗？敲入回车行能够到下一行吗？换句话说，控制台能响应你的请求吗，还是完全死了</DIV></DIV><BR>
<DIV class="simpletable smalltxt" style="WIDTH: 98%">
<DIV class="subtable altbg1"><SPAN class=right>2007-6-15 14:47</SPAN> 
<B>smalloc</B></DIV>
<DIV class="subtable altbg2 t_msg" style="WIDTH: auto; HEIGHT: auto">[quote]原帖由 
[i]augustusqing[/i] 于 2007-6-15 14:33 发表于 
10楼&nbsp;&nbsp;<BR><BR><BR>这里说的有你的加载模块的printk信息也贴出来<BR><BR>系统停住后，能够敲入字符回显吗？敲入回车行能够到下一行吗？换句话说，控制台能响应你的请求吗，还是完全死了