-
- Downloads
board common:Define default CONTROL_STATUS LED mapping
This commit is the groundwork to fix the power LED blinking on V5 Background: ---------- Early boards only had an AMBER LED that was used to indicate a High Load condition. This change defines the new logical inteface the LED_<color> should not be used in application code moving forward, only the minipulator macros should be used. Logical usage Legacy default ------------------------+------------- BOARD_OVERLOAD_LED | LED_RED Later boards defined BOARD_HAS_CONTROL_STATUS_LEDS and added the use of a BLUE and GREEN LED that were used as follows: Logical usage Legacy default ------------------------+------------- BOARD_ARMED_LED | LED_BLUE BOARD_ARMED_STATE_LED | LED_GREEN With this PR a board may now define _only_ a subset the leds and map them at the board level to the color LED it wants to use. Logical usage Legacy default ------------------------+------------- BOARD_OVERLOAD_LED | LED_RED when BOARD_HAS_CONTROL_STATUS_LEDS is defined BOARD_ARMED_LED | LED_BLUE BOARD_ARMED_STATE_LED | LED_GREEN If any of the BOARD_{OVERLOAD|ARMED|ARMED_STATE}_LED are not defined. The code output generates a null action for that LED.
Loading
Please register or sign in to comment