Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
livebox:hah_i2c [2011/12/31 19:31]
brett [Firmware debugging]
livebox:hah_i2c [2011/12/31 19:31] (current)
brett [Firmware debugging]
Line 86: Line 86:
 Although direct control with the AVR isn't necessary, its useful to understand how the underlying commands are being invoked. ​ If you are having problems and want to do some low level debugging with ''​microcom''​ directly talking to the AVR command interface this is what you need to know. Although direct control with the AVR isn't necessary, its useful to understand how the underlying commands are being invoked. ​ If you are having problems and want to do some low level debugging with ''​microcom''​ directly talking to the AVR command interface this is what you need to know.
  
-The firmware command "''​i2c scan''"​ is VERY useful ​when making ​sure that the hardware is correctly setup and configured. ​ Issuing this command will perform a scan of ALL I2C addresses from 0x00-0xFF to see what responds. ​ You can only run this with direct microcom connection to the AVR running in DEBUG mode.  See also [[hah_microcontroller]]+The firmware command "''​i2c scan''"​ is VERY useful ​to make sure that the hardware is correctly setup and configured. ​ Issuing this command will perform a scan of ALL I2C addresses from 0x00-0xFF to see what responds. ​ You can only run this with direct microcom connection to the AVR running in DEBUG mode.  See also [[hah_microcontroller]]
  
 Additional instructions are going to be needed to configure the I2C devices. Additional instructions are going to be needed to configure the I2C devices.