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 ?
On Thursday, September 28, 2017 at 11:33:26 AM UTC+5:30, Madhu K wrote:
>
> Hi,
>
> Can you try these addresses.
>
> uImage :0x82000000
> FDT :0x88080000
>
> On Wed, Sep 27, 2017 at 4:42 PM, Ashish Maurya
> <[email protected] <javascript:>> wrote:
> > 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.
> > On Wednesday, September 27, 2017 at 2:21:21 PM UTC+5:30, Madhu K wrote:
> >>
> >> Hi,
> >>
> >> what are all the files you are loading from the u-boot prompt, can you
> >> list those?
> >>
> >> Regards,
> >> Madhu
> >>
> >> On Wed, Sep 27, 2017 at 1:46 PM, Ashish Maurya
> >> <[email protected]> wrote:
> >> > 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.
> >> >
> >> > On Wednesday, September 27, 2017 at 11:29:01 AM UTC+5:30, Madhu K
> wrote:
> >> >>
> >> >> 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
> >> >>
> >> >>
> >> >>
> >> >> On Wed, Sep 27, 2017 at 8:51 AM, Ashish Maurya
> >> >> <[email protected]> wrote:
> >> >> > 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.
> >> >> >
> >> >> > --
> >> >> > 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 [email protected].
> >> >> > 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.
> >> >
> >> > --
> >> > 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 [email protected].
> >> > To view this discussion on the web visit
> >> >
> >> >
> https://groups.google.com/d/msgid/beagleboard/ad6325d7-b92d-4559-b6f9-5f029dc2662a%40googlegroups.com.
>
>
> >> >
> >> > For more options, visit https://groups.google.com/d/optout.
> >
> > --
> > 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 [email protected] <javascript:>.
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/beagleboard/814c6268-0a39-4469-a377-3180865ad83b%40googlegroups.com.
>
>
> >
> > For more options, visit https://groups.google.com/d/optout.
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/36e95d2e-5fc0-49e9-bf4a-c77de668a18c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
