Re: [beagleboard] Re: BBB doesn't boot after inserting uSD card having linux, even after pressing the S2 button for long
Hi William,
I finally got the Board working !!!
Right now, it's booting from the uSD card. The OS in the eMMC is still
causing problems though, but at least it's working somehow now.
I downloaded the image
:
https://debian.beagleboard.org/images/bone-debian-8.4-lxqt-4gb-armhf-2016-05-13-4gb.img.xz
from https://beagleboard.org/latest-images
You were right about the zImage issue. Makes sense now, now that I
downloaded the 2016 edition of the image. I realized that I had the 2013
version of the image earlier.
Thanks a lot, William for helping me come to this point at least.
Sincerely,
Viswadeep
On Tuesday, 20 September 2016 22:38:48 UTC+5:30, William Hermans wrote:
>
> zImage is the old way Robert *used* to build kernels. As in . . .
> http://www.embeddedhobbyist.com/2013/07/beaglebone-black-usb-boot/ Look
> towards the bottom where I discuss mkimage. But anyway that post I made way
> back in july 2013, and it's very outdated. It's not how things are done any
> more.
>
> But quite honestly I really do not understand the kernel images in depth,
> so perhaps as I'm an applications developer. Not a kernel developer.
> Granted with a good bit of low level software experience too . . .
>
> On Tue, Sep 20, 2016 at 6:13 AM, Dennis Lee Bieber > wrote:
>
>> On Tue, 20 Sep 2016 02:39:50 -0700 (PDT), Viswadeep Sarangi
>> > declaimed the
>> following:
>>
>> >
>> >Right now, I have installed the following image onto my uSD card :
>> >
>> https://debian.beagleboard.org/images/BBB-eMMC-flasher-debian-7.5-2014-05-14-2gb.img.xz
>> > --- but the BBB doesn't boot from it anymore (even after pressing the S2
>> >button) and still shows the top 2 LEDs lit forever.
>> >
>> Try the version that does not have "flasher" in the name, just to
>> see
>> if the system can boot from a plain SD card image.
>>
>> When booting a flasher image, the LEDs normally do a 0-3 fill
>> sequence
>> at the start of flashing, then to some pattern that may vary with the
>> image
>> before going to a solid all on at the end (Molloy's website says a
>> side-to-side sweep while flashing).
>>
>> You seem to be seeing the first phase of a flasher start.
>>
>> Hmm -- how are you powering the unit? A USB connection may not be
>> providing enough power to sustain eMMC flashing.
>>
>> >
>> >loadfdt=load mmc ${mmcdev}:${mmcpart} ${fdtaddr} /dtbs/${fdtfile}
>> >
>> Other than the fact that I don't know where the environment
>> variables
>> are defined... mmcdev, mmcpart, and fdtfile are not defined in uEnv.txt;
>> the first two define the flash device and partition, and the last
>> specifies
>> the device tree file.
>>
>> The contents do show that it expects the kernel image to be:
>> zImage
>> and initrd to be: initrd.img
>> so those match the directory content.
>> --
>> Wulfraed Dennis Lee Bieber AF6VN
>> wlf...@ix.netcom.com HTTP://wlfraed.home.netcom.com/
>>
>> --
>> 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/6oc2ubl9o4dl0qm3gpo8kn9jg0lt7l2r50%404ax.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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/06fa9b4a-a8ff-4a40-aed7-37c92ab41a0a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: BBB doesn't boot after inserting uSD card having linux, even after pressing the S2 button for long
zImage is the old way Robert *used* to build kernels. As in . . .
http://www.embeddedhobbyist.com/2013/07/beaglebone-black-usb-boot/ Look
towards the bottom where I discuss mkimage. But anyway that post I made way
back in july 2013, and it's very outdated. It's not how things are done any
more.
But quite honestly I really do not understand the kernel images in depth,
so perhaps as I'm an applications developer. Not a kernel developer.
Granted with a good bit of low level software experience too . . .
On Tue, Sep 20, 2016 at 6:13 AM, Dennis Lee Bieber
wrote:
> On Tue, 20 Sep 2016 02:39:50 -0700 (PDT), Viswadeep Sarangi
> declaimed the
> following:
>
> >
> >Right now, I have installed the following image onto my uSD card :
> >https://debian.beagleboard.org/images/BBB-eMMC-flasher-
> debian-7.5-2014-05-14-2gb.img.xz
> > --- but the BBB doesn't boot from it anymore (even after pressing the S2
> >button) and still shows the top 2 LEDs lit forever.
> >
> Try the version that does not have "flasher" in the name, just to
> see
> if the system can boot from a plain SD card image.
>
> When booting a flasher image, the LEDs normally do a 0-3 fill
> sequence
> at the start of flashing, then to some pattern that may vary with the image
> before going to a solid all on at the end (Molloy's website says a
> side-to-side sweep while flashing).
>
> You seem to be seeing the first phase of a flasher start.
>
> Hmm -- how are you powering the unit? A USB connection may not be
> providing enough power to sustain eMMC flashing.
>
> >
> >loadfdt=load mmc ${mmcdev}:${mmcpart} ${fdtaddr} /dtbs/${fdtfile}
> >
> Other than the fact that I don't know where the environment
> variables
> are defined... mmcdev, mmcpart, and fdtfile are not defined in uEnv.txt;
> the first two define the flash device and partition, and the last specifies
> the device tree file.
>
> The contents do show that it expects the kernel image to be: zImage
> and initrd to be: initrd.img
> so those match the directory content.
> --
> Wulfraed Dennis Lee Bieber AF6VN
> wlfr...@ix.netcom.comHTTP://wlfraed.home.netcom.com/
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/beagleboard/6oc2ubl9o4dl0qm3gpo8kn9jg0lt7l2r50%404ax.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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/CALHSORrOYteuC96-JHAmRCp9oDupj3v-pbVzHXc70S-uemOgoQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: BBB doesn't boot after inserting uSD card having linux, even after pressing the S2 button for long
Hi William, I couldn't find anything in the uEnv.txt having uname. I am attaching the uEnv.txt file here again for reference. The BBB currently has a flashed Ubuntu image from : https://rcn-ee.com/rootfs/2016-09-09/flasher/BBB-eMMC-flasher-ubuntu-16.04.1-console-armhf-2016-09-09-2gb.img.xz And I am trying to flash it with a Debian image from : https://debian.beagleboard.org/images/BBB-eMMC-flasher-debian-7.5-2014-05-14-2gb.img.xz I am not sure about the Ubuntu one, but I think the one below is definitely official, as it was mentioned on the BBB official site itself : http://beagleboard.org/latest-images Also interesting was that of the contents of /boot you mentioned, I went into the Ext4 partition of the uSD card and into /boot and found only one directory called "uboot" with No files inside. The directory was empty. But when I checked the FAT16 partition of the uSD, I found some of the files you mentioned, which I was supposed to find in /boot (red colored files are the ones I couldn't find) SOC.shconfig-4.4.14-ti-r34 initrd.img-4.4.14-ti-r34 uboot System.map-4.4.14-ti-r34 config-4.4.14-ti-rt-r34 initrd.img-4.4.14-ti-rt-r34 vmlinuz-4.4.14-ti-r34 System.map-4.4.14-ti-rt-r34 config-4.4.8-ti-r22 initrd.img-4.4.8-ti-r22 vmlinuz-4.4.14-ti-rt-r34 System.map-4.4.8-ti-r22 config-4.4.9-bone-rt-r10 initrd.img-4.4.9-bone-rt-r10 vmlinuz-4.4.8-ti-r22 System.map-4.4.9-bone-rt-r10 dtbs uEnv.txt vmlinuz-4.4.9-bone-rt-r10 I found these additional files and directories which you haven't mentioned : App (directory) debug (directory) Docs (directory) Drivers (directory) scripts (directory) flash-eMMC.txt ID.txt initrd.img MLO u-boot.img zImage I am using Win32 Disk Imager to transfer the contents of the .img file to the SD card. I used 'DiskInternals Linux Reader' to access the contents of the SD card's Linux Partition. Inside the 'dtbs' folder, I found the following : am335x-boneblack.dtb am335x-bone.dtb am335x-evm.dtb am335x-evmsk.dtb am335x-tester.dtb omap2420-h4.dtb omap3-beagle.dtb omap3-beagle-xm.dtb omap3-evm.dtb omap3-tobi.dtb omap4-panda-a4.dtb omap4-panda.dtb omap4-panda-es.dtb omap4-sdp.dtb omap4-var-som.dtb omap5-evm.dtb I am surprised that your directory and file structure and mine are completely different. Am I doing something wrong here ? On Tuesday, 20 September 2016 03:54:58 UTC+5:30, William Hermans wrote: > > As with anything else computer related. You should be mindful of where you > get your OS images from. Clearly the one the OP is working with is not a > standard "official" image. Since Robert has not built any using a FAT > partition in quite some time. As in more than a year ago. > > So in order to get better help. You should be contacting the people from > where you got your image from. As no one here is likely familiar with that > image. Unless the person who created it also lurks here. > > On Mon, Sep 19, 2016 at 3:15 PM, Dennis Lee Bieber > wrote: > >> On Mon, 19 Sep 2016 08:55:42 -0700 (PDT), Viswadeep Sarangi >> > declaimed the >> following: >> >> > >> >But when I started the BBB after flashing. Only the first two LEDs >> flashed >> >and stayed lit ( USR0 and USR1). But nothing else happened. It's been >> like >> >> USR1 is defined to be SD card access, and USR3 is the eMMC. >> >> But where in the OS those get controlled I can't say... nor if >> any of >> the third-party OS releases don't bother installing the handlers for the >> LEDs. >> >> >Any idea what might be happening and how I can fix it ? >> >> My first suggestion would be to revert to a 2GB compatible >> official >> image first -- which would be this old one: >> >> https://debian.beagleboard.org/images/BBB-eMMC-flasher-debian-7.5-2014-05-14-2gb.img.xz >> >> If the BBB won't run that after flashing (and removing the SD >> card) you >> have some significant problem. Actually, I'd suggest first booting an SD >> card with >> >> https://debian.beagleboard.org/images/bone-debian-7.5-2014-05-14-2gb.img.xz >> just to make sure the BBB runs with that OS, period... THEN flash the eMMC >> and check that it still runs. >> >> IF you get the unit to run with the 2GB flasher image above... >> THEN try >> your third party OS on the SD card in a NON-flasher mode; ensure that OS >> works before flashing it to the eMMC... And make sure it does fit >> (depending on how "GB" is being computed -- you may still be running over: >> decimal 2GB is only binary 1.86GB). >> -- >> Wulfraed Dennis Lee Bieber AF6VN >> wlf...@ix.netcom.com HTTP://wlfraed.home.netcom.com/ >> >> -- >> 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
Re: [beagleboard] Re: BBB doesn't boot after inserting uSD card having linux, even after pressing the S2 button for long
As with anything else computer related. You should be mindful of where you get your OS images from. Clearly the one the OP is working with is not a standard "official" image. Since Robert has not built any using a FAT partition in quite some time. As in more than a year ago. So in order to get better help. You should be contacting the people from where you got your image from. As no one here is likely familiar with that image. Unless the person who created it also lurks here. On Mon, Sep 19, 2016 at 3:15 PM, Dennis Lee Bieber wrote: > On Mon, 19 Sep 2016 08:55:42 -0700 (PDT), Viswadeep Sarangi > declaimed the > following: > > > > >But when I started the BBB after flashing. Only the first two LEDs flashed > >and stayed lit ( USR0 and USR1). But nothing else happened. It's been like > > USR1 is defined to be SD card access, and USR3 is the eMMC. > > But where in the OS those get controlled I can't say... nor if any > of > the third-party OS releases don't bother installing the handlers for the > LEDs. > > >Any idea what might be happening and how I can fix it ? > > My first suggestion would be to revert to a 2GB compatible official > image first -- which would be this old one: > https://debian.beagleboard.org/images/BBB-eMMC-flasher- > debian-7.5-2014-05-14-2gb.img.xz > > If the BBB won't run that after flashing (and removing the SD > card) you > have some significant problem. Actually, I'd suggest first booting an SD > card with > https://debian.beagleboard.org/images/bone-debian-7.5- > 2014-05-14-2gb.img.xz > just to make sure the BBB runs with that OS, period... THEN flash the eMMC > and check that it still runs. > > IF you get the unit to run with the 2GB flasher image above... > THEN try > your third party OS on the SD card in a NON-flasher mode; ensure that OS > works before flashing it to the eMMC... And make sure it does fit > (depending on how "GB" is being computed -- you may still be running over: > decimal 2GB is only binary 1.86GB). > -- > Wulfraed Dennis Lee Bieber AF6VN > wlfr...@ix.netcom.comHTTP://wlfraed.home.netcom.com/ > > -- > 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+unsubscr...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/beagleboard/vkn0ubt4p12lnqa6idda3ort0croord1pd%404ax.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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORon8n_Nq9aaqenEY7HHOgbMSA-XVSv%3DJCLqaro2ZAbGfw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: BBB doesn't boot after inserting uSD card having linux, even after pressing the S2 button for long
Ah, and right. This value can be modified in order to reflect a known
working kernel. Or "point" to a known working kernel. If you know what
you're doing . . . Which is not very simple to explain but not overly hard
either. For instance:
$ ls /boot/
SOC.shconfig-4.4.14-ti-r34
initrd.img-4.4.14-ti-r34 uboot
System.map-4.4.14-ti-r34 config-4.4.14-ti-rt-r34
initrd.img-4.4.14-ti-rt-r34 vmlinuz-4.4.14-ti-r34
System.map-4.4.14-ti-rt-r34 config-4.4.8-ti-r22
initrd.img-4.4.8-ti-r22 vmlinuz-4.4.14-ti-rt-r34
System.map-4.4.8-ti-r22 config-4.4.9-bone-rt-r10
initrd.img-4.4.9-bone-rt-r10 vmlinuz-4.4.8-ti-r22
System.map-4.4.9-bone-rt-r10 dtbs
uEnv.txt vmlinuz-4.4.9-bone-rt-r10
and
$ ls /boot/dtbs/
4.4.14-ti-r34 4.4.14-ti-rt-r34 4.4.8-ti-r22 4.4.9-bone-rt-r10
As you can see I have the possibility to load any of these 4 kernel
directory "trees" that I show listed in my last command. simply by editing
the "uname_r" parameter in the /boot.uEnv.txt file.
On Mon, Sep 19, 2016 at 3:07 PM, William Hermans wrote:
>
>
> On Mon, Sep 19, 2016 at 2:53 PM, Dennis Lee Bieber
> wrote:
>
>> On Sun, 18 Sep 2016 21:19:49 -0700 (PDT), Viswadeep Sarangi
>> declaimed the
>> following:
>>
>>
>> {I was running late getting to work and missed this part}
>>
>> >The contents of the FAT partition include :
>> >- a "dtbs" directory, which contains a lot of .dtb files
>> >- uEnv.txt
>> >- zImage file
>> >
>>
>> If the card isn't booting off the SD card, you might have to
>> examine
>> that uEnv.txt file for things that may be erroneous, since (as I
>> understand
>> things) it defines some of the stuff used by u-Boot to get to the rest of
>> the OS.
>>
>
> At minimum:
>
> $ cat /boot/uEnv.txt | grep uname
> uname_r=4.4.14-ti-r34
>
> This is needed in order to find. . . I forget off the top of my head, but
> for instance, it refers to the kernel version you wish to run. So without
> this set, the default 1st stage uEnv.txt file wont know where to look for
> the kernel, and probably the board file device tree overlay.
>
> This is really easy to check on a Linux system, but would require
> *something* in order for Windows to read ext4 file systems.
>
>
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/CALHSORozdWdx26PcdGO-VGg5Oo6V8i%2BcK4HF0a_Vw5K9UeW%3DzA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: BBB doesn't boot after inserting uSD card having linux, even after pressing the S2 button for long
On Mon, Sep 19, 2016 at 2:53 PM, Dennis Lee Bieber
wrote:
> On Sun, 18 Sep 2016 21:19:49 -0700 (PDT), Viswadeep Sarangi
> declaimed the
> following:
>
>
> {I was running late getting to work and missed this part}
>
> >The contents of the FAT partition include :
> >- a "dtbs" directory, which contains a lot of .dtb files
> >- uEnv.txt
> >- zImage file
> >
>
> If the card isn't booting off the SD card, you might have to
> examine
> that uEnv.txt file for things that may be erroneous, since (as I understand
> things) it defines some of the stuff used by u-Boot to get to the rest of
> the OS.
>
At minimum:
$ cat /boot/uEnv.txt | grep uname
uname_r=4.4.14-ti-r34
This is needed in order to find. . . I forget off the top of my head, but
for instance, it refers to the kernel version you wish to run. So without
this set, the default 1st stage uEnv.txt file wont know where to look for
the kernel, and probably the board file device tree overlay.
This is really easy to check on a Linux system, but would require
*something* in order for Windows to read ext4 file systems.
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/CALHSORrqvx7uNMQobm_y-FSD3hRZpwVFE9tz2jsqpixweAk-EA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
