Sign in
Search piclist
Subscribe to piclist
piclist by Keywords
12F675 | 16F628 | 16F84 | 16f877 | 16F877A | 16F88 | 18F458 | ADC | AVR | Bootloader | CAN | CCS | CRC | EAGLE | EEPROM | ICD | ICSP | IDE | JDM | LED | Macros | Microchip | MPLAB | PCB-CAD | PIC10F | Pic12f675 | PIC16F84 | PIC16F84A | PIC16F877 | PIC18 | PIC18F452 | PicBasic | PICC | PICSTART | PWM | RS-485 | RS232 | SMT | SPI | UART | USART | USB | Wireless | Wisp628 | Xilinx
Ads
Discussion Groups
See Also
Discussion Groups | Piclist | Can I share an external EEPROM
A discussion group for the PICMicro microcontroller. Also called the Microchip PIC, this list is dedicated to the use and abuse of this fine, simple, microcontroller. Close to topic posts are welcome, ie. general electronics.
Can I share an external EEPROM - Floyd Sense - May 1 18:14:58 2009
I have an existing PIC based application and need to add RS232 communications to a PC.
Due to timing constraints and other factors, I can't add that code to the existing PIC and
intend to do the RS232 work with an additional and separate PIC. What I need is a way to
occasionally pass information between the two. I've never used an external EEPROM chip
and wonder if there's a way to share access to one EEPROM chip from two different PIC
processors?
------------------------------------
to unsubscribe, go to http://www.yahoogroups.com and follow the instructions
(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )
------------------------------------
to unsubscribe, go to http://www.yahoogroups.com and follow the instructions
(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )
Re: Can I share an external EEPROM - demolitron - May 4 18:46:00 2009
I don't see why not. The mechanics depend on the EEPROM's interface. If it is I2C then
it should be easier because it can handle a multiple master topology out of the box. If
it is SPI then you would have weak pull-ups on the lines and both MCU's would go high
impedance when not accessing the device. Then when you want to access the EEPROM just
check the CS line, be sure its low, then switch the ports to output mode and talk. Set
back to inputs when done to release control.
I think the hard part will be in the software to handle collisions on the buss. Like if both MCU's tried to take control at the same exact time... They would both see a floating CS line and then both drive it low at the same time (Collision). One MCU could be a low master and require that the CS line be floating for two counts and the high master only one count. That way if both tried at the same time, the master would take the CS line low after 1 cycle and the low master would check once more, and see the CS line was taken...
I'm sure that others here have actually done this before and know a lot more than I! Personally, I would go with I2C and call it a day.
--- In p...@yahoogroups.com, "Floyd Sense" wrote:
>
> I have an existing PIC based application and need to add RS232 communications to a PC. Due to timing constraints and other factors, I can't add that code to the existing PIC and intend to do the RS232 work with an additional and separate PIC. What I need is a way to occasionally pass information between the two. I've never used an external EEPROM chip and wonder if there's a way to share access to one EEPROM chip from two different PIC processors?
>
------------------------------------
to unsubscribe, go to http://www.yahoogroups.com and follow the instructions
(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )
I think the hard part will be in the software to handle collisions on the buss. Like if both MCU's tried to take control at the same exact time... They would both see a floating CS line and then both drive it low at the same time (Collision). One MCU could be a low master and require that the CS line be floating for two counts and the high master only one count. That way if both tried at the same time, the master would take the CS line low after 1 cycle and the low master would check once more, and see the CS line was taken...
I'm sure that others here have actually done this before and know a lot more than I! Personally, I would go with I2C and call it a day.
--- In p...@yahoogroups.com, "Floyd Sense"
>
> I have an existing PIC based application and need to add RS232 communications to a PC. Due to timing constraints and other factors, I can't add that code to the existing PIC and intend to do the RS232 work with an additional and separate PIC. What I need is a way to occasionally pass information between the two. I've never used an external EEPROM chip and wonder if there's a way to share access to one EEPROM chip from two different PIC processors?
>
------------------------------------
to unsubscribe, go to http://www.yahoogroups.com and follow the instructions
(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )