Closed haslinghuis closed 2 weeks ago
@ctzsnooze was experiencing this issue - so I tried to narrow it done.
@ledvinap @SteveCEvans any idea why this could happen? Did not check flashing further back then 4.5.0 RC1.
Note moving set dshot_bidir = ON
to the end of the diff solves the issue
@haslinghuis : Can you test status if pasting manually? Maybe delay before save
is important
@ledvinap
save
dshot_bidir = ON
just before save in the diff - operation is successful.profile 0
, then I typed profile 0
and flight controller locks up.MCU F411 Clock=108MHz (PLLP-HSE), Vref=3.30V, Core temp=61degC
Stack size: 2048, Stack address: 0x2001fff0
Configuration: UNCONFIGURED, size: 3779, max available: 16384
Devices detected: SPI:1, I2C:0
Gyros detected: locked dma
GYRO=ICM42688P, ACC=ICM42688P
OSD: MAX7456 (30 x 13)
BUILD KEY: a53ecdf05462f8a9118ffe647edad54b (4.5.0-dev)
System Uptime: 137 seconds, Current Time: 2024-04-26T14:10:19.037+00:00
CPU:63%, cycle time: 124, GYRO rate: 8064, RX rate: 15, System rate: 9
Voltage: 0 * 0.01V (0S battery - INIT)
I2C Errors: 0
GPS: NOT ENABLED
Arming disable flags: RXLOSS ANGLE LOAD CLI MSP DSHOT_TELEM
# profile 0
profile 0
Please try moving dshot_bidir = ON just before save, but entering it manually - create delay before save
save
seems not be the issue - as manual applying the diff still hangs firmware at profile 0
- operation is successful when moving dshot_bidir = on
to the end before save in the diff - without delay.
So no crash when dshot_bidir = on is after profile 0 ? Even when save is delayed?
save
reboots the board - maybe the board is rebooted before dshot_bidir = on
can crash it. From you reply, it is not obvious if only order is important, not time.
Order is important. Not timing (as we don't reach save)
Loading diff locks up F411 when
dshot_bidir = ON
is present in the diff atprofile 0
Scope
Tested with NOX F411, CRAZYBEEF4SX1280 and BETAFPVF4SX1280
Workaround
Moving
set dshot_bidir = ON
to the end of the diff solves the issue