5-6-2012
Testing the I2C / TWI communication between the usb debugger and the target board. ( I chose I2C only because my robot board already used the serial lines as output )
Reference
http://lackawanna.hackhut.com/2011/10/10/easy-i2c/
http://www.engineersgarage.com/embedded/avr-microcontroller-projects/atmega32-twi-two-wire-interface?destination=node%2F1040 (code is wrong)
7-6-2012
Decided to write the code myself since many of the given codes are either wrong or polled. Interrupt driven is required. (reference: datasheet).
Having fun implementing interrupt driven I2C code. Lots of things to refer.
Finished the Master Transmitter. Can't test until the slave reciever is implemented. 2 new systems! Not the best idea. Will be a headache to debug if it doesn't work! :-(
http://www.atmel.com/Images/doc2564.pdf
The transmission part is acting strange even though some parts "seems" to be working. (the day has ended, so signing off).
Testing the I2C / TWI communication between the usb debugger and the target board. ( I chose I2C only because my robot board already used the serial lines as output )
Reference
http://lackawanna.hackhut.com/2011/10/10/easy-i2c/
http://www.engineersgarage.com/embedded/avr-microcontroller-projects/atmega32-twi-two-wire-interface?destination=node%2F1040 (code is wrong)
7-6-2012
Decided to write the code myself since many of the given codes are either wrong or polled. Interrupt driven is required. (reference: datasheet).
Having fun implementing interrupt driven I2C code. Lots of things to refer.
Finished the Master Transmitter. Can't test until the slave reciever is implemented. 2 new systems! Not the best idea. Will be a headache to debug if it doesn't work! :-(
http://www.atmel.com/Images/doc2564.pdf
The transmission part is acting strange even though some parts "seems" to be working. (the day has ended, so signing off).
No comments:
Post a Comment