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:~#
Hi,
Can you try with ext4 file system?
Regards,
Madhu
On Mon, Oct 9, 2017 at 11:53 AM, Ashish Maurya
wrote:
> 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 ÜÝÜ
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 ÜÝÜ wrote:
> I had this, when power supply was not 5V stable
>
> On Tuesday, 26 September 2017 18:12:19 UTC+10, Ashish Maurya wrote:
>>
>> This is what I
It is of ext3 type and it is on second partition of sd card.
On Friday, October 6, 2017 at 11:53:09 AM UTC+5:30, Madhu K wrote:
>
> Hi,
>
> Second partition "mmcblk0p2" is of which type ( ext2, ext3 or ext4)?.
>
> are you are making partition?
>
> Regards,
> Madhu
>
> On Fri, Oct 6, 2017 at
Hi,
Second partition "mmcblk0p2" is of which type ( ext2, ext3 or ext4)?.
are you are making partition?
Regards,
Madhu
On Fri, Oct 6, 2017 at 11:20 AM, Ashish Maurya
wrote:
> Also one more thing to notice is that this is causing problems when I boot
> from sd card
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.
On Fri, 6 Oct 2017 at 10:17, Ashish Maurya
wrote:
> I am powering up the board via USB cable connected to my laptop. Is it
>
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.
On Mon, Oct 2, 2017 at 3:57 PM, terra ÜÝÜ wrote:
> I had this, when power supply was not 5V stable
>
> On Tuesday, 26 September 2017 18:12:19
I had this, when power supply was not 5V stable
On Tuesday, 26 September 2017 18:12:19 UTC+10, Ashish Maurya wrote:
>
> 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
>
>
Tried with these too, same kernel panic...
On Thursday, September 28, 2017 at 11:33:26 AM UTC+5:30, Madhu K wrote:
>
> Hi,
>
> Can you try these addresses.
>
> uImage :0x8200
> FDT :0x8808
>
> On Wed, Sep 27, 2017 at 4:42 PM, Ashish Maurya
> wrote:
> > I
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="
Hi,
Can you try these addresses.
uImage :0x8200
FDT :0x8808
On Wed, Sep 27, 2017 at 4:42 PM, Ashish Maurya
wrote:
> I am doing this on u-boot prompt...
> U-Boot# fatload mmc 0:1 0x8060 uImage
> reading uImage
> 4964640 bytes read in 1714 ms (2.8
I am doing this on u-boot prompt...
U-Boot# fatload mmc 0:1 0x8060 uImage
reading uImage
4964640 bytes read in 1714 ms (2.8 MiB/s)
U-Boot# fatload mmc 0:1 0x8050 am335x-boneblack.dtb
reading am335x-boneblack.dtb
26024 bytes read in 19 ms (1.3 MiB/s)
U-Boot# setenv bootargs
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
wrote:
> Yes, after some searching I just came to know about both the methods. I am
> using method one: booting
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)
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
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
Hi,
where is your uEnv.txt file?
Regards,
Madhu
On Tuesday, September 26, 2017 at 1:42:19 PM UTC+5:30, Ashish Maurya wrote:
>
> 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
17 matches
Mail list logo