Peter thanks for sharing interesting performance data!
You may be right that delayTicks could be shortened. There is a note in the i2cbb.c source code that says
delayTicks = 400; // Delay value empirically chosen to be twice the value that just start to cause I2C NACKs - N3SB
That note was in the sbitx code for machines with the RPI4 processor. I don't know what it should be for the Raspberry Pi Zero 2W processor in the zbitx - maybe cut it down proportionate to processor speed difference?
--
Mike KB2ML
toggle quoted message
Show quoted text
On Fri, May 9, 2025 at 12:48 PM, Peter, DL4PIT wrote:
Just for test I changed delayTicks to 1 (so i2c_delay counts to 1 instead of
400), and this seems to remove the clogging of the ui_tick completely.
Anyone knowing the code much better than I do:
I guess the burning of CPU time in i2c_delay has some reason, can anyone
enlighten me why this is done?
