TI中文支持网硬件是AM3354，用的 ti-sdk-am335x-evm-08.00.00.00-Linux-x86-Install.bin 这套SDK
linux 3.14
NAND是1G的，在UBOOT启动时候可以正确识别到，但是在KERNEL里面df -h看到只有200M不到，请问这个分区是在哪里控制的。
tao sun4：
相同的板子，刷很早以前的SDK，3.2的KERNEL, 2011的UBOOT，识别到就比这个大，虽然也是不到1G
tao sun4：
回复 tao sun4:
有人能回答一下吗，TI的大神们。。。
Steven Liu1：
回复 tao sun4:
你看到的这个分区表，和我们默认给的一些配置差别很大，是自己改过kernel中间的分区表吧？应该是和这个部分的改动有相关，能否把这个传上来呢？没有这个不方便判断。
leo chen：
回复 tao sun4:
可以先看一下dts文件里面是怎么分区的
tao sun4：
回复 leo chen:
dts改了，没有效果
&gpmc { status = "okay"; pinctrl-names = "default", "sleep"; pinctrl-0 = <&nandflash_pins_default>; pinctrl-1 = <&nandflash_pins_sleep>; ranges = <0 0 0x08000000 0x20000000>; /* CS0: NAND */ nand@0,0 { reg = <0 0 0>; /* CS0, offset 0 */ ti,nand-ecc-opt = "bch8"; ti,elm-id = <&elm>; nand-bus-width = <8>; gpmc,device-width = <1>; gpmc,sync-clk-ps = <0>; gpmc,cs-on-ns = <0>; gpmc,cs-rd-off-ns = <44>; gpmc,cs-wr-off-ns = <44>; gpmc,adv-on-ns = <6>; gpmc,adv-rd-off-ns = <34>; gpmc,adv-wr-off-ns = <44>; gpmc,we-on-ns = <0>; gpmc,we-off-ns = <40>; gpmc,oe-on-ns = <0>; gpmc,oe-off-ns = <54>; gpmc,access-ns = <64>; gpmc,rd-cycle-ns = <82>; gpmc,wr-cycle-ns = <82>; gpmc,wait-on-read = "true"; gpmc,wait-on-write = "true"; gpmc,bus-turnaround-ns = <0>; gpmc,cycle2cycle-delay-ns = <0>; gpmc,clk-activation-ns = <0>; gpmc,wait-monitoring-ns = <0>; gpmc,wr-access-ns = <40>; gpmc,wr-data-mux-bus-ns = <0>; /* MTD partition table */ /* All SPL-* partitions are sized to minimal length * which can be independently programmable. For * NAND flash this is equal to size of erase-block */ #address-cells = <1>; #size-cells = <1>; partition@0 { label = "NAND.SPL"; reg = <0x00000000 0x000020000>; }; partition@1 { label = "NAND.SPL.backup1"; reg = <0x00020000 0x00020000>; }; partition@2 { label = "NAND.SPL.backup2"; reg = <0x00040000 0x00020000>; }; partition@3 { label = "NAND.SPL.backup3"; reg = <0x00060000 0x00020000>; }; partition@4 { label = "NAND.u-boot-spl-os"; reg = <0x00080000 0x00040000>; }; partition@5 { label = "NAND.u-boot"; reg = <0x000C0000 0x00100000>; }; partition@6 { label = "NAND.u-boot-env"; reg = <0x001C0000 0x00020000>; }; partition@7 { label = "NAND.u-boot-env.backup1"; reg = <0x001E0000 0x00020000>; }; partition@8 { label = "NAND.kernel"; reg = <0x00200000 0x00800000>; }; partition@9 { label = "NAND.file-system"; reg = <0x00A00000 0x30000000>; }; };};
tao sun4：
回复 Steven Liu1:
已经上传了，在上面，您帮忙看看，下面是Kernel启动时候的LOG信息
[ 2.287490] omap-gpmc 50000000.gpmc: GPMC revision 6.0[ 2.292956] gpmc_mem_init: disabling cs 0 mapped at 0x0-0x1000000[ 2.300696] nand: device found, Manufacturer ID: 0x01, Chip ID: 0xd3[ 2.307438] nand: AMD/Spansion S34ML08G1[ 2.311572] nand: 1024MiB, SLC, page size: 2048, OOB size: 64[ 2.317616] nand: using OMAP_ECC_BCH8_CODE_HW ECC scheme[ 2.323427] 10 ofpart partitions found on MTD device omap2-nand.0[ 2.329831] Creating 10 MTD partitions on "omap2-nand.0":[ 2.335540] 0x000000000000-0x000000020000 : "NAND.SPL"[ 2.342913] 0x000000020000-0x000000040000 : "NAND.SPL.backup1"[ 2.350664] 0x000000040000-0x000000060000 : "NAND.SPL.backup2"[ 2.358403] 0x000000060000-0x000000080000 : "NAND.SPL.backup3"[ 2.366165] 0x000000080000-0x0000000c0000 : "NAND.u-boot-spl-os"[ 2.374207] 0x0000000c0000-0x0000001c0000 : "NAND.u-boot"[ 2.382284] 0x0000001c0000-0x0000001e0000 : "NAND.u-boot-env"[ 2.389914] 0x0000001e0000-0x000000200000 : "NAND.u-boot-env.backup1"[ 2.398362] 0x000000200000-0x000000a00000 : "NAND.kernel"[ 2.412301] 0x000000a00000-0x000030a00000 : "NAND.file-system"
