Reserve IDs 1930-1949 for Agam Robotics - #280
Open
abhijithcv wants to merge 2 commits into
Open
Conversation
Author
|
Could you please review this? @peterbarker |
abhijithcv
force-pushed
the
agam-reserve-board-ids
branch
from
August 19, 2026 06:10
1fe67ab to
55c4791
Compare
abhijithcv
changed the title
abhijithcv
force-pushed
the
agam-reserve-board-ids
branch
from
August 19, 2026 06:19
55c4791 to
988a813
Compare
Author
|
Once again requesting your review for this, @peterbarker |
|
@abhijithcv Waiting for AP side to be merged. |
abhijithcv
added a commit
to agam-robotics/PX4-Autopilot
that referenced
this pull request
Aug 20, 2026
Agam Robotics, NXP, and Holybro all manufacture the same v6X-RT reference design and currently ship it under the shared px4/fmu-v6xrt target. Per the Manufacturer's PX4 Board Support Guide, each manufacturer should maintain its own target even when starting electrically identical to a reference design, since it gives a stable place to diverge sensor sets/connectors later and keeps board identity (board ID, USB VID/PID) under manufacturer control. Fork boards/px4/fmu-v6xrt to boards/agam-robotics/fmu-v6xrt with only identity fields changed (USB strings, HW_INFO_INIT_PREFIX/hwtypecmp from V6XRT to AGAMV6XRT, firmware.prototype board_id/magic/summary, path comments). No hardware/pin/sensor changes - the sensor set is unchanged from stock v6xrt today. board_id 1949 and USB PID 0x0002 (under the shared Dronecode VID 0x3643) match the AP_HW_AGAM_v6XRT reservation now in ArduPilot/ardupilot#34114 and PX4/PX4-Bootloader#280, and the PID pending request in Dronecode/usb-ids. Bootloader binary rebuilt from this target's own bootloader config rather than carried over from stock px4/fmu-v6xrt. Assisted-by: Claude:claude-sonnet-5 Signed-off-by: abhijithcv <abhijithcv1212@gmail.com>
abhijithcv
added a commit
to agam-robotics/PX4-Autopilot
that referenced
this pull request
Aug 20, 2026
Forked from boards/px4/fmu-v6xrt with own board identity (board_id, USB VID/PID) instead of sharing the stock target. Only identity fields changed - no pin/GPIO/sensor changes. board_id 1949 / USB PID 0x0002 match the reservations in ArduPilot/ardupilot#34114, PX4/PX4-Bootloader#280, and Dronecode/usb-ids. Assisted-by: Claude:claude-sonnet-5 Signed-off-by: abhijithcv <abhijithcv1212@gmail.com>
abhijithcv
added a commit
to agam-robotics/PX4-Autopilot
that referenced
this pull request
Aug 20, 2026
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reserve IDs 1930-1949 for Agam Robotics in
board_types.txt.Same block reserved on the ArduPilot side: ArduPilot/ardupilot#34114 (approved), which now assigns:
AP_HW_AGAM_GNSS-CAN= 1930AP_HW_AGAM_GNSSPLUS= 1931AP_HW_AGAM_BASE-RTK= 1932AP_HW_AGAM_CAN-RTK= 1933AP_HW_AGAM_FloRange= 1939AP_HW_AGAM_MegH7= 1940AP_HW_AGAM_v6XRT= 1949Mirroring it here per the Manufacturer's PX4 Board Support Guide, which recommends keeping the same board ID across both bootloaders for the same hardware.
Gaps at 1934-1938 and most of 1941-1948 are left open for future Agam products.
Ran
Tools/check_board_types_conflicts.shlocally — no conflicts.