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

Hi,

I'm developing an application that have to transmit data between a PC
and a LPC2138 using the I2C interface. The PC interface is a U2C-11
I2C Bridge from Dimax. This device can only operate in master mode so
the PC has to control the communication completely. I have the
PC->LPC2138 part working and partly the LPC2138->PC part working.
The problem is when the PC asks for data from the LPC2138 and there
aren't any.

Are there any flags that allow the LPC2138 application to abort the
communication?
I've tried resetting the AA flag but the PC can't "reconnect" after
the first attempt.

Is it better to add a minor protocol that handles this problem?

Regards
Jens Alsig



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