MR-CANHUBK3 FMU variant revisions

[dirksavage88]

Fixes to mr-canhubk3 fmu to include correcting rotation on the bmm150 integrated on the ADAP board

• increase lp_default size: increase lp default stack to 2000 #23109
• fix to uart buffers
• uart7 dma for gps or crossfire
• fixes to RC uart

[PetervdPerk-NXP]

Maybe it has to do with the timer output groups that get send to qgc.
https://github.com/PX4/PX4-Autopilot/blob/main/Tools/module_config/output_groups_from_timer_config.py

[dirksavage88]

@PetervdPerk-NXP is there a way to debug that script? This is what I am seeing with build output right now:

-- PLATFORM nuttx -- TOOLCHAIN arm-none-eabi -- ARCHITECTURE cortex-m7 -- ROMFSROOT px4fmu_common -- ETHERNET y -- SERIAL_GPS1 /dev/ttyS1 -- SERIAL_GPS2 /dev/ttyS4 -- SERIAL_TEL1 /dev/ttyS2 -- SERIAL_TEL4 /dev/ttyS3 -- SERIAL_RC /dev/ttyS5 -- UAVCAN_INTERFACES 1 -- PX4 config: nxp_mr-canhubk3_fmu -- PX4 platform: nuttx -- cmake build type: MinSizeRel -- ccache enabled (export CCACHE_DISABLE=1 to disable) -- Found PythonInterp: /usr/bin/python3 (found version "3.10.12") -- Using C++11 -- Release build type: MinSizeRel /usr/bin/python3: Error while finding module specification for 'symforce.symbolic' (ModuleNotFoundError: No module named 'symforce') -- ROMFS: ROMFS/px4fmu_common -- ROMFS: Adding boards/nxp/mr-canhubk3/init/rc.board_defaults -> /etc/init.d/rc.board_defaults -- ROMFS: Adding boards/nxp/mr-canhubk3/init/rc.board_sensors -> /etc/init.d/rc.board_sensors -- ROMFS: Adding boards/nxp/mr-canhubk3/init/rc.board_mavlink -> /etc/init.d/rc.board_mavlink -- Configuring done -- Generating done -- Build files have been written to: /home/papadrew/source/Firmware/build/nxp_mr-canhubk3_fmu [282/1128] Generating nuttx/arch/arm/src/libarch.a chip/s32k3xx_emac.c: In function 's32k3xx_addmac': chip/s32k3xx_emac.c:2335:12: warning: unused variable 'crc' [-Wunused-variable] 2335 | uint32_t crc; | ^~~ chip/s32k3xx_emac.c: In function 's32k3xx_rmmac': chip/s32k3xx_emac.c:2383:12: warning: unused variable 'crc' [-Wunused-variable] 2383 | uint32_t crc; | ^~~ [1126/1128] Linking CXX executable nxp_mr-canhubk3_fmu.elf Memory region Used Size Region Size %age Used BOOT_HEADER: 256 B 4 KB 6.25% flash: 1930964 B 3997695 B 48.30% sram0_stdby: 0 GB 32 KB 0.00% sram: 57584 B 272 KB 20.67% itcm: 0 GB 64 KB 0.00% dtcm: 0 GB 128 KB 0.00%

[PetervdPerk-NXP]

In your build directory it outputs an actuators json file.

[dirksavage88]

Actuators.json looks good. I wonder if it's because i'm flashing the bin file which is missing some metadata? @PetervdPerk-NXP
how are you flashing px4 firmware on the canhubk3
?

[PetervdPerk-NXP]

That actuator.json eventually ends up somewhere in .rodata.
I'm just flashing the bin file as well.

[dirksavage88]

@dagar is the bin file missing some metadata? I tracked the the issue in QGC to this error:

[dirksavage88]

FMU version details

[dirksavage88]

The issue of the actuators tab not populating is a separate problem that can be addressed in a different PR, for now I was able to get actuators tab and geometries to come up over the ( T1 converter)UDP mavlink connection.

[dirksavage88]

For anyone wanting to get crosfire to work on this board, I have a patch until this PR gets updated and goes through. I was unable to get SBUS to work over the ADAP rc port so resorted to crosfire on the ADAP board GPS port.
crsf_canhub.tar.gz

[dirksavage88]

https://review.px4.io/plot_app?log=d6e0a7c1-7fcf-4383-bf57-9b624416c011

https://review.px4.io/plot_app?log=370a4be3-5c26-4678-a4e7-40d1c9dd3fa6