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

[Frank Wille <frank%phoenix.owl.de@localhost>]

On Sun, 8 May 2011 20:57:24 +0200
Oscar Molin <oscarmolin%gmail.com@localhost> wrote:

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

Ok. So your chip looks exactly like mine to the driver.


> xmit failed

Too bad. But I didn't have much hope.


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

It never turns on? That's suspiscious!

At the latest it should turn on when the auto-negotiation takes place.
How does it know that it has a 100MBit link, without the link being
active?

I ran the initialization phase step by step on my 101g+ and the link-LED
on the switch should light up shortly before the MAC address is printed
(mii_initphy).

Then it does auto-negotiation (mii_dealan). The LED goes dark and lights
up again after one second. Then the link-speed is printed.

The only critical point here is that the GPHY reset depends on the
phyisical medium, and I have hard-coded copper instead of fiber.

So I made a new altboot_sk.bin test program (same location to download)
which prints the PMD (physical medium) register.

I'm also waiting for a character twice, to make it easier to observe
for you. Example from my NAS:

>> NetBSD/sandpoint altboot, revision 1.7 (Mon May  9 18:22:07 CEST 2011)
>> Synology DS, cpu 265 MHz, bus 132 MHz, 64MB SDRAM
mii_initphy pmd=0x54                  (1)<waiting for a char>
MAC address 00:11:32:00:59:75
mii_dealan                            (2)<waiting for a char>
100Mbps-FDX

When you hit a key at (1) the link LED should light up. After hitting a
key at (2) it should again turn off, then on. Then "100Mbps-FDX" appears.

When pmd is not 0x54 for you we have found a possible problem.


> my chip says 88E8001-LKJ1, in case that does any difference,

Indeed that seems to be the most common version. All screen shots from
Synology boards on the net show LKJ1 as well.

But mine is just "LKJ"! I hope it doesn't mean that all the other
boards won't work with my driver... ;)


> How do you debug the code?

By inserting printf() at interesting points. Additionally you can use
delay() and getchar() to delay or pause program execution.


> Is there any debug interface available on the board?

There is a JTAG interface. But I never had much luck with those.


> I'd like to compare your SK init code with the one in sk98 that
> synology uses if I get the time.

Great! Any help is much appreciated!

The altboot SKnet driver source we are talking about it at:
  src/sys/arch/sandpoint/stand/altboot/skg.c

In case you decide to set up a compilation machine, just contact me
privately if you have any problems. But it's really simple:
- install NetBSD on any hardware of your choice
- check out the current source with the anonymous cvs account
- build a cross compiler: build.sh -m sandpoint tools
- Compile altboot with nbmake-sandpoint

-- 
Frank Wille