hi Ben,
i got a project for you can you interface two micro controllers to transmit and receive data with a single wire no clock line should be added as both the micro controllers should be able to transmit and receive
hi Ben,
i got a project for you can you interface two micro controllers to transmit and receive data with a single wire no clock line should be added as both the micro controllers should be able to transmit and receive
RS-485 is often used to daisy-chain a master to a bunch of slaves. The master sends out a message that includes address bits and expects one of the slaves to respond. RS-485 is differential pair (a good idea if you're going any distance) but you can go single wire if you like. The UART has to ignore received data when it's transmitting -- this is called half duplex.
IMO the OP is probably better off with UART (two signal wires) or SPI (2, 3, or 4 wires depending on what you want to do).
As a footnote for your amusement, a lot of ARM processors use SWD (Single Wire Debug) in place of JTAG to talk to the chip's debug module. I've only seen SWD implemented as two signal wires: clock and bi-directional data. It's called SWD because there's an asynch version that uses a single data wire. But since everyone implements the two-wire synchronous version, it's pretty silly calling it SWD 
RS-485 is often used to daisy-chain a master to a bunch of slaves. The master sends out a message that includes address bits and expects one of the slaves to respond. RS-485 is differential pair (a good idea if you're going any distance) but you can go single wire if you like. The UART has to ignore received data when it's transmitting -- this is called half duplex.
IMO the OP is probably better off with UART (two signal wires) or SPI (2, 3, or 4 wires depending on what you want to do).
As a footnote for your amusement, a lot of ARM processors use SWD (Single Wire Debug) in place of JTAG to talk to the chip's debug module. I've only seen SWD implemented as two signal wires: clock and bi-directional data. It's called SWD because there's an asynch version that uses a single data wire. But since everyone implements the two-wire synchronous version, it's pretty silly calling it SWD
