Re: DS-207 network failure

[Julian Coleman <jdc%coris.org.uk@localhost>]

Hi,

> An alternative is to use "cp" to copy the binary image from 0x100000 to
> 0x1000000 after loading it.

This works perfectly:

  _MPC824X > bootp
  BOOTP broadcast 1
  BOOTP broadcast 2
  ARP broadcast 1
  TFTP from server 192.168.13.100; our IP address is 192.168.13.118
  Filename '/altboot.bin'.
  Load address: 0x100000
  Loading: ###############
  done
  Bytes transferred = 76364 (12a4c hex)
  _MPC824X > cp 0x100000 0x1000000 0x12a4c
  _MPC824X > loadb 2000000
  ize      = 0x0035d8c3 = 3528899 Bytes
  ## Start Addr      = 0x02000000
  _MPC824X > go 1000000 mem:2000000 debug
  ## Starting application at 0x01000000 ...

> BTW, did you ever try to run altboot directly after using PPCBoot's SK98
> driver? When it works this would mean we just forgot to initialize some
> register.

I also tried that after loading altboot via bootp.  No change.  However, I
guess that the reset that we do in skg_init() removes those settings.

I unpacked base.tgz and etc.tgz onto a CF card, and connected that via USB.
If I run tcpdump from there, it doesn't see any packets, so it's not just
sending that's broken.  As I mentioned before, the phy negotiates the link
speed correctly though.

So, it looks like hunting through the linux driver is needed.  I wonder
about dumping out the registers before we do a chip reset?

Thanks,

J

-- 
  My other computer also runs NetBSD    /        Sailing at Newbiggin
        http://www.netbsd.org/        /   http://www.newbigginsailingclub.org/