Hi, my tinyhawk doesnt comunicate with a xm+ receiver, i connected the xm+ to another fc and its binding and working correctly, but on the TH2 doesnt recognized it. I also tried conecting it to the RX1 terminal on the board, but the light on the receiver doesnt light up green. I flashed the fc and it still doesnt work, but now i cant even conect to the integrated receiver of the drone. 
Can somebody hep me please!!

Thanks

Can you please run both the "dump" and "diff all" commands in the Betaflight Configurator CLI tab and copy/paste the results back here.

Please also post some good clear photos of the actual wiring and connections between the XM+ and flight controller.

I did both comands with the receiver on and the transmitter on.

this is the wiring

Your wiring and your Betaflight settings all look to be correct.

Use a multimeter to check that you don't have a short between the yellow SBUS wire connection and either the 5V or GND connections of the XM+.

Are you getting a green LED on the XM+ when you switch on your transmitter?

It is very strange, because when i connect the xm+ to another drone it binds up perfectly and the led shines green, and on betaflight i can see it working perfectly, but when i conect it to the Tinyhawk, the light shines solid red. I also tried with another sbus receiver and it didnt bind to the controller as well if conected to the TH2. With a multimeter i checked and there is no short in the XM+ nor the FC. 
Also when i put back on the stock antenna and put the cofiguration stock, when i put the drone in bind mode the lights dont light up as they should and the controller doesnt bind.
The board havent had any strong crash or something, and it has just a couple of weeks of use.
I even removed the VTX in case it was doing something weird with the uarts.
I dont know how to fix this

OK, so this  appears to be a binding issue of some kind with the XM+ and not a wiring or Betaflight configuration issue.

The red / green LED status on the XM+ should not be affected by any configuration issues on the FC. Regardless of the FC connection status, the LED on the XM+ should still illuminate green when the transmitter that has been bound to it is switched on. Try moving the transmitter at least a metre or two away from the XM+ and see if you then get a green LED on the XM+

I tried to do that, but with no results. I think it may have something to do with fc, because the xm+ works perfectly with other fc. Also when connected to the TH the receiver wont even go into bind mode when i power it up while pressing the button. 
And why dont the spi receiver go into bind mode either?

edit: i realized that when i press the bind button on all in one board it freezes, at least on betaflight, thats why the red light dont flashes as it should

(29-Nov-2021, 01:10 AM)MatiMolfino Wrote: edit: i realized that when i press the bind button on all in one board it freezes, at least on betaflight, thats why the red light dont flashes as it should

I have not looked at the TH2 board layout, but does it have a "Boot" button too?  Betaflight should not freeze when you go to bind.
Could you possibly be pushing the wrong button ?

Just a possibility

Scott

(29-Nov-2021, 01:49 AM)Scott_M Wrote: I have not looked at the TH2 board layout, but does it have a "Boot" button too?  Betaflight should not freeze when you go to bind.
Could you possibly be pushing the wrong button ?

Just a possibility

Sott

no, look, i just flashed the board and dump the emax file, and the cpu load is at 100% literally doing nothing

The cpu on the board is still 100% so i run the tasks comand:

# tasks
Task list             rate/hz  max/us  avg/us maxload avgload     total/ms
00 - (         SYSTEM)      6       3       1    0.5%    0.5%         0
01 - (         SYSTEM)    489       4       1    0.6%    0.5%        73
02 - (       GYRO/PID)   7267     102      83   74.6%   60.8%     80729
03 - (            ACC)    332      15      10    0.9%    0.8%       483
04 - (       ATTITUDE)    167      17      12    0.7%    0.7%       276
05 - (             RX)     32      54      49    0.6%    0.6%       224
06 - (         SERIAL)     16    1458       2    2.8%    0.5%      1073
07 - (       DISPATCH)    491       3       1    0.6%    0.5%        57
08 - (BATTERY_VOLTAGE)     20       4       2    0.5%    0.5%         5
10 - ( BATTERY_ALERTS)      2       4       2    0.5%    0.5%         0
11 - (         BEEPER)     16       4       2    0.5%    0.5%         3
21 - (            OSD)      9     103      51    0.5%    0.5%        67
23 - (            CMS)      9       3       2    0.5%    0.5%         2
24 - (        VTXCTRL)     20       0       1    0.0%    0.5%         0
25 - (        CAMCTRL)     23       0       0    0.0%    0.0%         0
27 - (    ADCINTERNAL)     23       0       0    0.0%    0.0%         0
28 - (       PINIOBOX)     20       0       0    0.0%    0.0%         0
RX Check Function                  57      37                       171
Total (excluding SERIAL)                        81.0%   67.4%

The drone is on stock setting, using the d8 internal receiver, and when i use the bind comand this happens

# bind_rx_spi
###ERROR: UNKNOWN COMMAND, TRY 'HELP'###

edit: when i use bind_rx it goes to bind mode same as when i press the button and the fc stops comunicating with betaflight.

To use the internal SPI receiver you need to set the serial receiver provider back to an SPI receiver, or run the following commands. Unless that is done the "bind_rx" command won't work.


Regarding the 100% CPU utilisation, there is something wrong there. I've compared the dump you attached in post #3 with the stock dump for a TinyHawk II Freestyle and there are no differences that would cause that type of behaviour. Did you re-flash the FC with the "Full chip erase" option enabled? If you did then it looks like you have some kind of weird hardware issue with the FC that I'm not sure you can do anything about other than to replace the FC.

Still no luck with that code. I already contacted the seller to ask to return the drone For some reason now the VTX went down with a puff of smoke.
 Do you have suggestion for my next 2.5~3 inch drone?? I really liked the TH2 freestyle tho

I LOVE my TH Freestyle.. I think the only original part is the battery strap.. Check out my thread on RDQforum Tinyhawk freestyle upgrades..I’ve got it now on 3s, 400w vtx, crossfire, and cadxx baby ratel ..(soon to have HDzero nano and sharkbyte)…
I had several RXs on it from RXSR, Emax D-8, and now crossfire..even if u lost a uart, there are breakout pads on the bottom of that fc, they are a Bit*h to solder to, but it can be done