请问TCI-66XX ARM-linux 使用自己制作的rootfs，内核启动异常？rootfs是参考用户手册制作的

Hi, Peter,

你的问题是说使用ubinize工具和SDK提供的相关文件，得到的ubifs.ubi烧写到NAND后可以正常启动，使用mkfs.ubifs工具自己生成img文件后再使用ubinize工具生成的ubifs.ubi烧写到NAND后启动异常？

谢谢你的回复，我用的是SDK2.0.0.1的

还有个问题是ubinize.cfg文件内容中的[rootfs]区域没有配置vol_size， 我在用./ubinize制作的时候会有报错，你有没有遇到阿？

另外就是recovery，securedbv0和securedbv1 这三部分用sdk的就可以还是需要自己制作呢？请问如何制作？

Damon 你好，
我用sdk 2_02_00_02的版本制作还是不行呢，
2_02_00_02中的mkfs.ubifs和ubinize 是64位的，我的linux 使用不了，所以我用的是2_01_00_01中的工具
其他文件都是从2_02_00_02中获取的
rootfs 的源文件也是从2.02.00.02中解压缩的，然后制作成ubinize.cfg中的文件名的ubi文件
sudo ./mkfs.ubifs -r rootfs/ -F -o ti-scmcsdk-rootfs-tci6614-evm.ubifs -m 2048 -e 126976 -c 4039

rootfs-recovery 和 securedbv0/1是使用2_02_00_02中的提供的ubi文件，ubinize.cfg文件没有修改，制作
./ubinize -o tci6614-evm-ubifs.ubi -m 2048 -p 128KiB -s 2048 -O 2048 ubinize.cfg
这里出现了一个告警：ubinize: volume size was not specified in section "rootfs", assume minimum to fit image "ti-scmcsdk-rootfs-tci6614-evm.ubifs"33902592 bytes (32.3 MiB)

完成后烧写到nand里，然后启动，找不大init文件 内核panic了
TCI6614 EVM # boot
Creating 1 MTD partitions on "nand0":
0x000000180000-0x000008000000 : "mtd=2"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
UBI: volume 2 ("rootfs") re-sized from 267 to 726 LEBs
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=2"
UBI: MTD device size: 126 MiB
UBI: number of good PEBs: 1007
UBI: number of bad PEBs: 5
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 5
UBI: available PEBs: 0
UBI: total number of reserved PEBs: 1007
UBI: number of PEBs reserved for bad PEB handling: 10
UBI: max/mean erase counter: 1/0
UBIFS: mounted UBI device 0, volume 0, name "boot"
UBIFS: mounted read-only
UBIFS: file system size: 8253440 bytes (8060 KiB, 7 MiB, 65 LEBs)
UBIFS: journal size: 1523712 bytes (1488 KiB, 1 MiB, 12 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: LZO
UBIFS: reserved for root: 0 bytes (0 KiB)
Loading file 'uImage' to addr 0xb0000000 with size 3046624 (0x002e7ce0)...
Done
Loading file 'tci6614-evm.dtb' to addr 0xa8000200 with size 15855 (0x00003def)...
Done
## Booting kernel from Legacy Image at b0000000 ...
Image Name: Linux-3.3.0
Created: 2013-12-07 2:19:45 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3046560 Bytes = 2.9 MiB
Load Address: a8008000
Entry Point: a8008000
Verifying Checksum ... OK
## Flattened Device Tree blob at a8000200
Booting using the fdt blob at 0xa8000200
Loading Kernel Image ... OK
OK
Loading Device Tree to bfb3f000, end bfb45dee ... OK

Starting kernel ...

t Dec 7 10:18:43 CST 2013
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: TCI6614 EVM, model: Texas Instruments TCI6614 EVM
cma: CMA: reserved 16 MiB at be800000
Memory policy: ECC disabled, Data cache writeback
DaVinci tci6614 rev 1.3 variant 0x1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 97536
Kernel command line: console=ttyS0,115200n8 mem=384M rootwait=1 rootfstype=ubifs root=ubi0:rootfs rootflags=sync rw ubi.mtd=2,2048
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 384MB = 384MB total
Memory: 367352k/367352k available, 25864k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
vmalloc : 0xd8800000 - 0xff000000 ( 616 MB)
lowmem : 0xc0000000 - 0xd8000000 ( 384 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.text : 0xc0008000 - 0xc0531388 (5285 kB)
.init : 0xc0532000 - 0xc055c000 ( 168 kB)
.data : 0xc055c000 - 0xc05947c8 ( 226 kB)
.bss : 0xc05947ec - 0xc05bc9bc ( 161 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:544
IRQ: Found an omap-aintc at 0xd8800000 (revision 5.0) with 128 interrupts
IRQ: intd version 1.0 at fee10000
IRQ: cpintc version 1.0 at fee0c000
main_pll_clk rate is 983040000, postdiv = 2, pllm = 15, plld = 0
Calibrating delay loop... 978.94 BogoMIPS (lpj=4894720)
pid_max: default: 4096 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available
Setting up static identity map for 0xa83e3cf0 - 0xa83e3d24
gpiochip_add: registered GPIOs 0 to 31 on device: DaVinci
DaVinci: 32 gpio irqs
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
hw-breakpoint: debug architecture 0x4 unsupported.
bio: create slab <bio-0> at 0
keystone-ipc-irq 26202bc.ipcirq: ipc irq: irqchip registered, range 512-540
keystone-hwqueue 2a00000.hwqueue: qmgr start queue 0, number of queues 8192
keystone-hwqueue 2a00000.hwqueue: added qmgr start queue 0, num of queues 8192, reg_peek d8840000, reg_status d8808000, reg_config d8810000, reg_region d8818000, reg_push d8880000, reg_pop d88c0000
keystone-hwqueue 2a00000.hwqueue: qos: sched port @8096, drop sched @8000
keystone-hwqueue 2a00000.hwqueue: added pool pool-core: 4096 descriptors of size 512
keystone-hwqueue 2a00000.hwqueue: added pool pool-net: 2048 descriptors of size 128
keystone-hwqueue 2a00000.hwqueue: added pool pool-udma: 1152 descriptors of size 128
keystone-hwqueue 2a00000.hwqueue: added pool pool-rio: 128 descriptors of size 128
keystone-hwqueue 2a00000.hwqueue: registered queues 0-8191
keystone-hwqueue 2a00000.hwqueue: qos version 0x1000104, magic valid
keystone-pktdma 2a6c000.pktdma: registered 24 logical channels, flows 32, tx chans: 32, rx chans: 32, loopback
keystone-pktdma 2004000.pktdma: registered 15 logical channels, flows 32, tx chans: 9, rx chans: 24
keystone-pktdma 2901000.pktdma: registered 2 logical channels, flows 24, tx chans: 16, rx chans: 16
Switching to clocksource timer0_1
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
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)
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
JFFS2 version 2.2. (NAND) 漏 2001-2006 Red Hat, Inc.
NET: Registered protocol family 38
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
keystone-rapidio 2900000.rapidio: KeyStone RapidIO driver v1.1
keystone-rapidio 2900000.rapidio: RIO: port 0 not ready
keystone-udma udma0.2: registered udma device udma0
Serial: 8250/16550 driver, 3 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x2540000 (irq = 448) is a 16550A
console [ttyS0] enabled
serial8250.0: ttyS1 at MMIO 0x2541000 (irq = 451) is a 16550A
loop: module loaded
at24 1-0050: 131072 byte 24c1024 EEPROM, writable, 128 bytes/write
Generic platform RAM MTD, (c) 2004 Simtec Electronics
ONFI flash detected
ONFI param page 0 valid
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xa1 (Micron MT29F1G08ABBDAHC)
Bad block table found at page 65472, version 0x02
Bad block table found at page 65408, version 0x02
nand_read_bbt: bad block at 0x0000003e0000
Creating 3 MTD partitions on "davinci_nand.0":
0x000000000000-0x000000100000 : "u-boot"
0x000000100000-0x000000180000 : "params"
0x000000180000-0x000008000000 : "ubifs"
davinci_nand davinci_nand.0: controller rev. 2.5
UBI: attaching mtd2 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
UBI: max. sequence number: 2
UBI: attached mtd2 to ubi0
UBI: MTD device name: "ubifs"
UBI: MTD device size: 126 MiB
UBI: number of good PEBs: 1007
UBI: number of bad PEBs: 5
UBI: number of corrupted PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 5
UBI: available PEBs: 0
UBI: total number of reserved PEBs: 1007
UBI: number of PEBs reserved for bad PEB handling: 10
UBI: max/mean erase counter: 1/0
UBI: image sequence number: 921711016
UBI: background thread "ubi_bgt0d" started, PID 340
m25p80 spi0.0: n25q032 (4096 Kbytes)
Creating 2 MTD partitions on "m25p80":
0x000000000000-0x000000080000 : "u-boot-spl"
0x000000080000-0x000000400000 : "test"
spi_davinci spi_davinci.0: Controller at 0xd88a4000
davinci_mdio 2090300.mdio: davinci mdio revision 1.5
davinci_mdio 2090300.mdio: detected phy mask fffffffd
2090300.mdio: probed
davinci_mdio 2090300.mdio: phy[1]: device 2090300.mdio-fff:01, driver unknown
keystone-netcp 2090000.netcp: Created interface "eth0"
keystone-netcp 2090000.netcp: dma_chan_name nettx0
i2c /dev entries driver
watchdog watchdog: heartbeat 60 sec
keystone-crypto 20c0000.crypto: crypto accelerator enabled
register char-device: itl_qmss_dev.
arm-tfdq: queue id: 2040.
arm-rfdq: queue id: 2044.
arm-txq: queue id: 0804.
arm-rxq: queue id: 0657.
(ARM) tx-complete hwqueue id:2040.
set pktdma of core4 :rx_qn(657), rx_fdq(2044) on flow(4).
remoteproc dsp-core0: dsp-core0 is available
remoteproc dsp-core1: dsp-core1 is available
remoteproc dsp-core2: dsp-core2 is available
remoteproc dsp-core3: dsp-core3 is available
oprofile: using arm/armv7
GACT probability on
Mirror/redirect action on
Simple TC action Loaded
netem: version 1.3
u32 classifier
Performance counters on
input device check on
Actions configured
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (5995 buckets, 23980 max)
ctnetlink v0.93: registering with nfnetlink.
IPv4 over IPv4 tunneling driver
GRE over IPv4 demultiplexor driver
GRE over IPv4 tunneling driver
ip_tables: (C) 2000-2006 Netfilter Core Team
ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully
arp_tables: (C) 2002 David S. Miller
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 10
NET: Registered protocol family 17
NET: Registered protocol family 15
Bridge firewalling registered
Ebtables v2.0 registered
8021q: 802.1Q VLAN Support v1.8
sctp: Hash tables configured (established 16384 bind 32768)
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
UBIFS: parse sync
UBIFS: start fixing up free space
UBIFS: free space fixup complete
UBIFS: mounted UBI device 0, volume 2, name "rootfs"
UBIFS: file system size: 90787840 bytes (88660 KiB, 86 MiB, 715 LEBs)
UBIFS: journal size: 9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root: 0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:13.
Freeing init memory: 168K
request_module: runaway loop modprobe binfmt-0000
request_module: runaway loop modprobe binfmt-0000
Kernel panic - not syncing: No init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.

但是如果把我自己制作的ti-scmcsdk-rootfs-tci6614-evm.ubifs 替换为ti\sc_mcsdk_linux_2_02_00_02\images下的ti-scmcsdk-rootfs-tci6614-evm.ubifs
重新./ubinize -o tci6614-evm-ubifs.ubi -m 2048 -p 128KiB -s 2048 -O 2048 ubinize.cfg （也同样出现告警）
烧到nand里 启动内核 就正常了

唯一的区别就是
一个是我从\ti\sc_mcsdk_linux_2_02_00_02\images中copy出来的ti-scmcsdk-rootfs-tci6614-evm.tar.gz 解压缩后
放到rootfs目录下，sudo ./mkfs.ubifs -r rootfs/ -F -o ti-scmcsdk-rootfs-tci6614-evm.ubifs -m 2048 -e 126976 -c 4039 制作ti-scmcsdk-rootfs-tci6614-evm.ubifs
另外一个是我从\ti\sc_mcsdk_linux_2_02_00_02\images中copy出来ti-scmcsdk-rootfs-tci6614-evm.ubifs文件

另外i你上面回复的的启动过程信息只是uboot的吧，没有看到内核的启动过程呢

vol_size没有设置为具体大小时字编译中会有相应的警告信息，但是没关系，会自动按最小需要大小，我遇到过，如果想去掉这个警告信息，可以根据编译得到的rootfs大小在.cfg文件中设置。

这三个文件使用sdk的可以正常工作，制作过程可以参考mcsdk user guide的说明

ubinize等工具的制作可以参考http://www.deyisupport.com/question_answer/dsp_arm/c6000_multicore/f/53/t/51060.aspx，里面有详细的说明，内核启动过程下面的内容和sdk中提供的.ubi文件相同，当时实验的时候我就没存下来，可以参考下上面的文档，希望对你有帮助

我试一下

Damon 能不能帮我看一下这个问题阿？

6614开发板上面有2个sgmii网口，其中一个是外接RJ45，这个内核起来后ifconfig能够看到。
另外一个是接到金手指上面，内核起来后ifcongig -all 没有看到对应的网路接口，应该是没有驱动没有配置。
请问如何修改就能把该网口配置起来?这个网口需要连接到背板上面