IFLIGHT_BORG_F435 #614

sugaarK · 2024-11-22T03:09:05Z

No description provided.

configs/ IFLIGHT_BORG_F435/config.h

haslinghuis · 2024-12-02T01:16:53Z

Analog
betaflight_4.6.0_AT32F435G_IFLIGHT_BORG_F435.zip

Digital
betaflight_4.6.0_AT32F435G_IFLIGHT_BORG_F435_HD.zip

sugaarK

nice

Jason-iFlight · 2025-01-06T03:11:17Z

it’s tested already and it have been pass

ot0tot · 2025-01-06T04:55:43Z

configs/ IFLIGHT_BORG_F435/config.h

+                                        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 ) \


DMA request conflicts with ADC1

it is said that this ADC1 uses DMA to cause conflict, but ADC-CURR does not use this function due to inaccurate data, and I will disable this function.

so we removing adc1 define

it is said that this ADC1 uses DMA to cause conflict, but ADC-CURR does not use this function due to inaccurate data, and I will disable this function.

What does this mean?

@Jason-iFlight ?

it mean we can move this one out.

Move what one of of where?

@Jason-iFlight you have been asked questions... HERE....

ot0tot · 2025-01-06T04:56:32Z

configs/ IFLIGHT_BORG_F435/config.h

+#define MANUFACTURER_ID                 IFRC
+
+// LEDS
+#define LED0_PIN                        PC15


PC15 cannot be used to drive a status LED

LED drive current can be controlled at 3mA，and meet the requirements of the specification(we have check the specification)，so PC15 can be used to drive a status LED.

ot0tot · 2025-01-06T05:07:06Z

configs/ IFLIGHT_BORG_F435/config.h

+#define PINIO1_PIN                      PC14
+
+// TIMERS & DMA
+#define TIMER_PIN_MAPPING               TIMER_PIN_MAP(  0, PA8,  1,  8 ) \


Motor outputs are split over 4 timers, which is not acceptable.
https://betaflight.com/docs/development/manufacturer/manufacturer-design-guidelines#32-resource-selection-considerations

if we do not consider the 4 motors of the motor 5~~8, only the 4 motors of 1~~4 can be used, is it that these conflicts do not exist?

we removing motors 5-8?

configs/ IFLIGHT_BORG_F435/config.h

sugaarK · 2025-01-14T03:09:08Z

@Jason-iFlight needs some changes

configs/ IFLIGHT_BORG_F435/config.h

ot0tot · 2025-02-17T21:37:27Z

configs/ IFLIGHT_BORG_F435/config.h

+#define UART6_RX_PIN                    PC7
+#define UART6_TX_PIN                    PC6
+#define USB_DETECT_PIN                  PC5
+#define SERIALRX_UART                   SERIAL_PORT_USART2


UART2 is susceptible to DFU hijacking and should not be used for receivers/GPS

uart2 will not use on receiver and GPS，However, UART2 is used as power callback, power callback only works when the battery is powered on, there is no conflict in entering DFU, because entering DFU is usually USB powered state, and the battery is powered off.

uart2 will not use on receiver and GPS，However, UART2 is used as power callback, power callback only works when the battery is powered on, there is no conflict in entering DFU, because entering DFU is usually USB powered state, and the battery is powered off.

What does this mean? What is "power callback"?

@Jason-iFlight ?

we will not use it for receivers/GPS

Can you show the wiring guide for this FC?

@Jason-iFlight HERE

configs/ IFLIGHT_BORG_F435/config.h

sugaarK · 2025-02-18T10:07:48Z

@Jason-iFlight this will need retesting and PROPER testing... you would have had issues with the conflicts...

sugaarK · 2025-03-04T01:22:02Z

can you address any of the issues?

Co-authored-by: ot0tot <[email protected]>

remove motors 5-8

nerdCopter · 2025-03-07T14:59:41Z

rebased it on master, and force-pushed.
fixed the space in the folder-name.

nerdCopter

approving for workflow only.
did not deeply review, but did read some conversations
defer to other devs for validating the config.

sugaarK · 2025-05-26T04:03:47Z

@ot0tot this thing is in production.. they understand it will not be accepted to bring us a target like this already in production next time or they will be ignored.. can you commit any changes we can make in firmware and then we will approve as is.. this is the final time of this though next time we will simply reject a target like this.

ot0tot · 2025-06-09T16:11:17Z

This seems to be the same as the old https://github.com/betaflight/config/blob/master/configs/IFLIGHT_BLITZ_F435/config.h target. Why do we need to add this also?

If they're not willing to correct any of the design issues, might as well just use the old grandfathered target.

Jason-iFlight · 2025-06-11T00:53:57Z

Yes, we understand. If this request is approved, we will make the necessary changes in the future and introduce them subsequently.   张健 ***@***.***  

…

------------------ 原始邮件 ------------------ 发件人: ***@***.***>; 发送时间: 2025年5月26日(星期一) 中午12:04 收件人: ***@***.***>; 抄送: ***@***.***>; ***@***.***>; 主题: Re: [betaflight/config] IFLIGHT_BORG_F435 (PR #614) sugaarK left a comment (betaflight/config#614) @ot0tot this thing is in production.. they understand it will not be accepted to bring us a target like this already in production next time or they will be ignored.. can you commit any changes we can make in firmware and then we will approve as is.. this is the final time of this though next time we will simply reject a target like this. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

sugaarK · 2025-06-11T02:27:08Z

This seems to be the same as the old https://github.com/betaflight/config/blob/master/configs/IFLIGHT_BLITZ_F435/config.h target. Why do we need to add this also?

If they're not willing to correct any of the design issues, might as well just use the old grandfathered target.

would be easier and less hassle

nerdCopter changed the title ~~new iflight target~~ IFLIGHT_BORG_F435 Nov 22, 2024

nerdCopter force-pushed the iflight branch from 4066e3d to 22e22d6 Compare November 22, 2024 13:58

This comment was marked as off-topic.

Sign in to view

haslinghuis reviewed Dec 1, 2024

View reviewed changes

configs/ IFLIGHT_BORG_F435/config.h Outdated Show resolved Hide resolved

sugaarK commented Jan 4, 2025

View reviewed changes

sugaarK requested review from blckmn, haslinghuis and nerdCopter January 6, 2025 03:12

ot0tot reviewed Jan 6, 2025

View reviewed changes

configs/ IFLIGHT_BORG_F435/config.h Outdated Show resolved Hide resolved

ot0tot reviewed Feb 17, 2025

View reviewed changes

configs/ IFLIGHT_BORG_F435/config.h Outdated Show resolved Hide resolved

ot0tot reviewed Feb 17, 2025

View reviewed changes

configs/ IFLIGHT_BORG_F435/config.h Outdated Show resolved Hide resolved

sugaarK and others added 7 commits March 7, 2025 08:56

IFLIGHT_BORG_F435

86741b0

Update configs/ IFLIGHT_BORG_F435/config.h

51b3d30

Update configs/ IFLIGHT_BORG_F435/config.h

a3ac62d

Co-authored-by: ot0tot <[email protected]>

Update configs/ IFLIGHT_BORG_F435/config.h

4db6cf8

Co-authored-by: ot0tot <[email protected]>

Update configs/ IFLIGHT_BORG_F435/config.h

d9e963b

Co-authored-by: ot0tot <[email protected]>

Update config.h

1aefc27

remove motors 5-8

fix folder-name space

94d8680

nerdCopter force-pushed the iflight branch from 32b53a3 to 94d8680 Compare March 7, 2025 14:58

nerdCopter approved these changes Mar 7, 2025

View reviewed changes

haslinghuis assigned sugaarK Jul 26, 2025

IFLIGHT_BORG_F435 #614

Are you sure you want to change the base?

IFLIGHT_BORG_F435 #614

Uh oh!

Conversation

sugaarK commented Nov 22, 2024

Uh oh!

This comment was marked as off-topic.

Uh oh!

haslinghuis commented Dec 2, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

sugaarK left a comment

Choose a reason for hiding this comment

Uh oh!

Jason-iFlight commented Jan 6, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

sugaarK commented Jan 14, 2025

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

sugaarK commented Feb 18, 2025

Uh oh!

sugaarK commented Mar 4, 2025

Uh oh!

nerdCopter commented Mar 7, 2025

Uh oh!

nerdCopter left a comment

Choose a reason for hiding this comment

Uh oh!

sugaarK commented May 26, 2025

Uh oh!

ot0tot commented Jun 9, 2025

Uh oh!

Jason-iFlight commented Jun 11, 2025 via email

Uh oh!

sugaarK commented Jun 11, 2025

haslinghuis commented Dec 2, 2024 •

edited

Loading