Driving a design via TCP/IP

> FreeRtos (freertos.org) + NXP LPC17xx.


Thanks Nico but this isn't much simpler than implementing an OS & TCP/IP
on a NIOS (I presume).


Nial. 

On 2010-10-07, Nial Stewart <nial*REMOVE_THIS*@nialstewartdevelopments.co.uk> wrote:
>> FreeRtos (freertos.org) + NXP LPC17xx.
>
>
> Thanks Nico but this isn't much simpler than implementing an OS & TCP/IP
> on a NIOS (I presume).

Yes it is.  It's way, way, way, simpler.

I've used a NIOS core.  There's nothing even remotely simple about it.
[And we never did get the OpenCores Ethernet MAC to work very well.]

-- 
Grant Edwards               grant.b.edwards        Yow! I'm thinking about
                                  at               DIGITAL READ-OUT systems
                              gmail.com            and computer-generated
                                                   IMAGE FORMATIONS ...

>> Thanks Nico but this isn't much simpler than implementing an OS & TCP/IP
>> on a NIOS (I presume).
>
> Yes it is.  It's way, way, way, simpler.
>
> I've used a NIOS core.  There's nothing even remotely simple about it.

I'm OK with setting the NIOS system up, it's integrating the OS and
TCP/IP stack I haven't got a clue about.


> [And we never did get the OpenCores Ethernet MAC to work very well.]

It looks like the Lantronix XPort or a Wiznet chip (if volumes are big
enough) is the easiest way for me to get this done.

Thanks all for your feedback.


Nial. 

On Oct 7, 3:26=A0pm, "Nial Stewart"
<nial*REMOVE_TH...@nialstewartdevelopments.co.uk> wrote:
> >> Thanks Nico but this isn't much simpler than implementing an OS & TCP/=
IP
> >> on a NIOS (I presume).
>
> > Yes it is. =A0It's way, way, way, simpler.
>
> > I've used a NIOS core. =A0There's nothing even remotely simple about it=
.
>
> I'm OK with setting the NIOS system up, it's integrating the OS and
> TCP/IP stack I haven't got a clue about.
>
> > [And we never did get the OpenCores Ethernet MAC to work very well.]
>
> It looks like the Lantronix XPort or a Wiznet chip (if volumes are big
> enough) is the easiest way for me to get this done.
>
> Thanks all for your feedback.
>
> Nial.

Hi Nial

I have been using Wiznet in a number of 'in production' designs for
the last 4 years. Currently the W5300 or module with the same would be
the best choice. I evaluated the other options but required > 50Mb/s
and ability to use only UDP (harsh industial heavy welding
environments along with real time data meant TCP retries would not be
desirable to say the least).
A few registers to set up (from the client side) and thereafter it's
akin to FTDI.
The Wiznet chip cost is in the same ball park as a separate PHY or MAC/
PHY in 100 to 1k volume. Can buy from Wiznet (watch out for the new
VAT customs rubbish) or from their UK disty (Hero?)

Regards

DG

> I have been using Wiznet in a number of 'in production' designs for
> the last 4 years. Currently the W5300 or module with the same would be
> the best choice. I evaluated the other options but required > 50Mb/s
> and ability to use only UDP (harsh industial heavy welding
> environments along with real time data meant TCP retries would not be
> desirable to say the least).
> A few registers to set up (from the client side) and thereafter it's
> akin to FTDI.


Thanks David, it's an industrial environment this is going into so this
is useful to know.



Nial.