Betaflight V4.3+ problem FRSKY SPI

[chucky-whiskers]

Describe the bug

When I try to update the FC to v: 4.3 from 4.2.11 on my HappyModel Crux 35, the SPI receiver has issues with D16/D8 protocol within the newer firmwares. The RX signal flashes with the red signal loss LED indicator light. When the LED is lit, the signal is normal. When it flashes off, there is no signal. I'm unsure whether or not this is the right place for this request, but the firmware target is MATEKF411RX. This is a major bug considering I needed to revert to such an older firmware version for a relatively new FC.

To Reproduce

1. With CrazybeeF4FR flight controller, run Zadig to update driver to current US version of WinUSB.
2. Run ImpulseRC Driver Fixer to fix the driver issue preventing Betaflight from opening serial port.
3. Flash latest firmware (4.3+) for target: MATEKF411RX
4. In "Receiver" tab of Betaflight, set to SPI receiver and FRSKY "X" protocol
5. Using latest stable version of EdgeTX, bind in FRSKY D16 mode (channels 1-8 telemetry on, channels 9-16 telemetry off), bind receiver using "Bind Receiver" button in current (Aug 8, 2022 - version 10.8.0) stable version of Betaflight.
6. Observe channel signal values.

Expected behavior

intermittent signal loss and reestablishment in approximately 1 second pulses back and forth.

Configurator version

10.8.0

Flight controller configuration

# diff

# version
# Betaflight / STM32F411 (S411) 4.3.1 Jul 13 2022 / 03:32:52 (8d4f005) MSP API: 1.44
# config: manufacturer_id: MTKS, board_name: MATEKF411RX, version: edcd244b, date: 2022-06-29T02:24:46Z

# start the command batch
batch start

board_name MATEKF411RX
manufacturer_id MTKS

# name: CRUX35

# resources
resource MOTOR 1 B08
resource MOTOR 2 B07
resource MOTOR 3 B06
resource MOTOR 4 B10

# dma
dma ADC 1 0
# ADC 1: DMA2 Stream 0 Channel 0

# feature
feature -RX_PARALLEL_PWM
feature MOTOR_STOP
feature LED_STRIP

# serial
serial 1 2048 115200 57600 0 115200

# map
map TAER1234

# aux
aux 0 0 0 1700 2100 0 0
aux 1 1 1 1700 2100 0 0
aux 2 2 1 1300 1700 0 0

# adjrange
adjrange 0 0 2 900 1300 25 2 0 0
adjrange 1 0 2 1300 1700 25 2 0 0

# vtxtable
vtxtable bands 6
vtxtable channels 8
vtxtable band 1 BOSCAM_A A FACTORY 5865 5845 5825 5805 5785 5765 5745 5725
vtxtable band 2 BOSCAM_B B FACTORY 5733 5752 5771 5790 5809 5828 5847 5866
vtxtable band 3 BOSCAM_E E FACTORY 5705 5685 5665 5645 5885 5905 5925 5945
vtxtable band 4 FATSHARK F FACTORY 5740 5760 5780 5800 5820 5840 5860 5880
vtxtable band 5 RACEBAND R FACTORY 5658 5695 5732 5769 5806 5843 5880 5917
vtxtable band 6 LOWRACE  L FACTORY 5333 5373 5413 5453 5493 5533 5573 5613
vtxtable powerlevels 5
vtxtable powervalues 1 2 14 20 26
vtxtable powerlabels 0 RCE 25 100 400

# master
set dyn_notch_count = 1
set dyn_notch_q = 250
set acc_calibration = 6,-3,19,1
set mag_hardware = NONE
set baro_hardware = NONE
set serialrx_provider = SBUS
set dshot_bidir = ON
set motor_pwm_protocol = DSHOT300
set motor_poles = 12
set align_board_yaw = -45
set ibata_scale = 470
set yaw_motors_reversed = ON
set small_angle = 180
set osd_rssi_pos = 2082
set osd_tim_1_pos = 2454
set osd_tim_2_pos = 373
set osd_flymode_pos = 2103
set osd_throttle_pos = 388
set osd_vtx_channel_pos = 2132
set osd_current_pos = 2369
set osd_mah_drawn_pos = 2400
set osd_craft_name_pos = 427
set osd_avg_cell_voltage_pos = 2433
set osd_core_temp_pos = 406
set vtx_band = 5
set vtx_channel = 6
set vtx_power = 5
set vtx_freq = 5843
set frsky_spi_tx_id = 37,102,0
set frsky_spi_offset = -37
set frsky_spi_bind_hop_data = 6,114,224,99,209,84,194,69,179,54,164,39,149,24,136,9,119,229,104,214,89,199,74,184,59,169,44,154,29,139,14,124,234,109,219,94,204,79,189,64,174,49,159,34,144,19,129,0,0,0
set gyro_1_sensor_align = DEFAULT
set gyro_1_align_yaw = 900
set name = CRUX35

profile 1

# profile 1
set p_pitch = 50
set d_pitch = 43
set p_roll = 53
set i_roll = 95
set d_roll = 41
set p_yaw = 55
set i_yaw = 95
set d_min_roll = 33
set d_min_pitch = 35

rateprofile 0

# end the command batch
batch end

#

Add any other context about the problem that you think might be relevant here

sometimes my TX16S will not bind at all to the FC unless I revert to 4.2.11