Skip to content

Conversation

shellixyz
Copy link
Collaborator

@shellixyz shellixyz commented Mar 19, 2019

Closes #4262

@shellixyz shellixyz added this to the 2.2 milestone Mar 19, 2019
@dentex
Copy link

dentex commented Mar 19, 2019

@shellixyz Hi. If i'm not missing something, it's the same FC as this one: #4464

@shellixyz
Copy link
Collaborator Author

@dentex ehm ok maybe yes. The MambaF405 doesn't need anything to be changed compared to the FF4OSD target ? I don't have one I can't check anything. The analog channels are different between the two target files. Also the FF4OSD have a SS configured. And maybe other stuff different I didn't check everything.

@dentex
Copy link

dentex commented Mar 19, 2019

@shellixyz Yes, there are small differences between the two target files we have. Incidentally, for the one that has been already merged (32ca1a9), a couple of pins must be swapped, as per this comment: #4262 (comment)
I mean, the BF's target for the MambaF405 is the FURYF4OSD (that has some switches for other flavours - but not the one in iNav): so I think we are pushing two targets for the same FC.

@shellixyz
Copy link
Collaborator Author

OK so it would just need to be a variant of the FF4OSD then

@dentex
Copy link

dentex commented Mar 19, 2019

In BF it's like this.
Please note that the OSD variant is the Mamba.
Our target isn't set for the FURYF4 (non-OSD) also... So we basically need to only decide how to name the target and resolve those tiny differences... I flashed both and nothing changed... (apart from the two pins I was referencing above).

@shellixyz shellixyz force-pushed the add_MAMBAF405_target branch from 096c551 to 51483c9 Compare March 19, 2019 16:34
@shellixyz
Copy link
Collaborator Author

@dentex Ok, should be good now

@sergeyprokofev
Copy link

sergeyprokofev commented Mar 20, 2019

For Smart Audio if not used PPM. Verified by.
#define USE_SOFTSERIAL1
#define SOFTSERIAL_1_RX_PIN PA1 // or NONE
#define SOFTSERIAL_1_TX_PIN PC9 // FOR Smart Audio if not used PPM
#define SERIAL_PORT_COUNT 5

and (or am i wrong?)
#define MAX_PWM_OUTPUT_PORTS 6 // 4 - morots, softserial, led strip

@digitalentity
Copy link
Member

@shellixyz is this ready?

@shellixyz
Copy link
Collaborator Author

Yes it should be. I don't have a board to test though

@shellixyz shellixyz merged commit 5cab7d9 into iNavFlight:development Mar 26, 2019
@gsixx8
Copy link

gsixx8 commented Apr 25, 2019

@shellixyz I have the F4 Mamba and am trying to get it working correctly with INAV. I would be interested in testing out the version you all are referencing.

@SECOUM
Copy link

SECOUM commented Jun 23, 2019

Hello ,do you know why sbus on mambaf405 2.2 dont Work??
Impossible to connect

@sergeyprokofev
Copy link

I use mambaf405 and r9mm. Protocol f.port. Everything works.

@SECOUM
Copy link

SECOUM commented Jun 24, 2019

Ok ,thancks,i will test it ,on wich pad are you connectyour fport wire??
Any cli change?
If you Can test ,mine with sbus dont Work
I will test fport tonight....you have take inverted or non inverted smartport with your r9mm??

@datamann
Copy link

datamann commented Aug 5, 2019

I just tried to build mambaf405 from development and SBUS and softserial on PPM pad does not work. I tried the build (zip file above) and it works but that build is from an older code base. Did also try FuryF4OSD and SBUS does not work with that one either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants