Beagle Bone Black stopping at Starting Kernel....

[Ashish Maurya]

This is what I doing...

U-Boot 2014.04 (Sep 21 2017 - 11:25:07)

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, usb_ether

Hit any key to stop autoboot:  0 

U-Boot# 

U-Boot# fatls mmc 0:1

    76868   mlo 

   329548   u-boot.img 

  4964640   uimage 

    26024   am335x-boneblack.dtb 

            system volume information/

4 file(s), 1 dir(s)

U-Boot# fatload mmc 0:1 0x80600000 uImage

reading uImage

4964640 bytes read in 1714 ms (2.8 MiB/s)

U-Boot# fatload mmc 0:1 0x80500000 am335x-boneblack.dtb

reading am335x-boneblack.dtb

26024 bytes read in 19 ms (1.3 MiB/s)

U-Boot# setenv bootargs 'console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw'

U-Boot# print bootargs

bootargs=console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw

U-Boot# bootm 0x80600000 - 0x80500000

## Booting kernel from Legacy Image at 80600000 ...

   Image Name:   Linux-3.12.1-bbb

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    4964576 Bytes = 4.7 MiB

   Load Address: 80008000

   Entry Point:  80008000

   Verifying Checksum ... OK

## Flattened Device Tree blob at 80500000

   Booting using the fdt blob at 0x80500000

   Loading Kernel Image ... OK

   Using Device Tree in place at 80500000, end 805095a7

Starting kernel ...

This is how I built the images-
Using linux-3.12-bone-black kernel.

make -j 4 ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- zImage modules dtbs 

make -j 4 ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- uImage LOADADDR=0x80008000

make -j 4 ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- modules_install \

INSTALL_MOD_PATH=/mnt/rootfs

make -j 4 ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- \

uImage-dtb.am335x-boneblack LOADADDR=0x80008000

SD card has two partitions, first fat and another ext2. First contains - MLO,u-boot.img,uImage,am335x-boneblack.dtb
second contains rootfs.

Not getting where I am doing wrong, please help...
Thank You.

[Madhu K]

Hi,

where is your uEnv.txt file?

Regards,

Madhu

[Ashish Maurya]

Thanks Madhu for replying ...
I am a newbie, please correct my understanding about uEnv.txt if i am wrong, i am setting the env variables manually like-

U-Boot# setenv bootargs 'console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw'

Not sure whether this file is still needed?
If yes, then please guide me through the process how to get that.
Thank you very much for your time.

[Madhu K]

Hi,

There are two options to boot the beaglebone black.

1) Boot the beaglebone black from U-boot : In this method whenever
u-boot prompt comes, you can load the uImage and device tree from
u-boot prompt and let the board boot, in this case uEnv.txt is not
required. You can specify the load address and environment in u-boot
itself.

2) Boot the beaglebone black automatically: In this cas, what ever you
are doing above you neeed to specify in the uEnv.txt file.

So I wanted to know which method you are following.

Regards,
Madhu

> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/4e6e6149-3625-4d28-ac75-fe55643e1319%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Ashish Maurya]

Yes, after some searching I just came to know about both the methods. I am using method one: booting without uEnv.txt file.
Thanks for explaining.

[Madhu K]

Hi,

what are all the files you are loading from the u-boot prompt, can you
list those?

Regards,
Madhu

> https://groups.google.com/d/msgid/beagleboard/ad6325d7-b92d-4559-b6f9-5f029dc2662a%40googlegroups.com.

[Ashish Maurya]

I am doing this on u-boot prompt...

U-Boot# fatload mmc 0:1 0x80600000 uImage

reading uImage

4964640 bytes read in 1714 ms (2.8 MiB/s)

U-Boot# fatload mmc 0:1 0x80500000 am335x-boneblack.dtb

reading am335x-boneblack.dtb

26024 bytes read in 19 ms (1.3 MiB/s)

U-Boot# setenv bootargs 'console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw'

U-Boot# print bootargs

bootargs=console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw

U-Boot# bootm 0x80600000 - 0x80500000

Thanks.

[Madhu K]

Hi,

Can you try these addresses.

uImage :0x82000000
FDT :0x88080000

On Wed, Sep 27, 2017 at 4:42 PM, Ashish Maurya

> https://groups.google.com/d/msgid/beagleboard/814c6268-0a39-4469-a377-3180865ad83b%40googlegroups.com.

[Ashish Maurya]

HI Madhu,
Problem got solved with second method, i.e with uEnv.txt file and zImage instead of uImage.
But now it is getting panic at rootfs mounting at VFS:

[    1.906886] VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2): error -2
[    1.915395] Please append a correct "root=" boot option; here are the available partitions:
[    1.924330] b300          253440 mmcblk0  driver: mmcblk
[    1.929996]   b301           72261 mmcblk0p1 8d75861a-01
[    1.935575]   b302          176715 mmcblk0p2 8d75861a-02
[    1.941207] b308         3833856 mmcblk1  driver: mmcblk
[    1.946786]   b309           98304 mmcblk1p1 00000000-01
[    1.952391]   b30a         3734528 mmcblk1p2 00000000-02
[    1.958017] b318            1024 mmcblk1boot1  (driver?)
[    1.963599] b310            1024 mmcblk1boot0  (driver?)
[    1.969294] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)

This is ,my uEnv.txt file-
[ashish@ashish tmp]$ cat uEnv.txt
loadaddr=0x80200000
fdtaddr=0x80F80000
fdtfile=am335x-boneblack.dtb
kernel_file=zImage
bootdir=/boot
mmcdev=0
mmcpart=1
loadzimage=load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${kernel_file}
loadfdt=load mmc ${mmcdev}:${mmcpart} ${fdtaddr} ${fdtfile}
console=ttyO0,115200n8
mmcroot=/dev/mmcblk0p2 rw
mmcrootfstype=ext3 rootwait fixrtc
mmcargs=setenv bootargs console=${console} root=${mmcroot} rootfstype=${mmcrootfstype} ${optargs}
uenvcmd=run loadzimage; run loadfdt; run mmcargs; bootz ${loadaddr} - ${fdtaddr}

Any idea what is missing now ?

[Ashish Maurya]

Tried with these too, same kernel panic...

[terra ÜÝÜ]

I had this, when power supply was not 5V stable

[Ashish Maurya]

I am powering up the board via USB cable connected to my laptop. Is it
sufficient ?
Or if not then what are other ways to do it Thanks.

> --
> For more options, visit http://beagleboard.org/discuss
> ---

> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/hg30MOAJTd0/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to

> beagleboard...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/beagleboard/5975c40d-67ae-4567-9362-dc5a1829ec37%40googlegroups.com.

>
> For more options, visit https://groups.google.com/d/optout.



--

Ashish Maurya
Mob - 9545752036
LinkedIn - https://www.linkedin.com/in/ashish-maurya-3b95a149/

[Ashish Maurya]

Also one more thing to notice is that this is causing problems when I boot from sd card but no problem when booting from inbuilt emmc.

[Madhu K]

Hi,

Second partition "mmcblk0p2" is of which type ( ext2, ext3 or ext4)?.

are you are making partition?

Regards,
Madhu

> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to beagleboard...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/beagleboard/CAMhEQEn_q5BZjyQ7y-yOQ%2BkFArVU_VyjFpspk1gvf8pSgcMK2g%40mail.gmail.com.

[Ashish Maurya]

It is of ext3 type and it is on second partition of sd card.

[Ashish Maurya]

Hi terra,
I got 5V 2A power supply, still facing same issue.
Any thoughts ???

Thanks.

On Mon, Oct 2, 2017 at 3:57 PM, terra ÜÝÜ <r3l...@gmail.com> wrote:

[Madhu K]

Hi,

Can you try with ext4 file system?

Regards,
Madhu

> You received this message because you are subscribed to the Google Groups "BeagleBoard" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAMhEQEm0eySa5V8nbskr2C%3DnXjRwVdPVvfW%2BMdxwVE1xC3wkQQ%40mail.gmail.com.

[Ashish Maurya]

Hi all,
Thanks for your replies and time.
Problem got solved after properly understanding boot process and so many failed attempts.
Problem was that /dev/mmcblk0p2 entry was not present in /etc/fstab of the rootfs for beaglebone-black
Adding the entry mounted fs properly.

root@beaglebone:~# cat /etc/fstab
# stock fstab - you probably want to override this with a machine specific one

/dev/mmcblk0p2       /                    auto       defaults,sync,noauto,errors=remount-ro  0  1

> To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAA2oCOmkkT%3Dbr6gpERiGE1VcU4ZKUwSLB_Y-DoPvWGfELT%3DwVw%40mail.gmail.com.