Describe the bug
If we fail to set baudrate for the gyro port by either the old or new method, we will stop mcp. This is less than ideal, because failing to set baudrate on ONE of two (redundant) devices can bring down a flight computer, when we may otherwise be able to operate with a single gyro.
To Reproduce
N/A, design issue
Expected behaviormcp issues a warning for the offending serial port and continues.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment info (please complete the following information):
Describe the bug If we fail to set baudrate for the gyro port by either the old or new method, we will stop mcp. This is less than ideal, because failing to set baudrate on ONE of two (redundant) devices can bring down a flight computer, when we may otherwise be able to operate with a single gyro.
To Reproduce N/A, design issue
Expected behavior
mcp
issues a warning for the offending serial port and continues.Screenshots If applicable, add screenshots to help explain your problem.
Environment info (please complete the following information):
Additional context
dsp1760.c:341:
blast_fatal("Gyro %d baud not set by either method! Shutting down.\n", gyrobox);