You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Tree: 203e253dfe

main

master

my1.12

my1.12-iic

pr-sensor-distance

release/1.12

sbg

tf-1.12

tf-1.12-print_test

tf-iic2uart

tf_driver-1.12

tf_i2c-1.12

tf_i2c_collis_pre

v1.13.0-BW

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '203e253dfe'

${ noResults }

px4_autopilot/boards/uvify/core

History

Julian Oes 9686c81f7d boards: enable flow control on CDCACM ... This enables flow control on CDCACM for the NuttX boards which fixes a problem where HITL would stall. The stall could happen if the hardware would be a bit too slow in keeping up with the incoming messages. Often, this happened on arming because the logger would take some time to log all parameters right at the beginning. The stall would then not recover due to NuttX bug where the rx interrupt would not be restored correctly and instead only a slower watchdog would release the next read. This watchdog takes 200ms which means it's hard to impossible to get out of the situation without restarting sim and/or PX4. For more information about the issue, see: apache/incubator-nuttx#3633 As a workaround, until that bug is fixed, and because it makes sense anyway, I propose to enable FLOWCONTROL for the serial via USB.		3 years ago
..
extras	NuttX build in place	3 years ago
init	mavlink USB auto start/stop on boards with VBUS	3 years ago
nuttx-config	boards: enable flow control on CDCACM	3 years ago
src	boards: board_app_initialize() don't return early on failure	3 years ago
default.px4board	boards: add CONTROL_ALLOCATOR + ACTUATOR_TEST	3 years ago
firmware.prototype	…