Hi all,
?
from what I've understood about the timing issues with CW on zbitx, it seems that the CPU load is at least part of the problem.
?
I personally would love an option to switch off the waterfall (either in menu or set options), because I only need it when searching for signals, but not when I have found one.
?
Apart from that, I wonder why the binary is compiled with debug symbols and no optimization at all.
?
I exchanged the "gcc -g" with a "gcc -O3" in the build script, and the CPU load decreased from 60-70% to 45-55% running FT8, so there is quite some optimization that can be done.
?
Interestingly the CPU load is quite higher on CW, which is 65-70% optimized and 75-80% original (unoptimized). I guess this might be due to polling the key's GPIOs instead of handling them via interrupt (which would make the code more difficult of course).
?
Is there a reason why the build script is not using optimization? (for development side "-g" is perfectly understandable, but for "production" side?)
Maybe compiler optimization could at least contribute to the puzzle pieces for optimizing CW response.
?
vy73,
Peter DL4PIT
?
?
?
