feat(boards/agam-robotics): add Agam Robotics FMU-v6XRT board support - #28285
feat(boards/agam-robotics): add Agam Robotics FMU-v6XRT board support#28285abhijithcv wants to merge 7 commits into
Conversation
| #endif | ||
|
|
||
| #ifndef BOOT_DEVICES_SELECTION | ||
| # define BOOT_DEVICES_SELECTION USB0_DEV|SERIAL0_DEV|SERIAL1_DEV |
There was a problem hiding this comment.
[error] bugprone-macro-parentheses [error]
macro replacement list should be enclosed in parentheses
| # define BOOT_DEVICES_SELECTION USB0_DEV|SERIAL0_DEV|SERIAL1_DEV | |
| # define BOOT_DEVICES_SELECTION (USB0_DEV|SERIAL0_DEV|SERIAL1_DEV) |
| #endif | ||
|
|
||
| #ifndef BOOT_DEVICES_SELECTION | ||
| # define BOOT_DEVICES_SELECTION USB0_DEV|SERIAL0_DEV|SERIAL1_DEV |
There was a problem hiding this comment.
[error] bugprone-macro-parentheses [error]
macro replacement list should be enclosed in parentheses
| # define BOOT_DEVICES_SELECTION USB0_DEV|SERIAL0_DEV|SERIAL1_DEV | |
| # define BOOT_DEVICES_SELECTION (USB0_DEV|SERIAL0_DEV|SERIAL1_DEV) |
| #endif | ||
|
|
||
| #ifndef BOOT_DEVICES_SELECTION | ||
| # define BOOT_DEVICES_SELECTION USB0_DEV|SERIAL0_DEV|SERIAL1_DEV |
There was a problem hiding this comment.
[error] bugprone-macro-parentheses [error]
macro replacement list should be enclosed in parentheses
| # define BOOT_DEVICES_SELECTION USB0_DEV|SERIAL0_DEV|SERIAL1_DEV | |
| # define BOOT_DEVICES_SELECTION (USB0_DEV|SERIAL0_DEV|SERIAL1_DEV) |
| #endif | ||
|
|
||
| #ifndef BOOT_DEVICES_FILTER_ONUSB | ||
| # define BOOT_DEVICES_FILTER_ONUSB USB0_DEV|SERIAL0_DEV|SERIAL1_DEV |
There was a problem hiding this comment.
[error] bugprone-macro-parentheses [error]
macro replacement list should be enclosed in parentheses
| # define BOOT_DEVICES_FILTER_ONUSB USB0_DEV|SERIAL0_DEV|SERIAL1_DEV | |
| # define BOOT_DEVICES_FILTER_ONUSB (USB0_DEV|SERIAL0_DEV|SERIAL1_DEV) |
🔎 FLASH Analysispx4_fmu-v5x [Total VM Diff: 0 byte (0 %)]px4_fmu-v6x [Total VM Diff: 0 byte (0 %)]Updated: 2026-08-22T16:39:21 |
|
I should be able to review this some time next couple days. Ping me if it doesnt happen. |
|
This should have docs. IF it is a pixhawk standard board they could be modeled on https://docs.px4.io/main/en/flight_controller/pixhawk6x-rt. If it is manufacturer supported (i..e not perfectly compatible) then see that section of the docs. |
9dc4030 to
3027280
Compare
3027280 to
b8a65ca
Compare
Adds boards/agam-robotics/fmu-v6xrt, Agam Robotics' own build target for the Agam Autopilot v6X-RT — electrically and mechanically identical to the NXP v6X-RT reference design (same as boards/px4/fmu-v6xrt), differing only in enclosure. Per the Manufacturer's PX4 Board Support Guide, manufacturers of the v6X-RT reference design should maintain their own target even when starting electrically identical to it, since it keeps board identity (board ID, USB VID/PID) under manufacturer control and gives a stable place to diverge the sensor set later (which we plan to do soon for sensor availability reasons; so our own target will be useful). Only identity fields changed from the stock target (USB strings, HW_INFO_INIT_PREFIX/ver hwtypecmp from V6XRT to AGAMV6XRT, firmware.prototype board_id/magic/summary, path comments/include guards) — no pin/GPIO/sensor changes. Board ID / USB identity — in progress, coordinating with maintainers: - board_id: 1949, matching AP_HW_AGAM_v6XRT in ArduPilot/ardupilot#34114 (approved) and PX4/PX4-Bootloader#280 (open) - USB PID 0x0002 under the Dronecode VID 0x3643: Dronecode/usb-ids#2 (open) Flight log: https://review.px4.io/plot_app?log=2aacada6-4c48-4942-820d-44dcf369b8af Flown on the stock px4_fmu-v6xrt build rather than this target's own build — the hardware is electrically identical (this target is a byte-for-byte fork of boards/px4/fmu-v6xrt with only identity strings changed), so the flight validates the physical board. Signed-off-by: abhijithcv <abhijithcv1212@gmail.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…arens (bugprone-macro-parentheses) Signed-off-by: abhijithcv <abhijithcv1212@gmail.com>
…efault Signed-off-by: abhijithcv <abhijithcv1212@gmail.com>
…entation Flight controller product page, manufacturer-supported tier. Magnetometer listed as BMM150/BMM350 per rc.board_sensors (source material had a nonexistent part number). Signed-off-by: abhijithcv <abhijithcv1212@gmail.com>
b8a65ca to
49d332f
Compare
|
No broken links found in changed files. |
Docs have been added @hamishwillee |
|
Hi @farhangnaderi, sorry to bother but did you get time to review this? |
| if ver hwtypecmp AGAMV6XRT000 AGAMV6XRT001 | ||
| then | ||
| # Internal SPI bus ICM42686p (hard-mounted) | ||
| icm42688p -6 -R 12 -b 1 -s start | ||
|
|
||
| # Internal on IMU SPI BMI088 | ||
| bmi088 -A -R 4 -s start | ||
| bmi088 -G -R 4 -s start | ||
|
|
||
| # Internal on IMU SPI bus ICM42688p | ||
| icm42688p -R 6 -b 2 -s start | ||
| fi | ||
|
|
||
| if ver hwtypecmp AGAMV6XRT002 | ||
| then | ||
| # Internal SPI bus icm45686 (hard-mounted) | ||
| icm45686 -R 12 -b 1 -s start | ||
|
|
||
| # Internal on IMU SPI BMI088 | ||
| bmi088 -A -R 4 -s start | ||
| bmi088 -G -R 4 -s start | ||
|
|
||
| # Internal on IMU SPI bus icm45686 | ||
| icm45686 -R 6 -b 2 -s start | ||
| fi |
There was a problem hiding this comment.
are all these sensor types mentioned in the docs?
Adds
boards/agam-robotics/fmu-v6xrt, Agam Robotics' own build target for the Agam Autopilot v6X-RT — electrically and mechanically identical to the NXP v6X-RT reference design (same asboards/px4/fmu-v6xrt), differing only in enclosure. Per the Manufacturer's PX4 Board Support Guide, manufacturers of the v6X-RT reference design should maintain their own target even when starting electrically identical to it, since it keeps board identity (board ID, USB VID/PID) under manufacturer control and gives a stable place to diverge the sensor set later (which we plan to do soon for sensor availability reasons; so our own target will be useful).Only identity fields changed from the stock target (USB strings,
HW_INFO_INIT_PREFIX/ver hwtypecmpfromV6XRTtoAGAMV6XRT,firmware.prototypeboard_id/magic/summary, path comments/include guards) — no pin/GPIO/sensor changes.Board documentation: https://github.com/agam-robotics/PX4-Autopilot/blob/pr-agam-v6xrt-target/docs/en/flight_controller/agam_v6xrt.md
Board ID / USB identity — complete:
board_id: 1949, matchingAP_HW_AGAM_v6XRTin ArduPilot/ardupilot#34114 (merged) and PX4/PX4-Bootloader#280 (merged)0x0002under the Dronecode VID0x3643: Dronecode/usb-ids#2 (merged)Flight log: https://review.px4.io/plot_app?log=2aacada6-4c48-4942-820d-44dcf369b8af
Flown on the stock
px4_fmu-v6xrtbuild rather than this target's own build — the hardware is electrically identical (this target is a byte-for-byte fork ofboards/px4/fmu-v6xrtwith only identity strings changed), so the flight validates the physical board.