C/C++ for Microcontrollers - Dual Button Bricklet 2.0¶

This is the description of the C/C++ for Microcontrollers API bindings for the Dual Button Bricklet 2.0. General information and technical specifications for the Dual Button Bricklet 2.0 are summarized in its hardware description.

An installation guide for the C/C++ for Microcontrollers API bindings is part of their general description.

Examples¶

The example code below is Public Domain (CC0 1.0).

Callback¶

Download (example_callback.c)

// This example is not self-contained.
// It requires usage of the example driver specific to your platform.
// See the HAL documentation.

#include "src/bindings/hal_common.h"
#include "src/bindings/bricklet_dual_button_v2.h"

void check(int rc, const char *msg);
void example_setup(TF_HAL *hal);
void example_loop(TF_HAL *hal);

// Callback function for state changed callback
static void state_changed_handler(TF_DualButtonV2 *device, uint8_t button_l,
                                  uint8_t button_r, uint8_t led_l, uint8_t led_r,
                                  void *user_data) {
    (void)device; (void)led_l; (void)led_r; (void)user_data; // avoid unused parameter warning

    if (button_l == TF_DUAL_BUTTON_V2_BUTTON_STATE_PRESSED) {
        tf_hal_printf("Left Button: Pressed\n");
    } else if (button_l == TF_DUAL_BUTTON_V2_BUTTON_STATE_RELEASED) {
        tf_hal_printf("Left Button: Released\n");
    }

    if (button_r == TF_DUAL_BUTTON_V2_BUTTON_STATE_PRESSED) {
        tf_hal_printf("Right Button: Pressed\n");
    } else if (button_r == TF_DUAL_BUTTON_V2_BUTTON_STATE_RELEASED) {
        tf_hal_printf("Right Button: Released\n");
    }

    tf_hal_printf("\n");
}

static TF_DualButtonV2 db;

void example_setup(TF_HAL *hal) {
    // Create device object
    check(tf_dual_button_v2_create(&db, NULL, hal), "create device object");

    // Register state changed callback to function state_changed_handler
    tf_dual_button_v2_register_state_changed_callback(&db,
                                                      state_changed_handler,
                                                      NULL);

    // Enable state changed callback
    check(tf_dual_button_v2_set_state_changed_callback_configuration(&db,
                                                                     true), "call set_state_changed_callback_configuration");
}

void example_loop(TF_HAL *hal) {
    // Poll for callbacks
    tf_hal_callback_tick(hal, 0);
}

API¶

Most functions of the C/C++ bindings for microcontrollers return an error code (e_code).

Possible error codes are:

TF_E\ _OK = 0
TF_E\ _TIMEOUT = -1
TF_E\ _INVALID_PARAMETER = -2
TF_E\ _NOT_SUPPORTED = -3
TF_E\ _UNKNOWN_ERROR_CODE = -4
TF_E\ _STREAM_OUT_OF_SYNC = -5
TF_E\ _INVALID_CHAR_IN_UID = -6
TF_E\ _UID_TOO_LONG = -7
TF_E\ _UID_OVERFLOW = -8
TF_E\ _TOO_MANY_DEVICES = -9
TF_E\ _DEVICE_NOT_FOUND = -10
TF_E\ _WRONG_DEVICE_TYPE = -11
TF_E\ _LOCKED = -12
TF_E\ _PORT_NOT_FOUND = -13

(as defined in errors.h) as well as the errors returned from the hardware abstraction layer (HAL) that is used.

Use :cpp:func`tf_hal_strerror` (defined in the HAL's header file) to get an error string for an error code.

Data returned from the device, when a getter is called, is handled via output parameters. These parameters are labeled with the ret_ prefix. The bindings will not write to an output parameter if NULL or nullptr is passed. This can be used to ignore outputs that you are not interested in.

None of the functions listed below are thread-safe. See the API bindings description for details.

Basic Functions¶

int tf_dual_button_v2_create(TF_DualButtonV2 *dual_button_v2, const char *uid_or_port_name, TF_HAL *hal)¶

Parameters:	dual_button_v2 – Type: TF_DualButtonV2 * uid – Type: const char * hal – Type: TF_HAL *
Returns:	e_code – Type: int

Creates the device object dual_button_v2 with the optional unique device ID or port name uid_or_port_name and adds it to the HAL hal:

TF_DualButtonV2 dual_button_v2;
tf_dual_button_v2_create(&dual_button_v2, NULL, &hal);

Normally uid_or_port_name can stay NULL. For more details about this see section UID or Port Name.

int tf_dual_button_v2_destroy(TF_DualButtonV2 *dual_button_v2)¶

Parameters:	dual_button_v2 – Type: TF_DualButtonV2 *
Returns:	e_code – Type: int

Removes the device object dual_button_v2 from its HAL and destroys it. The device object cannot be used anymore afterwards.

int tf_dual_button_v2_set_led_state(TF_DualButtonV2 *dual_button_v2, uint8_t led_l, uint8_t led_r)¶

Parameters:	dual_button_v2 – Type: TF_DualButtonV2 * led_l – Type: uint8_t, Range: See constants, Default: 1 led_r – Type: uint8_t, Range: See constants, Default: 1
Returns:	e_code – Type: int

Sets the state of the LEDs. Possible states are:

0 = AutoToggleOn: Enables auto toggle with initially enabled LED.
1 = AutoToggleOff: Activates auto toggle with initially disabled LED.
2 = On: Enables LED (auto toggle is disabled).
3 = Off: Disables LED (auto toggle is disabled).

In auto toggle mode the LED is toggled automatically at each press of a button.

If you just want to set one of the LEDs and don't know the current state of the other LED, you can get the state with tf_dual_button_v2_get_led_state() or you can use tf_dual_button_v2_set_selected_led_state().

The following constants are available for this function:

For led_l:

TF_DUAL_BUTTON_V2_LED_STATE_AUTO_TOGGLE_ON = 0
TF_DUAL_BUTTON_V2_LED_STATE_AUTO_TOGGLE_OFF = 1
TF_DUAL_BUTTON_V2_LED_STATE_ON = 2
TF_DUAL_BUTTON_V2_LED_STATE_OFF = 3

For led_r:

TF_DUAL_BUTTON_V2_LED_STATE_AUTO_TOGGLE_ON = 0
TF_DUAL_BUTTON_V2_LED_STATE_AUTO_TOGGLE_OFF = 1
TF_DUAL_BUTTON_V2_LED_STATE_ON = 2
TF_DUAL_BUTTON_V2_LED_STATE_OFF = 3

int tf_dual_button_v2_get_led_state(TF_DualButtonV2 *dual_button_v2, uint8_t *ret_led_l, uint8_t *ret_led_r)¶

Parameters:	dual_button_v2 – Type: TF_DualButtonV2 *
Output Parameters:	ret_led_l – Type: uint8_t, Range: See constants, Default: 1 ret_led_r – Type: uint8_t, Range: See constants, Default: 1
Returns:	e_code – Type: int

Returns the current state of the LEDs, as set by tf_dual_button_v2_set_led_state().

The following constants are available for this function:

For ret_led_l:

TF_DUAL_BUTTON_V2_LED_STATE_AUTO_TOGGLE_ON = 0
TF_DUAL_BUTTON_V2_LED_STATE_AUTO_TOGGLE_OFF = 1
TF_DUAL_BUTTON_V2_LED_STATE_ON = 2
TF_DUAL_BUTTON_V2_LED_STATE_OFF = 3

For ret_led_r:

TF_DUAL_BUTTON_V2_LED_STATE_AUTO_TOGGLE_ON = 0
TF_DUAL_BUTTON_V2_LED_STATE_AUTO_TOGGLE_OFF = 1
TF_DUAL_BUTTON_V2_LED_STATE_ON = 2
TF_DUAL_BUTTON_V2_LED_STATE_OFF = 3

int tf_dual_button_v2_get_button_state(TF_DualButtonV2 *dual_button_v2, uint8_t *ret_button_l, uint8_t *ret_button_r)¶

Parameters:	dual_button_v2 – Type: TF_DualButtonV2 *
Output Parameters:	ret_button_l – Type: uint8_t, Range: See constants ret_button_r – Type: uint8_t, Range: See constants
Returns:	e_code – Type: int

Returns the current state for both buttons. Possible states are:

0 = pressed
1 = released

The following constants are available for this function:

For ret_button_l:

TF_DUAL_BUTTON_V2_BUTTON_STATE_PRESSED = 0
TF_DUAL_BUTTON_V2_BUTTON_STATE_RELEASED = 1

For ret_button_r:

TF_DUAL_BUTTON_V2_BUTTON_STATE_PRESSED = 0
TF_DUAL_BUTTON_V2_BUTTON_STATE_RELEASED = 1

Advanced Functions¶

int tf_dual_button_v2_set_selected_led_state(TF_DualButtonV2 *dual_button_v2, uint8_t led, uint8_t state)¶

Parameters:	dual_button_v2 – Type: TF_DualButtonV2 * led – Type: uint8_t, Range: See constants state – Type: uint8_t, Range: See constants
Returns:	e_code – Type: int

Sets the state of the selected LED.

The other LED remains untouched.

The following constants are available for this function:

For led:

TF_DUAL_BUTTON_V2_LED_LEFT = 0
TF_DUAL_BUTTON_V2_LED_RIGHT = 1

For state:

TF_DUAL_BUTTON_V2_LED_STATE_AUTO_TOGGLE_ON = 0
TF_DUAL_BUTTON_V2_LED_STATE_AUTO_TOGGLE_OFF = 1
TF_DUAL_BUTTON_V2_LED_STATE_ON = 2
TF_DUAL_BUTTON_V2_LED_STATE_OFF = 3

int tf_dual_button_v2_get_spitfp_error_count(TF_DualButtonV2 *dual_button_v2, uint32_t *ret_error_count_ack_checksum, uint32_t *ret_error_count_message_checksum, uint32_t *ret_error_count_frame, uint32_t *ret_error_count_overflow)¶

Parameters:	dual_button_v2 – Type: TF_DualButtonV2 *
Output Parameters:	ret_error_count_ack_checksum – Type: uint32_t, Range: [0 to 2³² - 1] ret_error_count_message_checksum – Type: uint32_t, Range: [0 to 2³² - 1] ret_error_count_frame – Type: uint32_t, Range: [0 to 2³² - 1] ret_error_count_overflow – Type: uint32_t, Range: [0 to 2³² - 1]
Returns:	e_code – Type: int

Returns the error count for the communication between Brick and Bricklet.

The errors are divided into

ACK checksum errors,
message checksum errors,
framing errors and
overflow errors.

The errors counts are for errors that occur on the Bricklet side. All Bricks have a similar function that returns the errors on the Brick side.

int tf_dual_button_v2_set_status_led_config(TF_DualButtonV2 *dual_button_v2, uint8_t config)¶

Parameters:	dual_button_v2 – Type: TF_DualButtonV2 * config – Type: uint8_t, Range: See constants, Default: 3
Returns:	e_code – Type: int

Sets the status LED configuration. By default the LED shows communication traffic between Brick and Bricklet, it flickers once for every 10 received data packets.

You can also turn the LED permanently on/off or show a heartbeat.

If the Bricklet is in bootloader mode, the LED is will show heartbeat by default.

The following constants are available for this function:

For config:

TF_DUAL_BUTTON_V2_STATUS_LED_CONFIG_OFF = 0
TF_DUAL_BUTTON_V2_STATUS_LED_CONFIG_ON = 1
TF_DUAL_BUTTON_V2_STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
TF_DUAL_BUTTON_V2_STATUS_LED_CONFIG_SHOW_STATUS = 3

int tf_dual_button_v2_get_status_led_config(TF_DualButtonV2 *dual_button_v2, uint8_t *ret_config)¶

Parameters:	dual_button_v2 – Type: TF_DualButtonV2 *
Output Parameters:	ret_config – Type: uint8_t, Range: See constants, Default: 3
Returns:	e_code – Type: int

Returns the configuration as set by tf_dual_button_v2_set_status_led_config()

The following constants are available for this function:

For ret_config:

TF_DUAL_BUTTON_V2_STATUS_LED_CONFIG_OFF = 0
TF_DUAL_BUTTON_V2_STATUS_LED_CONFIG_ON = 1
TF_DUAL_BUTTON_V2_STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
TF_DUAL_BUTTON_V2_STATUS_LED_CONFIG_SHOW_STATUS = 3

int tf_dual_button_v2_get_chip_temperature(TF_DualButtonV2 *dual_button_v2, int16_t *ret_temperature)¶

Parameters:	dual_button_v2 – Type: TF_DualButtonV2 *
Output Parameters:	ret_temperature – Type: int16_t, Unit: 1 °C, Range: [-2¹⁵ to 2¹⁵ - 1]
Returns:	e_code – Type: int

Returns the temperature as measured inside the microcontroller. The value returned is not the ambient temperature!

The temperature is only proportional to the real temperature and it has bad accuracy. Practically it is only useful as an indicator for temperature changes.

int tf_dual_button_v2_reset(TF_DualButtonV2 *dual_button_v2)¶

Parameters:	dual_button_v2 – Type: TF_DualButtonV2 *
Returns:	e_code – Type: int

Calling this function will reset the Bricklet. All configurations will be lost.

After a reset you have to create new device objects, calling functions on the existing ones will result in undefined behavior!

int tf_dual_button_v2_get_identity(TF_DualButtonV2 *dual_button_v2, char ret_uid[8], char ret_connected_uid[8], char *ret_position, uint8_t ret_hardware_version[3], uint8_t ret_firmware_version[3], uint16_t *ret_device_identifier)¶

Parameters:	dual_button_v2 – Type: TF_DualButtonV2 *
Output Parameters:	ret_uid – Type: char[8] ret_connected_uid – Type: char[8] ret_position – Type: char, Range: ['a' to 'h', 'z'] ret_hardware_version – Type: uint8_t[3] 0: major – Type: uint8_t, Range: [0 to 255] 1: minor – Type: uint8_t, Range: [0 to 255] 2: revision – Type: uint8_t, Range: [0 to 255] ret_firmware_version – Type: uint8_t[3] 0: major – Type: uint8_t, Range: [0 to 255] 1: minor – Type: uint8_t, Range: [0 to 255] 2: revision – Type: uint8_t, Range: [0 to 255] ret_device_identifier – Type: uint16_t, Range: [0 to 2¹⁶ - 1]
Returns:	e_code – Type: int

Returns the UID, the UID where the Bricklet is connected to, the position, the hardware and firmware version as well as the device identifier.

The position can be 'a', 'b', 'c', 'd', 'e', 'f', 'g' or 'h' (Bricklet Port). A Bricklet connected to an Isolator Bricklet is always at position 'z'.

The device identifier numbers can be found here. There is also a constant for the device identifier of this Bricklet.

Callback Configuration Functions¶

int tf_dual_button_v2_set_state_changed_callback_configuration(TF_DualButtonV2 *dual_button_v2, bool enabled)¶

Parameters:	dual_button_v2 – Type: TF_DualButtonV2 * enabled – Type: bool, Default: false
Returns:	e_code – Type: int

If you enable this callback, the State Changed callback is triggered every time a button is pressed/released

int tf_dual_button_v2_get_state_changed_callback_configuration(TF_DualButtonV2 *dual_button_v2, bool *ret_enabled)¶

Parameters:	dual_button_v2 – Type: TF_DualButtonV2 *
Output Parameters:	ret_enabled – Type: bool, Default: false
Returns:	e_code – Type: int

Returns the configuration as set by tf_dual_button_v2_set_state_changed_callback_configuration().

Callbacks¶

Callbacks can be registered to receive time critical or recurring data from the device. The registration is done with the corresponding tf_dual_button_v2_register_*_callback function. The user_data passed to the registration function as well as the device that triggered the callback are passed to the registered callback handler.

Only one handler can be registered to a callback at the same time. To deregister a callback, call the tf_dual_button_v2_register_*_callback function with NULL as handler.

Note

Using callbacks for recurring events is preferred compared to using getters. Polling for a callback requires writing one byte only. See here Optimizing Performance.

Warning

Calling bindings function from inside a callback handler is not allowed. See here Thread safety.

int tf_dual_button_v2_register_state_changed_callback(TF_DualButtonV2 *dual_button_v2, TF_DualButtonV2_StateChangedHandler handler, void *user_data)¶

void handler(TF_DualButtonV2 *dual_button_v2, uint8_t button_l, uint8_t button_r, uint8_t led_l, uint8_t led_r, void *user_data)

Callback Parameters:	dual_button_v2 – Type: TF_DualButtonV2 * button_l – Type: uint8_t, Range: See constants button_r – Type: uint8_t, Range: See constants led_l – Type: uint8_t, Range: See constants led_r – Type: uint8_t, Range: See constants user_data – Type: void *

This callback is called whenever a button is pressed.

Possible states for buttons are:

0 = pressed
1 = released

Possible states for LEDs are:

0 = AutoToggleOn: Auto toggle enabled and LED on.
1 = AutoToggleOff: Auto toggle enabled and LED off.
2 = On: LED on (auto toggle is disabled).
3 = Off: LED off (auto toggle is disabled).

This callback can be enabled with tf_dual_button_v2_set_state_changed_callback_configuration().

The following constants are available for this function:

For button_l:

TF_DUAL_BUTTON_V2_BUTTON_STATE_PRESSED = 0
TF_DUAL_BUTTON_V2_BUTTON_STATE_RELEASED = 1

For button_r:

TF_DUAL_BUTTON_V2_BUTTON_STATE_PRESSED = 0
TF_DUAL_BUTTON_V2_BUTTON_STATE_RELEASED = 1

For led_l:

TF_DUAL_BUTTON_V2_LED_STATE_AUTO_TOGGLE_ON = 0
TF_DUAL_BUTTON_V2_LED_STATE_AUTO_TOGGLE_OFF = 1
TF_DUAL_BUTTON_V2_LED_STATE_ON = 2
TF_DUAL_BUTTON_V2_LED_STATE_OFF = 3

For led_r:

TF_DUAL_BUTTON_V2_LED_STATE_AUTO_TOGGLE_ON = 0
TF_DUAL_BUTTON_V2_LED_STATE_AUTO_TOGGLE_OFF = 1
TF_DUAL_BUTTON_V2_LED_STATE_ON = 2
TF_DUAL_BUTTON_V2_LED_STATE_OFF = 3

Virtual Functions¶

Virtual functions don't communicate with the device itself, but operate only on the API bindings device object.

int tf_dual_button_v2_get_response_expected(TF_DualButtonV2 *dual_button_v2, uint8_t function_id, bool *ret_response_expected)¶

Parameters:	dual_button_v2 – Type: TF_DualButtonV2 * function_id – Type: uint8_t, Range: See constants
Output Parameters:	ret_response_expected – Type: bool
Returns:	e_code – Type: int

Returns the response expected flag for the function specified by the function ID parameter. It is true if the function is expected to send a response, false otherwise.

For getter functions this is enabled by default and cannot be disabled, because those functions will always send a response. For callback configuration functions it is enabled by default too, but can be disabled by tf_dual_button_v2_set_response_expected(). For setter functions it is disabled by default and can be enabled.

Enabling the response expected flag for a setter function allows to detect timeouts and other error conditions calls of this setter as well. The device will then send a response for this purpose. If this flag is disabled for a setter function then no response is sent and errors are silently ignored, because they cannot be detected.

The following constants are available for this function:

For function_id:

TF_DUAL_BUTTON_V2_FUNCTION_SET_LED_STATE = 1
TF_DUAL_BUTTON_V2_FUNCTION_SET_SELECTED_LED_STATE = 5
TF_DUAL_BUTTON_V2_FUNCTION_SET_STATE_CHANGED_CALLBACK_CONFIGURATION = 6
TF_DUAL_BUTTON_V2_FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
TF_DUAL_BUTTON_V2_FUNCTION_SET_STATUS_LED_CONFIG = 239
TF_DUAL_BUTTON_V2_FUNCTION_RESET = 243
TF_DUAL_BUTTON_V2_FUNCTION_WRITE_UID = 248

int tf_dual_button_v2_set_response_expected(TF_DualButtonV2 *dual_button_v2, uint8_t function_id, bool response_expected)¶

Parameters:	dual_button_v2 – Type: TF_DualButtonV2 * function_id – Type: uint8_t, Range: See constants response_expected – Type: bool
Returns:	e_code – Type: int

Changes the response expected flag of the function specified by the function ID parameter. This flag can only be changed for setter (default value: false) and callback configuration functions (default value: true). For getter functions it is always enabled.

The following constants are available for this function:

For function_id:

TF_DUAL_BUTTON_V2_FUNCTION_SET_LED_STATE = 1
TF_DUAL_BUTTON_V2_FUNCTION_SET_SELECTED_LED_STATE = 5
TF_DUAL_BUTTON_V2_FUNCTION_SET_STATE_CHANGED_CALLBACK_CONFIGURATION = 6
TF_DUAL_BUTTON_V2_FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
TF_DUAL_BUTTON_V2_FUNCTION_SET_STATUS_LED_CONFIG = 239
TF_DUAL_BUTTON_V2_FUNCTION_RESET = 243
TF_DUAL_BUTTON_V2_FUNCTION_WRITE_UID = 248

int tf_dual_button_v2_set_response_expected_all(TF_DualButtonV2 *dual_button_v2, bool response_expected)¶

Parameters:	dual_button_v2 – Type: TF_DualButtonV2 * response_expected – Type: bool
Returns:	e_code – Type: int

Changes the response expected flag for all setter and callback configuration functions of this device at once.

Internal Functions¶

Internal functions are used for maintenance tasks such as flashing a new firmware of changing the UID of a Bricklet. These task should be performed using Brick Viewer instead of using the internal functions directly.

int tf_dual_button_v2_set_bootloader_mode(TF_DualButtonV2 *dual_button_v2, uint8_t mode, uint8_t *ret_status)¶

Parameters:	dual_button_v2 – Type: TF_DualButtonV2 * mode – Type: uint8_t, Range: See constants
Output Parameters:	ret_status – Type: uint8_t, Range: See constants
Returns:	e_code – Type: int

Sets the bootloader mode and returns the status after the requested mode change was instigated.

You can change from bootloader mode to firmware mode and vice versa. A change from bootloader mode to firmware mode will only take place if the entry function, device identifier and CRC are present and correct.

This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.

The following constants are available for this function:

For mode:

TF_DUAL_BUTTON_V2_BOOTLOADER_MODE_BOOTLOADER = 0
TF_DUAL_BUTTON_V2_BOOTLOADER_MODE_FIRMWARE = 1
TF_DUAL_BUTTON_V2_BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
TF_DUAL_BUTTON_V2_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
TF_DUAL_BUTTON_V2_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4

For ret_status:

TF_DUAL_BUTTON_V2_BOOTLOADER_STATUS_OK = 0
TF_DUAL_BUTTON_V2_BOOTLOADER_STATUS_INVALID_MODE = 1
TF_DUAL_BUTTON_V2_BOOTLOADER_STATUS_NO_CHANGE = 2
TF_DUAL_BUTTON_V2_BOOTLOADER_STATUS_ENTRY_FUNCTION_NOT_PRESENT = 3
TF_DUAL_BUTTON_V2_BOOTLOADER_STATUS_DEVICE_IDENTIFIER_INCORRECT = 4
TF_DUAL_BUTTON_V2_BOOTLOADER_STATUS_CRC_MISMATCH = 5

int tf_dual_button_v2_get_bootloader_mode(TF_DualButtonV2 *dual_button_v2, uint8_t *ret_mode)¶

Parameters:	dual_button_v2 – Type: TF_DualButtonV2 *
Output Parameters:	ret_mode – Type: uint8_t, Range: See constants
Returns:	e_code – Type: int

Returns the current bootloader mode, see tf_dual_button_v2_set_bootloader_mode().

The following constants are available for this function:

For ret_mode:

TF_DUAL_BUTTON_V2_BOOTLOADER_MODE_BOOTLOADER = 0
TF_DUAL_BUTTON_V2_BOOTLOADER_MODE_FIRMWARE = 1
TF_DUAL_BUTTON_V2_BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
TF_DUAL_BUTTON_V2_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
TF_DUAL_BUTTON_V2_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4

int tf_dual_button_v2_set_write_firmware_pointer(TF_DualButtonV2 *dual_button_v2, uint32_t pointer)¶

Parameters:	dual_button_v2 – Type: TF_DualButtonV2 * pointer – Type: uint32_t, Unit: 1 B, Range: [0 to 2³² - 1]
Returns:	e_code – Type: int

Sets the firmware pointer for tf_dual_button_v2_write_firmware(). The pointer has to be increased by chunks of size 64. The data is written to flash every 4 chunks (which equals to one page of size 256).

This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.

int tf_dual_button_v2_write_firmware(TF_DualButtonV2 *dual_button_v2, const uint8_t data[64], uint8_t *ret_status)¶

Parameters:	dual_button_v2 – Type: TF_DualButtonV2 * data – Type: const uint8_t[64], Range: [0 to 255]
Output Parameters:	ret_status – Type: uint8_t, Range: [0 to 255]
Returns:	e_code – Type: int

Writes 64 Bytes of firmware at the position as written by tf_dual_button_v2_set_write_firmware_pointer() before. The firmware is written to flash every 4 chunks.

You can only write firmware in bootloader mode.

This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.

int tf_dual_button_v2_write_uid(TF_DualButtonV2 *dual_button_v2, uint32_t uid)¶

Parameters:	dual_button_v2 – Type: TF_DualButtonV2 * uid – Type: uint32_t, Range: [0 to 2³² - 1]
Returns:	e_code – Type: int

Writes a new UID into flash. If you want to set a new UID you have to decode the Base58 encoded UID string into an integer first.

We recommend that you use Brick Viewer to change the UID.

int tf_dual_button_v2_read_uid(TF_DualButtonV2 *dual_button_v2, uint32_t *ret_uid)¶

Parameters:	dual_button_v2 – Type: TF_DualButtonV2 *
Output Parameters:	ret_uid – Type: uint32_t, Range: [0 to 2³² - 1]
Returns:	e_code – Type: int

Returns the current UID as an integer. Encode as Base58 to get the usual string version.

Constants¶

TF_DUAL_BUTTON_V2_DEVICE_IDENTIFIER¶

This constant is used to identify a Dual Button Bricklet 2.0.

The functions tf_dual_button_v2_get_identity() and tf_hal_get_device_info() have a device_identifier output parameter to specify the Brick's or Bricklet's type.

TF_DUAL_BUTTON_V2_DEVICE_DISPLAY_NAME¶: This constant represents the human readable name of a Dual Button Bricklet 2.0.