Posted on May 17, 2011 at 13:18Ok, after yet some more debugging it now seems i solved my own bug *crosses fingers*. The problem was that i had configured the second I2C interface in the same priority group, but with a lower sub priority. Due to my ...
Posted on May 17, 2011 at 13:18I'm experiencing a real mind bogging bug in my I2C routines, the situation is this: - uP = STM32F103RBT6 rev Z (LQF64) - Using Raisonance/GCC build tools - uP using USART0, USART1, I2C1, I2C2, all using interrupts - I2...
Posted on May 17, 2011 at 13:18Lots ( most ) of the hardware SPI interfaces in uP's do not generate a clock if you don't send anything( write to the data register ). You could then of course send zero's .....
