This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM335x Flash Tool -- UniFlash 烧写工具使用简介及问题解决方案汇总(已更新SPI烧写部分…)

Other Parts Discussed in Thread: UNIFLASH, TMDSICE3359, AM3359, AM3715, FLASHTOOL, TMDSSK3358, TPS65910

大家好,目前很多人都在关注AM335x flash tool(UniFlash)的进展情况,这篇帖子会对当前的进展情况进行汇总,并就客户使用过程中遇到的问题,给出了相应的解决方案。欢迎大家加入讨论,给出宝贵意见。

使用Uniflash tool前,请大家先确认自己使用的AM335x的芯片版本,如果想使用USB的方式进行烧录,芯片版本必须为PG2.1.

目前的UniFlash官方发布的版本中,支持NAND FLASH、SPI FLASH的烧录,近期版本中将会更新对eMMC烧录功能的支持。

UniFlash的下载地址:

http://processors.wiki.ti.com/index.php/NowFlash%E2%84%A2_Programming_Tool

UniFlash的主机端安装用户指南:

http://processors.wiki.ti.com/index.php/Sitara_Uniflash_Quick_Start_Guide

UniFlash的image编译,脚本编译使用指南(Linux环境下):

http://processors.wiki.ti.com/index.php/Sitara_Linux_AM335x_Flash_Programming_Linux_Development

使用注意事项及问答:

  1. 使用该Uniflash进行NAND FLASH烧写时,Uniflash会先将u-boot-spl-restore.bin和u-boot-restore.img下载到开发板中,启动开发板进入到UBOOT阶段,从而调用脚本文件进行FLASH的烧写,所以需要先对SDK6.0开发包进行UBOOT的移植。移植时,一定要加入UBOOT 的patch:http://processors.wiki.ti.com/index.php/Sitara_Linux_AM335x_Flash_Programming_Linux_Development#Build_SPL_.28MLO.29_and_U-Boot_for_Flashing
  2. 请注意,制作用于Uniflash烧写的启动image时(u-boot-spl-restore.bin, u-boot-restore.img),使用的编译选项根据烧录方式不同进行选择:USB进行烧写请使用:am335x_evm_restore_flash_usbspl网口烧写请使用:am335x_evm_restore_flash
  3. 在Uniflash进行u-boot-spl-restore.bin的下载时,如果出现usb网络反应超时,请确认是否已经安装我们的usb patch:0001-u-boot-Change-default-cdc_connect_timeout-to-15s.patch。另外,一定要确认网络防火墙和杀毒软件是否已经关闭。
  4. 在u-boot-spl-restore.bin下载运行成功后,下载u-boot-restore.img时,网络一直在发IP请求,却没有得到回应,请参考以下解决方案:在操作过程中,插上USB时能在主机上找到USB RNDIS网络,默认时配置该网络IP为192.168.2.1。在烧写的不同阶段,部分主机会将该网络会识别成另外的USB RNDIS网络,因此,与之前的网络不同且没有IP配置,此时只需要再配置该网络的IP为192.168.2.1,即可正常使用(可能会弹出提示:该IP被未使用的网络占用,是否要清除未使用的网络?此时选择否)。
  5. 鉴于部分用户,对于SPI FLASH的烧写有强烈的需求,如果对Uniflash的烧录进度条显示并无严格需求时,可以参考SDK6.0开发包下的/board-support/u-boot-2013.01.01-psp06.00.00.00/doc/am335x.net-spl/debrick-spi.txt文件,进行SPI烧写脚本的编写,其使用方式与NAND flash烧写的使用方式类似,使用以下mkimage命令即可完成脚本的制作:./mkimage -A arm -O U-Boot -C none -T script -d debrick-nand.txt debrick.scr

经实例验证,该方式可以正常的进行SPI flash的烧写,但Uniflash中的进度条显示无法正常同步,该方式仅可作为进行功能验证的draft版。(烧写成功的显示可参考该链接中的文本:http://www.deyisupport.com/question_answer/dsp_arm/sitara_arm/f/25/t/51935.aspx

官方支持的SPI FLASH Tool脚本,可以在楼下的2014.4.15更新内容中找到,同时更新了自定义烧写脚本的修改方法。

以上,如有任何疑问或者建议,欢迎大家随时发表、讨论!谢谢!

AM335x Flash Tool -- UniFlash 烧写工具使用简介及问题解决方案汇总.pdf
  • 请问,这个工具可以用于烧写android固件吗?移植uboot工作量会不会很大?

  • 你是要烧写到NAND Flash里吗?初始化烧写环境时是需要用到Linux uboot的;烧写到FLASH里面的内容,是可以自定义的。Android,Linux等都可以。

  • 是烧写到NAND Flash里,首先是不是要将linux uboot部分的改动移植到android uboot上来,这部分改动大吗?

  • 不是这个意思。Linux的uboot是flash tool用于初始化烧写环境的,和你要烧写的android部分是两个独立的部分。你要烧写的Android,只是个image(应该是已经能够在你板子上面跑的),不需要改动。

    Linux的uboot和移植工作可以参考我们的培训资料:http://processors.wiki.ti.com/index.php/Sitara_Linux_Training:_UBoot_Board_Port

  • 你好,我下了linux sdk6.0,在编译uboot的时候发现交叉编译工具链有问题,我用的android sdk里面的工具链,出现:cc1: error: unrecognized command line option "-mno-unaligned-access"的错误。

    请问,编译linux的gcc是什么版本,能否给个你们用的版本的下载链接?非常感谢!

  • 最新版本的Linux 开发包中,使用的是Linaro的Tool chain,这里有说明:http://processors.wiki.ti.com/index.php/AM335x_U-Boot_User%27s_Guide#Updated_Toolchain

    在最新版本的Linux SDK开发包中,linux-devkit目录下面已经有了该工具链,具体的使用方法,在上面的链接中也能找到。

  • 2014.2.18更新内容:

    由于该Uniflash工具也可以烧写Android,RTOS等非Linux操作系统的image,这里有一些简单的tips,方便那些使用非Linux的客户,更快速的将Uniflash的烧写环境搭建起来,下文以NAND flash作为示例:

    1. 首先由于Uniflash必须要使用Linux的Uboot作为烧写固件的一部分,所以请先下载AM335x Linux SDK 6.0开发包:http://software-dl.ti.com/sitara_linux/esd/AM335xSDK/latest/index_FDS.html

    2. 下载完成后在Linux主机上进行安装,安装完成后,根目录下的board-support/u-boot-2013.01.01-psp06.00.00.00文件夹即为Linux uboot的源码,需做部分修改后编译。编译方法可参考:http://processors.wiki.ti.com/index.php/AM335x_U-Boot_User%27s_Guide

    3. Linux uboot需要修改的部分:这部分工作就是对Linux uboot进行移植的工作,主要修改的有三处地方:EEPROM, DDR2/3, NAND FLASH(包括pinmux)

    3.1 对于EEPROM操作的修改:由于在官方的开发板上,都会有EEPROM来进行板子的型号辨识,不同板子资源不同,配置也就不同,因此该处的配置会影响到DDR的配置以及NAND flash的配置;一般来说客户自己的开发板上没有eeprom,所以要对此处进行修改。文件位置:uboot的根目录/board/ti/am335x/board.c文件中搜索"eeprom“既可找到配置的地方。

    3.2 对于DDR的配置的修改:因为板子上可能使用DDR2或者DDR3,要根据实际情况对UBOOT进行修改。在uboot的根目录/board/ti/am335x/board.c文件中搜索"config_ddr“既可找到配置的地方。

    3.3 对于NAND FLASH的修改:这里最常遇到的问题是,选择的板卡并没有对NAND flash进行Pinmux的设置,简单的解决方法是:在uboot/board/ti/am335x/mux.c文件中,在 void enable_board_pin_mux (struct am335x_baseboard_id *header)这个函数实现的第一句中加入

    configure_module_pin_mux(nand_pin_mux); 确保nand的Pinmux配置成功。对于NAND Flash的位宽配置,时序参数配置,可参考TRM中的7.1 GPMC章节。其中,常用的NAND位宽配置(8bit和16bit)在GPMC_CONFIG1的13-12bit位上。

  • 2014.4.15更新内容:

    Uniflash 烧写脚本的修改和SPI 烧写的支持

    在前面的章节中,我们介绍了如何使用Uniflash进行NAND的烧写,主要列举了如何烧写Linux相关image的过程,收到了不少朋友的反馈。根据大家的反馈,我在这次的更新中,会对如何修改烧写脚本源文件debrick.txt进行介绍,并对SPI烧写的支持进行介绍。

    SPI的烧写方法,和之前NAND烧写流程基本一致,主要的工作是在于Uniflash的烧写脚本源文件debrick.txt的修改。所以附件中的文章,会以debrick-spi.txt脚本源文件作为参考,讲解一下如何修改烧写脚本源文件。(NAND flash源文件debrick-nand.txt的修改,与此也相差无几,请重点参考文章的第4 节。)

    PS: 支持spil flash烧录的源文件debrick-spi.txt在下一个帖子的附件中。

    Uniflash烧写脚本的修改和 SPI 烧写的支持.pdf
  • 2014.4.15更新:

    SPI烧写脚本的源文件:debrick-spi.txt

    • 采用USB烧写方式,target board需要选择boot bin为USB启动吗?如果设置为USB为第二个启动模式,如启动顺序设置为:

      11000b SPI0 MMC0 USB0 UART0 是否可行?我设置成该模式,启动Uniflash进行烧写时,没有动静。

     

  • 我安装完uniflash,把host和target board用usb连接好,并启动,我发现“我的连接”的“媒体状态”属于“禁用”状态,也不能烧写flash。请问这怎么解决?

  • 恩,需要选择USB启动。

    用你的序列可以,但是要注意一点,在USB进行烧写时,确保你接到SPI0的spi flash和MMC0的SD卡内不要有启动的image,否则,板子就会从位于前列的SPI0,MMC0方式启动了,就无法进入到USB烧写的方式了。

  • 你尝试一下:在Control Panel\Network and Internet\Network Connections

    里面右键点击这个网络,再点击enable,是不是就可以了?

  • 芯片为1.0版,不支持USB BOOT.

  • 但是我的TMDSICE3359 用UniFlash 烧写有问题..网络都无法连接上。。请问是怎么回事啊

  • ICE板子上的网口是PRU网口(是用来实现EtherCAT的),不是AM335x上的CPSW的以太网口。所以不行。

  • 那我这个板子好像没有PRU 。。那怎么办

  • ICE板子上用的是AM3359,是带有PRU单元的。

  • ICE板子上用的是AM3359,是带有PRU单元的。

  • 但我用的是这个板子,也是有带PRU单元的啊。。

  • 我的板子用的也是AM3359芯片,也是网络连不上,请问下你解决了没啊

  • 你楼上那位兄弟,使用的是ICE开发板,上面没有以太网口,只有PRU网口。PRU网口不能做烧录,需要是以太网口(CPSW)才行。

    你的是以太网口烧录不成功吗?还是说以太网口本身通信就有问题?

    如果是前者,给些具体的细节log出来;如果是后者,建议你开一个新帖讨论你当前遇到的具体以太网通信问题。

  • 奇怪的是Ti的这些wiki怎么都不能 Downlaod  as PDF?

  • 点击左侧的download as PDF,大部分还是可以的。我试过,应该只有这个链接是不行的,可能是因为太大了。

    http://processors.wiki.ti.com/index.php/Sitara_Linux_AM335x_Flash_Programming_Linux_Development

  • 使用Uniflash tool前,请大家先确认自己使用的AM335x的芯片版本,如果想使用USB的方式进行烧录,芯片版本必须为PG2.1.

    -----------

    请问 如何确认芯片版本号呢?

  • AM335x的datasheet中有写的。主要通过AM335x的丝印层,看335x后面是否带有“B"的字样,不带的话就是PG1.0,带"B"就是PG2.1。

    举个例子,如果上面的料号是AM3352ZCZ60,这个就是PG1.0的;如果是AM3352BZCZ60,这个就是PG2.1的。

  • 由于kingston一款emmc停产了,我们使用推荐的另外一款,发现就无法usb升级了。请问是否和工具有关系?

  • 请问我AM335x板子里没了u-boot,只有JTAG接口,可以用什么办法下载。

  • JTAG没有用过,应该有工具的。uniflash烧录可能你要看看楼主的附件了。

  • 能否烧写wince ,针对AM3715平台

  • Hi Steven,

    你上面提供的SDK 6.0开发包的下载链接下载的好像不是6.0版的,而是最新版的,这有关系么?我通过http://processors.wiki.ti.com/index.php/AMSDK_u-boot_User%27s_Guide 这篇文档里的SDK链接下载的SDK执行下面的命令

    make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- tisdk_am335x-evm_defconfig

    但提示我没有tisdk_am335x-evm_defconfig why?

  • 这里是SDK 6.0的下载地址:

    http://software-dl.ti.com/sitara_linux/esd/AM335xSDK/06_00_00_00/index_FDS.html

    你可能下了最新版本的PROCESSOR SDK了,最新版本中变动较大,所以没有那种配置了。

  • 你好 Steven,

           请问我用UniFlash3.0通过USB烧写时,做到文档Sitara Uniflash Quick Start Guide 的第26步后,Uniflash软件一直如下图,进度一直在0%没变,而且也没有出现新的网络需要我设置,


    opendhcp的log如下:

    [08-Jul-15 14:46:51] Open DHCP Server Version 1.59 Windows Build 1036 Starting...
    [08-Jul-15 14:46:51] Logging: All
    [08-Jul-15 14:46:51] DHCP Range: 192.168.2.2-192.168.2.254/255.255.255.0
    [08-Jul-15 14:46:51] Server Name: 2014-20140719FL
    [08-Jul-15 14:46:51] Detecting Static Interfaces..
    [08-Jul-15 14:46:51] Warning: Section [LISTEN_ON], Interface 192.168.2.1 not available, ignored
    [08-Jul-15 14:46:51] No Static Interface ready, Waiting...
    [08-Jul-15 14:46:51] Retrying failed Listening Interfaces..
    [08-Jul-15 14:46:51] Warning: 192.168.2.1 UDP Port 67 already in use
    [08-Jul-15 14:46:51] No Static Interface ready, Waiting...
    [08-Jul-15 14:46:51] Retrying failed Listening Interfaces..
    [08-Jul-15 14:46:51] Lease Status URL: http://127.0.0.1:6789
    [08-Jul-15 14:46:51] Listening On: 192.168.2.1
    [08-Jul-15 14:47:04] BOOTPREQUEST for d0:5f:b8:fb:e8:b3 () from interface 192.168.2.1 received
    [08-Jul-15 14:47:04] BOOTP Host d0:5f:b8:fb:e8:b3 (Hostd05fb8fbe8b3) allotted 192.168.2.3

    opentftp的log如下:

    [08-Jul-15 14:46:52] Open TFTP Server MultiThreaded Version 1.64 Windows Built 2001 Starting..
    [08-Jul-15 14:46:52] starting TFTP service
    [08-Jul-15 14:46:52] alias / is mapped to C:\AM335x_Flashtool\images\
    [08-Jul-15 14:46:52] permitted clients: all
    [08-Jul-15 14:46:52] server port range: all
    [08-Jul-15 14:46:52] max blksize: 65464
    [08-Jul-15 14:46:52] default blksize: 512
    [08-Jul-15 14:46:52] default timeout: 3
    [08-Jul-15 14:46:52] file read allowed: Yes
    [08-Jul-15 14:46:52] file create allowed: No
    [08-Jul-15 14:46:52] file overwrite allowed: No
    [08-Jul-15 14:46:52] thread pool size: 1
    [08-Jul-15 14:46:52] 192.168.2.1 Port 69 bind failed
    [08-Jul-15 14:46:52] No Static Interface ready, Waiting...
    [08-Jul-15 14:46:55] Retrying failed Listening Interfaces..
    [08-Jul-15 14:46:55] 192.168.2.1 Port 69 bind failed
    [08-Jul-15 14:46:55] No Static Interface ready, Waiting...
    [08-Jul-15 14:46:58] Retrying failed Listening Interfaces..
    [08-Jul-15 14:46:58] Listening On: 192.168.2.1:69
    [08-Jul-15 14:47:04] Client 192.168.2.3:1234 C:\AM335x_Flashtool\images\u-boot-spl-restore.bin, 208 Blocks Served

    到这个位置就卡主没有信息了

    请问这可能是什么原因?

  • 怎样能够擦除掉spi flash里面的内容啊?


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

  • 我按照TMDSSK3358设计的核心板,第一次烧写,想使用USB进行烧写,但是,设备管理器中没有AM335x USB 设备,我应该如何解决?

  • 你好,请问一下需要的文件是不是下面四个?

  • 同问,使用Sitara_Uniflash,在windows上面,烧写spi flash,需要哪些文件呢?

    按照这个指导http://processors.wiki.ti.com/index.php/Sitara_Uniflash_Quick_Start_Guide,可以将电脑和板子连接起来,但是下载进度一直为0,

    不知道下载的配置文件哪里可以找到呢?我的板子是裸机的,目标是从spi flash进行启动。

    谢谢了!

  • 这个能烧写StarterWare中的PLO和APP吗?

  • 我现在通过usb连接板子进入了uboot命令行模式:

    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
    PHY reset timed out
    cpsw, usb_ether
    Hit any key to stop autoboot:  0
    using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
    MAC 50:72:24:c7:2c:7f
    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.2.2
    using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
    MAC 50:72:24:c7:2c:7f
    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.2.1; our IP address is 192.168.2.2
    Filename 'uImage'.
    Load address: 0x81000000
    Loading: T T
    TFTP error: 'File not found or No Access' (1)
    Not retrying...
    U-Boot#
    U-Boot#
    U-Boot#

    之后如何将uboot、内核、文件系统烧写到板子上?用什么命令?

    请大家帮帮忙!!感谢!!

  • CCCCCCCC
    U-Boot SPL 2013.01.01 (Nov 24 2017 - 14:55:22)
    cld: Initalize the board header!!##############.
    cld: don't read_eeprom!!##############.
    cld: enable_board_pin_mux##############.
    cld: configure pinmux################.
    cld: enable_board_pin_mux end!!2##############.
    cld:header.name =
    cld: am33xx_spl_board_init!! end!##############.
    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 50:72:24:c7:2c:7f
    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.2.1; our IP address is 192.168.2.2
    Filename 'u-boot-restore.img'.
    Load address: 0x807fffc0
    Loading: #########################
             677.7 KiB/s
    done
    Bytes transferred = 364808 (59108 hex)


    U-Boot 2013.01.01 (Nov 24 2017 - 14:55:22)

    I2C:   ready
    DRAM:  128 MiB
    WARNING: Caches not enabled
    cld:board_init###################.
    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
    PHY reset timed out
    cpsw, usb_ether
    Hit any key to stop autoboot:  0
    using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
    MAC 50:72:24:c7:2c:7f
    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.2.2
    using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
    MAC 50:72:24:c7:2c:7f
    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.2.1; our IP address is 192.168.2.2
    Filename 'uImage'.
    Load address: 0x81000000
    Loading: T #################################################################
             #################################################################
             #################################################################
             #################################################################
             #################################################################
             #################################################################
             ######
             855.5 KiB/s
    done
    Bytes transferred = 5803888 (588f70 hex)
    ## Booting kernel from Legacy Image at 81000000 ...
       Image Name:   Linux-3.2.0
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    5803824 Bytes = 5.5 MiB
       Load Address: 80008000
       Entry Point:  80008000
       Verifying Checksum ... OK
       Loading Kernel Image ... OK
    OK

    Starting kernel ...

    Uncompressing Linux... done, booting the kernel.
    [    0.000000] Linux version 3.2.0 (cust@ubuntu) (gcc version 4.7.3 20130226 (prerelease) (crosstool-NG linaro-1.13.1-4.7-2013.03-20130313 - Linaro GCC 2013.03) ) #20 Fri Nov 24 22:31:11 PST 2017
    [    0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7d
    [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
    [    0.000000] Machine: am335xevm
    [    0.000000] Memory policy: ECC disabled, Data cache writeback
    [    0.000000] AM335X ES2.1 (neon )
    [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
    [    0.000000] Kernel command line: root=/dev/mmcblk0p2 rootwait console=ttyO0,115200
    [    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
    [    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
    [    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
    [    0.000000] Memory: 128MB = 128MB total
    [    0.000000] Memory: 117800k/117800k available, 13272k reserved, 0K highmem
    [    0.000000] Virtual kernel memory layout:
    [    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    [    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    [    0.000000]     vmalloc : 0xc8800000 - 0xff000000   ( 872 MB)
    [    0.000000]     lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
    [    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
    [    0.000000]       .text : 0xc0008000 - 0xc059b000   (5708 kB)
    [    0.000000]       .init : 0xc059b000 - 0xc0b3a000   (5756 kB)
    [    0.000000]       .data : 0xc0b3a000 - 0xc0ba3c00   ( 423 kB)
    [    0.000000]        .bss : 0xc0ba3c24 - 0xc0bd29a4   ( 188 kB)
    [    0.000000] NR_IRQS:396
    [    0.000000] IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
    [    0.000000] Total of 128 interrupts on 1 active controller
    [    0.000000] OMAP clockevent source: GPTIMER2 at 24000000 Hz
    [    0.000000] OMAP clocksource: GPTIMER1 at 32768 Hz
    [    0.000000] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms
    [    0.000000] Console: colour dummy device 80x30
    [    0.000091] Calibrating delay loop... 718.02 BogoMIPS (lpj=3590144)
    [    0.058929] pid_max: default: 32768 minimum: 301
    [    0.059051] Security Framework initialized
    [    0.059173] Mount-cache hash table entries: 512
    [    0.059539] CPU: Testing write buffer coherency: ok
    [    0.079833] omap_hwmod: gfx: failed to hardreset
    [    0.096130] omap_hwmod: pruss: failed to hardreset
    [    0.097229] print_constraints: dummy:
    [    0.097595] NET: Registered protocol family 16
    [    0.099731] OMAP GPIO hardware version 0.1
    [    0.102325] omap_mux_init: Add partition: #1: core, flags: 0
    [    0.104125]  omap_i2c.1: alias fck already exists
    [    0.104949]  omap2_mcspi.1: alias fck already exists
    [    0.105163]  omap2_mcspi.2: alias fck already exists
    [    0.106079]  edma.0: alias fck already exists
    [    0.106109]  edma.0: alias fck already exists
    [    0.106140]  edma.0: alias fck already exists
    [    0.132659] bio: create slab <bio-0> at 0
    [    0.134857] SCSI subsystem initialized
    [    0.136535] usbcore: registered new interface driver usbfs
    [    0.136840] usbcore: registered new interface driver hub
    [    0.137054] usbcore: registered new device driver usb
    [    0.137359] registerd cppi-dma Intr @ IRQ 17
    [    0.137359] Cppi41 Init Done Qmgr-base(c887a000) dma-base(c8878000)
    [    0.137359] Cppi41 Init Done
    [    0.137390] musb-ti81xx musb-ti81xx: musb0, board_mode=0x13, plat_mode=0x3
    [    0.137695] musb-ti81xx musb-ti81xx: musb1, board_mode=0x13, plat_mode=0x1
    [    0.138824] omap_i2c omap_i2c.1: bus 1 rev2.4.0 at 100 kHz
    [    0.140167] tps65910 1-002d: JTAGREVNUM 0x0
    [    0.142547] print_constraints: VRTC:
    [    0.143981] print_constraints: VIO: at 1500 mV
    [    0.146301] print_constraints: VDD1: 600 <--> 1500 mV at 1262 mV normal
    [    0.148590] print_constraints: VDD2: 600 <--> 1500 mV at 1137 mV normal
    [    0.149597] print_constraints: VDD3: 5000 mV
    [    0.151000] print_constraints: VDIG1: at 1800 mV
    [    0.152435] print_constraints: VDIG2: at 1800 mV
    [    0.153839] print_constraints: VPLL: at 1800 mV
    [    0.155273] print_constraints: VDAC: at 1800 mV
    [    0.156677] print_constraints: VAUX1: at 1800 mV
    [    0.158111] print_constraints: VAUX2: at 3300 mV
    [    0.159545] print_constraints: VAUX33: at 3300 mV
    [    0.160980] print_constraints: VMMC: at 3300 mV
    [    0.161468] tps65910 1-002d: No interrupt support, no core IRQ
    [    0.162811] Advanced Linux Sound Architecture Driver Version 1.0.24.
    [    0.163940] Switching to clocksource gp timer
    [    0.179321] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
    [    0.179504] musb-hdrc musb-hdrc.0: dma type: dma-cppi41
    [    0.179809] MUSB0 controller's USBSS revision = 4ea20800
    [    0.179840] musb0: Enabled SW babble control
    [    0.180755] musb-hdrc musb-hdrc.0: USB OTG mode controller at c883c000 using DMA, IRQ 18
    [    0.180908] musb-hdrc musb-hdrc.1: dma type: dma-cppi41
    [    0.181213] MUSB1 controller's USBSS revision = 4ea20800
    [    0.181243] musb1: Enabled SW babble control
    [    0.181671] musb-hdrc musb-hdrc.1: MUSB HDRC host driver
    [    0.181762] musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 1
    [    0.181884] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
    [    0.181915] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [    0.181915] usb usb1: Product: MUSB HDRC host driver
    [    0.181945] usb usb1: Manufacturer: Linux 3.2.0 musb-hcd
    [    0.181945] usb usb1: SerialNumber: musb-hdrc.1
    [    0.182739] hub 1-0:1.0: USB hub found
    [    0.182769] hub 1-0:1.0: 1 port detected
    [    0.183288] musb-hdrc musb-hdrc.1: USB Host mode controller at c883e800 using DMA, IRQ 19
    [    0.183715] NET: Registered protocol family 2
    [    0.183929] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
    [    0.184265] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
    [    0.184356] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
    [    0.184417] TCP: Hash tables configured (established 4096 bind 4096)
    [    0.184417] TCP reno registered
    [    0.184448] UDP hash table entries: 256 (order: 0, 4096 bytes)
    [    0.184478] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
    [    0.184661] NET: Registered protocol family 1
    [    0.184936] RPC: Registered named UNIX socket transport module.
    [    0.184936] RPC: Registered udp transport module.
    [    0.184967] RPC: Registered tcp transport module.
    [    0.184967] RPC: Registered tcp NFSv4.1 backchannel transport module.
    [    0.238647] NetWinder Floating Point Emulator V0.97 (double precision)
    [    0.246398] VFS: Disk quotas dquot_6.5.2
    [    0.246459] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    [    0.246978] msgmni has been set to 230
    [    0.250152] alg: No test for stdrng (krng)
    [    0.250823] io scheduler noop registered
    [    0.250823] io scheduler deadline registered
    [    0.250915] io scheduler cfq registered (default)
    [    0.252746] omap_uart.0: ttyO0 at MMIO 0x44e09000 (irq = 72) is a OMAP UART0
    [    0.899566] console [ttyO0] enabled
    [    0.903839] omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
    [    0.911682] omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
    [    0.919464] omap_uart.3: ttyO3 at MMIO 0x481a6000 (irq = 44) is a OMAP UART3
    [    0.927246] omap_uart.4: ttyO4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4
    [    0.935028] omap_uart.5: ttyO5 at MMIO 0x481aa000 (irq = 46) is a OMAP UART5
    [    0.943267] omap4_rng omap4_rng: OMAP4 Random Number Generator ver. 2.00
    [    0.959533] brd: module loaded
    [    0.967620] loop: module loaded
    [    0.971069] i2c-core: driver [tsl2550] using legacy suspend method
    [    0.977539] i2c-core: driver [tsl2550] using legacy resume method
    [    0.983978] at24 1-0050: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
    [    0.991241] The board is general purpose EVM in profile 0
    [    0.998718]  omap_i2c.3: alias fck already exists
    [    1.003997] omap_i2c omap_i2c.3: bus 3 rev2.4.0 at 100 kHz
    [    1.010620]  omap_i2c.2: alias fck already exists
    [    1.015899] omap_i2c omap_i2c.2: bus 2 rev2.4.0 at 40 kHz
    [    1.022094]  omap_hsmmc.0: alias fck already exists
    [    1.027526]  omap_hsmmc.1: alias fck already exists
    [    1.032867]  omap_hsmmc.2: alias fck already exists
    [    1.038269] Configure Bluetooth Enable pin...
    [    1.042816] ti81xx_interrupt 1146: VBUS error workaround (delay coming)
    [    1.049804]  d_can.0: alias fck already exists
    [    1.055847] ####################################################################################cld#########################
    [    1.069854] registered am33xx_sr device
    [    1.076385] mtdoops: mtd device (mtddev=name/number) must be supplied
    [    1.083557] omap2-nand driver initializing
    [    1.088043] OneNAND driver initializing
    [    1.093322] CAN device driver interface
    [    1.097351] CAN bus driver for Bosch D_CAN controller 1.0
    [    1.103820] d_can d_can.0: device registered (irq=52, irq_obj=53)
    [    1.154541] davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
    [    1.160980] davinci_mdio davinci_mdio.0: no live phy, scanning all
    [    1.167572] phy_id:0xC021C72C, addr:0x0
    [    1.171813] davinci_mdio: probe of davinci_mdio.0 failed with error -5
    [    1.178955] usbcore: registered new interface driver zd1201
    [    1.184997] usbcore: registered new interface driver cdc_ether
    [    1.191253] usbcore: registered new interface driver cdc_eem
    [    1.197326] usbcore: registered new interface driver dm9601
    [    1.203155] cdc_ncm: 04-Aug-2011
    [    1.206695] usbcore: registered new interface driver cdc_ncm
    [    1.212615] Initializing USB Mass Storage driver...
    [    1.217926] usbcore: registered new interface driver usb-storage
    [    1.224212] USB Mass Storage support registered.
    [    1.229492] mousedev: PS/2 mouse device common for all mice
    [    1.236480] omap_rtc am33xx-rtc: rtc core: registered am33xx-rtc as rtc0
    [    1.243713] i2c /dev entries driver
    [    1.248199] Linux video capture interface: v2.00
    [    1.253326] usbcore: registered new interface driver uvcvideo
    [    1.259338] USB Video Class driver (1.1.1)
    [    2.254638] omap_i2c omap_i2c.3: controller timed out
    [    2.259948] lm75: probe of 3-0048 failed with error -110
    [    3.034606] ti81xx_interrupt 1146: VBUS error workaround (delay coming)
    [    3.187042] ti81xx_interrupt 1146: VBUS error workaround (delay coming)
    [    3.324584] omap_i2c omap_i2c.3: controller timed out
    [    4.344604] omap_i2c omap_i2c.3: controller timed out
    [    5.184600] ti81xx_interrupt 1146: VBUS error workaround (delay coming)
    [    5.337005] ti81xx_interrupt 1146: VBUS error workaround (delay coming)
    [    5.364562] omap_i2c omap_i2c.3: controller timed out
    [    6.384613] omap_i2c omap_i2c.3: controller timed out
    [    7.334564] ti81xx_interrupt 1146: VBUS error workaround (delay coming)
    [    7.404571] omap_i2c omap_i2c.3: controller timed out
    [    7.486999] ti81xx_interrupt 1146: VBUS error workaround (delay coming)
    [    8.424682] omap_i2c omap_i2c.3: controller timed out
    [    9.444610] omap_i2c omap_i2c.3: controller timed out
    [    9.484588] ti81xx_interrupt 1146: VBUS error workaround (delay coming)
    [    9.636993] ti81xx_interrupt 1146: VBUS error workaround (delay coming)
    [   10.464569] omap_i2c omap_i2c.2: controller timed out
    [   11.484649] omap_i2c omap_i2c.2: controller timed out
    [   11.634582] ti81xx_interrupt 1146: VBUS error workaround (delay coming)
    [   11.787017] ti81xx_interrupt 1146: VBUS error workaround (delay coming)
    [   12.504577] omap_i2c omap_i2c.2: controller timed out
    [   13.524597] omap_i2c omap_i2c.2: controller timed out
    [   13.784576] ti81xx_interrupt 1146: VBUS error workaround (delay coming)
    [   13.937011] ti81xx_interrupt 1146: VBUS error workaround (delay coming)
    [   14.544647] omap_i2c omap_i2c.2: controller timed out
    [   15.564605] omap_i2c omap_i2c.2: controller timed out
    [   15.934570] ti81xx_interrupt 1146: VBUS error workaround (delay coming)
    [   16.087005] ti81xx_interrupt 1146: VBUS error workaround (delay coming)
    [   16.584594] omap_i2c omap_i2c.2: controller timed out
    [   17.604644] omap_i2c omap_i2c.2: controller timed out
    [   17.625610] OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
    [   17.636749] cpuidle: using governor ladder
    [   17.641632] cpuidle: using governor menu
    [   17.657806] omap4_aes_mod_init: loading AM33X AES driver
    [   17.663574] omap4-aes omap4-aes: AM33X AES hw accel rev: 3.02
    [   17.670440] omap4_aes_probe: probe() done
    [   17.674987] omap4_sham_mod_init: loading AM33X SHA/MD5 driver
    [   17.681182] omap4-sham omap4-sham: AM33X SHA/MD5 hw accel rev: 4.03
    [   17.717285] omap4_sham_probe: probe() done
    [   17.724761] usbcore: registered new interface driver usbhid
    [   17.730621] usbhid: USB HID core driver
    [   17.735748] tiadc tiadc: attached adc driver
    [   17.741149] usbcore: registered new interface driver snd-usb-audio
    [   17.749786] ALSA device list:
    [   17.752929]   No soundcards found.
    [   17.756561] oprofile: hardware counters not available
    [   17.761871] oprofile: using timer interrupt.
    [   17.766418] nf_conntrack version 0.5.0 (1840 buckets, 7360 max)
    [   17.773162] ip_tables: (C) 2000-2006 Netfilter Core Team
    [   17.778930] TCP cubic registered
    [   17.782318] NET: Registered protocol family 17
    [   17.787017] can: controller area network core (rev 20090105 abi 8)
    [   17.793640] NET: Registered protocol family 29
    [   17.798370] can: raw protocol (rev 20090105)
    [   17.802856] can: broadcast manager protocol (rev 20090105 t)
    [   17.808868] Registering the dns_resolver key type
    [   17.813903] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
    [   17.821990] ThumbEE CPU extension supported.
    [   17.826568] mux: Failed to setup hwmod io irq -22
    [   17.832275] Power Management for AM33XX family
    [   17.837219] Trying to load am335x-pm-firmware.bin (60 secs timeout)
    [   17.843933] Copied the M3 firmware to UMEM
    [   17.848358] Cortex M3 Firmware Version = 0x181
    [   17.854888] create_regulator: VDD1: Failed to create debugfs directory
    [   17.863403] smartreflex smartreflex: am33xx_sr_probe: Driver initialized
    [   17.877563] clock: disabling unused clocks to save power
    [   17.886596] mmc1: new high speed MMC card at address 0001
    [   17.897125] mmcblk0: mmc1:0001 016GE2 14.6 GiB
    [   17.906738] mmcblk0boot0: mmc1:0001 016GE2 partition 1 4.00 MiB
    [   17.913238] mmcblk0boot1: mmc1:0001 016GE2 partition 2 4.00 MiB
    [   17.921478]  mmcblk0: unknown partition table
    [   17.933074]  mmcblk0boot1: unknown partition table
    [   17.944793]  mmcblk0boot0: unknown partition table
    [   18.091247] mmc2: card claims to support voltages below the defined range. These will be ignored.
    [   18.115386] mmc2: queuing unknown CIS tuple 0x91 (3 bytes)
    [   18.123748] mmc2: new SDIO card at address 0001
    [   18.363189] Detected MACID=50:72:24:c7:2c:7f
    [   18.369110] cpsw: Detected MACID = 50:72:24:c7:2f:81
    [   18.375823] input: Unspecified device as /devices/virtual/input/input0
    [   18.383239] omap_rtc am33xx-rtc: setting system clock to 2000-01-01 00:00:17 UTC (946684817)
    [   18.392303] Warning: unable to open an initial console.
    [   18.398284] VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2)
    [   18.405731] Please append a correct "root=" boot option; here are the available partitions:
    [   18.414550] b300        15388672 mmcblk0  driver: mmcblk
    [   18.420166] b310            4096 mmcblk0boot1  (driver?)
    [   18.425781] b308            4096 mmcblk0boot0  (driver?)
    [   18.431396] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)
    [   18.440277] Backtrace:
    [   18.442901] [<c0017dbc>] (dump_backtrace+0x0/0x10c) from [<c04154b4>] (dump_stack+0x18/0x1c)
    [   18.451782]  r6:00008000 r5:c04fa5d0 r4:c0ba68c8 r3:c0b5cd8c
    [   18.457794] [<c041549c>] (dump_stack+0x0/0x1c) from [<c04156b0>] (panic+0x64/0x194)
    [   18.465881] [<c041564c>] (panic+0x0/0x194) from [<c059bc88>] (mount_block_root+0x174/0x228)
    [   18.474700]  r3:00000004 r2:00000000 r1:c701df40 r0:c04fa5d0
    [   18.480682]  r7:c04fa638
    [   18.483367] [<c059bb14>] (mount_block_root+0x0/0x228) from [<c059bef0>] (mount_root+0xc8/0xe8)
    [   18.492462] [<c059be28>] (mount_root+0x0/0xe8) from [<c059c07c>] (prepare_namespace+0x16c/0x1c0)
    [   18.501708]  r4:c0ba3ca0
    [   18.504394] [<c059bf10>] (prepare_namespace+0x0/0x1c0) from [<c059b8fc>] (kernel_init+0xf4/0x120)
    [   18.513732]  r5:c05d5628 r4:c05d5628
    [   18.517547] [<c059b808>] (kernel_init+0x0/0x120) from [<c0041498>] (do_exit+0x0/0x65c)
    [   18.525878]  r5:c059b808 r4:00000000

    卡在内核启动这里:主要是主句:

    [   18.431396] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)

    是什么原因引起的??还有 \AM335x_Flashtool\images 总共需要几个文件?

    我放的debrick.sh似乎没有效果、、之前在论坛下载的,其他人又说有问题、、

    一些问题都太分散了、、希望TI能把各个流程写得详细点、、、万分感谢!!

  • 请教下 u-boot 是怎么下载的 我用的是最新版的i-processor-sdk-linux-am335x-evm-04.02.00.09-Linux-x86-Install.bin
    在Sitara Uniflash Flash Programming with U-Boot(processors.wiki.ti.com/.../Sitara_Uniflash_Flash_Programming_with_U-Boot) 文档中的链接不可用了 您是怎么处理这个的呢
  • 请问UniFlash的USB驱动在哪里?
  • ti-processor-sdk-linux-am335x-evm-04.03.00.05-Linux-x86-Install.bin这个版本的Linux和Uboot移植的内容很多都不适用了,能麻烦提供个简要的大纲,方便我们迅速无遗漏的完成移植工作吗?
  • ti-processor-sdk-linux-am335x-evm-04.03.00.05-Linux-x86-Install.bin这个版本的Linux和Uboot移植的内容很多都不适用了,能麻烦提供个简要的大纲,方便我们迅速无遗漏的完成移植工作吗?
  • 我的板卡是AM437x,在win7系统上安装CCS UniFlash v3.4.1已经能成功烧录镜像文件了,现在的问题是:
    1、如果在Ubuntu系统(18.04)上使用这个进行烧录?官方各种资料并未提到在Linux系统上的烧录过程。
    2、理论上上参考software-dl.ti.com/.../How_to_Setup_Ubuntu_1404_Network_Boot.html
    3、CCS UniFlash v3.4.1软件的Linux版本在Ubuntu上执行没有任何反应。
    4、CCS UniFlash 现在已经更新到uniflash_sl.6.0.0.2710版本,但是这个版本支持对AM437x的烧录么?在里面并未找到AM437x这个平台。