看看这个信息是啥意思？

2019-03-26 15:57发布

站内问答 / DSP
16892 19 905
按照bbb烧写的教程来的串口打印出这些信息，四个灯就全灭了，每个动静，是正在烧镜像吗？
  1. U-Boot SPL 2013.04-dirty (Jun 19 2013 - 09:57:14)
  2. musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
  3. musb-hdrc: MHDRC RTL version 2.0
  4. musb-hdrc: setup fifo_mode 4
  5. musb-hdrc: 28/31 max ep, 16384/16384 memory
  6. USB Peripheral mode controller at 47401000 using PIO, IRQ 0
  7. musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
  8. musb-hdrc: MHDRC RTL version 2.0
  9. musb-hdrc: setup fifo_mode 4
  10. musb-hdrc: 28/31 max ep, 16384/16384 memory
  11. USB Host mode controller at 47401800 using PIO, IRQ 0
  12. OMAP SD/MMC: 0
  13. reading u-boot.img
  14. reading u-boot.img


  17. U-Boot 2013.04-dirty (Jun 19 2013 - 09:57:14)

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

  27. musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
  28. musb-hdrc: MHDRC RTL version 2.0
  29. musb-hdrc: setup fifo_mode 4
  30. musb-hdrc: 28/31 max ep, 16384/16384 memory
  31. USB Peripheral mode controller at 47401000 using PIO, IRQ 0
  32. musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
  33. musb-hdrc: MHDRC RTL version 2.0
  34. musb-hdrc: setup fifo_mode 4
  35. musb-hdrc: 28/31 max ep, 16384/16384 memory
  36. USB Host mode controller at 47401800 using PIO, IRQ 0
  37. Net:   <ethaddr> not set. Validating first E-fuse MAC
  38. cpsw, usb_ether
  39. Hit any key to stop autoboot:  0
  40. gpio: pin 53 (gpio 53) value is 1
  41. mmc0 is current device
  42. micro SD card found
  43. mmc0 is current device
  44. gpio: pin 54 (gpio 54) value is 1
  45. SD/MMC found on device 0
  46. reading uEnv.txt
  47. 14 bytes read in 2 ms (6.8 KiB/s)
  48. Loaded environment from uEnv.txt
  49. Importing environment from mmc ...
  50. gpio: pin 55 (gpio 55) value is 1
  51. 4270840 bytes read in 761 ms (5.4 MiB/s)
  52. gpio: pin 56 (gpio 56) value is 1
  53. 24125 bytes read in 54 ms (435.5 KiB/s)
  54. Booting from mmc ...
  55. ## Booting kernel from Legacy Image at 80007fc0 ...
  56.    Image Name:   Angstrom/3.8.13/beaglebone
  57.    Image Type:   ARM Linux Kernel Image (uncompressed)
  58.    Data Size:    4270776 Bytes = 4.1 MiB
  59.    Load Address: 80008000
  60.    Entry Point:  80008000
  61.    Verifying Checksum ... OK
  62. ## Flattened Device Tree blob at 80f80000
  63.    Booting using the fdt blob at 0x80f80000
  64.    XIP Kernel Image ... OK
  65. OK
  66.    Using Device Tree in place at 80f80000, end 80f88e3c

  68. Starting kernel ...

  70. Uncompressing Linux... done, booting the kernel.
  71. [    0.193926] omap2_mbox_probe: platform not supported
  72. [    0.204554] tps65217-bl tps65217-bl: no platform data provided
  73. [    0.281067] bone-capemgr bone_capemgr.9: slot #0: No cape found
  74. [    0.318172] bone-capemgr bone_capemgr.9: slot #1: No cape found
  75. [    0.355281] bone-capemgr bone_capemgr.9: slot #2: No cape found
  76. [    0.392389] bone-capemgr bone_capemgr.9: slot #3: No cape found
  77. [    0.411848] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN conflict P8.45 (#5:BB-BONELT-HDMI)
  78. [    0.421497] bone-capemgr bone_capemgr.9: slot #6: Failed verification
  79. [    0.428273] bone-capemgr bone_capemgr.9: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2)
  80. [    0.450828] omap_hsmmc mmc.4: of_parse_phandle_with_args of 'reset' failed
  81. [    0.515957] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8
  82. [    0.527674] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22
  83. [    0.534991] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single
  84. [    8.644991] libphy: PHY 4a101000.mdio:01 not found
  85. [    8.650053] net eth0: phy 4a101000.mdio:01 not found on slave 1

  87. .---O---.                                          
  88. |       |                  .-.           o o        
  89. |   |   |-----.-----.-----.| |   .----..-----.-----.
  90. |       |     | __  |  ---'| '--.|  .-'|     |     |
  91. |   |   |  |  |     |---  ||  --'|  |  |  '  | | | |
  92. '---'---'--'--'--.  |-----''----''--'  '-----'-'-'-'
  93.                 -'  |
  94.                 '---'

  96. The Angstrom Distribution beaglebone ttyO0

  98. Angstrom v2012.12 - Kernel 3.8.13

  100. beaglebone login: systemd-fsck[85]: eMMC-Flasher: clean, 12901/218592 files, 167203/873534 blocks
复制代码

此帖出自小平头技术问答
友情提示: 此问题已得到解决，问题已经关闭,关闭后问题禁止继续编辑，回答。
该问题目前已经被作者或者管理员关闭, 无法添加新回复
19条回答
wytalfred
1楼-- · 2019-03-26 23:46
< 灯全灭了以后你做什么了？有没有再多等一会看看？
白丁
2楼-- · 2019-03-27 05:22
<
wytalfred 发表于 2014-4-13 13:28
灯全灭了以后你做什么了？有没有再多等一会看看？

等了好长时间（有三四个小时），还是不行，拔掉sd卡重新上电，是这个
  1. U-Boot SPL 2014.01-dirty (Mar 11 2014 - 08:29:44)
  2. reading args
  3. spl: error reading image args, err - -1
  4. reading u-boot.img
  5. reading u-boot.img


  8. U-Boot 2014.01-dirty (Mar 11 2014 - 08:29:44)

  10. I2C:   ready
  11. DRAM:  512 MiB
  12. NAND:  0 MiB
  13. MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
  14. *** Warning - readenv() failed, using default environment

  16. Net:   <ethaddr> not set. Validating first E-fuse MAC
  17. cpsw, usb_ether
  18. Hit any key to stop autoboot:  0
  19. Card did not respond to voltage select!
  20. mmc0(part 0) is current device
  21. Card did not respond to voltage select!
  22. mmc1(part 0) is current device
  23. SD/MMC found on device 1
  24. reading uEnv.txt
  25. 26 bytes read in 3 ms (7.8 KiB/s)
  26. Loaded environment from uEnv.txt
  27. Importing environment from mmc ...
  28. ** File not found /boot/zImage **
  29. Booting from nand ...

  31. no devices available

  33. no devices available
  34. Bad Linux ARM zImage magic!
  35. U-Boot#
复制代码


chenzhufly
3楼-- · 2019-03-27 08:04
呵呵  不需要这么做嘛  等几个小时 时间太长了！
可以用一下步骤：
1、制作SD卡启动
2、挂在U盘
3、执行xz -cd xxxx.img.xz > /dev/mmcblk1

这样就可以把镜像写入eMMC了
白丁
4楼-- · 2019-03-27 10:33
chenzhufly 发表于 2014-4-13 16:15
呵呵  不需要这么做嘛  等几个小时 时间太长了！
可以用一下步骤：
1、制作SD卡启动

关键是等了几个小时还不行，现在能够从sd卡启动，智能连接串口，ssh连接不了
白丁
5楼-- · 2019-03-27 16:24
 精彩回答 2  元偷偷看……
chenzhufly
6楼-- · 2019-03-27 18:12
 精彩回答 2  元偷偷看……
1 2 3 4 下一页

一周热门 更多>

相关问题