Re: Beaglebone broken

[Shoichi Miyake <shoichi.miyake%gmail.com@localhost>]

Hi, ONODERA san, thank you for your reply!

My platform is classic arm, built with build.sh -m evbarm, and I'm not
familiar with
earm platform yet, sorry.
(where should I check to learn about earm platform ?)

And I found differences with your situation by seeing your log,
you actually reach to invoke init, but I cannot see any kernel boot
messages at all.
It seems to be a little different.
I'm going to update source and build new kernel both evbarm and
evbearm this weekend.

Best regards,
Shoichi Miyake


2013/10/16 Ryo ONODERA <ryo_on%yk.rim.or.jp@localhost>:
> Hi,
>
> From: Shoichi Miyake <shoichi.miyake%gmail.com@localhost>, Date: Sun, 13 Oct 
> 2013 18:26:44 +0900
>
>> Hi,
>>
>> I've been using DREAMPLUG with SHEEVAPLUG config file
>> of 6.99.19 fine until today.
>> But I updated to 6.99.24 today, built and tried new netbsd.ub and
>> failed to boot.
>>
>> I found your problem on list that is similar to my case,
>> but you seem to have solved, ..sigh.
>>
>> Does anybody have the similar problem with SHEEVAPLUG or DREAMPLUG ?
>
> My kirkwood NAS with MARVELL_NAS evbearm kernel config does not boot for me.
> See http://gnats.netbsd.org/48130 .
> Your platform is earm or classic arm?
>
> I have no time to test recent evbearm/evbarm kernel on my kirkwood NAS now.
>
>> Best regards,
>> Shoichi Miyake
>>
>> -------
>> U-Boot 2011.06 (Oct 15 2011 - 02:02:08)
>> Marvell-DreamPlug
>>
>> SoC:   Kirkwood 88F6281_A0
>> DRAM:  512 MiB
>> SF: Detected MX25L1606 with page size 256, total 1 MiB
>> In:    serial
>> Out:   serial
>> Err:   serial
>> Net:   egiga0, egiga1
>> 88E1121 Initialized on egiga0
>> 88E1121 Initialized on egiga1
>> Hit any key to stop autoboot:  0
>> iniializing usb bus
>> (Re)start USB...
>> USB:   Register 10011 NbrPorts 1
>> USB EHCI 1.00
>> scanning bus for devices... 7 USB Device(s) found
>>        scanning bus for storage devices... Device NOT ready
>>    Request Sense returned 00 00 00
>> 3 Storage Device(s) found
>> try sdcard-ext
>> loading nb kernel
>> reading netbsd.ub
>>
>> 5182080 bytes read
>> ## Booting kernel from Legacy Image at 06400000 ...
>>    Image Name:   NetBSD/sheevaplug 6.99.24
>>    Created:      2013-10-13   6:00:31 UTC
>>    Image Type:   ARM NetBSD Kernel Image (uncompressed)
>>    Data Size:    5182016 Bytes = 4.9 MiB
>>    Load Address: 00008000
>>    Entry Point:  00008000
>>    Verifying Checksum ... OK
>>    Loading Kernel Image ... OK
>> OK
>> ## Transferring control to NetBSD stage-2 loader (at address 00008000) ...
>> -----
>>
>>
>>
>> 2013/10/8 John Klos <john%ziaspace.com@localhost>:
>>> Hi,
>>>
>>>
>>>>> I tried updating my Beaglebone and saw that not only do we have hardware
>>>>> floating point (yay!) but that we also have a Beaglebone disk image.
>>>>> However, while the bootloader works, the kernel never launches:
>>>
>>>
>>>> For what it's worth I just copied a kernel from a -current build done
>>>> about 18 hours ago onto mine and it booted just fine (the board was
>>>> running a September 2 kernel prior to that).  Whatever the problem is,
>>>> it isn't a general problem.
>>>
>>>
>>> I think the problem is me :) The names Beaglebone and Beagleboard are so
>>> similar that I didn't notice that the image I was using was called
>>> beagleboard.img.gz. Although I still don't know how
>>> netbsd-BEAGLEBONE_INSTALL.gz or netbsd-BEAGLEBONE_INSTALL.bin.gz are
>>> supposed to be used because neither is in .ub format (both give "Wrong Image
>>> Format for bootm command"), I was able to boot netbsd-BEAGLEBONE.ub.gz after
>>> ungzipping to the PC-DOS partition, then giving ld0a for the root on boot.
>>> The Beagleboard image with the Beaglebone kernel seems to work OK.
>>>
>>> Thanks,
>>> John
>
> --
> Ryo ONODERA // ryo_on%yk.rim.or.jp@localhost
> PGP fingerprint = 82A2 DC91 76E0 A10A 8ABB  FD1B F404 27FA C7D1 15F3