#Not able/ don't know how to flash 4 in 1 Zorro and having many problems binding Zorro to spi reciver
165 messages · Page 1 of 1 (latest)
The Ranger is a 3.x device, so you need a 3.x-compatible betaflight firmware on the Tiny ape
!spi
https://www.expresslrs.org/3.0/hardware/spi-receivers/
Flight controllers with built-in ELRS SPI receivers are not flashed using ELRS Configurator, the ELRS firmware is "baked in" to Betaflight. Thus to update your ELRS firmware, you'll need to flash the latest version of Betaflight for your FC. Betaflight 4.3.x is compatible with ELRS v2.x.x, and Betaflight 4.4.x is compatible with ELRS v3.x.x.
To set a binding phrase on a SPI receiver, enter it here and paste the resulting code in the Betaflight CLI: https://www.expresslrs.org/3.0/hardware/spi-receivers/#binding-phrase
how do i flash the firmware on the tiny ape to 3.x
your Zorro, since it's a 4-in-1 doesn't really matter in this case.. you just have to set up the model so it uses the ranger instead of the 4-in-1
I have external rf set to crsf and internal rf off
the lastest firmware option is 4.3.2
becaause you'll need betaflight configurator 10.9.0-RC
I'd recommend using the Portable package. Extract it into a folder and execute the Configurator from there
lol yeah i realized that just now, i have betaflight 10.9 and did the load firmware online option
ok I tried to flash the tiny ape with betaflight 4.4 but its saying failed to open usb
use Impulse RC driver fixer or zadig driver fixer
okkk lets go it flashed
so it flashed but then when I plugged it back in it gave me a warning that I didn't have an output motor protocal selected
so i selected dshot 600 because i assume that would work
dshot 300
and you didn't saved a diff all dump from the old config?
no
this will mean you'll have to reconfigure it from scratch or you'll have to seek factory diff all dump
as in just the beta flight settings?
yes
so what exactly should I do from here
i set the motor protocol to dshot 300 but thats it
since you didn't save a diff all dump, acquire that first and apply it into this fc
how do i do that
copy-paste the content of this text file into the CLI tab, then press enter
type in save then press enter
Binding procedures for the Ranger and this SPI elrs AIO is here:
https://www.expresslrs.org/3.0/hardware/spi-receivers/
on the CLI tab, first execute the command set expresslrs_uid=0
press enter
type save again, and press enter
this set of commands clear the set binding phrase from the factory so you can either set your own or bind the tx and rx manually
it says theres errors in the batch
which particular errors?
###ERROR IN batch: ERRORS WERE DETECTED - PLEASE REVIEW BEFORE CONTINUING###
I mean which commands cause the errors?
can you copy-paste the content of the window into a file and upload it here?
you can ignore those errors for the most part..
do set expresslrs_uid = 0 press enter
then type saveand press enter again
did that
did it save and rebooted the FC?
yeah
then you should be able to bind now, following the guide in the SPI receivers page
well the gyro is not working now
its not showing the quad moving at all
and wont let me test motors
no gyro and accel icon up-top?
noope
before I started this entire process ( flashing to 4.4) it did
when you flashed to 4.4, zilch?
the gyro was working fine before flashing to 4.4
okay.. disconnect and go to firmware flasher, select the recent RC and the right target betafpvF4sx1280
have all of that selected
copy the settings from this screenshot aside from the version and the target/board
we will be reflashing the FC
ok succesful flash
do you have the gyro and accel after you "Apply custom defaults"?
nope
I'm not very familiar with how @fervent laurel does the DMA setups..
can you try reflashing 4.3.1 just to put it back to working order?
can you go into betaflight configurator CLI tab and execute status please
MCU F411 Clock=108MHz (PLLP-HSE), Vref=3.25V, Core temp=35degC
Stack size: 2048, Stack address: 0x2001fff0
Configuration: CONFIGURED, size: 3777, max available: 16384
Devices detected: SPI:0
Gyros detected: locked
OSD: MAX7456
System Uptime: 94 seconds, Current Time: 2023-01-14T07:03:59.887+00:00
CPU:0%, cycle time: 0, GYRO rate: 0, RX rate: 0, System rate: 9
Voltage: 7 * 0.01V (0S battery - NOT PRESENT)
I2C Errors: 0
Arming disable flags: NOGYRO BOOTGRACE CLI MSP
@naive crane any hint regarding the Locked gyros?
can you paste these into the CLI tab @shadow veldt ?
timer
timer B01 AF2
pin B01: TIM3 CH4 (AF2)
timer B08 AF2
pin B08: TIM4 CH3 (AF2)
timer A00 AF1
pin A00: TIM2 CH1 (AF1)
timer B10 AF1
pin B10: TIM2 CH3 (AF1)
timer B07 AF2
pin B07: TIM4 CH2 (AF2)
timer A08 AF1
pin A08: TIM1 CH1 (AF1)
timer A10 AF1
pin A10: TIM1 CH3 (AF1)
dma
dma SPI_TX 1 NONE
dma SPI_TX 2 NONE
dma SPI_TX 3 NONE
dma SPI_RX 1 NONE
dma SPI_RX 2 NONE
dma SPI_RX 3 NONE
dma ADC 1 0
ADC 1: DMA2 Stream 0 Channel 0
dma ADC 2 NONE
dma ADC 3 NONE
dma UART_TX 1 NONE
dma UART_TX 2 NONE
dma UART_TX 3 NONE
dma UART_TX 4 NONE
dma UART_TX 5 NONE
dma UART_TX 6 NONE
dma UART_TX 7 NONE
dma UART_TX 8 NONE
dma UART_RX 1 NONE
dma UART_RX 2 NONE
dma UART_RX 3 NONE
dma UART_RX 4 NONE
dma UART_RX 5 NONE
dma UART_RX 6 NONE
dma UART_RX 7 NONE
dma UART_RX 8 NONE
dma pin B01 0
pin B01: DMA1 Stream 2 Channel 5
dma pin B08 0
pin B08: DMA1 Stream 7 Channel 2
dma pin A00 0
pin A00: DMA1 Stream 5 Channel 3
dma pin B10 0
pin B10: DMA1 Stream 1 Channel 3
dma pin B07 0
pin B07: DMA1 Stream 3 Channel 2
dma pin A08 0
pin A08: DMA2 Stream 6 Channel 0
dma pin A10 0
pin A10: DMA2 Stream 6 Channel 0
save
did the configurator rebooted?
yes
connect back to betaflight configurator and see whether you got your gyro back
nope, still no gyro
The problem with these new targets is they are custom binaries that support specific gyros. I think wrong target has been flashed that doesnt support that particular gyro type, and the manufacturer flashes a custom hex with gyro drivers compiled in. I'd ask the manufacturer of the aio to provide a 4.4 hex with the diff
so what exactly would i say to them
Do you have any documentation of that AIO? BF target and gyro type would be nice
FC&ESC:F411 1-3S 15A FC(Built-in ELRS 2.4G receiver)
not sure where to find gyro type or if its even listed
That doesn't say much about the bf target unfortunately
shares target with BETAFPVF4SX1280
but doesn't seem to have info on which exact gyro it uses
DarwinFPV 15A 1-3S F411 AIO great for Ultralight and Whoop builds! Capacitor Pre-soldered for convenience! ESC Specifications Input voltage: 3.7 ~ 13V DCIN(1 ~ 3 6slipo) Constant current: 15A Peak current: 17A BEC Output: No Mcu: 48mhz efm8bb21f16g protocol: dshot/oneshot/multishot blheli_s firmware target: SH-50 Telem
says mpu6500 or icm20689
It says
BetaFlight target: MATEKF411
That doesn't make sense cause this target doesn't have elrs drivers.
yeah, that fc page is whacked.. different from the fc on the tiny ape
@supple delta could you check the list of betaflight targets with 'darwin' in the name?
there's DarwinF4sx1280HD which might be better suited..
theres also darwinf411
DarwinF411
and DarwinF722HD
Yup, seems like Darwin target doesn't support this gyro, but darwinHD does.
so this should work?
DarwinF4sx1280HD
Yes
should i flash it with DarwinF4sx1280HD?
@shadow veldt do you have experience with flashing bf target
Do you know what unified config is?
i dont
Basically you need to be 101% sure you are applying custom defaults after the flash
ok so flash it with DarwinF4sx1280HD and apply custom defaults one the flash finishes?
yes
Fun, new, and the only way to flash #Betaflight 4.4+, and also KAACK mod. Diving deep into Betaflight clouds with our regular expert over the line.
Support me on Patreon:
https://www.patreon.com/limon_fpv
00:00 - Intro
00:56 - FC not being recognized?
01:36 - Flashing basics
02:28 - New stuff - cloud building
03:42 - Cloud errors
04:38 - Flash...
Watch this video please, it's a solid resource by one of the bf devs
although, i still cant test motors
do you now have stick movements in betaflight receiver tab?
testing motors, imho, is still at the end of the usual process for me..
you may have working motors, but if your receiver is still not bound, you still won't be able to fly.. 😄
now theres no bind receiver button in the receiver tab
were the right settings set?
im pretty sure
are you on 4.3.1 still?
no
or now with 4.4-RC?
on 4.4
go into CLI and execute get expresslrs
done
can you show us the output?
get expresslrs
expresslrs_uid = 0,0,0,0,0,0
Array length: 6
expresslrs_domain = ISM2400
Allowed values: ISM2400, CE2400
expresslrs_rate_index = 0
Allowed range: 0 - 3
expresslrs_switch_mode = WIDE
Allowed values: WIDE, HYBRID
expresslrs_model_id = 255
Allowed range: 0 - 255
@shadow veldt regarding motors, check what motor protocol you have selected in the ui
dshot 300
can you show us a screenshot of the Receiver Tab please..
is it not like this?
You need to copy what @supple delta shown on his screen
And then bind button should appear
lmaoo completley missed changing to spi
You probably have a vanilla board with everything set to default
🎉
how are you testing? is the esc powered?
is a lipo connected?
yes
how are you testing motors?
giving throttle input from my radio with props off
Maybe he needs custom motor mapping....
are you "arming"?
are you doing this while still connected to betaflight configurator?
no
you can't ARM while connected to betaflight configurator (on normal circumstances)
im not connected to betaflight while trying
Also you need to configure arm switch
ok so im not sure how to configure and arm switch on my zorro
ive done it before on a flysky radio but im not sure how to do it now
Yup, once done you'll have to also do it in bf configurator
here's a typical Modes tab setup I use
YOOOO NO WAY IT WORKS NOW