TBS Lucid H7 Wing: Constant I2C errors (status 50) and LED Strip PWM failure

[m-fuka]

The official iNav target TBS_LUCID_H7 (v8.0.0/9.0.x) does not have a LED_STRIP resource defined. As shown in the attached CLI resource show all screenshots, many pins are marked as FREE, but LED_STRIP is completely absent from the mapping, even with the feature enabled.
Additionally, there are persistent 50 I2C errors shown in the status bar, even with all I2C peripherals disconnected and disabled in CLI. This suggests a hardware conflict or incorrect I2C bus initialization in the target files.
Request:
Please update the target.c / target.h for TBS Lucid H7 Wing to properly map the LED Strip to the designated PWM output (M9-M13) and fix the I2C bus conflict.

[m-fuka]

resource.txt

[m-fuka]

status.txt

[sensei-hacker]

The LED pin is defined on line # 57 of target.c

It's perfectly normal to get some i2c errors while booting. For example the baro may not be ready until some milliseconds after the CPU is. What indicates a problem is if the errors are INCREASING.

Can I see your diff, please?

[m-fuka]

diff.txt

[sensei-hacker]

I see you have no LEDs defined. And therefore there is no pin needed to not control any LEDs.

With all of that out of the way, is there something you are trying to accomplish that you are having trouble with?

[m-fuka]

led cannot be defined, still showing 0 remaining

[sensei-hacker]

The old user interfce for LEDs could be confusing. This version should be easier to use, more clear:

https://drive.google.com/file/d/1Nq7HEk2NWaa5PYKpMP5T1knHn2TlEzt1/view?usp=sharing

This is the UI we'll have in Configurator 9.1

If you have any feedback on this new interface, please let me know so I can make adjustments before the 9.1 release.

[m-fuka]

I still can't find out where the physical output for connecting the ledstrip is, I can't map the led in the ledstrip settings, the problem persists.

[m-fuka]

For fun, I installed Matek743 firmware on the board and the LEDs can be mapped and the LEDstrips work.

[sensei-hacker]

I just noticed you wrote "iNav target TBS_LUCID_H7", but then you wrote "TBS Lucid H7 Wing".

There is the TBS_LUCID_H7, the TBS_LUCID_H7_WING, and the TBS_LUCID_H7_WING_MINI.

Which of these three boards do you have, please?

The TBS_LUCID_H7 has an LED pin.
The TBS_LUCID_H7_WING does not.

Though you could perhaps test a new feature that allows assigning ANY timer to LED.

[m-fuka]

sorry if I wrote the wrong name somewhere fc, I have TBS Lucid H7 wing

[m-fuka]

In the official TBS Lucid H7 target, the LED Strip does not work on the dedicated M13 (PA8/A08) pin.
When attempting to enable LED_STRIP on this pin, a timer conflict occurs. Specifically, Timer 1 (which handles A08) seems to crash or deallocate, causing all other PWM outputs (M1–M12) to show as FREE in the resource list, rendering the board unusable.
The CLI command set led_strip_pin = A08 (or PA8) returns invalid name, suggesting the pin is not defined for LED functions in the target's hardware map.

The Workaround/Proof:

I flashed the MATEKH743 target onto the same board.
With the Matek target, the LED Strip on A08 (M13) works perfectly without any timer collisions.
All other PWM outputs remain active and functional.
This confirms the issue is a software misconfiguration in the TBS Lucid H7 target definition, specifically regarding DMA/Timer allocation for PA8.

Request:
Could you please update the TBS Lucid H7 target to allow LED Strip functionality on PA8 (M13) with proper Timer/DMA assignment, similar to how it is implemented in the MATEKH743 target? Thanks

[sensei-hacker]

If you would like to test a new feature, there is a feature which will allow you to put LED on m13 (or M11, M7, M3, or M1).

In a few minutes, the bot will add a comment with a download link on:

#11375