??? 02/10/06 16:00 Read: times |
#109723 - Good point Responding to: ???'s previous message |
If you use different chips, you must also learn and implement different HW-I2C. E.g. only on Philips devices there are four (or more ?) different HW-I2C implemented.
If development speed is more of an issue than run-time performance, it's generally easier to port a bit-bang I2C or SPI. I had the luck of moving some of my code to an Atmel device and it required a little but of SPI access. I re-used my bit-bang SPI from before and it worked fine. This Atmel device has/had a built in SPI and about a year later Atmel issued an Errata for the built in SPI. I didn't have to worry about it. GB |