Dear, I'm new on this forum, I've just built my first 5in drone based (more or less) on instructions of Bacon Ninja

 

(thank you for that it was great tutorial) so I do have: 
- SpeedyBee F405 V3 Stack
- SpeedyBee TX800 Analog VTX
- Foxeer T-Rex Micro 1500TVL
- SKYZONE SKY04X V2 OLED

I did first flight (without goggles), hovered a bit and it looks good... 
but so far I couldn't achieve any successes with BF OSD and it's simply not displaying any information from OSD chip (Foxer OSD is there)

So yes in BF configuration:
- I do have enabled OSD
- I can see list of profiles in OSD configuration
- I tried pal/secam/auto


one bit of info which maybe helpful, 
I was not able to upload fonts via font manager, it always stuck and it's doing nothing (with LiPo connected first than USB)
 
please see pics of wiring and dump from CLI
i'm loosing hopes, maybe you will be able to find something which I cannot see.
 

Thank you, 
Mag

The SpeedyBee F405 V3 FC is plagued with design flaws, one of which is an SPI bus conflict that means you can't have OSD switched on and Blackbox Logging switched on at the same time. I see that you have the Blackbox logging set to "SDCARD". Set that to "No Logging" and click the "Save and Reboot" button. Then see if your OSD is working as expected.

Wow! This was fast, thank you very much you saved me!!!, it works like a charm! Also fixed the problem with Uploading Fonts!
Now I need to think how to fix blackbox in such setup but this is for different story.

I'm thinking if I can disable this during the flight let's say temporarily disable OSD via radio and enable blackbox logging, I'm not brave enough to do whole flight without OSD

For reference for future generations:
https://github.com/betaflight/betaflight/issues/12583

Yeah. SpeedyBee made a complete balls up when they designed that FC. It also has a dma/timer conflict issue which causes problems with bidirectional DSHOT. I think they had a trainee design that FC without an experienced engineer then bothering to peer review the work.

As for flipping between blackbox logging and OSD, you can try what you suggested and see if it works. Otherwise you will just have to do it manually in the field using a laptop or using the SpeedyBee app on a mobile device. Other than that, it will be a new (different) FC.

Ironically, SpeedyBee have just released a V4 of the same FC which apparently fixes all the design flaws that are in the V3. Maybe they should be giving a V4 FC for free to people who bought the V3.

Quick update here, my idea with switching blackbox vs osd during the fly won't work I think.
While I can control this via aux/modes via radio. I still need to have enabled SD Card logging in my setup/configuration and it seems that this is not something I can control easily.

I have also contacted SpeedyBee to see how they see it, their answer was as below:

Quote:If you are using betaflight 4.4.2 firmware, please downgrade the firmware version to 4.4.0 or below first.
Currently, when using the 4.4.2 version of the firmware, there is an issue where the OSD on the flight controller will not display properly after inserting an SD card. Also, Please try to set the OSD format to PAL. Try to reduce the recording speed of the black box (suggested to reduce it to 1/4 or 1/8).

I didn't try that yet but maybe someone will find this informative

I don't think SpeedyBee's suggestion is going to work. All of those "workarounds" have already been discussed on Discord and none of them appear to work. If resolving the issue in the firmware was that simple then the Betaflight devs would have already fixed the problem (which has been an issue since March this year) in a Betaflight maintenance release. You can see the comments made by Steve Evans (an experienced embedded systems developer and a core member of the Betaflight dev team) in that GitHub issue you linked to, and especially the last comment he made (HERE) that it's not possible to fix the issue without changing the architecture of the Betaflight code to use polled SPI access instead of DMA, which he clearly stated they're not going to do.

Either way, if you do try SpeedyBee's suggestions then it would be good to hear what the results of trying those are.