With Networking
Memory region Used Size Region Size %age Used
flash: 722108 B 7 MB 9.84%
flashxip: 909032 B 1 MB 86.69%
sram: 780212 B 856 KB 89.01%
itcm: 0 GB 0 GB
dtcm: 0 GB 128 KB 0.00%
total used free largest nused nfree
total used free largest nused nfree
Umem: 267232 229136 38096 37264 906 53
No Network
[846/848] Linking CXX executable nxp_fmurt1062-v2_default.elf
Memory region Used Size Region Size %age Used
flash: 685340 B 7 MB 9.34%
flashxip: 895448 B 1 MB 85.40%
sram: 722356 B 856 KB 82.41%
itcm: 0 GB 0 GB
dtcm: 0 GB 128 KB 0.00%
total used free largest nused nfree
Umem: 325088 200992 124096 123376 813 46
This commit With Networking
[4/6] Linking CXX executable nxp_fmurt1062-v2_default.elf
Memory region Used Size Region Size %age Used
flash: 694852 B 7 MB 9.47%
flashxip: 936880 B 1 MB 89.35%
sram: 753588 B 856 KB 85.97%
itcm: 0 GB 0 GB
dtcm: 0 GB 128 KB 0.00%
total used free largest nused nfree
Umem: 293856 228432 65424 64448 900 51
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
- make it work again
- also supports Kconfig based clk source selection
- adapt to recent changes of default PWM limits
- support outputting in duty-cycle mode
- i2c addr use use hex representation
- revert back to common min/max value & move duty-cycle mode to advanced
We provide a latency measurement in the input capture handler.
However, since the timer was not enabled, none of the counter were
running therefore all counters were zero, thus latency was also zero.
Since the HRT is used to provide a timestamp, the lack of the running
timer was never noticed. After enabling the timer, latency now correctly
shows 9-10 counts.
* Fixed an issue where if the GCC_VER_STR would not contain the right NUTTX_GCC_VERSION, the grep -c command would throw a failure, silently exiting the entire ubuntu.sh setup script
This is a tool that can be used to generate advanced lift drag plugin parameters automatically using AVL. Rather than having to create .avl files yourself, pass them to AVL, read out the correct parameters and place them in the Advanced Lift Drag plugin, this tool will do all that for you and generate a complete advanced_lift_drag plugin sdf containing all necessary parameters for any vehicle. All that is required is to specify what the physical geometries of the vehicle are. The scripts are adaptable enough to support a self-selected number of control surfaces.
---------
Co-authored-by: frederik <frederik@auterion.com>
This switches from the horribly intertwined ringbuffer implementation to
the new VariableLengthRingbuffer implementation.
By ditching the previous implementation, we fix MAVLink message
forwarding, which didn't work reliably. The reason it didn't work is
that multiple mavlink messages could be added but only one of them was
sent out because the buffer didn't keep track of the messages properly
and only read the first one.
Signed-off-by: Julian Oes <julian@oes.ch>
This adds a reusable class for a FIFO ringbuffer that accepts variable
length packets. It is using the Ringbuffer class internally.
Signed-off-by: Julian Oes <julian@oes.ch>
* mission_base: reset inactivation index when user set a new mission index, or mission is reset.
* mission_base: check Climb required always on current mission item
This prevents accidental misconfiguration via I2C if there are
multiple SPI devices on the same bus. The device may hear it's i2c address
and write some register, while there is data transfer ongoing with another
device.
Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>
WorkItemSingleShot::_sem is a signaling semaphore, disable PI for it.
Set CONFIG_DEBUG_ASSERTIONS=y and the kernel panics due to the semaphore
having no holder, disabling PI fixes this.
The head/tail semaphores are not used as lock but rather as resource
counters and thus relate more as signaling semaphores. Disable PI for
them.
I run my code with CONFIG_DEBUG_ASSERTIONS=y and the kernel panics due
to the semaphore having no holder, disabling PI fixes this.
This prevents the mavlink transmit loop from waiting on the module mutex
thus not stopping transmissions when the mutex is already taken.
This can happen when calling `mavlink status` from the mavlink shell,
where `Mavlink::get_status_all_instances()` takes the mutex and then
prints the status via pipes to the mavlink transmit buffer.
If that pipe cannot be emptied a deadlock happens.
Since the MavlinkReceiver thread also waits on the module mutex, both
reception and transmission of Mavlink packets are then prevented thus
disabling communications entirely.
IMUs were replaced in V3 with 2x ICM42688P. This configuration should
work with all revisions of Matek F743 Slim board, including V1, V1.5
and interim variant of V3 (ICM42688P + ICM42605).
Signed-off-by: Andrei Korigodskii <akorigod@gmail.com>
In the lightware_parser function, LW_PARSE_STATE2_GOT_DIGIT0 state can be repeated unexpectedly without proper parserbuf_index or state checking. This behavior will trigger a heap buffer overflow vulnerability by allowing to write some data. And the writable size is sizeof(unsigned).
David Sidrane
Peter van der Perk
SalimTerryLi
Niklas Hauser
Roman Bapst
Julian Oes
Engin Oksuz
Titus
Robbie Drage
Daniel Agar
Frederik Markus
KonradRudin
Jukka Laitinen
Ville Juven
bresch
Andrei Korigodskii
Daniel Honies
jmackay2
vlad-serbanica
ZeroOne