2106 | ADC | ARM7 | Atmel | Bootloader | CAN | CrossStudio | CrossWorks | DDS | ECos | Ethernet | ETM | FIFO | FLASH | FPGA | GCC | GDB | GNU | GNUARM | GPIO | I2C | IAP | IAR | JTAG | Kickstart | LCD | Linux | LPC | LPC-E2294 | LPC2000 | LPC2100 | LPC2104 | Lpc2106 | Lpc210x | LPC2114 | LPC2119 | LPC2124 | LPC2129 | Lpc2138 | LPC213x | LPC21xx | LPC2210 | LPC2212 | LPC2214 | LPC2292 | LPC2294 | LPC2xxx | LPC3128 | MCB2100 | Olimex | Philips | PWM | Rowley | RTC | RTOS | SPI | SSP | UART | UART0 | UART1 | ULINK | USB | Watchdog | Wiggler

Has anybody managed to get the Olimex LPC-E2294 or E2214 to
communicate
across the ethernet?
If so was it a nightmare, are there any special tricks?

I need to find out soon if I am flogging a dead horse!

Would a ethernet/serial converter and the H2294 be a better - cheaper
option?

Any help. or reply would be welcome.





(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

Olimex messed up and connected the circuit wrong! You can use Ethernet
chip in 8-bit mode only. (16-bit will NOT work)
Try to read the chip ID and once you can do that, download the uIP
example from rowley website. You need to make changes on CS8900.c file
and you are ready to communicate!

Gus
--- In lpc2000@lpc2..., "pick2light" <mick.taylor@v...> wrote:
>
> Has anybody managed to get the Olimex LPC-E2294 or E2214 to
> communicate
> across the ethernet?
> If so was it a nightmare, are there any special tricks?
>
> I need to find out soon if I am flogging a dead horse!
>
> Would a ethernet/serial converter and the H2294 be a better -
cheaper
> option?
>
> Any help. or reply would be welcome.





(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )