Hi Tecu,
good question. I did not think about it sofar. I understanding was that this is only a single latch I change when enabling the clock. Basically one control gate which either puts the clock signal on the FSMC or not.
I am not aware of any dividers in between which in my understanding could be one reason why I need to wait until clock signal is available.
Please correct me if I am wrong.
Thx
Michael
STM32F103Z, problems with FSMC and i2c
Moderator: RoccoMarco
Re: STM32F103Z, problems with FSMC and i2c
Hi,
the performance is good. No difference to the code without turing on and off the clocks. I tried to put in a function call in order to mutal exclude the i2c access and ugfx seems to have problems with this.
The GUI does not work anymore, the screen stays gray, no widgets displayed anymore. All User threads keep running, no trap.
Once I removed the function calls to lock and unlock the GUI works again.
Then I removed the inline statement from the aquire_bus and release_bus function and I got the same effect, gray screen no widgets displayed.
To me it looks like once the aquire_bus and release bus take a little longer ugfx cannot function anymore.
Anybody any Ideas why?
Maybe a queue which overruns?
Regards
Michael
the performance is good. No difference to the code without turing on and off the clocks. I tried to put in a function call in order to mutal exclude the i2c access and ugfx seems to have problems with this.
The GUI does not work anymore, the screen stays gray, no widgets displayed anymore. All User threads keep running, no trap.
Once I removed the function calls to lock and unlock the GUI works again.
Then I removed the inline statement from the aquire_bus and release_bus function and I got the same effect, gray screen no widgets displayed.
To me it looks like once the aquire_bus and release bus take a little longer ugfx cannot function anymore.
Anybody any Ideas why?
Maybe a queue which overruns?
Regards
Michael