AM335x Beaglebone Black eMMC烧写记录

Hi Sean:

若你也是用bbb或參考其硬體設計, 看你 log, 是開機 mmc 沒有抓取到正確位置, 你可以參考 " BB Black EMMC烧写全记录.pdf"

最後 3.總結和參考文檔, 有說明如何修改 mmc 位置

"

Hi Hank,

    感谢你这么快的回复，已经能从emmc启动，感谢。

你好，

    我有一个疑问，我在U-BOOT里改成默认是从MMC1启动，在插上SD启动卡后是不是就不会从SD卡里启动了，因为我在内核添加的打印信息没有出来，

不是SD卡里的内核镜像文件，但是挂载的文件系统却是SD卡里面的，为什么会这样，有点不明白，希望你能为我答疑解惑

用官网release的debian img从SD烧写到flash（4G）时失败：

copying: [/dev/mmcblk0] -> [/dev/mmcblk1]
lsblk:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0 179:0 0 14.9G 0 disk
|-mmcblk0p1 179:1 0 96M 0 part /boot/uboot
`-mmcblk0p2 179:2 0 3.5G 0 part /
-----------------------------
df -h | grep rootfs:
df: cannot read table of mounted file systems: No such file or directory
-----------------------------
Error: [/dev/mmcblk1] does not exist
writing to [/dev/mmcblk1] failed...
[ 6.781693] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[ 6.781693]
[ 6.796160] [<c00114f1>] (unwind_backtrace+0x1/0x9c) from [<c04cb2fd>] (panic+0x59/0x15c)
[ 6.807215] [<c04cb2fd>] (panic+0x59/0x15c) from [<c0033acf>] (do_exit+0x5ff/0x68c)
[ 6.817759] [<c0033acf>] (do_exit+0x5ff/0x68c) from [<c0033b9f>] (do_group_exit+0x27/0x6c)

UBuntu都可以烧写成功，eMMC应该没坏，也是4G的，可能会是什么原因？

你好：

      请问我用UniFlash 通过USB烧写时一直显示0%不动，而且串口也没有信息输出，这可能是因为什么原因啊？

检查uniflash版本，V3版本，其它的坑爹。另外看下安装目录下的第三方软件，查看opendhcp（好像是）的log文件，里面网络连接方面的情况，如果是通信顺利，会有那些文件，类似uboot servered, rootfs servered...如果没有，表明网络通信根本不通，相应文件没当下来，更别说看串口输出了。

你好：

 我的opendhcp的log如下，能帮我看看是什么问题吗？

[07-Jul-15 09:58:57] Logging: All
[07-Jul-15 09:58:57] DHCP Range: 192.168.2.2-192.168.2.254/255.255.255.0
[07-Jul-15 09:58:57] Open DHCP Server Version 1.59 Windows Build 1036 Starting...
[07-Jul-15 09:58:57] Server Name: 2014-20140719FL
[07-Jul-15 09:58:57] Detecting Static Interfaces..
[07-Jul-15 09:58:57] Lease Status URL: http://127.0.0.1:6789
[07-Jul-15 09:58:57] Listening On: 192.168.2.1
[07-Jul-15 09:59:01] BOOTPREQUEST for d0:5f:b8:fb:e8:b3 () from interface 192.168.2.1 received
[07-Jul-15 09:59:44] BOOTPREQUEST for d0:5f:b8:fb:e8:b3 () from interface 192.168.2.1 received
[07-Jul-15 09:59:44] BOOTP Host d0:5f:b8:fb:e8:b3 (Hostd05fb8fbe8b3) allotted 192.168.2.3
[07-Jul-15 09:59:47] BOOTPREQUEST for d0:5f:b8:fb:e8:b3 () from interface 192.168.2.1 received
[07-Jul-15 09:59:47] BOOTP Host d0:5f:b8:fb:e8:b3 (Hostd05fb8fbe8b3) allotted 192.168.2.3
[07-Jul-15 10:24:37] Open DHCP Server Version 1.59 Windows Build 1036 Starting...
[07-Jul-15 10:24:37] Logging: All
[07-Jul-15 10:24:37] DHCP Range: 192.168.2.2-192.168.2.254/255.255.255.0
[07-Jul-15 10:24:37] Server Name: 2014-20140719FL
[07-Jul-15 10:24:37] Detecting Static Interfaces..
[07-Jul-15 10:24:37] Lease Status URL: http://127.0.0.1:6789
[07-Jul-15 10:24:37] Listening On: 192.168.2.1
[07-Jul-15 10:27:51] Network changed, re-detecting Static Interfaces..
[07-Jul-15 10:27:51] Warning: Section [LISTEN_ON], Interface 192.168.2.1 not available, ignored
[07-Jul-15 10:27:51] No Static Interface ready, Waiting...
[07-Jul-15 10:27:51] Retrying failed Listening Interfaces..
[07-Jul-15 10:27:51] Warning: Section [LISTEN_ON], Interface 192.168.2.1 not available, ignored
[07-Jul-15 10:27:51] No Static Interface ready, Waiting...
[07-Jul-15 10:27:51] Retrying failed Listening Interfaces..
[07-Jul-15 10:27:51] Warning: Section [LISTEN_ON], Interface 192.168.2.1 not available, ignored
[07-Jul-15 10:27:51] No Static Interface ready, Waiting...
[07-Jul-15 10:27:51] Retrying failed Listening Interfaces..
[07-Jul-15 10:27:51] Warning: Section [LISTEN_ON], Interface 192.168.2.1 not available, ignored
[07-Jul-15 10:27:51] No Static Interface ready, Waiting...
[07-Jul-15 10:27:51] Retrying failed Listening Interfaces..
[07-Jul-15 10:27:51] Warning: Section [LISTEN_ON], Interface 192.168.2.1 not available, ignored
[07-Jul-15 10:27:51] No Static Interface ready, Waiting...
[07-Jul-15 10:27:51] Retrying failed Listening Interfaces..
[07-Jul-15 10:27:51] Warning: Section [LISTEN_ON], Interface 192.168.2.1 not available, ignored
[07-Jul-15 10:27:51] No Static Interface ready, Waiting...
[07-Jul-15 10:27:51] Retrying failed Listening Interfaces..
[07-Jul-15 10:27:51] Warning: Section [LISTEN_ON], Interface 192.168.2.1 not available, ignored
[07-Jul-15 10:27:51] No Static Interface ready, Waiting...
[07-Jul-15 10:27:51] Retrying failed Listening Interfaces..
[07-Jul-15 10:27:51] Warning: Section [LISTEN_ON], Interface 192.168.2.1 not available, ignored
[07-Jul-15 10:27:51] No Static Interface ready, Waiting...
[07-Jul-15 10:27:51] Closing Network Connections...
[07-Jul-15 10:27:51] Open DHCP Server Stopped !

而且am335x的UART0接的USB TO UART 也一点东西都没有输出，am335x的UART0需要做什么配置吗？

opentftp的log如下：

[07-Jul-15 15:14:43] Open TFTP Server MultiThreaded Version 1.64 Windows Built 2001 Starting..
[07-Jul-15 15:14:43] starting TFTP service
[07-Jul-15 15:14:43] alias / is mapped to C:\AM335x_Flashtool\images\
[07-Jul-15 15:14:43] permitted clients: all
[07-Jul-15 15:14:43] server port range: all
[07-Jul-15 15:14:43] max blksize: 65464
[07-Jul-15 15:14:43] default blksize: 512
[07-Jul-15 15:14:43] default timeout: 3
[07-Jul-15 15:14:43] file read allowed: Yes
[07-Jul-15 15:14:43] file create allowed: No
[07-Jul-15 15:14:43] file overwrite allowed: No
[07-Jul-15 15:14:43] thread pool size: 1
[07-Jul-15 15:14:43] Listening On: 192.168.2.1:69
[07-Jul-15 15:14:48] Client 192.168.2.3:1234 C:\AM335x_Flashtool\images\u-boot-spl-restore.bin, 208 Blocks Served

每次都是到这里就卡住了，这是为什么啊？

貌似pc端没什么问题，相应的文件有送出，只是开发板没有执行。用uart串口看调试信息，如果没有如何输出，只有“CCCCCC...”，基本上就是spl有问题了。按照楼主文档制作spl。或者你试下附件里的spl，直至log文件里挨个顺序有所需文件servered。

开发板上USB-to-serial，一开始不能用，我也没用过。就uart了（用的FTDI232转，淘宝上有），115200，flowcontrol-no。

另外，至于烧写各种文件，完全取决于debrick脚本。如果新添了功能需要kernel支持，flasher的kernel就得重新编译。

我也是自己买的USB-to-serial，直接接在了am3358的uart0上，但是板子上电时，什么都没有输出，连“CCCCCCC”都没有，这是为什么？uart0显示log输出需要特别的配置吗？

我用你给的flasher也试了一下，还是不行，我如果提供的spl的名字不为u-boot-spl-restore.bin uniflash3.0安装目录中third_party/sitara/log/opentftp.log中就会有

[09-Jul-15 13:56:26] Client 192.168.2.3:1234 C:\AM335x_Flashtool\images\u-boot-spl-restore.bin, File not found or No Access

上面这个信息输出，我一改回来log输出就如下了

[09-Jul-15 14:00:38] Client 192.168.2.3:1234 C:\AM335x_Flashtool\images\u-boot-spl-restore.bin, 200 Blocks Served

请问我的tftp服务有没有问题？

文件名是由opendhcp配置文件规定的，从输出上看，dhcp没问题。

串口我买的这个淘宝红色的，先把你的串口搞定。另外就是注意是否还有要求配置网络IP。一共有2次需要配置server IP在windows网络配置下。

串口插上后（ubuntu）会有ttyUSBx出现，minicom配置到那个端口

USB转TTL 支持3.3V 5V双电源 FT232RL Arduino FTDI MWC调试器

在Ubuntu上插上USB to TTL 后有ttyUSB0出现，我将minicom配置到了这个端口，但上电依然没有“CCCCC”，也没有其他的信息。

另外下图中的Device MAC ADDR 和IP ADDR指的是我板子的MAC 和IP 吗？

确定你的串口是否工作，先用sd卡的启动看有信息没，没有，配置你的minicom，直到有正常的输出。

没意外的话，mac和IP是你开发板的资源。

你好， 能将你这边正确的opendhcp, opentftp log日志发一份给我看看么？ 我好对比一下，谢谢。

The log following is waiting for request from board. The attachment is the successful file log.

The opendhcp.ini file is the configuration file.

[03-Jun-15 15:45:28] Logging: All
er Version 1.59 Windows Build 1036 Starting...
[03-Jun-15 15:45:28] Server Name: WKS-57
[03-Jun-15 15:45:28] Detecting Static Interfaces..
nterface 192.168.100.1 not available, ignored
[03-Jun-15 15:45:28] No Static Interface ready, Waiting...
[03-Jun-15 15:45:28] Retrying failed Listening Interfaces..
[03-Jun-15 15:45:28] No Static Interface ready, Waiting...
[03-Jun-15 15:45:28] Warning: 192.168.100.1 UDP Port 67 already in use
[03-Jun-15 15:45:28] Retrying failed Listening Interfaces..
[03-Jun-15 15:45:28] Lease Status URL: http://127.0.0.1:6789
[03-Jun-15 15:45:28] Listening On: 192.168.100.1
[03-Jun-15 15:45:40] BOOTPREQUEST for d0:39:72:4b:78:19 () from interface 192.168.100.1 received
[03-Jun-15 15:45:40] BOOTP Host d0:39:72:4b:78:19 (Hostd039724b7819) allotted 192.168.100.2
[03-Jun-15 15:45:42] Network changed, re-detecting Static Interfaces..
[03-Jun-15 15:45:42] Warning: Section [LISTEN_ON], Interface 192.168.100.1 not available, ignored
[03-Jun-15 15:45:42] No Static Interface ready, Waiting...
[03-Jun-15 15:45:42] Retrying failed Listening Interfaces..
[03-Jun-15 15:45:42] Warning: 192.168.100.1 UDP Port 67 already in use
[03-Jun-15 15:45:42] No Static Interface ready, Waiting...
[03-Jun-15 15:45:42] Retrying failed Listening Interfaces..
[03-Jun-15 15:45:42] Lease Status URL: http://127.0.0.1:6789
[03-Jun-15 15:45:42] Listening On: 192.168.100.1
[03-Jun-15 15:45:48] BOOTPREQUEST for d0:39:72:4b:78:19 () from interface 192.168.100.1 received
[03-Jun-15 15:45:48] BOOTP Host d0:39:72:4b:78:19 (Hostd039724b7819) allotted 192.168.100.2
[03-Jun-15 15:45:50] Network changed, re-detecting Static Interfaces..
[03-Jun-15 15:45:50] Warning: Section [LISTEN_ON], Interface 192.168.100.1 not available, ignored
[03-Jun-15 15:45:50] No Static Interface ready, Waiting...
[03-Jun-15 15:45:50] Retrying failed Listening Interfaces..
[03-Jun-15 15:45:50] No Static Interface ready, Waiting...
[03-Jun-15 15:45:50] Warning: 192.168.100.1 UDP Port 67 already in use
[03-Jun-15 15:45:50] Retrying failed Listening Interfaces..
[03-Jun-15 15:45:50] Lease Status URL: http://127.0.0.1:6789
[03-Jun-15 15:45:50] Listening On: 192.168.100.1
[03-Jun-15 15:45:56] DHCPDISCOVER for d0:39:72:4b:78:19 () from interface 192.168.100.1 received
[03-Jun-15 15:45:56] Host d0:39:72:4b:78:19 (Hostd039724b7819) offered 192.168.100.2
[03-Jun-15 15:45:56] DHCPREQUEST for d0:39:72:4b:78:19 () from interface 192.168.100.1 received
[03-Jun-15 15:45:56] Host d0:39:72:4b:78:19 (Hostd039724b7819) allotted 192.168.100.2 for 600 seconds
[03-Jun-15 15:45:59] Network changed, re-detecting Static Interfaces..
[03-Jun-15 15:45:59] No Static Interface ready, Waiting...
[03-Jun-15 15:45:59] Warning: Section [LISTEN_ON], Interface 192.168.100.1 not available, ignored
[03-Jun-15 15:45:59] Retrying failed Listening Interfaces..
[03-Jun-15 15:45:59] Warning: 192.168.100.1 UDP Port 67 already in use
[03-Jun-15 15:45:59] No Static Interface ready, Waiting...
[03-Jun-15 15:45:59] Retrying failed Listening Interfaces..
[03-Jun-15 15:45:59] Lease Status URL: http://127.0.0.1:6789
[03-Jun-15 15:45:59] Listening On: 192.168.100.1
[03-Jun-15 15:46:06] Network changed, re-detecting Static Interfaces..
[03-Jun-15 15:46:06] Warning: Section [LISTEN_ON], Interface 192.168.100.1 not available, ignored
[03-Jun-15 15:46:06] No Static Interface ready, Waiting...
[03-Jun-15 15:46:06] Retrying failed Listening Interfaces..
[03-Jun-15 15:46:06] Warning: Section [LISTEN_ON], Interface 192.168.100.1 not available, ignored
[03-Jun-15 15:46:06] No Static Interface ready, Waiting...
[03-Jun-15 15:46:06] Retrying failed Listening Interfaces..
[03-Jun-15 15:46:06] Lease Status URL: http://127.0.0.1:6789
[03-Jun-15 15:46:06] Listening On: 192.168.100.1
[03-Jun-15 15:46:20] DHCPDISCOVER for ba:c4:39:f1:13:4d () from interface 192.168.100.1 received
[03-Jun-15 15:46:20] Host ba:c4:39:f1:13:4d (Hostbac439f1134d) offered 192.168.100.7
[03-Jun-15 15:46:20] DHCPREQUEST for ba:c4:39:f1:13:4d () from interface 192.168.100.1 received
[03-Jun-15 15:46:20] Host ba:c4:39:f1:13:4d (Hostbac439f1134d) allotted 192.168.100.7 for 600 seconds
[03-Jun-15 15:51:20] DHCPREQUEST for ba:c4:39:f1:13:4d () from interface 192.168.100.1 received
[03-Jun-15 15:51:20] Host ba:c4:39:f1:13:4d (Hostbac439f1134d) renewed 192.168.100.7 for 600 seconds
[03-Jun-15 15:56:20] DHCPREQUEST for ba:c4:39:f1:13:4d () from interface 192.168.100.1 received
[03-Jun-15 15:56:20] Host ba:c4:39:f1:13:4d (Hostbac439f1134d) renewed 192.168.100.7 for 600 seconds
[03-Jun-15 15:58:06] Network changed, re-detecting Static Interfaces..
[03-Jun-15 15:58:06] Warning: Section [LISTEN_ON], Interface 192.168.100.1 not available, ignored
[03-Jun-15 15:58:06] No Static Interface ready, Waiting...
[03-Jun-15 15:58:06] Retrying failed Listening Interfaces..
[03-Jun-15 15:58:06] Warning: Section [LISTEN_ON], Interface 192.168.100.1 not available, ignored
[03-Jun-15 15:58:06] No Static Interface ready, Waiting...
[03-Jun-15 15:58:06] Retrying failed Listening Interfaces..
[03-Jun-15 15:58:06] Warning: Section [LISTEN_ON], Interface 192.168.100.1 not available, ignored
[03-Jun-15 15:58:06] No Static Interface ready, Waiting...
[03-Jun-15 15:58:06] Retrying failed Listening Interfaces..
[03-Jun-15 15:58:06] Warning: Section [LISTEN_ON], Interface 192.168.100.1 not available, ignored
[03-Jun-15 15:58:06] No Static Interface ready, Waiting...
[03-Jun-15 15:58:06] Retrying failed Listening Interfaces..
[03-Jun-15 15:58:06] Warning: Section [LISTEN_ON], Interface 192.168.100.1 not available, ignored
[03-Jun-15 15:58:06] No Static Interface ready, Waiting...

收到了，非常感谢。 我们的opentftp 到 u-boot-spl-restore.bin, 200 Blocks Served这项就停住了，后面的u-boot-restore.img，uImage，debrick.sh， boot_partition.tar.gz， rootfs_partition.tar.bz2都没有加载上。 

同时串口通信也起不来。

我们检查了下  1  电源管理芯片的供电电压正确。  2 32K 的晶振波形好像不正确。  所以可能是晶振有问题。准备换晶振试试。 

问一下，u-boot-restore.img文件是否和硬件配置强相关？即u-boot-restore.img文件不正确会影响到加载不上去？

All the images are based on BBB. For customized board, you may need ccsv (JTAG) to debug the bare-metal, if the images cannot run on the board.

你好，Jian Zhou ，我根据你的文件，用SD来烧写是，总是烧写不成功：

ifconfig: SIOCGIFFLAGS: No such device

********************************************

Sitara Flash Fetcher is complete. Executing /home/root/debrick.sh.

****************************************************

****************************************************

Sitara Example Flashing Script - 02/11/2014

1+0 records in

1+0 records out

No partition found. Continuing.

Partitioning the eMMC...

Checking that no-one is using this disk right no[ 10.321380] mmcblk1: unknown partition table

w ...

OK

Disk /dev/mmcblk1: 477 cylinders, 255 heads, 63 sectors/track

sfdisk: ERROR: sector 0 does not have an msdos signature

sfdisk: /dev/mmcblk1: unrecognized partition table type

Old situation:

sfdisk: No partitions found

New situation:

Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

 Device Boot Start End [ 10.374633] mmcblk1: p1 p2

 #cyls #blocks Id System

/dev/mmcblk1p1 * 0+ 8 9- 72261 c W95 FAT32 (LBA)

/dev/mmcblk1p2 10 476 467 3751177+ 83 Linux

/dev/mmcblk1p3 0 - 0 0 0 Empty

/dev/mmcblk1p4 0 - 0 0 0 Empty

Successfully wrote the new partition table

Re-reading the partition table ...

If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)

to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1

(See fdisk(8).)

[ 11.044891] kjournald starting. Commit interval 5 seconds

[ 11.064300] EXT3-fs (mmcblk1p2): using internal journal

[ 11.069824] EXT3-fs (mmcblk1p2): mounted filesystem with ordered data mode

Found mounted partition(s) on /dev/mmcblk1: /media/mmcblk1p1 /media/mmcblk1p2

4k erase on /dev/mmcblk1p1

1+0 records in

1+0 records out

4k erase on /dev/mmcblk1p2

1+0 records in

1+0 records out

1+0 records in

1+0 records out

Formatting the eMMC into 2 partitions...

mkfs.vfat 2.11 (12 Mar 2005)

mke2fs 1.42.1 (17-Feb-2012)

Discarding device blocks: done

Filesystem label=rootfs

OS type: Linux

Block size=4096 (log=2)

Fragment size=4096 (log=2)

Stride=0 blocks, Stripe width=0 blocks

234784 inodes, 937794 blocks

46889 blocks (5.00%) reserved for the super user

First data block=0

Maximum filesystem blocks=960495616

29 block groups

32768 blocks per group, 32768 fragments per group

8096 inodes per group

Superblock backups stored on blocks:

 32768, 98304, 163840, 229376, 294912, 819200, 884736

Allocating group tables: done

Writing inode tables: done

Creating journal (16384 blocks): done

Writing superblocks and filesystem accounting information: done

Formatting done.

mkdir: can't create directory 'tmp_boot': File exists

mkdir: can't create directory 'tmp_rootfs': File exists

[ 84.492828] kjournald starting. Commit interval 5 seconds

[ 84.501068] EXT3-fs (mmcblk1p2): using internal journal

[ 84.506591] EXT3-fs (mmcblk1p2): mounted filesystem with ordered data mode

Copying Files...

tar: can't open 'boot_partition.tar.gz': No such file or directory

Command exited with non-zero status 1

real 0m 0.07s

user 0m 0.00s

sys 0m 0.00s

rm: can't remove 'boot_partition.tar.gz': No such file or directory

Boot partition done.

tar: can't open 'rootfs_partition.tar.gz': No such file or directory

Command exited with non-zero status 1

real 0m 0.00s

user 0m 0.00s

sys 0m 0.00s

rm: can't remove 'rootfs_partition.tar.gz': No such file or directory

RootFS partition done.

It took 74 seconds to complete this task...

********************************************

Sitara Example Flash Script is complete.

Stopping Bootlog daemon: bootlogd.

这可能是什么原因，总是说找不到boot_partition.tar.gz与rootfs_partition.tar.gz，但我确实是把他们与debrick.sh都放在/home/root下的？

To shanshan wan

检查下是不是相对路径和绝对路径的关系。。。

您好，芯片协议4.41选择MMC0还是MMC1呢？

请TI员工更新SDK07或SDK08支持EMMC，我自己试了好多次都没成功，把uboot和rootfs复制到tf卡的2个分区，插入tf卡可以启动，把同样的文件复制到emmc中的2个分区，一直无法启动

eMMC卡启动信息有什么打印失败信息么？

to shanshan wan,

更改下这两个文件的属性为777，另外改为绝对路径试下

要使用emmc，ti的工程师推荐的uboot编译参数是

make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- O=am335x_evm am335x_boneblack

以此方式编译出来的uboot，即使在am335x_evm.h中修改了fdtfile和devnum等参数，但是启动时却是默认参数，也就是修改am335x_evm.h文件无效，只有编译时以make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- O=am335x_evm am335x_evm方式，修改am335x_evm.h文件参数才会有效，请问是什么原因

我们的板子的emmc是4.0的，现在接在mmc1上面。那这个板子是否就肯定不能从emmc启动了？或者说除了上面的方法，是否还有其他方法烧写emmc，让mmc1上面的低于4.4.1的emmc启动。

U-Boot SPL 2013.01.01 (Oct 21 2014 - 14:08:51)
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
Using default environment

usb_ether
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC 54:4a:16:bc:1b:48
HOST MAC de:ad:be:af:00:00
RNDIS ready
musb-hdrc: peripheral reset irq lost!
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
USB RNDIS network up!
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
Using usb_ether device
TFTP from server 192.168.100.1; our IP address is 192.168.100.2
Filename 'u-boot-restore.img'.
Load address: 0x807fffc0
Loading: *#########################
890.6 KiB/s
done
Bytes transferred = 365104 (59230 hex)

U-Boot 2013.01.01 (Oct 21 2014 - 14:08:51)

I2C: ready
DRAM: 512 MiB
WARNING: Caches not enabled
NAND: No NAND device found!!!
0 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - readenv() failed, using default environment

musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
Net: <ethaddr> not set. Validating first E-fuse MAC
cpsw, usb_ether
Hit any key to stop autoboot: 0
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC 54:4a:16:bc:1b:48
HOST MAC de:ad:be:af:00:00
RNDIS ready
musb-hdrc: peripheral reset irq lost!
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
USB RNDIS network up!
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
DHCP client bound to address 192.168.100.2
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC 54:4a:16:bc:1b:48
HOST MAC de:ad:be:af:00:00
RNDIS ready
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
USB RNDIS network up!
Using usb_ether device
TFTP from server 192.168.100.1; our IP address is 192.168.100.2
Filename 'uImage'.
Load address: 0x81000000
Loading: *T #################################################################
#################################################################
#################################################################
#################################################################
################################
680.7 KiB/s
done
Bytes transferred = 4283056 (415ab0 hex)
## Booting kernel from Legacy Image at 81000000 ...
Image Name: linux-3.14.26
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4282992 Bytes = 4.1 MiB
Load Address: 30008000
Entry Point: 30008000
Verifying Checksum ... OK
Loading Kernel Image ...

IP也设了两次，成功读取u-boot-restore.img和uImage，然后就一直停在这。。。这是为什么？

另外我是用adk08的版本，这种方法还适用么？

AM335x BeagleBone BlackSD卡启动正常，当使用flasher.sh烧写eMMC后（SDK02.00），出现以下信息，请问是什么原因？

当eMMC内有内容后，使用flasher.sh烧写一遍后，不能启动打印CCC，再烧写一遍后，就可以启动了，是需要烧写两遍吗？谢谢！

U-Boot SPL 2015.07 (Oct 07 2015 - 14:27:57)

reading args
spl_load_image_fat_os: error reading image args, err - -1
reading u-boot.img
reading u-boot.img

U-Boot 2015.07 (Oct 07 2015 - 14:27:57 -0400)

Watchdog enabled
I2C: ready
DRAM: 512 MiB
NAND: 0 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Card did not respond to voltage select!
** Bad device mmc 0 **
Using default environment

Net: <ethaddr> not set. Validating first E-fuse MAC
cpsw, usb_ether
Hit any key to stop autoboot: 0
Card did not respond to voltage select!
Card did not respond to voltage select!
switch to partitions #0, OK
mmc1(part 0) is current device
SD/MMC found on device 1
reading boot.scr
** Unable to read file boot.scr **
reading uEnv.txt
** Unable to read file uEnv.txt **
** File not found /boot/zImage **
Booting from nand ...

no devices available

no devices available
Bad Linux ARM zImage magic!
U-Boot#

eMMC烧写SDK02.00里预编译好的文件系统，启动后出现如下问题，请问是什么原因？谢谢

[ 1.591593] VFS: PARTUUID= is invalid.
[ 1.591593] Expected PARTUUID=<valid-uuid-id>[/PARTNROFF=%d]
[ 1.601146] Disabling rootwait; root= is invalid.
[ 1.606159] VFS: Cannot open root device "PARTUUID=" or unknown-block(0,0): error -6
[ 1.614046] Please append a correct "root=" boot option; here are the available partitions:
[ 1.622478] 0100 16384 ram0 (driver?)
[ 1.627124] 0101 16384 ram1 (driver?)
[ 1.631801] 0102 16384 ram2 (driver?)
[ 1.636445] 0103 16384 ram3 (driver?)
[ 1.641086] 0104 16384 ram4 (driver?)
[ 1.645755] 0105 16384 ram5 (driver?)
[ 1.650394] 0106 16384 ram6 (driver?)
[ 1.655051] 0107 16384 ram7 (driver?)
[ 1.659692] 0108 16384 ram8 (driver?)
[ 1.664346] 0109 16384 ram9 (driver?)
[ 1.668988] 010a 16384 ram10 (driver?)
[ 1.673730] 010b 16384 ram11 (driver?)
[ 1.678458] 010c 16384 ram12 (driver?)
[ 1.683200] 010d 16384 ram13 (driver?)
[ 1.687928] 010e 16384 ram14 (driver?)
[ 1.692668] 010f 16384 ram15 (driver?)
[ 1.697403] b300 3776512 mmcblk0 driver: mmcblk
[ 1.702754] b301 72261 mmcblk0p1 00000000-01
[ 1.708093] b302 3694950 mmcblk0p2 00000000-02
[ 1.713444] b310 2048 mmcblk0boot1 (driver?)
[ 1.718782] b308 2048 mmcblk0boot0 (driver?)
[ 1.724133] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 1.732436] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

现在我也通过usb口来烧写程序，用的BBB，也是遇到27%就停下来的问题。从串口抓的log如下，

TFTP from server 192.168.100.1; our IP address is 192.168.100.3
Filename 'uImage'.
Load address: 0x81000000
Loading: T #################################################################
#################################################################
#################################################################
#################################################################
############################
674.8 KiB/s
done
Bytes transferred = 4215568 (405310 hex)
## Booting kernel from Legacy Image at 81000000 ...
Image Name: Linux-3.8.6
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4215504 Bytes = 4 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Error: unrecognized/unsupported machine ID (r1 = 0x00000e05).

Available machine support:

ID (hex) NAME
ffffffff Generic OMAP4 (Flattened Device Tree)
ffffffff Generic AM33XX (Flattened Device Tree)
ffffffff Generic OMAP3-GP (Flattened Device Tree)
ffffffff Generic OMAP3 (Flattened Device Tree)
0000060a OMAP3 Beagle Board
00000a9d IGEP OMAP3 module
00000928 IGEP v2 board
00000ae7 OMAP4 Panda board

Please check your kernel config and/or bootloader.

似乎是机器码不对，uboot跟linux的机器码不对？

我编译uboot跟内核程序的时候都是按照说明来的，

make O=am335x CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm am335x_evm  这个是编译uboot的

make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- uImage dtbs  这个是编译kernel的

在tftp的根目录下，我放了如下几个文件，之前我只放前面三个文件，但是不能用，都放上之后，能够有27%的进度了，但是仍然不行。

debrick.sh

boot_partition.tar.gz

rootfs_partition.tar.gz

u-boot.img

u-boot-restore.img

u-boot-spl-restore.bin

uImage

请问下，我用的是V3.4.1.00012，这个版本可以吗？我的dhcp和tftp的log情况如下

还有我的uniflash默认配置入下，点击start flashing，下面的状态栏什么都没有，串口输出信息为正常的启动，应该是完全没有从Windows目录load什么东西

你好我把移植好的andriod4.2的内核烧写到了eMMC中，启动安卓的时候发现了如下的错误，并且系统启动不起来了。请问下，这个问题如何解决，

当前的内核在SD卡中是可以正确启动的。

附件是我写的脚本文件。

[ 2.805023] mmc1: new high speed MMC card at address 0001
[ 2.811767] mmcblk0: mmc1:0001 S10004 3.56 GiB 
[ 2.816864] mmcblk0boot0: mmc1:0001 S10004 partition 1 4.00 MiB
[ 2.823394] mmcblk0boot1: mmc1:0001 S10004 partition 2 4.00 MiB
[ 2.831787] mmcblk0: p1 p2
[ 2.839294] mmcblk0boot1: unknown partition table
[ 2.847991] mmcblk0boot0: unknown partition table
[ 3.569366] EXT4-fs (mmcblk0p2): recovery complete
[ 3.576873] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 3.585632] VFS: Mounted root (ext4 filesystem) on device 179:2.
[ 3.593170] Freeing init memory: 344K
[ 3.621154] init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
[ 3.787139] init: cannot open '/initlogo.rle'
[ 8.105102] fs_mgr: Cannot mount filesystem on /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p3 at /data
[ 8.115203] init: fs_mgr_mount_all returned an error
[ 8.159057] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
[ 8.230346] android_usb: already disabled
[ 8.237792] android_usb: already disabled
[ 8.242462] android_usb: already disabled
[ 8.263916] adb_bind_config
[ 8.270477] adb_bind_config
[ 8.410430] adb_open
[ 8.450775] Disabling lock debugging due to kernel taint
root@android:/ # [ 8.528106] android_work: sent uevent USB_STATE=CONNECTED
[ 8.534088] android_work: sent uevent USB_STATE=DISCONNECTED
[ 8.555847] omaplfb: OMAPLFB_Init: OMAPLFBInit failed
[ 8.651916] android_work: sent uevent USB_STATE=CONNECTED
[ 8.730743] gadget: high-speed config #1: android
[ 8.736206] android_work: sent uevent USB_STATE=CONFIGURED
[ 10.611083] init: untracked pid 66 exited
[ 14.540649] init: untracked pid 137 exited
[ 19.443481] init: untracked pid 303 exited

你好，我的情况和你一样，请问你解决了吗？能否分享下如何解决的。谢谢了

您好，我现在参照beaglbone black的外围自己做了一块板，emmc接在emmc1上，根据您的文章，是说的使用USB进行TFTP传送文件，我现在使用以太网口进行传送，前面几个和usb传输的patch我就不用打了？包括后面kernel对USB 对RNDIS等都不需要配置？

另外，我使用以太网口需不需要额外修改什么？生存u-boot.img和u-boot-spl.bin时，我需要使用什么配置文件？

我使用的sdk版本不是6.0，是ti-processor-sdk-linux-am335x-evm-02.00.02.11-Linux-x86-Install.bin。

我参考了很多文章，包括ti的教程，都没有效果，可能我使用的SDK版本较新，很多地方有出入。我也是第一次搞这玩意，麻烦您能否详细解答下。谢谢。。。

 Jian Zhou,你看我这是什么问题啊，

********************************************
Sitara Flash Fetcher is complete. Executing /home/root/debrick.sh.

****************************************************
****************************************************

Sitara Example Flashing Script - 02/11/2014

1+0 records in
1+0 records out
(standard_in) 1: parse error
No partition found. Continuing.
Partitioning the eMMC...

Usage:
sfdisk [options] <device> [...]

Options:
-s, --show-size list size of a partition
-c, --id change or print partition Id
--change-id change Id
--print-id print Id
-l, --list list partitions of each device
-d, --dump idem, but in a format suitable for later input
-i, --increment number cylinders etc. from 1 instead of from 0
-u, --unit <letter> units to be used; <letter> can be one of
S (sectors), C (cylinders), B (blocks), or M (MB)
-1, --one-only reserved option that does nothing currently
-T, --list-types list the known partition types
-D, --DOS for DOS-compatibility: waste a little space
-E, --DOS-extended DOS extended partition compatibility
-R, --re-read make the kernel reread the partition table
-N <number> change only the partition with this <number>
-n do not actually write to disk
-O <file> save the sectors that will be overwritten to <file>
-I <file> restore sectors from <file>
-V, --verify check that the listed partitions are reasonable
-v, --version display version information and exit
-h, --help display this help text and exit

Dangerous options:
-f, --force disable all consistency checking
--no-reread do not check whether the partition is in use
-q, --quiet suppress warning messages
-L, --Linux do not complain about things irrelevant for Linux
-g, --show-geometry print the kernel's idea of the geometry
-G, --show-pt-geometry print geometry guessed from the partition table
-A, --activate[=<device>] activate bootable flag
-U, --unhide[=<dev>] set partition unhidden
-x, --show-extended also list extended partitions in the output,
or expect descriptors for them in the input
--leave-last do not allocate the last cylinder
--IBM same as --leave-last
--in-order partitions are in order
--not-in-order partitions are not in order
--inside-outer all logicals inside outermost extended
--not-inside-outer not all logicals inside outermost extended
--nested every partition is disjoint from all others
--chained like nested, but extended partitions may lie outside
--onesector partitions are mutually disjoint

Override the detected geometry using:
-C, --cylinders <number> set the number of cylinders to use
-H, --heads <number> set the number of heads to use
-S, --sectors <number> set the number of sectors to use

No partition found. Continuing.
1+0 records in
1+0 records out
Formatting the eMMC into 2 partitions...
mkfs.vfat 2.11 (12 Mar 2005)
mkfs.vfat: Too few blocks for viable file system
mke2fs 1.42.1 (17-Feb-2012)
Could not stat /dev/mmcblk1p2 --- No such file or directory

The device apparently does not exist; did you specify it correctly?
Formatting done.
[ 13.826364] FAT-fs (loop0): bogus number of reserved sectors
[ 13.832343] FAT-fs (loop0): Can't find a valid FAT filesystem
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

mount: special device /dev/mmcblk1p2 does not exist
Copying Files...
tar: can't open 'boot_partition.tar.gz': No such file or directory
Command exited with non-zero status 1
real 0m 0.00s
user 0m 0.00s
sys 0m 0.00s
umount: /dev/mmcblk1p1: not mounted
rm: can't remove 'boot_partition.tar.gz': No such file or directory
Boot partition done.
tar: can't open 'rootfs_partition.tar.gz': No such file or directory
Command exited with non-zero status 1
real 0m 0.00s
user 0m 0.00s
sys 0m 0.00s
umount: /dev/mmcblk1p2: not found
rm: can't remove 'rootfs_partition.tar.gz': No such file or directory
RootFS partition done.
It took 2 seconds to complete this task...

********************************************
Sitara Example Flash Script is complete.

    你好，我是要用BBB这块核心板，但是产品于要做成通过USB接口更新固件的方式。感觉这篇文章写的应该正好可以解决我的问题，但是我不会Linux,按照网上的教程，总算是把Linux和SDK装起来了，但是还是没有编译成功。

    所以想问一下，网上有没编译好的文件呀，就是教程里面用到的这些，我的理解是烧写用的SPL,u-boot,linux uimage,还有要烧写的spl,u-boot,uimage,文件系统。

如果能找到这些的话，我是不是就可以不用自己编译了？

windows环境下使用，好像两个网卡不能设置成同一个IP地址，请问这种情况怎么处理呀？

谢谢

你好！根据这个文档和http://processors.wiki.ti.com/index.php/Sitara_Linux_Program_the_eMMC_on_Beaglebone_Black的介绍都已经设置好了，可为什么就是连不上呢？

怎么都连不上？哪里出现问题了？

hi 请问你这个问题解决了吗？ 现在我也遇见和你一样的问题，求教一下

目前还没有！继续研究并等待答案！

 @ rubin Li 请问你的问题解决了吗？

M3350_EV_BOARD 评估板

M3352-N128LI V2.04 核心板

使用am335x-evm-linux-sdk-src-03.00.00.04.tar 源码

我的报以下error 

Error: unrecognized/unsupported machine ID (r1 = 0x00000e05).

Available machine support:

ID (hex) NAME
ffffffff Generic DT based system
ffffffff Generic AM33XX (Flattened Device Tree)

请问您要什么文件，我之前已经把我做的一些文件贴上去了。

哦，谢谢！

我是说烧写用的这些文件，

烧写用的mlo,u-boot,uimage

要烧写到板子上的boot_partition.tar.gz，rootfs_partition.tar.gz

还有脚本：debrick.sh

有些我在楼上找到了，有些我自己也编译好了，但是感觉，对我一个没有入门的人来说，自己编译这些，比较麻烦，而且一出错，就不知道是自己编译错了，还是下载错了，也不知道是u-boot编译错了，还是内核编译错了。

要是能给我一个可以直接在BBB中国版开发板eMMC里运行的u-boot和内核那就非常感谢了。

我现在的是uboot启动起来，但是没有加载内核，不知道什么原因。

烧写用的相关文件我已经在这个帖子的第一页附上去了，你看一下。

您好，

请问是这个吗？

这个是就是要烧写到eMMC里面的吧？

这个是烧写用的MLO和U-boot。

烧写到BBB eMMC的image，用SDK里的就可以了

好的，我再试试，谢谢了。

现在等于说烧写用的SPL，u-boot，脚本都有了。

emmc启动用的从SDK    prebuilt-images 里也找到了。

现在只有烧写用的uimage是我自己编译的了。