-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IFLIGHT_BORG_F435 #614
base: master
Are you sure you want to change the base?
IFLIGHT_BORG_F435 #614
Conversation
This comment was marked as off-topic.
This comment was marked as off-topic.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice
it’s tested already and it have been pass |
TIMER_PIN_MAP( 3, PB1, 2, 2 ) \ | ||
TIMER_PIN_MAP( 4, PC8, 2, 1 ) \ | ||
TIMER_PIN_MAP( 5, PC9, 2, 3 ) \ | ||
TIMER_PIN_MAP( 6, PB6, 1, 11 ) \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
DMA request conflicts with ADC1
#define MANUFACTURER_ID IFRC | ||
|
||
// LEDS | ||
#define LED0_PIN PC15 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PC15 cannot be used to drive a status LED
#define PINIO1_PIN PC14 | ||
|
||
// TIMERS & DMA | ||
#define TIMER_PIN_MAPPING TIMER_PIN_MAP( 0, PA8, 1, 8 ) \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Motor outputs are split over 4 timers, which is not acceptable.
https://betaflight.com/docs/development/manufacturer/manufacturer-design-guidelines#32-resource-selection-considerations
@Jason-iFlight needs some changes |
#define UART6_RX_PIN PC7 | ||
#define UART6_TX_PIN PC6 | ||
#define USB_DETECT_PIN PC5 | ||
#define SERIALRX_UART SERIAL_PORT_USART2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
UART2 is susceptible to DFU hijacking and should not be used for receivers/GPS
Co-authored-by: ot0tot <[email protected]>
Co-authored-by: ot0tot <[email protected]>
Co-authored-by: ot0tot <[email protected]>
@Jason-iFlight this will need retesting and PROPER testing... you would have had issues with the conflicts... |
No description provided.