I2C connectivity?
Up to Devices and Hardware
EBo --
ps: do you have any plans for a new version of the app. board with the various fixes?
:tongue:
(By support, I mean I'd buy one.)
Features that I would be really interested in are: higher power handling for outputs, better i2c and spi support, a RTC with api support, and USB host capability.
I'm still loving app board v1 though.
DARYLict
Things we're planning to include:
- a better power supply story
- improved outputs
- better I2C and SPI support
We can't really justify the cost of an RTC for everybody who uses the App Board, and USB host is not an implementation issue - the SAM7X does not support it.
The I2C signals do indeed come down off the Controller v2.0 board, but there's not good firmware support for it right at the moment.
I'm probably going to be trying to finish my push to transition the firmware over to c++ and then turn my attention to things like that. Of course, if anybody else makes some progress please chime in!
Previously Liam Staskawicz wrote:
The I2C signals do indeed come down off the Controller v2.0 board, but there's not good firmware support for it right at the moment.
I'm probably going to be trying to finish my push to transition the firmware over to c++ and then turn my attention to things like that. Of course, if anybody else makes some progress please chime in!
I'm still a bit confused about I2C, I have 2 Make Controller boards v2.0.
One on a Application board v1.0 and one on a Interface board v1.0.
Does any of these work with I2C without I have to make the alterations describes here:
http://makingthings.com/documentation/tutorial/using-i2c-on-the-make-contoller-board/tutorial-all-pages
How about TWI and SPI ?
regards
Christian
You no longer need to make hardware changes to use I2C (which is the same as TWI). However, at the moment there is not much software support for I2C.
SPI should be fine.
Previously Liam Staskawicz wrote:
You no longer need to make hardware changes to use I2C (which is the same as TWI). However, at the moment there is not much software support for I2C.
SPI should be fine.
So the Application board v1.0 and the Interface board v1.0 supports I2C without hardware changes ?
Is there any examples etc. on using the SPI ?
No, sorry - the changes for I2C rely on a hardware bug fix on the Controller Board v2.0.
The best place to look for SPI example code is in the EEPROM system, for example, which relies on it.
Previously Liam Staskawicz wrote:
No, sorry - the changes for I2C rely on a hardware bug fix on the Controller Board v2.0.
Just to be 100% correct, I have 2 controller boards v2.0, each respectively on a application board and an interface board, does any of these support I2C as they are now ?
If not, can they be altered to do it.
The best place to look for SPI example code is in the EEPROM system, for example, which relies on it.
Thanks, I will look at that.
Previously Liam Staskawicz wrote:
Yes - Application Board v2.0 and Interface Boards support I2C.
OK 
As I have an Application board v1.0 it doesn't have I2C without me altering it.
Sorry for asking again, the interface board, does it also have to be v2.0, the one I have is Interface board v1.0 ?
Previously Liam Staskawicz wrote:
Yes, the App Board v1.0 doesn't support that unfortunately.There's only v1.0 for the Interface Board - you're all set
Thanks
Site Outage
Forgot your password?
New user?
