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
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
The API is cleaner if the control_data is const reference and the device
compid is an explicit output argument.
Signed-off-by: Julian Oes <julian@oes.ch>
The resets in the modes (eg Loiter mode) are not active yet, so manually
set rep->current.cruising_speed = -1.f if not already in the same flight mode.
Signed-off-by: Silvan Fuhrer <silvan@auterion.com>
When flow control is used together with DMA, we need to add a pulldown
to CTS. Without it, it assumes flow control and gets stuck when
CTS is not connected.
Signed-off-by: Julian Oes <julian@oes.ch>
When we fall back to another link, we are already doing a uORB copy when
checking the data. Therefore, we should further down use/send that data
instead of overwriting it immediately.
Signed-off-by: Julian Oes <julian@oes.ch>
I don't think it makes sense to slow down switching RTCM injection to
once every 5 seconds. If we don't have corrections, we should check and
use whatever we get as soon as possible.
Signed-off-by: Julian Oes <julian@oes.ch>
We need to reset the instance after looping through all instances.
Otherwise, we are left with the last instance if none is valid but have
not updated the _selected_rtcm_instance which is what is logged.
Therefore, this change fixes the logged RTCM instance.
Signed-off-by: Julian Oes <julian@oes.ch>
It turns out that I had omitted implementing the gimbal_device_id which
is the component ID of the gimbal device that the gimbal manager (in
this case PX4) is responsible for.
Signed-off-by: Julian Oes <julian@oes.ch>
David Sidrane