Hi William,
It seems it's a power issue. I used the SD image:
bone-ubuntu-16.04-console-armhf-2016-06-09-2gb.img.xz
But I saw the same failure while in u-boot. Then, I started to suspect
power as I was powering it with USB only. This was never a problem in older
images though (couple of years ago). Anyways, with external power, I got it
proceeding but it failed in finding the kernel (the boot log is attached in
the email, if you are interested).
I tried to proceed by mounting the SD on my Ubuntu, but the filesystem was
corrupt for my Linux box to read. So I stopped this endeavor.
I was happy at least the u-boot is working and I worked the wiki,
https://eewiki.net/display/linuxonarm/BeagleBone for reformatting partition
1, kernel, root file system, uEnv.txt, modules, and dts. i.e. all but
u-boot part and partitioning the card. It has booted successfully.
I have minor problem in power though. It doesn't power-up by plugging the
5V but I have to plug the USB and immediately after I plug the 5V, this way
it works. It's a little inconvenient but at least it works!
Thanks all!
-Hesham
On Tue, Jun 28, 2016 at 9:55 AM, William Hermans <[email protected]> wrote:
> BY the way, the latest console image for me, with Nodejs 4.6.2 and npm
> 3.10 only weights in at around 400M total. I'd expect before Nodejs sme
> where aroudn 280M maybe slightly less. I didn't check . . .
>
> On Tue, Jun 28, 2016 at 6:53 AM, William Hermans <[email protected]>
> wrote:
>
>> 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 <[email protected]>
>> 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 <[email protected]>
>>>> 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 <[email protected]>
>>>>> 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 <[email protected]>
>>>>>> 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 <[email protected]
>>>>>>>> > 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 <[email protected]>
>>>>>>>>> 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
>>>>>>>>>>> [email protected]
>>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> 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/de6efcfc-ecf7-4b51-ab36-8204e79e469e%40googlegroups.com
>>>>>>>>>> <https://groups.google.com/d/msgid/beagleboard/de6efcfc-ecf7-4b51-ab36-8204e79e469e%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>>>>>> .
>>>>>>>>>>
>>>>>>>>>> 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/1fd2c068-bf70-4119-8cb9-5ea330306109%40googlegroups.com
>>>>>>> <https://groups.google.com/d/msgid/beagleboard/1fd2c068-bf70-4119-8cb9-5ea330306109%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>>> .
>>>>>>>
>>>>>>> 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/160f0683-5f0d-4f7f-859e-f9cc23950f87%40googlegroups.com
>>> <https://groups.google.com/d/msgid/beagleboard/160f0683-5f0d-4f7f-859e-f9cc23950f87%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>> 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
> [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CALHSORp7-Rs2-eWdc2NFyaWKDUHR0WapMnCawB9HS3Oy8P7F%2BQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/beagleboard/CALHSORp7-Rs2-eWdc2NFyaWKDUHR0WapMnCawB9HS3Oy8P7F%2BQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> 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/CA%2BfECkUt6r2Eu4NoRiVe1w%2Bcyo_GkWnuKu4azpG1TxX%2B%2BkOY7Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
U-Boot SPL 2016.03-00001-g148e520 (Jun 06 2016 - 11:27:44)
Trying to boot from MMC
bad magic
U-Boot 2016.03-00001-g148e520 (Jun 06 2016 - 11:27:44 -0500), Build: jenkins-gi5
Watchdog enabled
I2C: ready
DRAM: 256 MiB
Reset Source: Global external warm reset has occurred.
Reset Source: Power-on reset has occurred.
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment
Net: <ethaddr> not set. Validating first E-fuse MAC
cpsw, usb_ether
Press SPACE to abort autoboot in 2 seconds
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
gpio: pin 53 (gpio 53) value is 1
switch to partitions #0, OK
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt ...
1179 bytes read in 11 ms (104.5 KiB/s)
gpio: pin 55 (gpio 55) value is 1
Loaded environment from uEnv.txt
Importing environment from mmc ...
Checking if uenvcmd is set ...
gpio: pin 56 (gpio 56) value is 1
Running uenvcmd ...
4096 bytes read in 53 ms (75.2 KiB/s)
debug: [/boot/vmlinuz-] ...
** File not found /boot/vmlinuz- **
debug: [/boot/initrd.img-] ...
** File not found /boot/initrd.img- **
debug: [/boot/dtbs//am335x-bone.dtb] ...
** File not found /boot/dtbs//am335x-bone.dtb **
debug: [console=tty0 console=ttyO0,115200n8 root=/dev/mmcblk0p1 rootfstype=ext4.
debug: [bootz 0x82000000 0x88080000:1000 0x88000000] ...
Bad Linux ARM zImage magic!
Checking if client_ip is set ...
Checking for: /boot.scr ...
Checking for: /boot/boot.scr ...
Checking for: /boot/uEnv.txt ...
gpio: pin 55 (gpio 55) value is 1
4096 bytes read in 54 ms (73.2 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt...
** Invalid partition 2 **
** Invalid partition 3 **
** Invalid partition 4 **
** Invalid partition 5 **
** Invalid partition 6 **
** Invalid partition 7 **
Card did not respond to voltage select!
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
gpio: pin 53 (gpio 53) value is 1
Card did not respond to voltage select!
gpio: pin 54 (gpio 54) value is 1
Card did not respond to voltage select!
** Bad device mmc 1 **
Checking for: /uEnv.txt ...
Card did not respond to voltage select!
** Bad device mmc 1 **
Checking for: /boot.scr ...
Card did not respond to voltage select!
** Bad device mmc 1 **
Checking for: /boot/boot.scr ...
Card did not respond to voltage select!
** Bad device mmc 1 **
Checking for: /boot/uEnv.txt ...
Card did not respond to voltage select!
** Bad device mmc 1 **
Card did not respond to voltage select!
** Bad device mmc 1 **
Card did not respond to voltage select!
** Bad device mmc 1 **
Card did not respond to voltage select!
** Bad device mmc 1 **
Card did not respond to voltage select!
** Bad device mmc 1 **
Card did not respond to voltage select!
** Bad device mmc 1 **
Card did not respond to voltage select!
** Bad device mmc 1 **
## Error: "bootcmd_nand0" not defined
cpsw Waiting for PHY auto negotiation to complete......... TIMEOUT !
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
BOOTP broadcast 6
BOOTP broadcast 7
BOOTP broadcast 8
BOOTP broadcast 9
BOOTP broadcast 10
BOOTP broadcast 11
BOOTP broadcast 12
BOOTP broadcast 13
BOOTP broadcast 14
BOOTP broadcast 15
BOOTP broadcast 16
BOOTP broadcast 17
BOOTP broadcast 18
BOOTP broadcast 19
BOOTP broadcast 20
BOOTP broadcast 21
BOOTP broadcast 22
BOOTP broadcast 23
BOOTP broadcast 24
BOOTP broadcast 25
BOOTP broadcast 26
BOOTP broadcast 27
BOOTP broadcast 28
BOOTP broadcast 29
Retry time exceeded; starting again
missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/01-00-18-31-90-0a-03
cpsw Waiting for PHY auto negotiation to complete......... TIMEOUT !
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/00000000
cpsw Waiting for PHY auto negotiation to complete......... TIMEOUT !
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/0000000
cpsw Waiting for PHY auto negotiation to complete......... TIMEOUT !
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/000000
cpsw Waiting for PHY auto negotiation to complete......... TIMEOUT !
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/00000
cpsw Waiting for PHY auto negotiation to complete......... TIMEOUT !
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/0000
cpsw Waiting for PHY auto negotiation to complete.
