TI中文支持网hi,
我最近在使用AM3517,烧录官方的winCE demo. 官方提供的文件: AM35x_nand.raw(hamming1Bit), AM35x-nand-logo.raw(hamming1bit),NK_demo.bin.都放在NANDFLASH中．使用Ti提供的FLASH V1.6.0.0烧录工具．
烧录地址: 0–> AM35x_nand.raw
c0000-> AM35x-nand-logo.raw
0x1c0000-> NK_demo.bin
最终结果，bootloader可以起来，但wince系统起不来．请各位多多指教！谢谢！
Heng Feng：
看你内核启动参数有没有设对，把报错的信息贴上来~~
Token：
回复 Heng Feng:
分两种情况:
第一种情况:HWECC(4Bit)选择winCEOS,烧录内核NK_demo.bin
Texas Instruments Windows CE NAND X-Loader for AM35x
Built May 19 2011 at 22:24:42
Version BSP_WINCE_ARM_A8 1.02.00.02
.$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$.
Jumping to bootloader
Microsoft Windows CE Bootloader Common Library Version 1.4 Built May 19 2011 22:13:31
Texas Instruments Windows CE EBOOT for AM35x, Built May 19 2011 at 22:23:47
EBOOT Version 1.2, BSP 1.02.00.02
TI AM3517 Version 0x0 (Hawkeye 0xb868 / manufacturer ID 0x17)
System ready!
Preparing for download…
INFO: Predownload….
Checking bootloader blocks are marked as reserved (Num = 14)
ERROR: EBOOT!BLReadBootCfg: Flash sector 383 read failed
WARN: Boot config wasn't found, using defaults
24ba 50cb01 -> 0 24 ba 50 cb 1
INFO: SW4 boot setting: 0x0c
IsValidMBR: MBR sector = 0x380 (valid MBR)
OpenPartition: Partition Exists=0x0 for part 0x20.
OS partition does not exist!!
Formatting flash…
Enter LowLevelFormat [0x0, 0xfff].
Erasing flash block(s) [0x0, 0xfff] (please wait): EraseBlocks: preserving reserved block (0x0)
EraseBlocks: preserving reserved block (0x1)
EraseBlocks: preserving reserved block (0x2)
EraseBlocks: preserving reserved block (0x3)
EraseBlocks: preserving reserved block (0x4)
EraseBlocks: preserving reserved block (0x5)
EraseBlocks: preserving reserved block (0x6)
EraseBlocks: preserving reserved block (0x7)
EraseBlocks: preserving reserved block (0x8)
EraseBlocks: preserving reserved block (0x9)
EraseBlocks: preserving reserved block (0xa)
EraseBlocks: preserving reserved block (0xb)
EraseBlocks: preserving reserved block (0xc)
EraseBlocks: preserving reserved block (0xd)
EraseBlocks: found a bad block (0x351) – skipping…
EraseBlocks: found a bad block (0x37c) – skipping…
EraseBlocks: found a bad block (0x384) – skipping…
EraseBlocks: found a bad block (0x432) – skipping…
EraseBlocks: found a bad block (0x52c) – skipping…
EraseBlocks: found a bad block (0x774) – skipping…
EraseBlocks: found a bad block (0x8c6) – skipping…
EraseBlocks: found a bad block (0xb94) – skipping…
Done.
WriteMBR: MBR block = 0xe.
Done.
IsValidMBR: MBR sector = 0x380 (valid MBR)
OpenPartition: Partition Exists=0x0 for part 0x20.
CreatePartition: Enter CreatePartition for 0x20.
LastLogSector: Last log sector is: 0x3fa7f.
CreatePartition: Start = 0x1, Num = 0x5fff.
第二种情况:
HWECC(hamming1Bit)选择kernel选项:
Txas Instruments Windows CE NAND X-Loader for AM35x
Built May 19 2011 at 22:24:42
Version BSP_WINCE_ARM_A8 1.02.00.02
.$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$.
Jumping to bootloader
Microsoft Windows CE Bootloader Common Library Version 1.4 Built May 19 2011 22:13:31
Texas Instruments Windows CE EBOOT for AM35x, Built May 19 2011 at 22:23:47
EBOOT Version 1.2, BSP 1.02.00.02
TI AM3517 Version 0x0 (Hawkeye 0xb868 / manufacturer ID 0x17)
System ready!
Preparing for download…
INFO: Predownload….
Checking bootloader blocks are marked as reserved (Num = 14)
ERROR: EBOOT!BLReadBootCfg: Flash sector 383 read failed
WARN: Boot config wasn't found, using defaults
24ba 50cb01 -> 0 24 ba 50 cb 1
INFO: SW4 boot setting: 0x0c
IsValidMBR: MBR sector = 0x380 (valid MBR)
OpenPartition: Partition Exists=0x1 for part 0x20.
>>> Forcing cold boot (non-persistent registry and other data will be wiped) <<<
Hit space to enter configuration menu 5…
Hit space to enter configuration menu 4…
Hit space to enter configuration menu 3…
Hit space to enter configuration menu 2…
Hit space to enter configuration menu 1…
OALFlashStoreOpen: 4096 blocks, 64 sectors/block
OALFlashStoreOpen: 2048 bytes/sector, 14 reserved blocks
Turning on the LCD
Turning on the LCD
Load NK image from flash memory
IsValidMBR: MBR sector = 0x380 (valid MBR)
OpenPartition: Partition Exists=0x1 for part 0x20.
BP_SetDataPointer at 0x0
ReadData: Start = 0x0, Length = 0x1000.
Log2Phys: Logical 0x1 -> Physical 0x381
ERROR: Image signature not found
Heng Feng：
回复 Token:
我感觉是你的uboot参数没有设对，用了默认的启动参数，从uboot中会传给kernel一个启动参数，这个参数可以在内核编译的时候填写，也可以在uboot中传入，你用的默认的kernel，应该是需要自己在uboot里写一个。
Token：
回复 Heng Feng:
这里我跑的是WINCE系统，我是怀疑TI提供的FLASH TOOL 1.6.0.0烧录WINCE内核时，有什么设置，或者本身就不能这样干，而是需要其它方式更新wince内核。
alvin lu：
回复 Token:
建议你在SD卡上试试能不能启动？如果能启动，首先排除所谓的uboot向kernel机器号不一样的问题。
