Hi all, I hope I make it clear my problem.
I just bought a Tinyhawk 2 FS BNF wishing to bind it to my TX (EMAX E6 FrSky D8) from the tinyhawk. 
Despite all attempts using different versions of BF (10.5 / 10.6 / 10.8) and different firmware releases as well as different CLIs I am not yet able to control the drone properly. I applied the procedures reported on emax website but no success.
I was able to bind the drone RX to the TX but the system does not work properly.
So far the best result was:
I can see the TX properly working on BF (actually the gas control is not smooth)
I can activate the motor via BF
I can see the flight modes changing on BF using the AUX 1 and 2
I can not arm the drone when disconnected from BF.
Any help would be much appreciated.

.. if I am reading this correctly .. u are bound, you just need to sort out ur channels..
First, in betaflight, (connected to the quad).. when u go to the receiver tab .. you say aux1 /aux2 responds.. when u move the throttle , yaw, pitch, roll.. do the CORRECT channels correspond? You may have to change the line ATER to TAER or whatever the correct one is.. I can’t remember I think the Frsky drop down will help,
Also, go to the modes tab, make sure ur “arm” is activated with the correct switch / channel..
I’m doing a crappy job describing this.. Bardwell has great instruction videos on setting this up proper .
Also, if u used the Emax site u could have easily followed the Tinyhawk instructions .. Emax used the same fc in the th freestyle but it’s set 90% off.. and the motors are changed.. so also make sure when u check the motors individually they also respond in the correct location.. ur 90%there..

Thanks for your reply, it is a kind of messy situation. I tried several combinations ma none is working.
When connected to BF, the receiver shows proper sticks action. But I am missing some flying modes...e.g. I do have ARM, BEEPER, but I miss HORIZON, ANGLE. I will record the tests I did as to have a complete view.
Right now using FB 10.5, customized firmware suggested by EMAX and relevant CLI. I have RX /TX working BUT no action on the drone.
I can not see the motors running and motors do not appear on FB I can not calybrate accelerometer.

Do u mean Betaflight CONFIGURATOR? 10.5? That is the for the computer ..
First update betaflight configurator for the computer.. do NOT update any betaflight (flight controller) firmware.. let’s get things in working order first.. then we can mess it up..
Watch this DONT DO ANYTHING YET.. just watch.. we need to figure out what version of betaflight your flight controller has first..

Thanks, I appreciate and I will have a look...there's always somthing new to learn.
BTW, honestly I have had three FPV drones - build by myself - including a tinyhawk RTF and always succedeed in binding and having them flying in addition I fly a DJI mini 2.
No problems at all with betaflight and flashing firmware.
I really do not understand what the problem is.
I am aware about different versions of BF (pc side) non handling all the firmware release, but I went carefully through EMAX procedures and other website. 
Well, I have to admit i made the mistake of NOT saving the original configuration of the Freestyle a shipped as I was so sure I could manage it. But, shit happens. So here I am.
Last try...BF 10.8, firmware BF 4.1.3 for MATEKF11RX (CLI tells betaflight / STM32F411 (S411) 4.3.1 Jul 13 2022 / 03:32:52 (8d4f005) MSP API: 1.44).
Binded, troubles in connecting TX/RX, motors works with BF, acc works. Beeper, arming switch (AUX 2) ok, flight mode on aux 1 switches work,
Hope I made myself clear.

Ok.. cool .. sorry, wasn’t sure of how familiar I were with this stuff..
Double check the fc orientation, and the ATER / EATR ect. .. like I said Emax used these in different configurations.. the firmware target is correct..
Same with modes..

I am getting really "pissed off" not getting this stupid thing working.
AETR is ok. I really do not understand why drone isn't arming...again motors run under BF control.
Should I try flashing back form the beginning a BNF firmware?
Let me ask a silly question just in case. Is it mandatory to bind AFTER flashing a new firmware...am I right or not?

Not silly, I think u do with the spi RXs..but If u have channels and six modes responding in betaflight after updating ur bound..
Out of curiosity. .. check ur modes tab.. see if u have “flip after crash”/turtlemode turned on?
What controller are u using? And have u got any other d-8 quads flying on it??

Problem solved. I flashed BF firm 4.2.x using BF 10..8.0 and last working CLI and I was able to fly.
Still need a good tuning and fix some discrepancies in flight modes listing.

Glad u go it sorted out..
I’m still curious why it wouldn’t arm? Maybe a bug? Who knows?…

I  have read on the web it seems that SPI receiver FrSky D8 mode will not bind in BF 4.3. I am a little bit sceptic about it and I am going to do some tests but this time I will save config before .

You and me BOTH!! I have a bunch of whoops with d-8 spi RXs… and that’s one reason I didn’t update my taranis ..
Keep us posted on ur findings.. maybe start a thread for someone having binding issues on d8 w/ bf 4.3.*.
I heard of spi ELRS having 4.3.* issues but not D-8 (Frsky)

Ok. I noticed something that looks strange to me in the CLI dump all text.
When flashing, I selected MATEKF411RX. This should be the board name.
In the CLI text I noticed a text line like this:
Betaflight / STM32F411 (S411) 4.2.0 Jun 14 2020 / 03:04:43 (8f2d21460) MSP API: 1.43
As BF 10.5 DOES not have MATEKF411 under its list but it has STM32F411 could it be possible to flash matek FC with STM32F411 firmware?

.. yes, I have seen people online flash very similar or similarity labeled firmware on the “not correct” fc..
I have a couple unopened Emax ez pro rtf setups that came a couple weeks ago.. I will pop one open.. check the firmware target for you…
I would start with configurator 10.8.. if u want I may have my old timyhawk freestyle cli dumps that I KNOW are good.. just have to make sure u have the same betaflight version on ur fc..
I also have toasted th FCs and will try to install 4.3.1.. see if I can bind

Yes that is the correct firmware target..but it shows more in the betaflight screen..I updated this (damaged) fc, but I had to physically enter it into DFU my pushing the boot loader button and plugging in..I’ve only updated to the next level.. i tried 4.3.1 but it failed..
I can’t do SH*T at the moment, just lost power at the house..