[已解决]fastboot烧写SPI成功

3516这种东西，一般都是spi的flash吧，你试试，选择ＳＰＩ，信息里不是有嘛，他都找到SPI flash了，

所有模块都选spi

[quote][url=forum.php?mod=redirect&goto=findpost&pid=32635&ptid=11765]ngswfx 发表于 2016-6-28 13:59[/url]
3516这种东西，一般都是spi的flash吧，你试试，选择ＳＰＩ，信息里不是有嘛，他都找到SPI flash了，

所 ...[/quote]

谢谢您的回复

hisilicon #
hisilicon #
hisilicon # ▒


U-Boot 2010.06 (Oct 22 2015 - 14:46:56)

Check spi flash controller v350... Found
Spi(cs1) ID: 0xC2 0x20 0x19 0xC2 0x20 0x19
Spi(cs1): Block:64KB Chip:32MB Name:"MX25L(256/257)35(E/F)"
Check Nand Flash Controller v610 ... found
Special NAND id table Version 1.36
Nand ID: 0x01 0xDA 0x90 0x95 0x44 0x01 0xDA 0x90
Block:128KB Page:2KB Chip:256MB*1 OOB:64B ECC:4bit/512
Nand total size: 256MB
*** Warning - bad CRC or NAND, using default environment

In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
Wrong Image Format for bootm command
ERROR: can't get kernel image!
hisilicon #

[quote][url=forum.php?mod=redirect&goto=findpost&pid=32635&ptid=11765]ngswfx 发表于 2016-6-28 13:59[/url]
3516这种东西，一般都是spi的flash吧，你试试，选择ＳＰＩ，信息里不是有嘛，他都找到SPI flash了，

所 ...[/quote]

选择用 nand flash through cable 232
Fastboot setting：
1 Fastboot Nand
2 Kernel  Nand
3 rootfs Nand


Current status
Partition Burning Started! Please power off and then power on the board.
Boot 100 % Downloaded.
Boot Downloading completed!


U-Boot 2010.06 (Oct 22 2015 - 14:46:56)

Check spi flash controller v350... Found
Spi(cs1) ID: 0xC2 0x20 0x19 0xC2 0x20 0x19
Spi(cs1): Block:64KB Chip:32MB Name:"MX25L(256/257)35(E/F)"
Check Nand Flash Controller v610 ... found
Special NAND id table Version 1.36
Nand ID: 0x01 0xDA 0x90 0x95 0x44 0x01 0xDA 0x90
Block:128KB Page:2KB Chip:256MB*1 OOB:64B ECC:4bit/512
Nand total size: 256MB

*** Warning - bad CRC or NAND, using default environment

In:    serial
Out:   serial
Err:   serial
start download process.

Boot Started successfully!
version: 3.0.3
(OK)
"getinfo version" command sent successfully!
nand
(OK)
"getinfo bootmode" command sent successfully!
Block:64KB Chip:32MB*1
ID:0xC2 0x20 0x19
Name:"MX25L(256/257)3"
(OK)
"getinfo spi" command sent successfully!
Block:128KB Chip:256MB*1 Page:2KB OOB:64B ECC:1bit/512Byte
ID:0x01 0xDA 0x90 0x95 0x44 0x01 0xDA 0x90
Name:"NAND 256MiB 3,3"
(OK)
"getinfo nand" command sent successfully!
NAND erase: device 0 offset 0x0, size 0x100000

Erasing at 0x0 --  12% complete.
Erasing at 0x20000 --  25% complete.
Erasing at 0x40000 --  37% complete.
Erasing at 0x60000 --  50% complete.
Erasing at 0x80000 --  62% complete.
Erasing at 0xa0000 --  75% complete.
Erasing at 0xc0000 --  87% complete.
Erasing at 0xe0000 -- 100% complete.
OK
(OK)
"nand erase 0 0x100000" command sent successfully!
NAND write: device 0 offset 0x0, size 0x40000
262144 bytes written: OK
(OK)
"nand write 0x81000000 0 0x40000" command sent successfully!
Fastboot partition burnt successfully!
(OK)
"setenv serverip 192.168.1.82" command sent successfully!
(OK)
"setenv ethaddr 00:e0:88:37:fa:b1" command sent successfully!
(OK)
"setenv ipaddr 192.168.1.40" command sent successfully!
(OK)
"setenv netmask 255.255.255.0" command sent successfully!
(OK)
"setenv gatewayip 192.168.1.1" command sent successfully!
###
(OK)
"mw.b 0x81000000 0xff 0x2e0000" command sent successfully!
###
ETH0: PHY(phyaddr=1, rgmii) link UP: DUPLEX=FULL : SPEED=1000M
MAC:   00-E0-88-37-FA-B1
#####
host 192.168.1.82 is alive
(OK)
"ping 192.168.1.82" command sent successfully!
ETH0: PHY(phyaddr=1, rgmii) link UP: DUPLEX=FULL : SPEED=1000M
MAC:   00-E0-88-37-FA-B1
TFTP from server 192.168.1.82; our IP address is 192.168.1.40
Download Filename 'uImage_hi3516a'.
Download to address: 0x81000000
Downloading: *
###################################################
done
Bytes transferred = 2985656 (2d8eb8 hex)
(OK)
"tftp 0x81000000 uImage_hi3516a" command sent successfully!
NAND erase: device 0 offset 0x100000, size 0xf00000

Erasing at 0x100000 --   0% complete.
Erasing at 0x120000 --   1% complete.
Erasing at 0x140000 --   2% complete.
Erasing at 0x160000 --   3% complete.
Erasing at 0x180000 --   4% complete.
Erasing at 0x1a0000 --   5% complete.
Erasing at 0x1e0000 --   6% complete.
Erasing at 0x200000 --   7% complete.
Erasing at 0x220000 --   8% complete.
Erasing at 0x240000 --   9% complete.
Erasing at 0x260000 --  10% complete.
Erasing at 0x2a0000 --  11% complete.
Erasing at 0x2c0000 --  12% complete.
Erasing at 0x2e0000 --  13% complete.
Erasing at 0x300000 --  14% complete.
Erasing at 0x320000 --  15% complete.
Erasing at 0x360000 --  16% complete.
Erasing at 0x380000 --  17% complete.
Erasing at 0x3a0000 --  18% complete.
Erasing at 0x3c0000 --  19% complete.
Erasing at 0x3e0000 --  20% complete.
Erasing at 0x420000 --  21% complete.
Erasing at 0x440000 --  22% complete.
Erasing at 0x460000 --  23% complete.
Erasing at 0x480000 --  24% complete.
Erasing at 0x4a000
#
0 --  25% complete.
Erasing at 0x4e0000 --  26% complete.
Erasing at 0x500000 --  27% complete.
Erasing at 0x520000 --  28% complete.
Erasing at 0x540000 --  29% complete.
Erasing at 0x560000 --  30% complete.
Erasing at 0x5a0000 --  31% complete.
Erasing at 0x5c0000 --  32% complete.
Erasing at 0x5e0000 --  33% complete.
Erasing at 0x600000 --  34% complete.
Erasing at 0x620000 --  35% complete.
Erasing at 0x660000 --  36% complete.
Erasing at 0x680000 --  37% complete.
Erasing at 0x6a0000 --  38% complete.
Erasing at 0x6c0000 --  39% complete.
Erasing at 0x6e0000 --  40% complete.
Erasing at 0x720000 --  41% complete.
Erasing at 0x740000 --  42% complete.
Erasing at 0x760000 --  43% complete.
Erasing at 0x780000 --  44% complete.
Erasing at 0x7a0000 --  45% complete.
Erasing at 0x7e0000 --  46% complete.
Erasing at 0x800000 --  47% complete.
Erasing at 0x820000 --  48% complete.
Erasing at 0x840000 --  49% complete.
Erasing at 0x860000 --  50% complete.
Erasing at 0x8a0000 --  51% complete.
Erasing at 0x8c0
000 --  52% complete.
Erasing at 0x8e0000 --  53% complete.
Erasing at 0x900000 --  54% complete.
Erasing at 0x920000 --  55% complete.
Erasing at 0x960000 --  56% complete.
Erasing at 0x980000 --  57% complete.
Erasing at 0x9a0000 --  58% complete.
Erasing at 0x9c0000 --  59% complete.
Erasing at 0x9e0000 --  60% complete.
Erasing at 0xa20000 --  61% complete.
Erasing at 0xa40000 --  62% complete.
Erasing at 0xa60000 --  63% complete.
Erasing at 0xa80000 --  64% complete.
Erasing at 0xaa0000 --  65% complete.
Erasing at 0xae0000 --  66% complete.
Erasing at 0xb00000 --  67% complete.
Erasing at 0xb20000 --  68% complete.
Erasing at 0xb40000 --  69% complete.
Erasing at 0xb60000 --  70% complete.
Erasing at 0xba0000 --  71% complete.
Erasing at 0xbc0000 --  72% complete.
Erasing at 0xbe0000 --  73% complete.
Erasing at 0xc00000 --  74% complete.
Erasing at 0xc20000 --  75% complete.
Erasing at 0xc60000 --  76% complete.
Erasing at 0xc80000 --  77% complete.
Erasing at 0xca0000 --  78% complete.
Erasing at 0xc
c0000 --  79% complete.
Erasing at 0xce0000 --  80% complete.
Erasing at 0xd20000 --  81% complete.
Erasing at 0xd40000 --  82% complete.
Erasing at 0xd60000 --  83% complete.
Erasing at 0xd80000 --  84% complete.
Erasing at 0xda0000 --  85% complete.
Erasing at 0xde0000 --  86% complete.
Erasing at 0xe00000 --  87% complete.
Erasing at 0xe20000 --  88% complete.
Erasing at 0xe40000 --  89% complete.
Erasing at 0xe60000 --  90% complete.
Erasing at 0xea0000 --  91% complete.
Erasing at 0xec0000 --  92% complete.
Erasing at 0xee0000 --  93% complete.
Erasing at 0xf00000 --  94% complete.
Erasing at 0xf20000 --  95% complete.
Erasing at 0xf60000 --  96% complete.
Erasing at 0xf80000 --  97% complete.
Erasing at 0xfa0000 --  98% complete.
Erasing at 0xfc0000 --  99% complete.
Erasing at 0xfe0000 -- 100% complete.
OK
(OK)
"nand erase 0x100000 0xf00000" command sent successfully!
NAND write: device 0 offset 0x100000, size 0x2e0000
3014656 bytes written: OK
(OK)
"nand write 0x81000000 0x100000 0x2e0000" command sent successfully!
kernel Partition burnt successfully!
Block:128KB Chip:256MB*1 Page:2KB OOB:64B ECC:1bit/512Byte
ID:0x01 0xDA 0x90 0x95 0x44 0x01 0xDA 0x90
Name:"NAND 256MiB 3,3"
(OK)
"getinfo nand" command sent successfully!
(OK)
"mw.b 0x81000000 0xff 0xbdb7c0" command sent successfully!
ETH0: PHY(phyaddr=1, rgmii) link UP: DUPLEX=FULL : SPEED=1000M
MAC:   00-E0-88-37-FA-B1
host 192.168.1.82 is alive
(OK)
"ping 192.168.1.82" command sent successfully!
ETH0: PHY(phyaddr=1, rgmii) link UP: DUPLEX=FULL : SPEED=1000M
MAC:   00-E0-88-37-FA-B1
TFTP from server 192.168.1.82; our IP address is 192.168.1.40
Download Filename 'rootfs_hi3516a_2k_4bit.yaffs2'.
Download to address: 0x81000000
Downloading: *
###########################################################
done
Bytes transferred = 12433344 (bdb7c0 hex)
(OK)
"tftp 0x81000000 rootfs_hi3516a_2k_4bit.yaffs2" command sent successfully!
NAND erase: device 0 offset 0x1000000, size 0x2000000

Erasing at 0x1000000 --   0% complete.
Erasing at 0x1040000 --   1% complete.
Erasing at 0x10a0000 --   2% complete.
Erasing at 0x10e0000 --   3% complete.
Erasing at 0x1140000 --   4% complete.
Erasing at 0x1180000 --   5% complete.
Erasing at 0x11e0000 --   6% complete.
Erasing at 0x1220000 --   7% complete.
Erasing at 0x1280000 --   8% complete.
Erasing at 0x12e0000 --   9% complete.
Erasing at 0x1320000 --  10% complete.
Erasing at 0x1380000 --  11% complete.
Erasing at 0x13c0000 --  12% complete.
Erasing at 0x1420000 --  13% complete.
Erasing at 0x1460000 --  14% complete.
Erasing at 0x14c0000 --  15% complete.
Erasing at 0x1500000 --  16% complete.
Erasing at 0x1560000 --  17% complete.
Erasing at 0x15c0000 --  18% complete.
Erasing at 0x1600000 --  19% complete.
Erasing at 0x1660000 --  20% complete.
Erasing at 0x16a0000 --  21% complete.
Erasing at 0x1700000 --  22% complete.
Erasing at 0x1740000 --  23% complete.
Erasing at 0x17a0000 --  24% complete.
Erasing at 0x17e0000 --  25% complete.
Erasing at 0x1840000 --  26% complete.
Erasing at 0x18a0000 --  27% complete.
Erasing at 0x18e0000 --  28% complete.
Erasing at 0x1940000 --  29% complete.
Erasing at 0x1980000 --  30% complete.
Erasing at 0x19e0000 --  31% complete.
Erasing at 0x1a20000 --  32% complete.
Erasing at 0x1a80000 --  33% complete.
Erasing at 0x1ae0000 --  34% complete.
Erasing at 0x1b20000 --  35% complete.
Erasing at 0x1b
80000 --  36% complete.
Erasing at 0x1bc0000 --  37% complete.
Erasing at 0x1c20000 --  38% complete.
Erasing at 0x1c60000 --  39% complete.
Erasing at 0x1cc0000 --  40% complete.
Erasing at 0x1d00000 --  41% complete.
Erasing at 0x1d60000 --  42% complete.
Erasing at 0x1dc0000 --  43% complete.
Erasing at 0x1e00000 --  44% complete.
Erasing at 0x1e60000 --  45% complete.
Erasing at 0x1ea0000 --  46% complete.
Erasing at 0x1f00000 --  47% complete.
Erasing at 0x1f40000 --  48% complete.
Erasing at 0x1fa0000 --  49% complete.
Erasing at 0x1fe0000 --  50% complete.
Erasing at 0x2040000 --  51% complete.
Erasing at 0x20a0000 --  52% complete.
Erasing at 0x20e0000 --  53% complete.
Erasing at 0x2140000 --  54% complete.
Erasing at 0x2180000 --  55% complete.
Erasing at 0x21e0000 --  56% complete.
Erasing at 0x2220000 --  57% complete.
Erasing at 0x2280000 --  58% complete.
Erasing at 0x22e0000 --  59% complete.
Erasing at 0x2320000 --  60% complete.
Erasing at 0x2380000 --  61% complete.
Erasing at 0x23c0000 --  62% complete.
Erasing at 0x2420000 --  63% complete.
Erasing at 0x2460000 --  64% complete.
Erasing at 0x24c0000 --  65% complete.
Erasing at 0x2500000 --  66% complete.
Erasing at 0x2560000 --  67% complete.
Erasing at 0x25c0000 --  68% complete.
Erasing at 0x2600000 --
69% complete.
Erasing at 0x2660000 --  70% complete.
Erasing at 0x26a0000 --  71% complete.
Erasing at 0x2700000 --  72% complete.
Erasing at 0x2740000 --  73% complete.
Erasing at 0x27a0000 --  74% complete.
Erasing at 0x27e0000 --  75% complete.
Erasing at 0x2840000 --  76% complete.
Erasing at 0x28a0000 --  77% complete.
Erasing at 0x28e0000 --  78% complete.
Erasing at 0x2940000 --  79% complete.
Erasing at 0x2980000 --  80% complete.
Erasing at 0x29e0000 --  81% complete.
Erasing at 0x2a20000 --  82% complete.
Erasing at 0x2a80000 --
83% complete.
Erasing at 0x2ae0000 --  84% complete.
Erasing at 0x2b20000 --  85% complete.
Erasing at 0x2b80000 --  86% complete.
Erasing at 0x2bc0000 --  87% complete.
Erasing at 0x2c20000 --  88% complete.
Erasing at 0x2c60000 --  89% complete.
Erasing at 0x2cc0000 --  90% complete.
Erasing at 0x2d00000 --  91% complete.
Erasing at 0x2d60000 --  92% complete.
Erasing at 0x2dc0000 --  93% complete.
Erasing at 0x2e00000 --  94% complete.
Erasing at 0x2e60000 --  95% complete.
Erasing at 0x2ea0000 --  96% complete.
Erasing
at 0x2f00000 --  97% complete.
Erasing at 0x2f40000 --  98% complete.
Erasing at 0x2fa0000 --  99% complete.
Erasing at 0x2fe0000 -- 100% complete.
OK
(OK)
#
"nand erase 0x1000000 0x2000000" command sent successfully!
NAND write: device 0 offset 0x1000000, size 0xbdb7c0
data length:0xb7f800, include bad block length: 0xb80000
##
12433344 bytes written: OK
(OK)
"nand write.yaffs 0x81000000 0x1000000 0xbdb7c0" command sent successfully!
rootfs Partition burnt successfully!
Partition burning completed!

[quote][url=forum.php?mod=redirect&goto=findpost&pid=32644&ptid=11765]2272943826 发表于 2016-6-28 14:48[/url]
谢谢您的回复

hisilicon #
[/quote]

你这个有2片，第一个是32Ｍ的ＳＰＩ，另外一片是256Ｍ的ＮＡＮＤ。

通常ＳＰＩ用来放uboot kernel rootfs等，nand用来放比较大的程序等。

如果板子上还有选择启动的跳线，你也可以所有东西都搞到nand上。

/////通常默认应该是从spi启动，然后支持访问nand，也就是支持把uboot搞到spi上，其他模块根据大小，选择放到哪个片子上。

本帖最后由 2272943826 于 2016-7-21 15:07 编辑

[quote][url=forum.php?mod=redirect&goto=findpost&pid=32635&ptid=11765]ngswfx 发表于 2016-6-28 13:59[/url]
3516这种东西，一般都是spi的flash吧，你试试，选择ＳＰＩ，信息里不是有嘛，他都找到SPI flash了，

所 ...[/quote]

我刚刚尝试 断开 fastboot ， 连接 puttty ，
1 输入command ：ls 没有回应
2 输入 command：printenv  有回应


hisilicon # ls
Unknown command 'ls' - try 'help'
hisilicon # printenv
bootargs=mem=96M console=ttyAMA0,115200
bootcmd=bootm 0x82000000
bootdelay=1
baudrate=115200
ethaddr=00:00:23:34:45:66
ipaddr=192.168.1.10
serverip=192.168.1.2
netmask=255.255.255.0
bootfile="uImage"
stdin=serial
stdout=serial
stderr=serial
verify=n
ver=U-Boot 2010.06 (Oct 22 2015 - 14:46:56)

Environment size: 294/262140 bytes

本帖最后由 ngswfx 于 2016-6-28 15:00 编辑

[quote][url=forum.php?mod=redirect&goto=findpost&pid=32645&ptid=11765]2272943826 发表于 2016-6-28 14:50[/url]
选择用 nand flash through cable 232
Fastboot setting：
1 Fastboot Nand
[/quote]

你都烧到nand了，看看板子能否选择从nand启动，这样就可以启动了

////////如果找不到，就烧写的时候都选择ＳＰＩ，烧到那个32Ｍ的ＳＰＩ里面，板子默认应该先从这里执行的。

[quote][url=forum.php?mod=redirect&goto=findpost&pid=32648&ptid=11765]2272943826 发表于 2016-6-28 14:55[/url]
我刚刚尝试 断开 fastboot ， 连接 puttty ，
1 输入command ：ls 没有回应
2 输入 command：printenv ...[/quote]

你就是烧错芯片了，烧写到哪个芯片，要根据跳线来，

你这个还真是个开发板，应该可以选择启动方式吧，跳一下跳线就应该对了。

你现在进入的应该还是ＳＰＩ那个flash启动的信息。

[quote][url=forum.php?mod=redirect&goto=findpost&pid=32648&ptid=11765]2272943826 发表于 2016-6-28 14:55[/url]
我刚刚尝试 断开 fastboot ， 连接 puttty ，
1 输入command ：ls 没有回应
2 输入 command：printenv ...[/quote]

要通过命令看，help看，哪些命令前面带nand的才能用。ls不是uboot下的命令。

uboot下只能用help能看见的命令。

因为你已经烧到nand flash了，看log而且成功了。如果想正常启动，只能跳跳线让芯片直接访问nand flash芯片，从这里启动。否则，90%可能性，你的板子默认从ＳＰＩ启动的。

本帖最后由 2272943826 于 2016-11-25 09:39 编辑

[quote][url=forum.php?mod=redirect&goto=findpost&pid=32647&ptid=11765]ngswfx 发表于 2016-6-28 14:55[/url]
你这个有2片，第一个是32Ｍ的ＳＰＩ，另外一片是256Ｍ的ＮＡＮＤ。

通常SPI用来放uboot kernel roo ...[/quote]

谢谢 纠正错误

我应该放在spi上面,
如何设置开发板的ip addresss

[quote][url=forum.php?mod=redirect&goto=findpost&pid=32652&ptid=11765]ngswfx 发表于 2016-6-28 15:05[/url]
要通过命令看，help看，哪些命令前面带nand的才能用。ls不是uboot下的命令。

uboot下只能用help能看 ...[/quote]

我现在 准备重新烧去 spi，
1 怎么洗掉 nand flash 上的刚刚的程序
2 怎么设置 开发板的ip address
谢谢

本帖最后由 ngswfx 于 2016-6-28 15:13 编辑

[quote][url=forum.php?mod=redirect&goto=findpost&pid=32655&ptid=11765]2272943826 发表于 2016-6-28 15:10[/url]
我现在 准备重新烧去 spi，
1 怎么洗掉 nand flash 上的刚刚的程序
2 怎么设置 开发板的ip address
[/quote]

这个不难，只要在uboot环境，直接改env信息即可。改写完，printenv看看对没对，然后reset重启即可应用了。

setenv ipaddr 192.168.2.10             //板子的ｉＰ
setenv serverip 192.168.2.245       //PＣ机器ＩＰ，就是ＴＦＴＰ所在机器ＩＰ
sa             //uboot支持命令简写 其实就是saveenv

本帖最后由 2272943826 于 2016-7-21 15:07 编辑

[quote][url=forum.php?mod=redirect&goto=findpost&pid=32656&ptid=11765]ngswfx 发表于 2016-6-28 15:11[/url]
这个不难，只要在uboot环境，直接改env信息即可。改写完，printenv看看对没对，然后reset重启即可应用 ...[/quote]

连接开发板的时候，
1 连接 RS232 cable
2 连接网线

谢谢

本帖最后由 ngswfx 于 2016-6-28 15:27 编辑

[quote][url=forum.php?mod=redirect&goto=findpost&pid=32658&ptid=11765]2272943826 发表于 2016-6-28 15:16[/url]
连接开发板的时候，
1 连接 RS232 cable
2 是否需要连接 网线，如果需要的话， 网线一头插在 开发板上 ...[/quote]

连接方式和你现在一样呀，你烧nand的时候，应该已经用过网络了。


host 192.168.1.82 is alive
(OK)
"ping 192.168.1.82" command sent successfully!
ETH0: PHY(phyaddr=1, rgmii) link UP: DUPLEX=FULL : SPEED=1000M                      ///////////啥ＮＢ开发板，网络还是千兆的。{:3_53:}
MAC:   00-E0-88-37-FA-B1
TFTP from server 192.168.1.82; our IP address is 192.168.1.40
Download Filename 'rootfs_hi3516a_2k_4bit.yaffs2'.
Download to address: 0x81000000
Downloading: *
###########################################################
done

//////////////////////////如果自己配置tftp服务器，然后自己通过命令方式练习烧写的话，主要就是在windows或者ubuntu上弄个TFTP server，然后把需要开发板访问的升级包，都放到tftp目录下。开发板通过tftp命令就可以直接访问了。

///关于232连接和网络连接的问题，你就记着：如果只通过工具烧写fastboot(u-boot)，可以不用接网线，其他的就必须用网线了，uboot小，是通过232直接传过去的，其他模块通过网络ＴＦＴＰ传的。你仔细看你烧写ＮＡＮＤ那个log，里面有好多命令，流程，有好多具体命令动作。

本帖最后由 2272943826 于 2016-11-25 09:40 编辑

[quote][url=forum.php?mod=redirect&goto=findpost&pid=32659&ptid=11765]ngswfx 发表于 2016-6-28 15:18[/url]
连接方式和你现在一样呀，你烧nand的时候，应该已经用过网络了。


[/quote]

谢谢您的用心回复

本帖最后由 2272943826 于 2016-7-21 15:07 编辑

[quote][url=forum.php?mod=redirect&goto=findpost&pid=32659&ptid=11765]ngswfx 发表于 2016-6-28 15:18[/url]
连接方式和你现在一样呀，你烧nand的时候，应该已经用过网络了。


[/quote]

谢谢您的回复

本帖最后由 2272943826 于 2016-7-21 15:08 编辑

[quote][url=forum.php?mod=redirect&goto=findpost&pid=32659&ptid=11765]ngswfx 发表于 2016-6-28 15:18[/url]
连接方式和你现在一样呀，你烧nand的时候，应该已经用过网络了。


[/quote]

谢谢您的回复

[quote][url=forum.php?mod=redirect&goto=findpost&pid=32661&ptid=11765]2272943826 发表于 2016-6-28 15:25[/url]
谢谢您的用心回复

1 我现在nand flash 刚才烧写的 程序 需要删除吗？ 如果需要，怎么办
[/quote]

不用管它，不影响，如果想擦除，等spi成功后，在uboot环境下，help，看看有没有nand erase命令，擦了就是了。

本帖最后由 2272943826 于 2016-7-21 15:08 编辑

[quote][url=forum.php?mod=redirect&goto=findpost&pid=32647&ptid=11765]ngswfx 发表于 2016-6-28 14:55[/url]
你这个有2片，第一个是32Ｍ的ＳＰＩ，另外一片是256Ｍ的ＮＡＮＤ。

通常ＳＰＩ用来放uboot kernel roo ...[/quote]

我的想法，板子先去 spi flash， 然后再去 nand flash 。  
我是新手，谢谢， 多多关照:P

本帖最后由 ngswfx 于 2016-6-28 16:25 编辑

[quote][url=forum.php?mod=redirect&goto=findpost&pid=32671&ptid=11765]2272943826 发表于 2016-6-28 16:10[/url]
我的想法，板子先去 spi flash， 然后再去 nand flash 。 那么板子什么去 bootrom 呢？
我是新手，谢谢 ...[/quote]

bootrom指的是芯片里面的一个引导，很小，说白了，你用fastboot功能能烧写，就是靠这个bootrom起作用的，它就负责从串口上读取数据，识别是不是符合要求的数据，如果是就按照要求写spi等flash的数据。

它这个引导模块，和单片机上的引导程序类似，很小，只有4Ｋ左右。里面的程序都是汇编的。如果默认这个模块启动，才会接收串口过来的升级数据。

如果启动时，一定时间内，没有收到串口过来符合要求的数据，自动转入SPI启动或者nand启动。

只要把ＳＰＩ里面Ｕboot搞定，通过配置env变量，接写来由那个flash负责接下来的Ｋernel过程，都可以做到了。
甚至可以让usb盘接管，或者ＳＤ卡，或者其他存储介质。只不过牵扯东西多，另外要看芯片厂商是否这么设计，提供了相应解决方案没。

3516通常不会设计sd或者usb启动。

///////////板子上，你看有没有跳线，设置启动顺序的，如果没有，就别纠结了，默认就是spi启动，启动uboot后，你倒是可以通过配置env，让kernel在nand里面。这个应该能做通（虽然我没调试过这中2片flash的板子）。

//另外32Ｍ的ＳＰＩ非常大了，对于ＩＰＣ方案而言，都已经浪费了（大量市场上卖的成品，有些小的是8Ｍ flash ,比较大的也就16Ｍ，32Ｍ估计是厂商脑子坏了（贵，一个板子差几块钱），或者内部集成了好多特殊程序才可能用这么大的flash），256Ｍ nand主要还是体现开发板研究学习之用，体现在特殊后期功能研发上，例如做一些更ＮＢ的功能。