DINK32 R13.1 on Sandpoint X2

[Milliorn Gary-rxcr80]

  You cannot 'ping' DINK as the stack is not persistent.
It is only usable when networking tasks are being
performed.  You might be able to ping it while doing a
tftp, but I wouldn't count on it.

  Use Linux if you want ping working.

Regards,
Gary Milliorn


> -----Original Message-----
> From: Yuxiao Xi [mailto:xiyuxiao at harbournetworks.com]
> Sent: Friday, September 05, 2003 12:07 AM
> To: Mark A. Greer
> Cc: linuxppc-embedded at lists.linuxppc.org
> Subject: Re: DINK32 R13.1 on Sandpoint X2
>
>
>
> hi,
>     I succeed in downloading my linux kernel image using DINK32 r13.1
> tftp function to my Sandpoint X2 board. Before I used ftp
> servers which
> need user name and password and I could not download anything.Today I
> use Cisco ftp server which needs nothing and I succeed.
>
>     But there are another question yet: when I use command 'ping', to
> ping my target from the host,I get info:destination address
> unreachable
> to ping my host from the target??It's OK why?
>
> >We have an 8139 and have successfully downloaded and run a
> kernel with
> >DINK version 13.1.1.  I didn't do it but the instructions
> sent from the
> >person who did are:
> >
> >    To download via the network, DINK uses fixed IP
> >    address and Realtek8139 NIC. The steps are:
> >
> >    1. do "ppr" verify NIC card has been identified
> vendor/device ID as
> >    10EC/8139
> >    2. do "env IO=COM1:9600 at 100, Then "reset".
> >    3. do "ni -i " to set up your network parameters.  For example:
> >
> >     DINK32[MPC7457] {1} >>ni
> >     NETWORK INFORMATION
> >       PCI CARD
> >         Type 8139/10EC on slot 16
> >
> >       SETTINGS
> >         SERVER(TFTP) : 192.168.  1.  1
> >         GATEWAY      : 192.168.  1.  1
> >         NETMASK      : 255.255.255.  0
> >         DHCP         : 192.168.  1.  1
> >         CLIENT(DINK) : 192.168.  1.  7
> >
> >       DHCP: Disabled
> >       SESSION TIMEOUT: Never
> >
> >    4. set up you tftp server at host side
> >    5. The download command is "dl -nw -b -o800000
> -fzImage.sandpoint"
> >    6. "go 810000"
> >
> >You can change IP addr, image name, to fit your setup.
> >
> >As far as differences in the X2 vs. X3, yes there are important
> >differences.  Does DINK v13.1.1 run successfully & download via the
> >network successfully on an X2?  I don't know, you'll have to
> figure that
> >out for yourself or talk to Motorola.
> >
> >>     From the mailing lists,I know that someone use DINK32's tftp
> >>download function to download his image successfully on a
> Sandpoint X3
> >>board.Is there any important differences between Sandpoint X3 and X2
> >>board so that I can not use the DINK32's tftp function on X2 board?
> >>
> >>======= 2003-09-03 11:04:00 ?o=======
> >>
> >>>On Tue, Sep 02, 2003 at 05:22:08PM +0800, Yuxiao Xi wrote:
> >>>
> >>>>    Now I'm working on a Motorola Sandpoint X2 board with ppc8240.
> >>>>I use DINK32 r13.1 to boot my linux kernel image. From
> DINK32 r13.1
> >>>>user manual,I know that DINK32 r13.1 supports ethernet
> card Realtek
> >>>>8139,but after these steps:
> >>>>
> >>>What I would suggest is that instead of using the ethernet card
> >>>support, you use the serial support still. DINK32 r13.0.0 and newer
> >>>support 115200 baud, so loading a kernel via serial is now
> much less
> >>>painful than it used to be.
>
> = = = = = = = = = = = = = = = = = = = =
>
> !!!!!!!!!!!!!!!!Yuxiao Xi
> !!!!!!!!!!!!!!!!xiyuxiao at harbournetworks.com
> !!!!!!!!!!!!!!!!!!!!2003-09-05
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Gary Milliorn (E-mail).vcf
Type: application/octet-stream
Size: 457 bytes
Desc: not available
Url : http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20030905/a678cd64/attachment.obj