sorry, can I clarify again: yours is linux x86 host <==> AT91 MCU (via uart on USB (FTDI)) <==> PIC (via GPIO on MCU) correct? and the GPIO is the interface with uart bitbanging is needed?
On Wednesday, November 19, 2014 4:09:11 PM UTC+8, Daniel Doron wrote: > > Hi Peter, > > Thanks for the info, but: > > 1. I am using linux OS > 2. I was looking at UART, not I2C. > > Daniel. > > On Tuesday, November 18, 2014 7:41:59 AM UTC+2, Peter Teoh wrote: >> >> hi, >> >> >> On Monday, November 10, 2014 8:36:42 PM UTC+8, Daniel Doron wrote: >>> >>> Hi all, >>> >>> I have tried to look an answer for this on the web, but I mainly got "no >>> can do" (timing issue). >>> >>> Kernel: 2.6.3x >>> MCU: atmel at91 (9263) >>> >> >> take a look at this: >> >> http://codinglab.blogspot.sg/2008/10/i2c-on-avr-using-bit-banging.html >> >> seemed like it is using atmega16, which slower than at91 (96Mhz), so I >> supposed yours AT91 should have no issue then? >> >> embedded with the URL is also the bitbanging code as well. >> >> >>> I wish to get/write a driver to bitbang a couple of gpios to emulate a >>> uart. the communication is with a remote PIC (PIC12F683) to which I have >>> already wrote the software and checked with linux terminal. >>> the communication does not have to be fast at all (1200 would be fine). >>> only a few bytes are exchanged. >>> >>> can someone point me in the right direction? did someone already develop >>> such a driver? is there an example/guide I can follow to do it? >>> >>> Daniel. >>> >>> -- You received this message because you are subscribed to the Google Groups "linuxkernelnewbies" group. To unsubscribe from this group and stop receiving emails from it, send an email to linuxkernelnewbies+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
