Re: Synology CS 407e: altboot fails to load installer.

[Oscar Molin <oscarmolin%gmail.com@localhost>]

I tried both the snapshot and the debug version and they both gave the
same result, the output was from the debug version then I guess.

I just tried your test version, it gives the same output you predicted:

_MPC824X > go 1000000 tftp:netbsd-INSTALL
## Starting application at 0x01000000 ...

>> NetBSD/sandpoint altboot, revision 1.7 (Sun May  8 18:46:50 CEST 2011)
>> Synology DS, cpu 265 MHz, bus 132 MHz, 64MB SDRAM

config=93 chipver=b1  <<-- same values

MAC address 00:11:xx:xx:xx:xx
100Mbps-FDX
Hit any key to enter interactive mode: 0
xmit failed
xmit failed
xmit failed
xmit failed
bootp: no reply
"" not found
load failed. Restarting...


still nothing from wireshark and the network link light never turns on
in my switch either, when altboot is running.

my chip says 88E8001-LKJ1, in case that does any difference, I
couldn't find any detailed data on this chip, since it seems to be
pretty old.

How do you debug the code? Is there any debug interface available on the board?
I'd like to compare your SK init code with the one in sk98 that
synology uses if I get the time.
I'm having my last exam in a few weeks, then I might have some time to spare.

Thanks for your help

/Oscar


2011/5/8 Frank Wille <frank%phoenix.owl.de@localhost>:
> On Sun, 8 May 2011 16:42:14 +0200
> Oscar Molin <oscarmolin%gmail.com@localhost> wrote:
>
>> _MPC824X > go 1000000 debug
>> ## Starting application at 0x01000000 ...
>
> The "debug" option is only recognized by the NetBSD kernel. Altboot has
> to be recompiled to include debugging output (see below).
>
>
>> >> NetBSD/sandpoint altboot, revision 1.7 (Tue Apr 19 09:38:13 CEST 2011)
>> >> Synology DS, cpu 265 MHz, bus 132 MHz, 64MB SDRAM
>> [...]
>
> You are using the debug version from /pub/NetBSD/misc/phx/sandpoint,
> not 201105062100Z. That shouldn't make any difference for SKnet, but
> it fortunately allows me to compare it with my DS-101g+.
>
> The only difference I have seen is that the CS-407e got an additional
> Satalink device at 12. The rest is completely identical, including the
> PCI device revisions.
>
>
>> MAC address 00:11:xx:xx:xx:xx
>> PHY 0 (0141.0c25)
>> 100Mbps-FDX
>
> And you also have the same PHY and connect with the same media.
> That's frustrating, as there is no obvious reason why it shouldn't work
> for you.
>
> Our SKnet chip is a Yukon-Lite. It has a config and chiprev register
> which could be different, so I added a line to altboot which prints
> something like:
>
> config=93 chipver=b1
>
> I would hope your output is not the same. Otherwise I'm running out of
> ideas.
>
> Additionally I reworked the PHY-reset code and extended the transmit
> timeout.
>
> I have compiled a test version for you which you can download at
>  ftp://ftp.netbsd.org/pub/NetBSD/misc/phx/sandpoint/altboot_sk.bin.gz
>
>
>> This xmit failed message I assume is a message from net driver,
>> hopefully from the sk98 driver or whatever you have in altboot for sk.
>
> Yes, it is. I wrote a minimal SKnet driver for altboot last year, based on
> the kernel's sys/dev/pci/if_sk.c code, as there is no public documentation
> available for this chip.
>
> It happens in skg_send() of sys/arch/sandpoint/stand/altboot/skg.c.
>
>
>> I guess the "xmit failed" is a failed transmission, possibly of the
>> first dhcp request message?
>
> I would bet it already happens with the first frame to be transmitted
> (which could indeed be the DHCP request). Your driver doesn't send a
> single byte.
>
>
> --
> Frank Wille
>