RT7 Boot from debugger now
RT7 Version OCOTP GUID/Rev Fix
RT7 I2C & SPI Partly working
RT7 Add FRAM support
Co-authored-by: David Sidrane <david.sidrane@nscdg.com>
nxp_imxrt1170-evk:Finish 1170 iomux versioning
px4io_update: Add px4io FW on nxp_fmurt1062-v2
nxp_fmurt1062-v2:Use DMA on SPI
nxp_fmurt1062-v2:Timer configuration for 1 channel per group (timer)
nxp_fmurt1062-v2:Normalize with V5X - start PX4IO and Mavlink on TELEM2
nxp_fmurt1062-v2:Update PX4IO Firmware
nxp_fmurt1062-v2:Normalize boardconfig to upstream
nxp_fmurt1062-v2:Corect roataion of ICM20602
nxp_fmurt1062-v2 RC04 HW Changes
nxp_fmurt1062-v2:Use TJA1103 PHY
nxp_fmurt1062-v2:Update to NuttX 10.3+
nxp_fmurt1062:Use Buffer based HW flow control
nxp_fmurt1062-v2:Free Memory
nxp_fmurt1062-v2:Remove fixed wing
This consolidates the version/revision detection function.
This should allow for actual changes in a follow up commit.
Signed-off-by: Julian Oes <julian@oes.ch>
Bootloader needs to have a mechanism to de-initialize crypto, in case some HW accelerator
is being used. This adds the needed function for it
Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>
PX4_SIM model need the simulator (gz_) prefix
Fix post debug task
Add x500_depth, rc_cessna, standard_vtol
Signed-off-by: Beniamino Pozzan <beniamino.pozzan@phd.unipd.it>
* Changed the method of checking and setting the server file lock on Posix to avoid conditions where the server can indicate that it is running but still hasn't finished it's initialization
- vectornav library (libvnc) fixed for NuttX
- open serial port O_NONBLOCK (like __APPLE__)
- set serial port baud rate with cfsetspeed (like __APPLE__)
- vectornav backend thread increase stack and run at higher priority (SCHED_FIFO)
- reduce boost priority to PX4_WQ_HP_BASE - 6
- add cli command 'trigger_watchdog' to manually trigger watchdog
- add perf counters when triggering watchdog
- reduce top measurement to 300ms
- restore priorities after 1.5s
There are precautions in case the SD card code itself has a busy-loop.
The static object is destroyed on at_exit while threads might still be
inside a CS. This can lead to a hanging process.
Cleaner would be to gracefully stop the threads.
According to https://linux.die.net/man/3/pthread_cond_destroy:
Attempting to destroy a condition variable upon which other threads are
currently blocked results in undefined behavior.
- use `gazebo-classic` everywhere consistently referring to the original Gazebo (eg version 9,10,11)
- additional `gazebo_*` helper targets added for compatibility, but warn about deprecation and tell you the new target naming
- use `gz` everywhere when referring to Gazebo (aka Ignition Gazebo or new Gazebo)
David Sidrane