So my understanding is I’ll have to edit these library so they call the hardware I2C instead of software I2C library (please recall I’m a beginner).Ĭan anyone give me some rough instructions how to do this ?. My problem is I’m not calling directly the I2C library as I’m using these library (they both worked OK as is on the STM32) : Now to run at 400Khz I’ll need to use the hardware I2C. OK that’s one good thing, I now understand that. So my module is one of those who requires Soft_Standard = 16 instead of 27 to run at 100Khz,Īnd Soft_Fast = 0 only reach around 260Khz instead of 400Khz on my module. No through the thread, I realized I’m using software bit-bangeg I2C. It must be kept as is, without being modified by the end-user.ģ.Re-downloaded the most recent master zip (the one I had was 2 months old). This device tree part is related to STM32 microprocessors.
If the peripheral is assigned to another execution context, refer to How to assign an internal peripheral to a runtime context article for guidelines on peripheral assignment and configuration. It is used by the STM32 I2C Linux ® driver that registers relevant information in the I2C framework. The configuration is performed using the device tree mechanism.
Add to that the time taken to actually create and process the data, running the instructions to do everything, you can expect about half that. At 400kbps that equates to (400000/29) 13793 settings per second. Setting the DAC takes three bytes plus start/stop/ack bits (total 29 bits).
0 kommentar(er)
