Re: [beagleboard] BBW fails to boot

[hesham . eembedded]

Hi William, I want the kernel tree so that I can build a kernel module. I'll follow your advise and start with a working image. It might be easier that way to get a working tree of the kernel instead of bothering with uboot and MLO. Thanks, -Hesham Sent from my BlackBerry 10 smartphone on the Rogers network. From: William Hermans Sent: Tuesday, June 28, 2016 9:53 AM To: beagleboard@googlegroups.com Reply To: beagleboard@googlegroups.com Subject: Re: [beagleboard] BBW fails to boot Hesham, I think at this point, the safest thing to do is to get the newest standalone( non flasher ) console image, boot it, and observe the serial debug output. After that, check out the file structure, and perhaps rip out some needed files to put into your system. Question though. Is there a specific reason why you're compiling your own kernel ? If not, it may be best to just use the latest console image, and strip that down to something smaller if that's what you need. On Tue, Jun 28, 2016 at 5:39 AM, Hesham <hesham.eembed...@gmail.com> wrote: There is nothing but the /boot/uEnv.txt that I sent you earlier. Also, there is no initrd.img as well in the tree. I followed the steps in the eewiki page but this is what I got! On Monday, June 27, 2016 at 1:57:33 PM UTC-4, William Hermans wrote: Ok, no nothing there s critical for booting your board. capemgr is still installed, it only the device overlays that are not installed. So, can you show us what the file /uEnv.txt contains ? Not /bootuEnv.txt, but /uEnv.txt. Thats the first stage uboot environment file, thats super important for booting the board. On Mon, Jun 27, 2016 at 10:54 AM, William Hermans <yyr...@gmail.com> wrote: Or wait, my bad I see what you mean now. Let me look On Mon, Jun 27, 2016 at 10:53 AM, William Hermans <yyr...@gmail.com> wrote: You should show us all your debug output at once. It's too hard to troubleshoot based on only one debug line. Unless it's really obvious. On Mon, Jun 27, 2016 at 5:44 AM, Hesham <hesham.e...@gmail.com> wrote: I stopped at : capemgr: v4.1.x+ I don't have/plan to use capes. Is this fatal? On Monday, June 27, 2016 at 3:03:16 AM UTC-4, William Hermans wrote: Hesham, you followed the guide exactly ? Or did you make any modifications. Such as changing the partition structure, putting files in different locations, or leaving steps outs ? Just looking at that guide, which is very similar to the BBB guide mind you( possibly exactly alike baring eMMC ) . . .One thing I noticed missing was the first stage uEnv.txt file. I assumed that is now included in the rootfs Robert tells you to use . . . but I do not know that for a fact. Anyway, if there is a /uEnv.txt file ( root of the rootfs ) it should have a suitable, and valid path for files needed at system up. Also, I *think* but am not 100% sure. That you can comment  out the path for the initrd file, and then this problem should go away. However, I'd prefer Robert to comment on that as it has been a while for me . . . On Sun, Jun 26, 2016 at 11:51 PM, William Hermans <yyr...@gmail.com> wrote: By my reckoning you're missing a few files. You're missing an initrd, and a System.map* file. You're also missing SOH.sh, and the config file. The config file is probably not required, but I'm unsure of the SOC.sh file. However, judging by your error message. You've built with using an initrd in mind, yet you do not have one.  However, I'm not sure of a fix, unless you skipped some steps from the guide. As I haven't built my own kernel in over a year using Robert guide . . . so I'm not 100% up to speed on what all he's doing now. However. For most intents and purposes. The BBW, and BBB are very alike. I'd say exactly, but obviously the BBW does not have a few thing the BBB does. The BBW also has JTAG. But I think the biggest difference is DDR voltage difference. Which would not be the reason for this issue. Besides, I happen to know that uboot checks for, and detects this. The board file is also slightly different. Anyhow, the point is, that anything that runs on the BBB should technically run on the BBW too. william@beaglebone:~$ ls /boot SOC.sh                        config-4.4.8-ti-r22       initrd.img-4.4.8-ti-r22       uboot 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 On Sun, Jun 26, 2016 at 10:37 PM, Hesham <hesham.e...@gmail.com> wrote: Hi Charles, I'm open to try older builds. Can you point me to a working older instructions that can help me get this board booting? Thanks, -Hesham On Sunday, June 26, 2016 at 6:09:39 PM UTC-4, Charles Steinkuehler wrote: Of course!  <doh!> You can tell how long it's been since I booted my BBW.  :blush: Anyway, there have been lots of changes with the boot loader since the BBW, and I'd recommend starting with a working console image with a recent kernel and u-Boot, with the console images probably being the best starting point if you're wanting to craft your own image. The ROM boot code of the AM335x hasn't changed, but there are very specific constraints on what makes a bootable uSD image (specifically the MLO boot-loader and it's location on the physical media).  The easiest way to deal with the constraints is to start with a working image. On 6/26/2016 4:34 PM, evilwulfie wrote: > BBW has no emmc :) > > On 6/26/2016 12:59 PM, Charles Steinkuehler wrote: >> On 6/26/2016 7:56 AM, Hesham wrote: >>> Hi all, >>> >>> I have an old BBW that I wanted to revive. It boots fine with the SD card that >>> came with it. It boots well with an old SD that I built following come old >>> instructions, pre-dates DTS. >>> >>> Now, I've tried to build it following the instructions on: >>> https://eewiki.net/display/linuxonarm/BeagleBone >>> It fails to boot. I think something is wrong regarding the bootloader, either >>> the way I built it or the instructions might be wrong for this old platform. >> An old BBW is going to have an ancient (in computer time-scale) >> boot-loader.  I recommend you flash the on-board eMMC with a new boot >> loader.  You can do this manually if you really want to (and know >> how), but the easiest way would be to use a recent console image >> flasher like: >> >> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Flasher:_.28console.29_.28BeagleBone_Black.2FGreen_eMMC.29 >> >> ...assuming you don't mind trashing whatever is in the eMMC, of course! >> > -- Charles Steinkuehler cha...@steinkuehler.net -- 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/de6efcfc-ecf7-4b51-ab36-8204e79e469e%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 beagleboard...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/1fd2c068-bf70-4119-8cb9-5ea330306109%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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/160f0683-5f0d-4f7f-859e-f9cc23950f87%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 a topic in the Google Groups "BeagleBoard" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/b4_W6UC6KKk/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORo8c4P_fkgWq__cbw5Dn0jG%2BPf3vS5GH0u6uYCNsRt8MA%40mail.gmail.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/20160628200747.5492820.17569.1088%40gmail.com. For more options, visit https://groups.google.com/d/optout.