Reste du texte
v3.1.7 and later: LED strip pin assignment has changed for OMNIBUSF4SD target
THIS ALSO APPLIES TO ASGARD
v3.1.x and earlier uses PWM5 (OMNIBUSF4 target) or PWM6 (OMNIBUSF4SD target) for LED strip, not the LED labelled pin. This was a work around for the original OMNIBUS F4 AIO having invalid pin on the designated pin. However, newer revisions of the OMNIBUS F4 family has valid (usable) pin assigned to the LED pin. Unfortunately, the pin was not ready for use with BF3.1.6 and earlier, but is was made default after BF3.1.7 and later. It means the current working connection to non-LED connector/through-hole in BF3.1.6 and earlier does not work unless explicitly remapped to the current pin.
Those users with working LED strip on PWM5 or PWM6 can either migrate to the new assignment if the board supports the mapping, or explicitly assign older mapping with the resource CLI command.
Migrating to the new assignment
Users of the following boards can migrate (rewire the LED strip signal) to the new assignment that uses the designated LED through-hole/connector.
OMNIBUS F4 V2 (J9)
OMNIBUS F4 V3 (J9)
OMNIBUS F4 Pro V3 (J1)
ASGARD V1 and V2 (J1)
Notes: (1) v3.1.7 firmware is already modified to use these through-hole/connector. (2) Unfortunately, PPM users can't use this new assignment because The new pin (MCU PB6) has a timer collision with PPM input pin (PB8); these users are forced to use the remap method below.
Explicit pin assignment remapping.
Users who choose (or forced in PPM case) not to migrate to the new assignment have to explicitly remap the assignment to the older default using the resource CLI command below.