MATEK F405-OSD with 1.8RC version matekf405OSD LEDstrip

[artusmuc]

I have tested this firmware with on a new standalone Matek F405OSD connected to a FSHUB-6S via Ribbon cable.

I have made my test first step by step ony connect one of the parts listed:
GY-63 Baro (MS6511) I2C - connect to UART3 -- works fins
GPS-NAZA-Clone - connect to UART1 --- GPS is marked as aktiv - Magno is marked as activ - first test with mago seems to work but "slow reaction"
FrSky XRSB connected to SBUS - works fine - i have to make a new test with telemetry

But LEDstrip WS2812 is not working in the moment. To see what happens you dont need to connect the strip.
(Before you do the next step - please save your configuration)

with Configurator go to Configuration Tab - scroll down to "other features" and actived their "multi-color-Led strip" with this switch - "save&reboot". Board is rebooting now - but blue LED is not blinking. Board is connected to Com and Com is activated - but Configuator is not able to connect to the board.
You have to reflash the board

[Pairan]

Greetings to you in Munich!

1. What setup do you fly ? FW or MC ?
2. Where did you connect the ws2812?

[artusmuc]

I flashed the version INAV/MATEKF405OSD 1.8.0 Oct 16 2017 12:40:38 Stronnag posted a link to rcgroups.
As I described there is nothing else connected - you can test this effect without and new flashed board without changing anything and nothing connected.

My setup ist only (as discribed) a MATEK F405-OSD with a MATEK FSHUB-6S connected with the ribbon cable. But i have devided this both to see the issue is caused by the FSHUB - without success.

The WS2812 is not connected anywhere to this board - cause i dont now where to connect. The see my described issue - only actives "multi-led-strip support" in configuration software - i have a short discussion with stronnag in rcgroups and he confirms this issue and said to me a should post here.

I have tested this 2 nights long - also go back to betaflight - and make a test with this - and there all works fine. I make 5 or more test - all with the same effect.

So - a naked board on my desk - connected with nothing - new flashed - nothing changed - only switch on the LED support in Configurator causes this issue.

I make this tests with everything i want to connect with no combinations first - so i have not connected for example Baro with GPS - ony baro - baro deconnect - then GPS - GPS deconnect - then reciever. The next step will be the connect them all.

If you want a know an idea what can cause this issue - i will write this. But i am not an hardware expert and dont know anything about programming a flight controller - i am only a user of hard & software :)

[artusmuc]

Hello again Parian :) sorry i only explain - and dont answer your question correct

1:) no setup using - but i plan to setup a quadcopter (4 motors)
2:) WS2812 is connected nowhere - cause i dont exactly know where

But - this is independent of causing this error of the board.

Thank you a lot for your support

[digitalentity]

So, to summarize. Once I activate LEDSTRIP on Matek F405 OSD - the board hangs on boot. Right?

[artusmuc]

Yes - exactly

[Pairan]

Just flashed 1.8RC1 to a fresh Matek F405 OSD, activated Multi-Color RGB LED strip in configuration and saved/rebooted ..

But my board works ... anything else ?

[artusmuc]

I dont have an "official" release of f405OSD iNav firmware - i have only the F405-AIO. Stronnag has postet an version for OSD in regroups. And he confirms that he has the same problem. Can i have this version you have flashed ? Thanks for your help.

[Pairan]

sure ... simply flash the Rc1 from the Configurator onto you board! (hit the switch "show unstable releases")

[stronnag]

So you're using the MATEKF405 target, not the MATEKF405OSD target firmware. That's not the subject of the PR.

[artusmuc]

Yepp - this one works .... but this is for AIO - i am not able to select the version for the OSD - my information is there is a special one for the OSD board - as discribed "slightly different firmware for the OSD Board. Stronnag posted a link for a special firmware in regroups - with is able to use I2C over UART3. I have asked if there is a special one for the OSD board.

[artusmuc]

Thanks a lot for your help stronnag :))

[Pairan]

confusing!

[stronnag]

Unfortunately so, but not much we can do about it.

[Pairan]

no. thats just how it is- as long as we can get v1.8 on the Matek Im fine :D

[artusmuc]

Maybe it helps a litte to solve - i have seen a picture in another forum - someone has soldered direct to one the I2C pins of the CPU - and the other one he use was the pin marked of LED on the port to use the I2C port. Maybe if you activate LEDs strips an the board is booting there will be a collision between the soft-I2C and the WS2812.