Beaglebone black可以进uboot,但是不能进linux

[复制链接]
741|2
 楼主 | 2017-12-20 22:40 | 显示全部楼层 ||阅读模式
小弟有块BBB,sd卡刷Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone-2013.06.20.img
可以进uboot,在uboot待多久都没关系。
但是一过uboot进系统就会突然断电,每次断电时候串口打出的信息都在同一个位置。这是为啥呢?试了几个系统都是这样,BBB的芯片是AM3359。
启动log如下:
U-Boot 2013.04-dirty (Jun 19 2013 - 09:57:14)

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, 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, 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
gpio: pin 53 (gpio 53) value is 1
mmc0 is current device
micro SD card found
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
SD/MMC found on device 0
reading uEnv.txt
33 bytes read in 4 ms (7.8 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc ...
gpio: pin 55 (gpio 55) value is 1
4270840 bytes read in 764 ms (5.3 MiB/s)
gpio: pin 56 (gpio 56) value is 1
24129 bytes read in 45 ms (523.4 KiB/s)
Booting from mmc ...
## Booting kernel from Legacy Image at 80007fc0 ...
   Image Name:   Angstrom/3.8.13/beaglebone
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4270776 Bytes = 4.1 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 80f80000
   Booting using the fdt blob at 0x80f80000
   XIP Kernel Image ... OK
OK
   Using Device Tree in place at 80f80000, end 80f88e40

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.230531] omap2_mbox_probe: platform not supported
[    0.244117] tps65217-bl tps65217-bl: no platform data provided
[    0.327462] bone-capemgr bone_capemgr.8: slot #0: No cape found
[    0.366517] bone-capemgr bone_capemgr.8: slot #1: No cape found
[    0.405577] bone-capemgr bone_capemgr.8: slot #2: No cape found
[    0.444639] bone-capemgr bone_capemgr.8: slot #3: No cape found
[    0.469690] bone-capemgr bone_capemgr.8: slot #6: BB-BONELT-HDMIN conflict P8.45 (#5:BB-BONELT-HDMI)
[    0.481744] bone-capemgr bone_capemgr.8: slot #6: Failed verification
[    0.490222] bone-capemgr bone_capemgr.8: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2)
[    0.518555] omap_hsmmc mmc.4: of_parse_phandle_with_args of 'reset' failed
[    0.585791] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.7
[    0.600436] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.7) status -22
[    0.609598] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single



然后power灯就灭了。。。
| 2017-12-21 22:12 | 显示全部楼层
有些外设没有 检测通过     重点查 tps65217-bl

使用特权

评论回复
| 2018-1-1 16:17 | 显示全部楼层
我还遇到过一种情况   系统起来  进不了桌面
最后发现是存储里面放的东西太多了    只能远程登录进去删除超大文件

使用特权

评论回复
扫描二维码,随时随地手机跟帖
您需要登录后才可以回帖 登录 | 注册

本版积分规则

我要发帖 投诉建议 创建版块 申请版主

快速回复

您需要登录后才可以回帖
登录 | 注册
高级模式

论坛热帖

在线客服 快速回复 返回顶部 返回列表