Re: DS207 fails to auto boot (Bad Magic Number)

--e89a8f50356296386404eebf979d
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

2013/12/30 Frank Wille <[email protected]>

> On Sat, 28 Dec 2013 22:06:43 +0100
> Nick =D8stergaard <[email protected]> wrote:
>
> > I have a DS207, which I decided to install netbsd on.
>
> The DS207 is listed as being successfully tested, although not by me.
> So I hope this is correct. :)
>
> Indeed it works now, though with a bit modified approach than described i=
n
the wiki. Basically the commands described in theis mail, and using the
.img instead of .bin as you pointed out.

>
> > The difference in this and the wiki is that I use tftpload for the
> > netbsd-INSTALL file also, rather than using go 1000000
> > tftp:netbsd-INSTALL, which did not work at all.
>
> Can you provide some more information about the problem?
>
> Did altboot detect and initialize your network interface? There should
> be a Marvell 88E8001 on the board, using the sk(4) driver.
>
> Otherwise altboot would print: "no NET device driver was found".
>
> Or were there any problems with DHCP? Altboot tries to retrieve the
> client and server IP address. Maybe the MAC address did not match?
> Check the log file of your DHCP server.
>
> The network seems to work fine on my network (tftpload works) even with
1000Mbps-FDX here illustrated with a 100Mbps switch (works the same
without).

_MPC824X > go 1000000 tftp:netbsd-INSTALL

## Starting application at 0x01000000 ...

>> NetBSD/sandpoint altboot, revision 1.9
>> Synology DS, cpu 265 MHz, bus 132 MHz, 64MB SDRAM
port 0 present
wd0: <Corsair CSSD-F60GB2> DMA LBA LBA48 57241 MB
wd0: no disklabel
MAC address 00:11:32:03:52:af
100Mbps-FDX
Hit any key to enter interactive mode: 2
Hit any key to enter interactive mode: 1
Hit any key to enter interactive mode: 0

timeout
timeout
timeout
timeout
load failed. Restarting...

>
> > _MPC824X > protect off ffc00000 ffc1ffff
> > Un-Protected 2 sectors
>
> Did you check whether ffc00000 is really the correct address for the
> boot image? Type "printenv" in PPCBoot and look for the line starting
> with "bootcmd=3D".
>
> Yes, the address is correct, printenv tells me:
bootcmd=3Dbootm FFC00000 FFE00000

>
> > But it does not auto boot, I get the following boot message.
> >
> > [...]
> > Press Ctrl+C to abort autoboot in 1 second
> > ## Booting image at ffc00000 ...
>
> Ok. This message tells us at least that ffc00000 was correct. ;)
>
>
> > Bad Magic Number
> > _MPC824X >
> >
> > I have no idea where to go from here. Any help to getting the autoboot
> > work will be appreciated.
>
> The 2007 PPCBoot firmware usually has something like
>   bootcmd=3Dbootm FFC00000 FFE00000
> stored in the environment.
>
> "bootm" means that it wants to boot an UBoot-image, so you cannot simply
> copy a raw binary there. The UBoot image has a header, which is the
> reason that it prints "Bad Magic Number", because the header is missing.
>
> To make it short: You have to use altboot.img instead of altboot.bin. :)
>
> --
> Frank Wille
>
Ahh, YES, that was my mistake. i completely forgot the thing about the
different altboot files. So merely the only thing I did differnet than from
the wiki was to do:
tftpload 2000000 netbsd-INSTALL
go 1000000 mem:2000000 debug

Instead of:
go 1000000 tftp:netbsd-INSTALL

And of course us the .img altboot version, _as explained_ in the wiki, to
make it automatically boot. "Load altboot.img into memory, for example at
0x1000000 again [...]"

Thank you.

[wiki]: http://www.netbsd.org/ports/sandpoint/instSynology.html

--e89a8f50356296386404eebf979d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">2013=
/12/30 Frank Wille <span dir=3D"ltr">&lt;<a href=3D"mailto:[email protected]=
l.de" target=3D"_blank">[email protected]</a>&gt;</span><br><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex">

<div class=3D"im">On Sat, 28 Dec 2013 22:06:43 +0100<br>
Nick =D8stergaard &lt;<a href=3D"mailto:[email protected]">[email protected]=
m</a>&gt; wrote:<br>
<br>
&gt; I have a DS207, which I decided to install netbsd on.<br>
<br>
</div>The DS207 is listed as being successfully tested, although not by me.=
<br>
So I hope this is correct. :)<br>
<div class=3D"im"><br></div></blockquote><div>Indeed it works now, though w=
ith a bit modified approach than described in the wiki. Basically the comma=
nds described in theis mail, and using the .img instead of .bin as you poin=
ted out.<br>

</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex"><div class=3D"im">
<br>
&gt; The difference in this and the wiki is that I use tftpload for the<br>
&gt; netbsd-INSTALL file also, rather than using go 1000000<br>
&gt; tftp:netbsd-INSTALL, which did not work at all.<br>
<br>
</div>Can you provide some more information about the problem?<br>
<br>
Did altboot detect and initialize your network interface? There should<br>
be a Marvell 88E8001 on the board, using the sk(4) driver.<br>
<br>
Otherwise altboot would print: &quot;no NET device driver was found&quot;.<=
br>
<br>
Or were there any problems with DHCP? Altboot tries to retrieve the<br>
client and server IP address. Maybe the MAC address did not match?<br>
Check the log file of your DHCP server.<br>
<div class=3D"im"><br></div></blockquote><div>The network seems to work fin=
e on my network (tftpload works) even with 1000Mbps-FDX here illustrated wi=
th a 100Mbps switch (works the same without).<br><br>_MPC824X &gt; go 10000=
00 tftp:netbsd-INSTALL<br>

<br>## Starting application at 0x01000000 ...<br><br>&gt;&gt; NetBSD/sandpo=
int altboot, revision 1.9<br>&gt;&gt; Synology DS, cpu 265 MHz, bus 132 MHz=
, 64MB SDRAM<br>port 0 present<br>wd0: &lt;Corsair CSSD-F60GB2&gt; DMA LBA =
LBA48 57241 MB<br>

wd0: no disklabel<br>MAC address 00:11:32:03:52:af<br>100Mbps-FDX<br>Hit an=
y key to enter interactive mode: 2<br>Hit any key to enter interactive mode=
: 1<br>Hit any key to enter interactive mode: 0<br><br>timeout<br>timeout<b=
r>

timeout<br>timeout<br>load failed. Restarting...<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div class=3D"im">
<br>
&gt; _MPC824X &gt; protect off ffc00000 ffc1ffff<br>
&gt; Un-Protected 2 sectors<br>
<br>
</div>Did you check whether ffc00000 is really the correct address for the<=
br>
boot image? Type &quot;printenv&quot; in PPCBoot and look for the line star=
ting<br>
with &quot;bootcmd=3D&quot;.<br>
<div class=3D"im"><br></div></blockquote><div>Yes, the address is correct, =
printenv tells me:<br>bootcmd=3Dbootm FFC00000 FFE00000 <br></div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex">

<div class=3D"im">
<br>
&gt; But it does not auto boot, I get the following boot message.<br>
&gt;<br>
&gt; [...]<br>
&gt; Press Ctrl+C to abort autoboot in 1 second<br>
&gt; ## Booting image at ffc00000 ...<br>
<br>
</div>Ok. This message tells us at least that ffc00000 was correct. ;)<br>
<div class=3D"im"><br>
<br>
&gt; Bad Magic Number<br>
&gt; _MPC824X &gt;<br>
&gt;<br>
&gt; I have no idea where to go from here. Any help to getting the autoboot=
<br>
&gt; work will be appreciated.<br>
<br>
</div>The 2007 PPCBoot firmware usually has something like<br>
=A0 bootcmd=3Dbootm FFC00000 FFE00000<br>
stored in the environment.<br>
<br>
&quot;bootm&quot; means that it wants to boot an UBoot-image, so you cannot=
 simply<br>
copy a raw binary there. The UBoot image has a header, which is the<br>
reason that it prints &quot;Bad Magic Number&quot;, because the header is m=
issing.<br>
<br>
To make it short: You have to use altboot.img instead of altboot.bin. :)<br=
>
<span class=3D""><font color=3D"#888888"><br>
--<br>
Frank Wille<br>
</font></span></blockquote></div>Ahh, YES, that was my mistake. i completel=
y forgot the thing about the different altboot files. So merely the only th=
ing I did differnet than from the wiki was to do:<br>tftpload 2000000 netbs=
d-INSTALL<br>

go 1000000 mem:2000000 debug<br><br>Instead of:<br>go 1000000 tftp:netbsd-I=
NSTALL<br><br>And of course us the .img altboot version, _as explained_ in =
the wiki, to make it automatically boot. &quot;Load altboot.img into memory=
, for example at 0x1000000 again [...]&quot;<br>

<br>Thank you.<br><br>[wiki]: <a href=3D"http://www.netbsd.org/ports/sandpo=
int/instSynology.html">http://www.netbsd.org/ports/sandpoint/instSynology.h=
tml</a><br></div></div>

--e89a8f50356296386404eebf979d--