Nxphlite Flight Controller Issues

[RomanBapst]

1. Cannot upload mission, says 'unable to write to SD card'

• removing the 'dataman start' call from the init script and starting it manually from the terminal after boot solves the problem
• stopping and restarting dataman also solves the problem
• at the lowest level, the ::read/::write to the dataman file on the SD card fails, the errno is EBADF, which means 'Bad file number'

2. RC link seems flaky, sometimes does not connect, often needs reboot, also SBUS does not work

3. Telemetry link is awfully slow and sometimes QGC fails to load params

• possibly related to missing flow control

4. external mag is not detected as external, possibly because it's not started with -X option (different bus architecture)

5. sometimes board freezes on boot, needs reboot (can be seen if safety switch LED light does not blink)

[dk7xe]

@RomanBapst please add
can not set 115200 baud as speed rate for TELEM2.
in case i try to set 3115200 via QGC on SYS_COMPANION to get normal telemetry 115k2 bd i get
Value must be within 0 and 1921600
error message.

[DanielePettenuzzo]

@dk7xe try to tick the force save box. This should allow you to set any value.

[dagar]

The telem 2 settings (SYS_COMPANION) are enums and not directly used as baudrates. See the init script https://github.com/PX4/Firmware/blob/master/ROMFS/px4fmu_common/init.d/rcS#L626.

https://github.com/PX4/Firmware/blob/master/src/modules/systemlib/system_params.c#L111-L140

I think we can do better than this, but it's a larger discussion. #8302

[davids5]

@RomanBapst Please retest this on https://github.com/PX4/Firmware/commits/leitwert-nxphlite-serial-dma 7fbca79

1. Cannot upload mission, says 'unable to write to SD card'
   removing the 'dataman start' call from the init script and starting it manually from the terminal after boot solves the problem
   stopping and restarting dataman also solves the problem
   at the lowest level, the ::read/::write to the dataman file on the SD card fails, the errno is EBADF, which means 'Bad file number'

I have not confirmed this. But this is an AI to get the SDIO DMA working. I am not sure if it is related. Please re-test.

2. RC link seems flaky, sometimes does not connect, often needs reboot, also SBUS does not work

S.BUS is working. Tested with FRsky XSR. There was a bug fix in the UART driver for a baud rate and format error that affected the parity when not none (SBUS is 8e2).

Telemetry link is awfully slow and sometimes QGC fails to load params
possibly related to missing flow control

There was a bug fix in the UART driver for a baud rate and format error. The link is slow but will work, when tested over FTDI (tested with a 5 Volt FTDI - TTL232RG 5V) cable and sometimes over the RADIO*. *The HW has an issue with oscillation on the UART4 level translators. It is observable on the 5V of P10-1. When the oscillation is not present the RADIO will work. But I see a delay compared to the USB-CDC connection to QGC.

Also note: With HW HS connected, the radio comes up in bootload mode (RED LED on solid)

I currently have RTS/CTS disconnected. I grounded P10-4 (CTS_b) and grounded pin 5 on the radio (marked RTS on mine). This configuration works.

Also Note the V5 when powered from USB is 4.5V - There is a diode that needs to be re-spec-ed

external mag is not detected as external, possibly because it's not started with -X option (different bus architecture)

This sort of fix is needed for drivers. Passing an an option as to how to report the internal/external

sometimes board freezes on boot, needs reboot (can be seen if safety switch LED light does not blink)

There was a bug in the USB driver that created and interrupt storm. This was fixed ~ Apr. 27

[RomanBapst]

@davids5 Thanks for the update!
@dk7xe Have you by chance already tested this and can you confirm that these issues are solved with the latest firmware?

[davids5]

I think these are resolved on https://github.com/PX4/Firmware/tree/leitwert-nxphlite-serial-dma. Please reopen if not,