ArduPilot / ArduPilot/MissionPlanner

mission planner connect problem

Open
#2,418 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
2.4k
Forks
2.9k
Avg merge
19h 16m
Merged PRs (30d)
4

Description

hello everyone, I have deigned my own custom flight controller board using STM32F7. I have modified existing mRoX21-777 hwdef.dat file as per the ardupilot suggest. I build and flashed new bootloader and boards LED also blinking. then i used the bootloader to upload the firmware with Mission Planner.It is detecting the USB in windows device manager but the problem is connecting to Mission Planner.

Can i use any APJ_BOARD_ID for this device ? Could you please suggest any necessary changes ?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the modified mRoX21-777 hwdef.dat and the APJ_BOARD_ID used for the custom STM32F7 board, then review how Mission Planner handles the uploaded firmware and connection. Reproduce the bootloader upload and connection attempt; done means the custom board is recognized and connects successfully, with the required board configuration identified.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop, embedded-iot
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
18/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.