Betaflight for Asgard32 Public test version

[jflyper]

Target name AG3X

Branch location Master https://github.com/jflyper/cleanflight/tree/bfdev-ag3x 3.3.1 Maintenance https://github.com/jflyper/cleanflight/tree/bfdev-ag3x-3.3.x-maint

Commits https://github.com/jflyper/cleanflight/commits/bfdev-ag3x

Pin functions AG3X-pinfunc-3a09f300.pdf

[jflyper]

Known hardware issues

1. LED Strip pad does not work (Timer collision with M4). There is a very little choice of pads for workaround; PA2 (TX2, labelled S/A for SmartAudio) is a descent choice. SmartAudio can be moved to one of available timer channels.

2. BEEPER control is overloaded onto LED status control pin, and beeper is just a audible status LED. No beeper feature is available, and beeper beeps on events that normal beeper doesn't beep (like attitude on ground). The other way around may be possible, but I decided not to. EDIT --- See https://github.com/jflyper/cleanflight/issues/14#issuecomment-367741302 for workaround.

[jflyper]

Individual function tests

• [x] M1~4 OS125, OS42, MS

• [x] M1~4 DS in burst mode

• [x] PPM on SBUS(PA8)
• [x] S.BUS on SBUS(RX1)
• [x] DSMX on TX1, TX3, TX5, TX6 ((Requires serialrx_halfduplex = ON) Bind facility also works.
• [x] SRXL on TX3, TX5, TX6 (Requires serialrx_halfduplex = ON, doesn't work on TX1)

• [x] F.Port (UIM) on TX1, TX5 (Requires serialrx_halfduplex = ON)

• [x] ESC pass through (BLHeli32)
• [x] ESC telemetry on RX4 (Default Configuration)
• [x] SmartAudio on TX2 (TX2 will be used for LED strip), Softserial on PB14 (M7), PA9(TX1)

• [x] SmartPort over Softserial on PA9 (TX1)

• [x] GPS (FD-Serial) on RX6/TX6, RX5/TX5

• [x] RC Split V2 (FD-Serial) on RX6/TX6

• [x] I2C2 at [PB10,PB11], I2C OLED display, HMC5883L compass, BMP280 barometer
• [x] LED strip on PA2(S/A = TX2), PA8(PPM=SBUS)
• [x] Camera Control on PA3 (CAMC = RX3)

[jflyper]

Wiring plans

[jflyper]

First cut firmware Equivalent to 3.3-RC1 + alpha ~[betaflight_3.3.0_AG3X-0-bd169d7a.hex.zip]()~

[jflyper]

Fixed PPM ~[betaflight_3.3.0_AG3X-1-0cc3824.hex.zip]()~

[jflyper]

Fixed target name to AG3X ~[betaflight_3.3.0_AG3X-2-604c5a5.hex.zip]()~

[jflyper]

Fixed UART3 pin assignments. Fixed channel number for CAMCTL. ~[betaflight_3.3.0_AG3X-3-59403a2.hex.zip]()~ ~[betaflight_3.3.0_AG3X-4-9006e84.hex.zip]()~

[jflyper]

LED strip to S/A pad (=TX2) pad. pg mod for OLED display I2C bus initialization. betaflight_3.3.0_AG3X-5-3a09f30.hex.zip

[jflyper]

Rebased onto master, 3.3.0-RC2 equivalent firmware. ~[betaflight_3.3.0_AG3X-6-17abb6c.hex.zip]()~ Taken down due to broken firmware

[coreysnyder]

@jflyper FYI this version released a day ago locks up my board when trying to connect. I was forced to flash this back to the OmnibusF4SD3.3.0RC1

[IsmaFPV]

Same issue here when flashing the latest hex.

[CJ-Davies]

Same issue here, halfway through dismantling my build to access the boot pins on the bottom of the board ;_;

[jflyper]

Folks, my apologies for your inconvenience. I'm traveling atm and can't investigate the problem with the actual board. The problematic firmware was taken down, and will take at least another day or two to fix.

[jflyper]

Okay, problem solved, RC2 equivalent is here. betaflight_3.3.0_AG3X-7-4f554ca.hex.zip

Active regression test will not be performed starting this one.

[coreysnyder]

@jflyper Appreciate it. Are you actually working with the hardware? Do you have a paper/digital sketch of how you're hooking everything up? I'm currently working on the wiring diagrams & build video for Airbot so if I can get this figured out I'm able to make materials to help others.

[jflyper]

Beeper is configured, but not assigned.

betaflight_3.3.0_AG3X-8-8fa067e.hex.zip

To use this facility to drive an actual beeper, you will need one of the followings.

1. External MOSFET switch for self activating beeper/buzzer (the one that beeps only by applying an appropriate voltage at + and -.
2. A buzzer unit, such as http://www.mateksys.com/?portfolio=dbuz5v or similar level triggered buzzer.

To activate it as a level I/O, pick a pin and assign it as a beeper resource. For example, M7 pad (PB14) is a good candidate.

resource beeper b14

Connect selected pad to buzzer's signal pad. For Mateksys unit mentioned above, "B-" is the signal pad.

You may need to adjust the polarity of the signal.

set beeper_inversion = OFF # if your beeper beeps when it supposed to be silent
set beeper_inversion = ON # default

EDIT This is the circuit used for testing.

[jflyper]

@coreysnyder

• Connection in the "function test" comment has been tested to work.
• Did you see the pin function map in the first comment?

This is my setup. Wire jungle has been cleaned up as development is almost over; it is wired for external beeper test.

[jflyper]

This is similar to what it looked like a week ago.

[jflyper]

@coreysnyder I will rely on your skill to do the flyable one 🤣

[jflyper]

RC3 equivalent betaflight_3.3.0_AG3X-9-cc8254e.hex.zip

[jflyper]

3.3.0 Release betaflight_3.3.0_AG3X-10-5cdb095.hex.zip

[coreysnyder]

@jflyper Man.. your picture with all your wiring... That looks intense! If smoke came out of the board.. I'd be staring at that for an hour trying to figure out where I mis-wired something. I assume you have a pretty standard setup that doesn't change much from board to board? Kudos to you for putting in the hard work to help figure this stuff out.

[jflyper]

3.3.1 Release betaflight_3.3.1_AG3X-f4c6331.hex.zip

3.4 master as of 2018-04-04 betaflight_3.4.0_AG3X-20180405-415e7bb.hex.zip

[Princefpv]

does this hex have the 3D fix in it or can i use the latest 3.4 omnibusf4sd

[juanquy]

Hi I recently got and AG32F7 from http://readytoflyquads.com, board alignment is wrong on default config PITCH and YAW are wrong (inverted), ROLL is ok. so setting ROLL to 180 fix the issue. Any ideas if this is a software issue? anyone reporting the same issue?, or this board came hardware defective? regards JC