getting a loop rate of around 130 on both now
source modules/esp_idf/export.sh
./waf configure --board=esp32s3empty --debug
./waf copter
cd build/esp32buzz/esp-idf_build/
ninja menuconfig
./waf configure --board=esp32buzz --debug
./waf copter
cd build/esp32buzz/esp-idf_build/
ninja menuconfig
and try to get both the resulting modified sdkconfig as smiilar as possible - this causes s3 to use qio, which is faster, and also puts the wifi stuff onto CORE1 on both configs.
s3:
loop_rate: actual: 148.097137Hz, expected: 400Hz
loop_rate: actual: 147.908691Hz, expected: 400Hz
classic:
loop_rate: actual: 188.718842Hz, expected: 400Hz
loop_rate: actual: 191.819748Hz, expected: 400Hz
This reverts commit 010cfa2f4c.
AP_HAL_ESP32: scheduler timing information was lying to us, this puts it back so both 'esp32buzz' and 'esp32s3empty' loop rates are "better than before. Still terrible, but an improvement
revert of part of pr #27181
- Add INS_ACC offsets to param to skip calibration for esp32empty
- Update esp32empty.h
- Change tabs to whitespace.
- Define HAL_INS_DEFAULT to HAL_INS_NONE
- Update wifi details
- Format comment in esp32empty
- Update serial defaults and uarts
- Use IO_MUX for UART_NUM_2 (TX 17, RX 16)
- Update scheduler
- Disable initialisation check in timer thread if HAL_INS_NONE
- Print main loop rate every 10s
- Remove serial(n)->begin() calls
Signed-off-by: Rhys Mainwaring <rhys.mainwaring@me.com>
David Buzz
Rhys Mainwaring
Nicholas Kruzan