-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
revoltosd and OmniNXTF4 flash does not show up on Betaflight 4.4 #12643
Comments
Here is the support data for the omninxt4 version Betaflight / STM32F405 (S405) 4.4.1 Apr 9 2023 / 06:39:43 (e43d591) MSP API: 1.45config: YESboard: manufacturer_id: AIRB, board_name: OMNINXT4statusMCU F40X Clock=168MHz (PLLP-HSE), Vref=3.34V, Core temp=42degC flash_infoFlash sectors=256, sectorSize=65536, pagesPerSector=256, pageSize=256, totalSize=16777216 JEDEC ID=0x00ef4018 dump hardwareversionBetaflight / STM32F405 (S405) 4.4.1 Apr 9 2023 / 06:39:43 (e43d591) MSP API: 1.45config: YESstart the command batchbatch start board_name OMNINXT4 resourcesresource BEEPER 1 C13 timertimer B05 AF2 pin B05: TIM3 CH2 (AF2)timer B04 AF2 pin B04: TIM3 CH1 (AF2)timer B00 AF2 pin B00: TIM3 CH3 (AF2)timer B01 AF2 pin B01: TIM3 CH4 (AF2)timer C09 AF3 pin C09: TIM8 CH4 (AF3)timer C08 AF3 pin C08: TIM8 CH3 (AF3)timer B09 AF3 pin B09: TIM11 CH1 (AF3)timer B08 AF3 pin B08: TIM10 CH1 (AF3)timer B07 AF2 pin B07: TIM4 CH2 (AF2)timer A09 AF1 pin A09: TIM1 CH2 (AF1)timer B15 AF9 pin B15: TIM12 CH2 (AF9)timer B06 AF2 pin B06: TIM4 CH1 (AF2)timer A02 AF3 pin A02: TIM9 CH1 (AF3)timer A03 AF3 pin A03: TIM9 CH2 (AF3)timer B10 AF1 pin B10: TIM2 CH3 (AF1)timer B11 AF1 pin B11: TIM2 CH4 (AF1)timer A00 AF2 pin A00: TIM5 CH1 (AF2)timer A01 AF2 pin A01: TIM5 CH2 (AF2)timer C06 AF3 pin C06: TIM8 CH1 (AF3)timer C07 AF3 pin C07: TIM8 CH2 (AF3)timer A10 AF1 pin A10: TIM1 CH3 (AF1)dmadma SPI_MOSI 1 NONE ADC 1: DMA2 Stream 4 Channel 0dma ADC 2 NONE pin B05: DMA1 Stream 5 Channel 5dma pin B04 0 pin B04: DMA1 Stream 4 Channel 5dma pin B00 0 pin B00: DMA1 Stream 7 Channel 5dma pin B01 0 pin B01: DMA1 Stream 2 Channel 5dma pin C09 0 pin C09: DMA2 Stream 7 Channel 7dma pin C08 1 pin C08: DMA2 Stream 4 Channel 7dma pin B09 NONE pin B07: DMA1 Stream 3 Channel 2dma pin A09 0 pin A09: DMA2 Stream 6 Channel 0dma pin B15 NONE pin B06: DMA1 Stream 0 Channel 2dma pin A02 NONE pin B10: DMA1 Stream 1 Channel 3dma pin B11 0 pin B11: DMA1 Stream 7 Channel 3dma pin A00 0 pin A00: DMA1 Stream 2 Channel 6dma pin A01 0 pin A01: DMA1 Stream 4 Channel 6dma pin C06 0 pin C06: DMA2 Stream 2 Channel 0dma pin C07 1 pin C07: DMA2 Stream 3 Channel 7dma pin A10 0 pin A10: DMA2 Stream 6 Channel 0featurefeature -RX_PPM serialserial 20 1 115200 57600 0 115200 masterset gyro_to_use = FIRST end the command batchbatch end |
RevoltOSD: You can add |
Same for OMNINXT4 :) |
Enable show release candidates and enable expert mode and try again. That bug is also resolved in latest configurator |
Great, thanks! Got it working :) |
BTW, its the same issue for the SynergyF4 board. and the fix is the same |
Same error on OMNIBUSF4 board. |
@fireduckfpv OMNIBUSF4 should already work on 4.5 without custom defines |
Add W25Q128FV to OMNINXT4 Fixes: #12643
Add W25Q128FV to REVOLTOSD Fixes: #12643
Add W25Q128FV to OMNINXT4 Fixes: betaflight#12643
Add W25Q128FV to REVOLTOSD Fixes: betaflight#12643
Describe the bug
When flashing 4.4.0 or 4.4.1 on the RevoltOSD and the OmniNXTF4 boards, the flash memory does not show up. when flashing back to 4.3.2, the flash memory is available on both boards.
When flashing the Core only to the revoltosd, the flash memory is available, but when I flash the normal 4.4.1 again, the flash memory is not available.
I have tried adding the different flash memory configs like described in this post for the revoldtosd board without any luck
#12082
Thanks
To Reproduce
Flash BF 4.4
Expected behavior
Flash Memory for Blackbox should be available
Support ID
Flight controller
RevoltOSD / OMNINXTF4
Other components
No response
How are the different components wired up (including port information)
No response
Add any other context about the problem that you think might be relevant here
No response
The text was updated successfully, but these errors were encountered: