hi, my old succex-e f4 V1 is damaged and i ordered a new one on ebay. unfortunately that*s version 2.2 which has another pinout. it was not s easy to find out how i had to compile iNav with target BETAFLIGHT F4 for V1. so since i have a complete other pinout in V2.2 i ask in advance: does anyone has this FC and compiled iNav for it and with which changes?

regards!

While I do not have this board, I did find the following:

https://github.com/iNavFlight/inav-confi...ssues/1057

It looks like there is a target that should work, worth a try anyway. Would attach a tether to the aircraft...just incase it tries to run away.

(27-Nov-2021, 05:20 AM)kaitylynn Wrote: While I do not have this board, I did find the following:

https://github.com/iNavFlight/inav-confi...ssues/1057

It looks like there is a target that should work, worth a try anyway.  Would attach a tether to the aircraft...just incase it tries to run away.

hi, thanks for your message but i already found that post by myself; it deals with the V2.1 which is also different from 2.2

here are pictures of the 3: 


from, left to right: V1, V2.1, V2.2

The reality is that iNav devs do not receive any cooperation from iFlight which is why they do not provide official targets for these boards.

You can make an iNav Target yourself using pinout info from Betaflight targets. Its not really that hard and I have done this once myself.

Here is an example:

Just keep in mind that if you do go down the route of creating your own target fir the iFlight FC then it will be something that won't have gone through any official testing by the INAV devs so it will be down to you to test and find out if there are any issues, and hopefully not while your model is miles away from you.

If it was me I would just keep that FC for a non INAV build and get a different FC that is officially supported by INAV such as one of the Matek FC's.

(27-Nov-2021, 11:58 AM)SnowLeopardFPV Wrote: Just keep in mind that if you do go down the route of creating your own target fir the iFlight FC then it will be something that won't have gone through any official testing by the INAV devs so it will be down to you to test and find out if there are any issues, and hopefully not while your model is miles away from you.

If it was me I would just keep that FC for a non INAV build and get a different FC that is officially supported by INAV such as one of the Matek FC's.

@kafie: thank you very much for that enlightening clip
@SnowLeopardFPV: Hi, nice to hear of you again. Your point is a good one. Otherwise if you remember (talking to you helped a lot) my build with the V1 of this FC worked very well and making a custom inav target was important for my learning curve. I ordered the same FC in V1 again from china but got V2. So FCs are very expensive now and before i spend so much money again and have to wait another month to get another FC i think i'll try my luck. I just thought it would be a good idea to ask here first in case somebody else reads this here who already worked out a target for this FC.

Fun fact: iflight seems not only lacks in supporting INAV but also themselves. When i asked the iflight support why the wiring diagram for the V2.2 FC on iflights homepage is the one for V2.1 i got this answer:

Quote:Hi,
Sorry about that.My colleague still don't update the V2.2.
I have told her to update it.

There are too many topics on here so there is virtually no chance that I remember a topic from more than few weeks ago unless I'm reminded  

We see quite a number of issues with iFlight electronics on here. It's why I won't personally but iFlight FC's or ESCs.

(27-Nov-2021, 07:56 PM)SnowLeopardFPV Wrote: There are too many topics on here so there is virtually no chance that I remember a topic from more than few weeks ago unless I'm reminded  

We see quite a number of issues with iFlight electronics on here. It's why I won't personally but iFlight FC's or ESCs.

Yes of course but i hope you at least noticed the credit in my blog article i linked above. And be sure,with my next LR build i won't choose iflight again, but if you like to learn it the hard way, it's a good start

hmmm maybe i should have listened to you.


this was the version info of the stock settings:
# Betaflight / STM32F405 (S405) 4.2.9 Apr 27 2021 / 19:33:01 (e097f4ab7) MSP API: 1.43
# config: manufacturer_id: IFRC, board_name: IFLIGHT_F405_TWING, version: bc19b7dc, date: 2020-04-01T04:37:12Z

according to the product info, target is "IFRC/BASE_F4" which is a target i can't find in the betaflight configurator. first thing i tried is to flash inav BETAFLIGHTF4 target. when i try to do the accellerometer calitration and hold the board with the arrow down the configurator calibrates that as arrow up and vide versa, also arrow left as arrow right and vice versa. i will try around a bit but it seems to be complicated, unfortunately i also don't have a clue witch betaflight target to flash back - also when i try one, betaflight confioigurator tells me "No response from the boot loader, programming failed". oh my oh my.

If you are accessing the FC in DFU mode, the bootloader should be able to connect. The error in your post is one I have only seen when I have not entered the firmware flasher in DFU.

When you have Betaflight Configurator open, the button on the FC pressed and then plug in the USB cable...the upper right hand corner should read DFU. If it is displaying any COM* port, you are not achieving a boot into DFU.

(28-Nov-2021, 08:55 PM)Cyfly Wrote: hmmm maybe i should have listened to you.


this was the version info of the stock settings:
# Betaflight / STM32F405 (S405) 4.2.9 Apr 27 2021 / 19:33:01 (e097f4ab7) MSP API: 1.43
# config: manufacturer_id: IFRC, board_name: IFLIGHT_F405_TWING, version: bc19b7dc, date: 2020-04-01T04:37:12Z

according to the product info, target is "IFRC/BASE_F4" which is a target i can't find in the betaflight configurator. first thing i tried is to flash inav BETAFLIGHTF4 target. when i try to do the accellerometer calitration and hold the board with the arrow down the configurator calibrates that as arrow up and vide versa, also arrow left as arrow right and vice versa. i will try around a bit but it seems to be complicated, unfortunately i also don't have a clue witch betaflight target to flash back - also when i try one, betaflight confioigurator tells me "No response from the boot loader, programming failed". oh my oh my.

There is no such target "IFRC/BASE_F4" in Betaflight and I assume iFlight has made a typo on the product listing.

Here are a list of all targets in Betaflight and IFRC-IFLIGHT_F405_TWING does exist and is available via the Configurator: https://github.com/betaflight/unified-ta...gs/default



Try connecting in DFU or Bootloader mode as Kaity suggested and then try flashing the IFRC-IFLIGHT_F405_TWING firmware and do not forget to apply custom defaults.

(28-Nov-2021, 09:11 PM)kaitylynn Wrote: If you are accessing the FC in DFU mode, the bootloader should be able to connect.  The error in your post is one I have only seen when I have not entered the firmware flasher in DFU.

When you have Betaflight Configurator open, the button on the FC pressed and then plug in the USB cable...the upper right hand corner should read DFU.  If it is displaying any COM* port, you are not achieving a boot into DFU.

dear kaity i alread did that, no luck with that target, one of the other was better but also not ideal. i am back to playing with the inav target.h now. stucked with the i2c wiring. don't know whih pins are te ones for sda/scl. the ones i got out of my backed up betafight dump are not working, it is of course also possible that there is another error. what d you do i you don't know which pin number you have to assign?

Betaflight's config suggests B08 and B09 for his particular board:

Quote:resource I2C_SCL 1 B08

resource I2C_SDA 1 B09

Based on that the iNav target setup for this board in the target.h file should be:

Quote:#define I2C1_SCL                PB8

#define I2C1_SDA                PB9

There are other pins that have I2C capabilities listed in the specs sheet but the question is which ones are actually broken out on the board: https://www.st.com/resource/en/datasheet...f405rg.pdf

hi kafie, thank you! i already tried it with pb8/9, but for I2C2. in inavs BETAFLIGHTF4 target there is only I2C2. should i change all this instances to I2C1? does that matter? what stands the 1/2 for?

an hour later ... in target.h, i changed USE_I2C_DEVICE_2 into USE_I2C_DEVICE_1 (i assume the 1/2 is the number of the deviice) and generally replaced I2C2 with I2C1; baro and magnetometer are still not working, i think i will try to check the hardware somehow.

also i found out that i can change the wrong default accelerometer alignment if i change
IMU_MPU6000_ALIGN to CW0DEG

iflight meanwhile wrote to me: the betaflight - target for this board is IFLIGHT_SUCCEX_E_F4. but they changed a lot with resource mapping, so as you wrote the i2c settings are as you wrote, while in the betaflight target they are different.

The I2C1 or I2C2 definitions for the pins are based on the STM32 chip you are using and I will assume this is hardcoded as per the documentation:



In the above image I have highlighted in yellow the pins in question.

You mentioned earlier that the the stock setup showed "board_name: IFLIGHT_F405_TWING".

The pins I suggested i.e. the PB8 and PB9 are based on the Betaflight "IFRC-IFLIGHT_F405_TWING" target definition which I assume are properly broken out and mapped as I2C1_SCL and I2C1_SDA respectively. 

If you are now telling me that the board is using the "IFRC-IFLIGHT_SUCCEX_E_F4" target in Betaflight then you will need to setup your iNav target.h to map the resources I2C2_SCL to PB10 and I2C2_SDA to PB11 respectively.

What barometer and magnetometer are you using? Did you test them with Betaflight to check if they actually work?