Closed truckerDrew closed 2 years ago
We found a regression in the gps code causing the UART stop working. For now the workaround would be removing the 921600 entry in the folowing table. https://github.com/PX4/PX4-GPSDrivers/blob/master/src/ubx.cpp#L110
We're looking for a more permanent fix.
Any idea what the root cause is?
When attempting to use PX4 with the NXP S32K146 evaluation board with the instructions from their gitbook, here, there is an error thrown ostensibly from gps.cpp. I am using Ubuntu 20.04 LTS.
The intended use for the eval board is to communicate PWM to an ESC via UAVCAN/Cyphal. Currently, when a serial connection is established, the gps error "ERROR [gps] failed to open /dev/ttyS1 err: 1" is repeatedly thrown in an infinite loop. The nuttx/px4 shell is available while the errors are being thrown.
What is the best course of action for disabling GPS checks with PX4 when the firmware is used for mavlink/uavcan compatibility and not as the main FMU CAN node?
Alternatively, would one of the other options listed on the NXP gitbook make more sense for the purposes of setting up a CAN node?