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

Hello, I spent all weekend trying to get the ethernet to work on olimex LPC- E2294 board http://www.olimex.com/dev/lpc-e2294.html with no luck Looking at the board schematics, they have the Ethernet chip "selected" all the time through R57!!! This is WRONG!! I don't understand why!!! So I removed R57 and installed R56 instead. Now, when I read the chip, I always get the "chip ID" no matter what register I select! Was anyone able to read the registers from CS8900A? Any hints? Even with thier test code, I wasn't able to get things going. The plan is to get uIP going on that board http://www.sics.se/~adam/uip/ Thanks, Gus

Re: olimex LPC-E2294 with ethernet


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

Gus, I ported uIP to the E2124 and it works on that part, but that's in polled mode. I don't have a port of uIP for that board as I don't have the board. If you have any success with it, please let me know--I'd be interested to see what you make of the board as it's way over specified to run uIP, better would be lwIP. -- Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk CrossWorks for MSP430, ARM, AVR and (soon) MAXQ processors > -----Original Message----- > From: Gus [mailto:] > Sent: 07 February 2005 15:39 > To: > Subject: [lpc2000] olimex LPC-E2294 with ethernet > > Hello, > > I spent all weekend trying to get the ethernet to work on olimex LPC- > E2294 board http://www.olimex.com/dev/lpc-e2294.html with no luck > > Looking at the board schematics, they have the Ethernet chip > "selected" all the time through R57!!! This is WRONG!! I > don't understand why!!! So I removed R57 and installed R56 > instead. Now, when I read the chip, I always get the "chip > ID" no matter what register I select! > > Was anyone able to read the registers from CS8900A? Any > hints? Even with thier test code, I wasn't able to get things > going. The plan is to get uIP going on that board > http://www.sics.se/~adam/uip/ > > Thanks, > > Gus > > > Yahoo! Groups Links >

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

I sm actually starting out with your code. The major work here is that, in this case, the ethernat chip is connected to the external bus as 16-bit. So, I have to change your driver to use the external bus. It seems easy to me but I always read the "chip id" no matter what I do!!!! I think the write_register() code is not working in my case. The big goal is to run IwIP in the fututre or any full TCP/IP stack. Gus --- In , "Paul Curtis" <plc@r...> wrote: > Gus, > > I ported uIP to the E2124 and it works on that part, but that's in > polled mode. I don't have a port of uIP for that board as I don't have > the board. > > If you have any success with it, please let me know--I'd be interested > to see what you make of the board as it's way over specified to run uIP, > better would be lwIP. > > -- > Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk > CrossWorks for MSP430, ARM, AVR and (soon) MAXQ processors > > > -----Original Message----- > > From: Gus [mailto:gus_is_working@y...] > > Sent: 07 February 2005 15:39 > > To: > > Subject: [lpc2000] olimex LPC-E2294 with ethernet > > > > > > > > Hello, > > > > I spent all weekend trying to get the ethernet to work on olimex LPC- > > E2294 board http://www.olimex.com/dev/lpc-e2294.html with no luck > > > > Looking at the board schematics, they have the Ethernet chip > > "selected" all the time through R57!!! This is WRONG!! I > > don't understand why!!! So I removed R57 and installed R56 > > instead. Now, when I read the chip, I always get the "chip > > ID" no matter what register I select! > > > > Was anyone able to read the registers from CS8900A? Any > > hints? Even with thier test code, I wasn't able to get things > > going. The plan is to get uIP going on that board > > http://www.sics.se/~adam/uip/ > > > > Thanks, > > > > Gus > > > > > > > > > > > > > > > > Yahoo! Groups Links > > > > > > > > > > > > > > > > >

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

Gus, > > > I spent all weekend trying to get the ethernet to work on olimex > LPC- > > > E2294 board http://www.olimex.com/dev/lpc-e2294.html with no luck > > > > > > Looking at the board schematics, they have the Ethernet chip > > > "selected" all the time through R57!!! This is WRONG!! I don't > > > understand why!!! So I removed R57 and installed R56 > instead. Now, > > > when I read the chip, I always get the "chip ID" no matter what > > > register I select! For register reads, I believe that is really doesn't matter that the chip is always selected using /CHIPSEL as it will only present or latch data on an IOR or IOW strobe. However, I have not used the chip in its 16-bit mode; it looks like the registers are memory mapped to 0x0000'0300. Can you post a small piece of code that reads and writes the registers? -- Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk CrossWorks for MSP430, ARM, AVR and (soon) MAXQ processors

Re: olimex LPC-E2294 with ethernet


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

Paul, > chip is always selected using /CHIPSEL as it will only present or > latch data on an IOR or IOW strobe. Yes that is correct but we have FLASH and RAM on the bus!!! when RD is strobed for RAM read, the ethernet chip will access the data bus. I could be wrong somehow! I am trying to do it in 8-bit now, was 16!! I just want to get it to work for a starter. I am using the code posted on olimex website unsigned short cs8900a_read(unsigned addr) { unsigned short Data1,Data2; pAdd_CS = (unsigned char*)(CS8900A_BASE+addr); Data1 = *pAdd_CS; Data2 = ((*++pAdd_CS) << 8); return(Data1|Data2); // the folowing should work as well since we have 16 bit bus // return *((unsigned short *)(CS8900A_BASE+addr)); } void cs8900a_write(unsigned addr, unsigned int data) { pAdd_CS = (unsigned char*)(CS8900A_BASE+addr); *pAdd_CS = data; ++pAdd_CS; *pAdd_CS = data>>8; } void cs8900a_init(void) { int i; // I am using this since the folowing code will not work BCFG2=0x00003501; /* // CS8900A 8bit; BCFG2_bit.MW = 0; // IDCY = 1+1 ~ 33ns BCFG2_bit.IDCY=1; // WST1 = 8+3 (read) ~183ns BCFG2_bit.WST1=8; // WST2 = 6+1 (write) ~ 117ns BCFG2_bit.WST2=6; // RBLE = 1 - ako e 0 ne zapiswa BCFG2_bit.RBLE = 1; // WP =0, BM = 0 BCFG2_bit.WP = BCFG2_bit.BM = 0; //*/ // this code was not changed from the example // P3.25 - CS2 (CS8900A) // P3.0 - A0 PINSEL2 |= 0x00804000; //read chip id cs8900a_write(ADD_PORT,0); i = cs8900a_read(DATA_PORT); if (i != CRYSTAL_SEMI_ID) while(1); // read revesion cs8900a_write(ADD_PORT,0x2); i = cs8900a_read(0xC); // i will still be the "manufacture id" no matter what register I select Gus --- In , "Paul Curtis" <plc@r...> wrote: > Gus, > > > > > I spent all weekend trying to get the ethernet to work on olimex > > LPC- > > > > E2294 board http://www.olimex.com/dev/lpc-e2294.html with no luck > > > > > > > > Looking at the board schematics, they have the Ethernet chip > > > > "selected" all the time through R57!!! This is WRONG!! I don't > > > > understand why!!! So I removed R57 and installed R56 > > instead. Now, > > > > when I read the chip, I always get the "chip ID" no matter what > > > > register I select! > > For register reads, I believe that is really doesn't matter that the > chip is always selected using /CHIPSEL as it will only present or latch > data on an IOR or IOW strobe. However, I have not used the chip in its > 16-bit mode; it looks like the registers are memory mapped to > 0x0000'0300. > > Can you post a small piece of code that reads and writes the registers? > > -- > Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk > CrossWorks for MSP430, ARM, AVR and (soon) MAXQ processors

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

Gus, > > chip is always selected using /CHIPSEL as it will only present or > > latch data on an IOR or IOW strobe. > Yes that is correct but we have FLASH and RAM on the bus!!! > when RD is strobed for RAM read, the ethernet chip will > access the data bus. > I could be wrong somehow! IOR and IOW are gated using CS2 (look down by the copyright symbol) hence even though CHIPSEL is always selected, you won't get an IOR or IOW strobe unless CS2 is selected, I think--I'm not particularly good with this type of thing. > I am trying to do it in 8-bit now, was 16!! I just want to > get it to work for a starter. I am using the code posted on > olimex website > > unsigned short cs8900a_read(unsigned addr) { > unsigned short Data1,Data2; > pAdd_CS = (unsigned char*)(CS8900A_BASE+addr); > Data1 = *pAdd_CS; > Data2 = ((*++pAdd_CS) << 8); > return(Data1|Data2); > // the folowing should work as well since we have 16 bit > bus // return *((unsigned short *)(CS8900A_BASE+addr)); } > void cs8900a_write(unsigned addr, unsigned int data) { > pAdd_CS = (unsigned char*)(CS8900A_BASE+addr); > *pAdd_CS = data; > ++pAdd_CS; > *pAdd_CS = data>>8; > } This sort of looks OK modulo volatile. > void cs8900a_init(void) > { > int i; > // I am using this since the folowing code will not work > BCFG2=0x00003501; > /* > // CS8900A 8bit; > BCFG2_bit.MW = 0; > // IDCY = 1+1 ~ 33ns > BCFG2_bit.IDCY=1; > // WST1 = 8+3 (read) ~183ns > BCFG2_bit.WST1=8; > // WST2 = 6+1 (write) ~ 117ns > BCFG2_bit.WST2=6; > // RBLE = 1 - ako e 0 ne zapiswa > BCFG2_bit.RBLE = 1; > // WP =0, BM = 0 > BCFG2_bit.WP = BCFG2_bit.BM = 0; > //*/ > // this code was not changed from the example > // P3.25 - CS2 (CS8900A) > // P3.0 - A0 > PINSEL2 |= 0x00804000; > //read chip id > cs8900a_write(ADD_PORT,0); > i = cs8900a_read(DATA_PORT); > if (i != CRYSTAL_SEMI_ID) > while(1); > // read revesion > cs8900a_write(ADD_PORT,0x2); > i = cs8900a_read(0xC); > // i will still be the "manufacture id" no matter what > register I select Need to assume that the bitfield stuff workds of course. It seems you probably haven't written the address correctly in the first place and the address port defaults to zero. What's your cs8900a_write function like after you modified it? Also, have you reset the CS8900A and waited for it to come out of reset? // Reset the CS8900A cs8900a_write(ADD_PORT, PP_SelfCTL); cs8900a_write(DATA_PORT, POWER_ON_RESET); // Wait until chip-reset is done cs8900a_write(ADD_PORT, PP_SelfST); while ((cs8900a_read(DATA_PORT) & INIT_DONE) == 0) ; I don't know whether this makes any difference or not, or is the manufacturing data only available after a POR or somesuch? -- Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk CrossWorks for MSP430, ARM, AVR and (soon) MAXQ processors -- Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk CrossWorks for MSP430, ARM, AVR and (soon) MAXQ processors

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

Paul, > IOR and IOW are gated I didn't see that LOL!! But why olimex did that anyways? weard! >What's your cs8900a_write function I removed the changes and trying to use this one unmodefied void cs8900a_write(unsigned addr, unsigned int data) { pAdd_CS = (unsigned char*)(CS8900A_BASE+addr); *pAdd_CS = data; ++pAdd_CS; *pAdd_CS = data>>8; } Gus --- In , "Paul Curtis" <plc@r...> wrote: > Gus, > > > > chip is always selected using /CHIPSEL as it will only present or > > > latch data on an IOR or IOW strobe. > > > Yes that is correct but we have FLASH and RAM on the bus!!! > > when RD is strobed for RAM read, the ethernet chip will > > access the data bus. > > I could be wrong somehow! > > IOR and IOW are gated using CS2 (look down by the copyright symbol) > hence even though CHIPSEL is always selected, you won't get an IOR or > IOW strobe unless CS2 is selected, I think--I'm not particularly good > with this type of thing. > > > I am trying to do it in 8-bit now, was 16!! I just want to > > get it to work for a starter. I am using the code posted on > > olimex website > > > > unsigned short cs8900a_read(unsigned addr) { > > unsigned short Data1,Data2; > > pAdd_CS = (unsigned char*)(CS8900A_BASE+addr); > > Data1 = *pAdd_CS; > > Data2 = ((*++pAdd_CS) << 8); > > return(Data1|Data2); > > // the folowing should work as well since we have 16 bit > > bus // return *((unsigned short *)(CS8900A_BASE+addr)); } > > void cs8900a_write(unsigned addr, unsigned int data) { > > pAdd_CS = (unsigned char*)(CS8900A_BASE+addr); > > *pAdd_CS = data; > > ++pAdd_CS; > > *pAdd_CS = data>>8; > > } > > This sort of looks OK modulo volatile. > > > void cs8900a_init(void) > > { > > int i; > > // I am using this since the folowing code will not work > > BCFG2=0x00003501; > > /* > > // CS8900A 8bit; > > BCFG2_bit.MW = 0; > > // IDCY = 1+1 ~ 33ns > > BCFG2_bit.IDCY=1; > > // WST1 = 8+3 (read) ~183ns > > BCFG2_bit.WST1=8; > > // WST2 = 6+1 (write) ~ 117ns > > BCFG2_bit.WST2=6; > > // RBLE = 1 - ako e 0 ne zapiswa > > BCFG2_bit.RBLE = 1; > > // WP =0, BM = 0 > > BCFG2_bit.WP = BCFG2_bit.BM = 0; > > //*/ > > // this code was not changed from the example > > // P3.25 - CS2 (CS8900A) > > // P3.0 - A0 > > PINSEL2 |= 0x00804000; > > //read chip id > > cs8900a_write(ADD_PORT,0); > > i = cs8900a_read(DATA_PORT); > > if (i != CRYSTAL_SEMI_ID) > > while(1); > > // read revesion > > cs8900a_write(ADD_PORT,0x2); > > i = cs8900a_read(0xC); > > // i will still be the "manufacture id" no matter what > > register I select > > Need to assume that the bitfield stuff workds of course. It seems you > probably haven't written the address correctly in the first place and > the address port defaults to zero. What's your cs8900a_write function > like after you modified it? > > Also, have you reset the CS8900A and waited for it to come out of reset? > // Reset the CS8900A > cs8900a_write(ADD_PORT, PP_SelfCTL); > cs8900a_write(DATA_PORT, POWER_ON_RESET); > > // Wait until chip-reset is done > cs8900a_write(ADD_PORT, PP_SelfST); > while ((cs8900a_read(DATA_PORT) & INIT_DONE) == 0) > ; > > I don't know whether this makes any difference or not, or is the > manufacturing data only available after a POR or somesuch? > > -- > Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk > CrossWorks for MSP430, ARM, AVR and (soon) MAXQ processors > > -- > Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk > CrossWorks for MSP430, ARM, AVR and (soon) MAXQ processors

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

On 7 Feb 2005 at 15:38, Gus wrote: > > Hello, > > I spent all weekend trying to get the ethernet to work on olimex LPC- > E2294 board http://www.olimex.com/dev/lpc-e2294.html with no luck > > Looking at the board schematics, they have the Ethernet > chip "selected" all the time through R57!!! This is WRONG!! I don't > understand why!!! So I removed R57 and installed R56 instead. Now, > when I read the chip, I always get the "chip ID" no matter what > register I select! They qualify the IOR and IOW signals with CS2, hence one will only read from, write to the chip when CS2 is active. They probably could have achived the same by connecting CS2 to the CS8900 Chip select pin, and OE to IOR and WE to IOW. Regards Anton Erasmus -- A J Erasmus

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

Hi Gus, > > IOR and IOW are gated > I didn't see that LOL!! But why olimex did that anyways? weard! > > >What's your cs8900a_write function > I removed the changes and trying to use this one unmodefied > > void cs8900a_write(unsigned addr, unsigned int data) { > pAdd_CS = (unsigned char*)(CS8900A_BASE+addr); > *pAdd_CS = data; > ++pAdd_CS; > *pAdd_CS = data>>8; > } Looks fine; I guess the next step is to scope the waveforms arriving at the CS8900A. -- Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk CrossWorks for MSP430, ARM, AVR and (soon) MAXQ processors

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

I got it to work last night. The problem is that olimex board has the chip connected to 16-bit data bus but it will NOT work. It works in 8-bit mode only. What are the negative things about uIP? I used telnet and http last night and it worked fine! Gus --- In , "Paul Curtis" <plc@r...> wrote: > Hi Gus, > > > > IOR and IOW are gated > > I didn't see that LOL!! But why olimex did that anyways? weard! > > > > >What's your cs8900a_write function > > I removed the changes and trying to use this one unmodefied > > > > void cs8900a_write(unsigned addr, unsigned int data) { > > pAdd_CS = (unsigned char*)(CS8900A_BASE+addr); > > *pAdd_CS = data; > > ++pAdd_CS; > > *pAdd_CS = data>>8; > > } > > Looks fine; I guess the next step is to scope the waveforms arriving at > the CS8900A. > > -- > Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk > CrossWorks for MSP430, ARM, AVR and (soon) MAXQ processors

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

Gus, > I got it to work last night. The problem is that olimex board > has the chip connected to 16-bit data bus but it will NOT > work. It works in 8-bit mode only. > > What are the negative things about uIP? I used telnet and > http last night and it worked fine! The negative things? The fact you need to intertwine the application with the stack; no socket interface; only one packet in flight at any one time; not a "standard" programming interface; lacks many features such as DHCP client... And so on. -- Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk CrossWorks for MSP430, ARM, AVR and (soon) MAXQ processors

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

> I got it to work last night. The problem is that olimex board has > the chip connected to 16-bit data bus but it will NOT work. It works > in 8-bit mode only. AFAIK, the cs8900a starts in 8bit mode, and has to be switched to 16bit mode. But did read this only in a Phytec manual for the mpc565. -- 42Bastian Schick

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

As far as I understand, this is imposibble on the olimex board because of the SBHE# pin. If I am wrong, please correct me. why olimex is not responding to this post? Gus --- In , 42Bastian Schick <bastian42@m...> wrote: > > I got it to work last night. The problem is that olimex board has > > the chip connected to 16-bit data bus but it will NOT work. It works > > in 8-bit mode only. > > AFAIK, the cs8900a starts in 8bit mode, and has to be switched to 16bit > mode. > But did read this only in a Phytec manual for the mpc565. > -- > 42Bastian Schick

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

Gus, I fear you may be 100% correct. SBHE is held high, sigh. I think you're buggered for 16-bit mode, mate. Perhaps Olimex didn't test the Ethernet interface in 16 bit mode, only 8 bit mode. It might have been useful if one of the INTRQ lines was connected up too. You might want to take a look at http://www.thearmpatch.com/lpc-sbc2.html which has a CS8900A on it. We've just received one, courtesy of Bill Knight, and I'll take a look at it at some point, but I'm sure CrossWorks will sprout a BSP for it real soon. Regards, -- Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk CrossWorks for MSP430, ARM, AVR and (soon) MAXQ processors > -----Original Message----- > From: Gus [mailto:] > Sent: 08 February 2005 15:43 > To: > Subject: [lpc2000] Re: olimex LPC-E2294 with ethernet > > As far as I understand, this is imposibble on the olimex > board because of the SBHE# pin. > > If I am wrong, please correct me. > > why olimex is not responding to this post? > > Gus > > --- In , 42Bastian Schick <bastian42@m...> > wrote: > > > I got it to work last night. The problem is that olimex board has > > > the chip connected to 16-bit data bus but it will NOT work. It > works > > > in 8-bit mode only. > > > > AFAIK, the cs8900a starts in 8bit mode, and has to be switched to > 16bit > > mode. > > But did read this only in a Phytec manual for the mpc565. > > > > > > -- > > 42Bastian Schick > > Yahoo! Groups Links >

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

Gus, Checking the LPC-SBC2 and talking to Bill Knight confirms that this board is ready to rock when it comes to Ethernet in 16 bit mode (and interrupt driven even). Probably a better bet than the Olimex board; bit of a shame about the Olimex board, though. Rgds, -- Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk CrossWorks for MSP430, ARM, AVR and (soon) MAXQ processors > -----Original Message----- > From: Gus [mailto:] > Sent: 08 February 2005 15:43 > To: > Subject: [lpc2000] Re: olimex LPC-E2294 with ethernet > > As far as I understand, this is imposibble on the olimex > board because of the SBHE# pin. > > If I am wrong, please correct me. > > why olimex is not responding to this post? > > Gus > > --- In , 42Bastian Schick <bastian42@m...> > wrote: > > > I got it to work last night. The problem is that olimex board has > > > the chip connected to 16-bit data bus but it will NOT work. It > works > > > in 8-bit mode only. > > > > AFAIK, the cs8900a starts in 8bit mode, and has to be switched to > 16bit > > mode. > > But did read this only in a Phytec manual for the mpc565. > > > > > > -- > > 42Bastian Schick > > Yahoo! Groups Links >

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

> Hello, > > I spent all weekend trying to get the ethernet to work on olimex LPC- > E2294 board http://www.olimex.com/dev/lpc-e2294.html with no luck > > Looking at the board schematics, they have the Ethernet > chip "selected" all the time through R57!!! This is WRONG!! I don't > understand why!!! So I removed R57 and installed R56 instead. Now, > when I read the chip, I always get the "chip ID" no matter what > register I select! Hi Gus, Sorry for the late reply, but I have full time job also :) The CS8900A is connected correctly, so you don't have to swap R56 and R57, anyway it will work in both cases. In the current version CS8900A will work in 8-bit mode only and with polling (no interrupts). This is the way this boards was intend to work (our engineers decided to make it "compatible" to LPC-E212x) , the 16 bit data bus was wired by mistake ;) it doesn't make any problems though. I catched this issue on very late stage when 300 boards were alerady assembled. Our new OKI-E5003 which now is routing will have 16-bit mode and interrupts supported. Best regards Tsvetan --- PCB prototypes for $26 at http://run.to/pcb (http://www.olimex.com/pcb) PCB any volume assembly (http://www.olimex.com/pcb/protoa.html) Development boards for ARM, AVR, PIC, and MSP430 (http://www.olimex.com/dev)

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

> > They qualify the IOR and IOW signals with CS2, hence one will only read from, write > to the chip when CS2 is active. They probably could have achived the same by > connecting CS2 to the CS8900 Chip select pin, and OE to IOR and WE to IOW. not really, according to CS8900A datasheets CHIPSELECT is used only in Memory mode, in IO and DMA mode *should* be connected to ground. Best regards Tsvetan --- PCB prototypes for $26 at http://run.to/pcb (http://www.olimex.com/pcb) PCB any volume assembly (http://www.olimex.com/pcb/protoa.html) Development boards for ARM, AVR, PIC, and MSP430 (http://www.olimex.com/dev)

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