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.

BB-black 内核编译完成之后,板子启动不了了



按照element14_BeagleBone_Black用户手册_V2.0,u盘传送新映像到BB_Black,完成所有操作之后,BB-black启动不了了?怎么回事,新人求指教!

  • 这意思是说,你更新了emmc里面的MLO,uboot等镜像文件,之后就起不来了吗?

    那就是这个启动镜像文件有问题呗。你用的是TI官方发布的BBB吗?那个手册没见过,估计是第三方做的吧,建议你把手册贴上来,或者描述一下你都做了什么步骤,更新的文件都是哪里来的。

  • 更新文件都是在这个用户手册里直接wget得到的,Debian系统开发,内核和uboot编译都正常通过了,执行u盘挂载之后reboot,板子就起不来了

    element14_BeagleBone_Black用户手册_V2.0.pdf
  • 头一次做这个,基本按照手册上做的,求指教

  • 建议你先用TF卡做一个系统出来,然后插入到这个板子的接口上。在上电的时候,先按着启动选择按键不要松开,然后上电,这样看板子从你的SD卡是否能启动成功,如果能启动成功,应该就是你当时烧录出了问题;如果还是不能启动成功,可能是你的boot image编的有问题。

    • 这是我用sd卡做的系统,结果就是Uncompressing Linux... done, booting the kernel.之后,就自动重启,能给看一下哪里出问题了吗

    • U-Boot SPL 2015.01-00001-gb2412df (Jan 29 2015 - 15:01:06)


      U-Boot 2015.01-00001-gb2412df (Jan 29 2015 - 15:01:06), Build: jenkins-github_Bo                                                                             otloader-Builder-105

             Watchdog enabled
      I2C:   ready
      DRAM:  512 MiB
      MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
      Using default environment

      Net:   <ethaddr> not set. Validating first E-fuse MAC
      cpsw
      Hit any key to stop autoboot:  0
      gpio: pin 53 (gpio 53) value is 1
      switch to partitions #0, OK
      mmc0 is current device
      gpio: pin 54 (gpio 54) value is 1
      Checking for: /uEnv.txt ...
      reading uEnv.txt
      933 bytes read in 5 ms (181.6 KiB/s)
      gpio: pin 55 (gpio 55) value is 1
      Loaded environment from uEnv.txt
      Importing environment from mmc ...
      Checking if uenvcmd is set ...
      gpio: pin 56 (gpio 56) value is 1
      Running uenvcmd ...
      1698 bytes read in 40 ms (41 KiB/s)
      reading /boot/vmlinuz-3.8.13-rt9-00899-gf053161-dirty
      ** Unable to read file /boot/vmlinuz-3.8.13-rt9-00899-gf053161-dirty **
      reading /boot/initrd.img-3.8.13-rt9-00899-gf053161-dirty
      ** Unable to read file /boot/initrd.img-3.8.13-rt9-00899-gf053161-dirty **
      reading /boot/dtbs/3.8.13-rt9-00899-gf053161-dirty/am335x-boneblack.dtb
      ** Unable to read file /boot/dtbs/3.8.13-rt9-00899-gf053161-dirty/am335x-bonebla                                                                             ck.dtb **
      Bad Linux ARM zImage magic!
      Checking if client_ip is set ...
      Checking for: /boot.scr ...
      Checking for: /boot/boot.scr ...
      Checking for: /boot/uEnv.txt ...
      gpio: pin 55 (gpio 55) value is 1
      1698 bytes read in 39 ms (42 KiB/s)
      Loaded environment from /boot/uEnv.txt
      Checking if uname_r is set in /boot/uEnv.txt...
      gpio: pin 56 (gpio 56) value is 1
      Running uname_boot ...
      loading /boot/vmlinuz-3.8.13-rt9-00899-gf053161-dirty ...
      4449904 bytes read in 288 ms (14.7 MiB/s)
      loading /boot/dtbs/3.8.13-rt9-00899-gf053161-dirty/am335x-boneblack.dtb ...
      23769 bytes read in 51 ms (455.1 KiB/s)
      loading /boot/initrd.img-3.8.13-rt9-00899-gf053161-dirty ...
      7303369 bytes read in 449 ms (15.5 MiB/s)
      debug: [console=ttyO0,115200n8 root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait f                                                                             ixrtc init=/usr/lib/systemd/systemd] ...
      debug: [bootz 0x82000000 0x88080000:6f70c9 0x88000000] ...
      Kernel image @ 0x82000000 [ 0x000000 - 0x43e670 ]
      ## Flattened Device Tree blob at 88000000
         Booting using the fdt blob at 0x88000000
         Using Device Tree in place at 88000000, end 88008cd8

      Starting kernel ...

      Uncompressing Linux... done, booting the kernel.

       

  • 请问您用的是什么版本的sdk?

  • 注意这个

    Bad Linux ARM zImage magic!