Deutsch
English
Menu
Software / API Bindings / Rust / API Reference and Examples / Bricklets / XMC1400 Breakout Bricklet

Rust - XMC1400 Breakout Bricklet

This is the description of the Rust API bindings for the XMC1400 Breakout Bricklet. General information and technical specifications for the XMC1400 Breakout Bricklet are summarized in its hardware description.

An installation guide for the Rust API bindings is part of their general description. Additional documentation can be found on docs.rs.

Examples

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

Gpio

Download (example_gpio.rs)

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
use std::{error::Error, io, thread, time::Duration};
use tinkerforge::{ip_connection::IpConnection, xmc1400_breakout_bricklet::*};

const HOST: &str = "localhost";
const PORT: u16 = 4223;
const UID: &str = "XYZ"; // Change XYZ to the UID of your XMC1400 Breakout Bricklet.

fn main() -> Result<(), Box<dyn Error>> {
    let ipcon = IpConnection::new(); // Create IP connection.
    let xb = Xmc1400BreakoutBricklet::new(UID, &ipcon); // Create device object.

    ipcon.connect((HOST, PORT)).recv()??; // Connect to brickd.
                                          // Don't use device before ipcon is connected.

    // Set Port 1, Pin 0 alternating high/low for 5 times with 1s delay
    for _i in 0..5 {
        thread::sleep(Duration::from_millis(1000));
        xb.set_gpio_config(1, 0, XMC1400_BREAKOUT_BRICKLET_GPIO_MODE_OUTPUT_PUSH_PULL, 0, false).recv()?;
        thread::sleep(Duration::from_millis(1000));
        xb.set_gpio_config(1, 0, XMC1400_BREAKOUT_BRICKLET_GPIO_MODE_OUTPUT_PUSH_PULL, 0, true).recv()?;
    }

    println!("Press enter to exit.");
    let mut _input = String::new();
    io::stdin().read_line(&mut _input)?;
    ipcon.disconnect();
    Ok(())
}

API

To allow non-blocking usage, nearly every function of the Rust bindings returns a wrapper around a mpsc::Receiver. To block until the function has finished and get your result, call one of the receiver's recv variants. Those return either the result sent by the device, or any error occurred.

Functions returning a result directly will block until the device has finished processing the request.

All functions listed below are thread-safe, those which return a receiver are lock-free.

Basic Functions

pub fn Xmc1400BreakoutBricklet::new(uid: &str, ip_connection: &IpConnection) → Xmc1400BreakoutBricklet
Parameters:
  • uid – Type: &str
  • ip_connection – Type: &IPConnection
Returns:
  • xmc1400_breakout – Type: Xmc1400BreakoutBricklet

Creates a new Xmc1400BreakoutBricklet object with the unique device ID uid and adds it to the IPConnection ip_connection:

let xmc1400_breakout = Xmc1400BreakoutBricklet::new("YOUR_DEVICE_UID", &ip_connection);

This device object can be used after the IP connection has been connected.

pub fn Xmc1400BreakoutBricklet::set_gpio_config(&self, port: u8, pin: u8, mode: u8, input_hysteresis: u8, output_level: bool) → ConvertingReceiver<()>
Parameters:
  • port – Type: u8, Range: [0 to 4]
  • pin – Type: u8, Range: ?
  • mode – Type: u8, Range: See constants
  • input_hysteresis – Type: u8, Range: See constants
  • output_level – Type: bool

Example for a setter function. The values are the values that can be given to the XMC_GPIO_Init function. See communication.c in the firmware.

The following constants are available for this function:

For mode:

  • XMC1400_BREAKOUT_BRICKLET_GPIO_MODE_INPUT_TRISTATE = 0
  • XMC1400_BREAKOUT_BRICKLET_GPIO_MODE_INPUT_PULL_DOWN = 1
  • XMC1400_BREAKOUT_BRICKLET_GPIO_MODE_INPUT_PULL_UP = 2
  • XMC1400_BREAKOUT_BRICKLET_GPIO_MODE_INPUT_SAMPLING = 3
  • XMC1400_BREAKOUT_BRICKLET_GPIO_MODE_INPUT_INVERTED_TRISTATE = 4
  • XMC1400_BREAKOUT_BRICKLET_GPIO_MODE_INPUT_INVERTED_PULL_DOWN = 5
  • XMC1400_BREAKOUT_BRICKLET_GPIO_MODE_INPUT_INVERTED_PULL_UP = 6
  • XMC1400_BREAKOUT_BRICKLET_GPIO_MODE_INPUT_INVERTED_SAMPLING = 7
  • XMC1400_BREAKOUT_BRICKLET_GPIO_MODE_OUTPUT_PUSH_PULL = 8
  • XMC1400_BREAKOUT_BRICKLET_GPIO_MODE_OUTPUT_OPEN_DRAIN = 9

For input_hysteresis:

  • XMC1400_BREAKOUT_BRICKLET_GPIO_INPUT_HYSTERESIS_STANDARD = 0
  • XMC1400_BREAKOUT_BRICKLET_GPIO_INPUT_HYSTERESIS_LARGE = 4
pub fn Xmc1400BreakoutBricklet::get_gpio_input(&self, port: u8, pin: u8) → ConvertingReceiver<bool>
Parameters:
  • port – Type: u8, Range: [0 to 4]
  • pin – Type: u8, Range: ?
Returns:
  • value – Type: bool

Example for a getter function. Returns the result of a XMC_GPIO_GetInput call for the given port/pin.

pub fn Xmc1400BreakoutBricklet::set_adc_channel_config(&self, channel: u8, enable: bool) → ConvertingReceiver<()>
Parameters:
  • channel – Type: u8, Range: [0 to 7]
  • enable – Type: bool

Enables a ADC channel for the ADC driver example (adc.c/adc.h).

There are 8 ADC channels and they correspond to the following pins:

  • Channel 0: P2_6
  • Channel 1: P2_8
  • Channel 2: P2_9
  • Channel 3: P2_10
  • Channel 4: P2_11
  • Channel 5: P2_0
  • Channel 6: P2_1
  • Channel 7: P2_2
pub fn Xmc1400BreakoutBricklet::get_adc_channel_config(&self, channel: u8) → ConvertingReceiver<bool>
Parameters:
  • channel – Type: u8, Range: [0 to 7]
Returns:
  • enable – Type: bool

Returns the config for the given channel as set by Xmc1400BreakoutBricklet::set_adc_channel_config.

pub fn Xmc1400BreakoutBricklet::get_adc_channel_value(&self, channel: u8) → ConvertingReceiver<u16>
Parameters:
  • channel – Type: u8, Range: [0 to 7]
Returns:
  • value – Type: u16, Range: [0 to 212 - 1]

Returns the 12-bit value of the given ADC channel of the ADC driver example.

pub fn Xmc1400BreakoutBricklet::get_adc_values(&self) → ConvertingReceiver<[u16; 8]>
Returns:
  • values – Type: [u16; 8], Range: [0 to 212 - 1]

Returns the values for all 8 ADC channels of the adc driver example.

This example function also has a corresponding callback.

See Xmc1400BreakoutBricklet::set_adc_values_callback_configuration and Xmc1400BreakoutBricklet::get_adc_values_callback_receiver callback.

pub fn Xmc1400BreakoutBricklet::get_count(&self) → ConvertingReceiver<u32>
Returns:
  • count – Type: u32, Range: [0 to 232 - 1]

Returns the value of the example count (see example.c).

This example function uses the "add_callback_value_function"-helper in the generator. The getter as well as the callback and callback configuration functions are auto-generated for the API as well as the firmware.

If you want to get the value periodically, it is recommended to use the Xmc1400BreakoutBricklet::get_count_callback_receiver callback. You can set the callback configuration with Xmc1400BreakoutBricklet::set_count_callback_configuration.

Advanced Functions

pub fn Xmc1400BreakoutBricklet::get_spitfp_error_count(&self) → ConvertingReceiver<SpitfpErrorCount>
Return Object:
  • error_count_ack_checksum – Type: u32, Range: [0 to 232 - 1]
  • error_count_message_checksum – Type: u32, Range: [0 to 232 - 1]
  • error_count_frame – Type: u32, Range: [0 to 232 - 1]
  • error_count_overflow – Type: u32, Range: [0 to 232 - 1]

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.

pub fn Xmc1400BreakoutBricklet::set_status_led_config(&self, config: u8) → ConvertingReceiver<()>
Parameters:
  • config – Type: u8, Range: See constants, Default: 3

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:

  • XMC1400_BREAKOUT_BRICKLET_STATUS_LED_CONFIG_OFF = 0
  • XMC1400_BREAKOUT_BRICKLET_STATUS_LED_CONFIG_ON = 1
  • XMC1400_BREAKOUT_BRICKLET_STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
  • XMC1400_BREAKOUT_BRICKLET_STATUS_LED_CONFIG_SHOW_STATUS = 3
pub fn Xmc1400BreakoutBricklet::get_status_led_config(&self) → ConvertingReceiver<u8>
Returns:
  • config – Type: u8, Range: See constants, Default: 3

Returns the configuration as set by Xmc1400BreakoutBricklet::set_status_led_config

The following constants are available for this function:

For config:

  • XMC1400_BREAKOUT_BRICKLET_STATUS_LED_CONFIG_OFF = 0
  • XMC1400_BREAKOUT_BRICKLET_STATUS_LED_CONFIG_ON = 1
  • XMC1400_BREAKOUT_BRICKLET_STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
  • XMC1400_BREAKOUT_BRICKLET_STATUS_LED_CONFIG_SHOW_STATUS = 3
pub fn Xmc1400BreakoutBricklet::get_chip_temperature(&self) → ConvertingReceiver<i16>
Returns:
  • temperature – Type: i16, Unit: 1 °C, Range: [-215 to 215 - 1]

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.

pub fn Xmc1400BreakoutBricklet::reset(&self) → ConvertingReceiver<()>

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!

pub fn Xmc1400BreakoutBricklet::get_identity(&self) → ConvertingReceiver<Identity>
Return Object:
  • uid – Type: String, Length: up to 8
  • connected_uid – Type: String, Length: up to 8
  • position – Type: char, Range: ['a' to 'h', 'z']
  • hardware_version – Type: [u8; 3]
    • 0: major – Type: u8, Range: [0 to 255]
    • 1: minor – Type: u8, Range: [0 to 255]
    • 2: revision – Type: u8, Range: [0 to 255]
  • firmware_version – Type: [u8; 3]
    • 0: major – Type: u8, Range: [0 to 255]
    • 1: minor – Type: u8, Range: [0 to 255]
    • 2: revision – Type: u8, Range: [0 to 255]
  • device_identifier – Type: u16, Range: [0 to 216 - 1]

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

pub fn Xmc1400BreakoutBricklet::set_adc_values_callback_configuration(&self, period: u32, value_has_to_change: bool) → ConvertingReceiver<()>
Parameters:
  • period – Type: u32, Unit: 1 ms, Range: [0 to 232 - 1], Default: 0
  • value_has_to_change – Type: bool, Default: false

The period is the period with which the Xmc1400BreakoutBricklet::get_adc_values_callback_receiver callback is triggered periodically. A value of 0 turns the callback off.

If the value has to change-parameter is set to true, the callback is only triggered after the value has changed. If the value didn't change within the period, the callback is triggered immediately on change.

If it is set to false, the callback is continuously triggered with the period, independent of the value.

pub fn Xmc1400BreakoutBricklet::get_adc_values_callback_configuration(&self) → ConvertingReceiver<AdcValuesCallbackConfiguration>
Return Object:
  • period – Type: u32, Unit: 1 ms, Range: [0 to 232 - 1], Default: 0
  • value_has_to_change – Type: bool, Default: false

Returns the callback configuration as set by Xmc1400BreakoutBricklet::set_adc_values_callback_configuration.

pub fn Xmc1400BreakoutBricklet::set_count_callback_configuration(&self, period: u32, value_has_to_change: bool, option: char, min: u32, max: u32) → ConvertingReceiver<()>
Parameters:
  • period – Type: u32, Unit: 1 ms, Range: [0 to 232 - 1], Default: 0
  • value_has_to_change – Type: bool, Default: false
  • option – Type: char, Range: See constants, Default: 'x'
  • min – Type: u32, Range: [0 to 232 - 1], Default: 0
  • max – Type: u32, Range: [0 to 232 - 1], Default: 0

The period is the period with which the Xmc1400BreakoutBricklet::get_count_callback_receiver callback is triggered periodically. A value of 0 turns the callback off.

If the value has to change-parameter is set to true, the callback is only triggered after the value has changed. If the value didn't change within the period, the callback is triggered immediately on change.

If it is set to false, the callback is continuously triggered with the period, independent of the value.

It is furthermore possible to constrain the callback with thresholds.

The option-parameter together with min/max sets a threshold for the Xmc1400BreakoutBricklet::get_count_callback_receiver callback.

The following options are possible:

Option Description
'x' Threshold is turned off
'o' Threshold is triggered when the value is outside the min and max values
'i' Threshold is triggered when the value is inside or equal to the min and max values
'<' Threshold is triggered when the value is smaller than the min value (max is ignored)
'>' Threshold is triggered when the value is greater than the min value (max is ignored)

If the option is set to 'x' (threshold turned off) the callback is triggered with the fixed period.

The following constants are available for this function:

For option:

  • XMC1400_BREAKOUT_BRICKLET_THRESHOLD_OPTION_OFF = 'x'
  • XMC1400_BREAKOUT_BRICKLET_THRESHOLD_OPTION_OUTSIDE = 'o'
  • XMC1400_BREAKOUT_BRICKLET_THRESHOLD_OPTION_INSIDE = 'i'
  • XMC1400_BREAKOUT_BRICKLET_THRESHOLD_OPTION_SMALLER = '<'
  • XMC1400_BREAKOUT_BRICKLET_THRESHOLD_OPTION_GREATER = '>'
pub fn Xmc1400BreakoutBricklet::get_count_callback_configuration(&self) → ConvertingReceiver<CountCallbackConfiguration>
Return Object:
  • period – Type: u32, Unit: 1 ms, Range: [0 to 232 - 1], Default: 0
  • value_has_to_change – Type: bool, Default: false
  • option – Type: char, Range: See constants, Default: 'x'
  • min – Type: u32, Range: [0 to 232 - 1], Default: 0
  • max – Type: u32, Range: [0 to 232 - 1], Default: 0

Returns the callback configuration as set by Xmc1400BreakoutBricklet::set_count_callback_configuration.

The following constants are available for this function:

For option:

  • XMC1400_BREAKOUT_BRICKLET_THRESHOLD_OPTION_OFF = 'x'
  • XMC1400_BREAKOUT_BRICKLET_THRESHOLD_OPTION_OUTSIDE = 'o'
  • XMC1400_BREAKOUT_BRICKLET_THRESHOLD_OPTION_INSIDE = 'i'
  • XMC1400_BREAKOUT_BRICKLET_THRESHOLD_OPTION_SMALLER = '<'
  • XMC1400_BREAKOUT_BRICKLET_THRESHOLD_OPTION_GREATER = '>'

Callbacks

Callbacks can be registered to receive time critical or recurring data from the device. The registration is done with the corresponding get_*_callback_receiver function, which returns a receiver for callback events.

Note

Using callbacks for recurring events is always preferred compared to using getters. It will use less USB bandwidth and the latency will be a lot better, since there is no round trip time.

pub fn Xmc1400BreakoutBricklet::get_adc_values_callback_receiver(&self) → ConvertingCallbackReceiver<[u16; 8]>
Event:
  • values – Type: [u16; 8], Range: [0 to 212 - 1]

Receivers created with this function receive ADC Values events.

This callback is triggered periodically according to the configuration set by Xmc1400BreakoutBricklet::set_adc_values_callback_configuration.

The members of the received struct are the same as Xmc1400BreakoutBricklet::get_adc_values.

pub fn Xmc1400BreakoutBricklet::get_count_callback_receiver(&self) → ConvertingCallbackReceiver<u32>
Event:
  • count – Type: u32, Range: [0 to 232 - 1]

Receivers created with this function receive Count events.

This callback is triggered periodically according to the configuration set by Xmc1400BreakoutBricklet::set_count_callback_configuration.

The received variable is the same as Xmc1400BreakoutBricklet::get_count.

Virtual Functions

Virtual functions don't communicate with the device itself, but operate only on the API bindings device object. They can be called without the corresponding IP Connection object being connected.

pub fn Xmc1400BreakoutBricklet::get_api_version(&self) → [u8; 3]
Return Object:
  • api_version – Type: [u8; 3]
    • 0: major – Type: u8, Range: [0 to 255]
    • 1: minor – Type: u8, Range: [0 to 255]
    • 2: revision – Type: u8, Range: [0 to 255]

Returns the version of the API definition implemented by this API bindings. This is neither the release version of this API bindings nor does it tell you anything about the represented Brick or Bricklet.

pub fn Xmc1400BreakoutBricklet::get_response_expected(&mut self, function_id: u8) → bool
Parameters:
  • function_id – Type: u8, Range: See constants
Returns:
  • response_expected – Type: bool

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 Xmc1400BreakoutBricklet::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:

  • XMC1400_BREAKOUT_BRICKLET_FUNCTION_SET_GPIO_CONFIG = 1
  • XMC1400_BREAKOUT_BRICKLET_FUNCTION_SET_ADC_CHANNEL_CONFIG = 3
  • XMC1400_BREAKOUT_BRICKLET_FUNCTION_SET_ADC_VALUES_CALLBACK_CONFIGURATION = 7
  • XMC1400_BREAKOUT_BRICKLET_FUNCTION_SET_COUNT_CALLBACK_CONFIGURATION = 11
  • XMC1400_BREAKOUT_BRICKLET_FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
  • XMC1400_BREAKOUT_BRICKLET_FUNCTION_SET_STATUS_LED_CONFIG = 239
  • XMC1400_BREAKOUT_BRICKLET_FUNCTION_RESET = 243
  • XMC1400_BREAKOUT_BRICKLET_FUNCTION_WRITE_UID = 248
pub fn Xmc1400BreakoutBricklet::set_response_expected(&mut self, function_id: u8, response_expected: bool) → ()
Parameters:
  • function_id – Type: u8, Range: See constants
  • response_expected – Type: bool

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.

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:

  • XMC1400_BREAKOUT_BRICKLET_FUNCTION_SET_GPIO_CONFIG = 1
  • XMC1400_BREAKOUT_BRICKLET_FUNCTION_SET_ADC_CHANNEL_CONFIG = 3
  • XMC1400_BREAKOUT_BRICKLET_FUNCTION_SET_ADC_VALUES_CALLBACK_CONFIGURATION = 7
  • XMC1400_BREAKOUT_BRICKLET_FUNCTION_SET_COUNT_CALLBACK_CONFIGURATION = 11
  • XMC1400_BREAKOUT_BRICKLET_FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
  • XMC1400_BREAKOUT_BRICKLET_FUNCTION_SET_STATUS_LED_CONFIG = 239
  • XMC1400_BREAKOUT_BRICKLET_FUNCTION_RESET = 243
  • XMC1400_BREAKOUT_BRICKLET_FUNCTION_WRITE_UID = 248
pub fn Xmc1400BreakoutBricklet::set_response_expected_all(&mut self, response_expected: bool) → ()
Parameters:
  • response_expected – Type: bool

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.

pub fn Xmc1400BreakoutBricklet::set_bootloader_mode(&self, mode: u8) → ConvertingReceiver<u8>
Parameters:
  • mode – Type: u8, Range: See constants
Returns:
  • status – Type: u8, Range: See constants

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:

  • XMC1400_BREAKOUT_BRICKLET_BOOTLOADER_MODE_BOOTLOADER = 0
  • XMC1400_BREAKOUT_BRICKLET_BOOTLOADER_MODE_FIRMWARE = 1
  • XMC1400_BREAKOUT_BRICKLET_BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
  • XMC1400_BREAKOUT_BRICKLET_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
  • XMC1400_BREAKOUT_BRICKLET_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4

For status:

  • XMC1400_BREAKOUT_BRICKLET_BOOTLOADER_STATUS_OK = 0
  • XMC1400_BREAKOUT_BRICKLET_BOOTLOADER_STATUS_INVALID_MODE = 1
  • XMC1400_BREAKOUT_BRICKLET_BOOTLOADER_STATUS_NO_CHANGE = 2
  • XMC1400_BREAKOUT_BRICKLET_BOOTLOADER_STATUS_ENTRY_FUNCTION_NOT_PRESENT = 3
  • XMC1400_BREAKOUT_BRICKLET_BOOTLOADER_STATUS_DEVICE_IDENTIFIER_INCORRECT = 4
  • XMC1400_BREAKOUT_BRICKLET_BOOTLOADER_STATUS_CRC_MISMATCH = 5
pub fn Xmc1400BreakoutBricklet::get_bootloader_mode(&self) → ConvertingReceiver<u8>
Returns:
  • mode – Type: u8, Range: See constants

Returns the current bootloader mode, see Xmc1400BreakoutBricklet::set_bootloader_mode.

The following constants are available for this function:

For mode:

  • XMC1400_BREAKOUT_BRICKLET_BOOTLOADER_MODE_BOOTLOADER = 0
  • XMC1400_BREAKOUT_BRICKLET_BOOTLOADER_MODE_FIRMWARE = 1
  • XMC1400_BREAKOUT_BRICKLET_BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
  • XMC1400_BREAKOUT_BRICKLET_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
  • XMC1400_BREAKOUT_BRICKLET_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4
pub fn Xmc1400BreakoutBricklet::set_write_firmware_pointer(&self, pointer: u32) → ConvertingReceiver<()>
Parameters:
  • pointer – Type: u32, Unit: 1 B, Range: [0 to 232 - 1]

Sets the firmware pointer for Xmc1400BreakoutBricklet::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.

pub fn Xmc1400BreakoutBricklet::write_firmware(&self, data: [u8; 64]) → ConvertingReceiver<u8>
Parameters:
  • data – Type: [u8; 64], Range: [0 to 255]
Returns:
  • status – Type: u8, Range: [0 to 255]

Writes 64 Bytes of firmware at the position as written by Xmc1400BreakoutBricklet::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.

pub fn Xmc1400BreakoutBricklet::write_uid(&self, uid: u32) → ConvertingReceiver<()>
Parameters:
  • uid – Type: u32, Range: [0 to 232 - 1]

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.

pub fn Xmc1400BreakoutBricklet::read_uid(&self) → ConvertingReceiver<u32>
Returns:
  • uid – Type: u32, Range: [0 to 232 - 1]

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

Constants

pub const Xmc1400BreakoutBricklet::DEVICE_IDENTIFIER

This constant is used to identify a XMC1400 Breakout Bricklet.

The Xmc1400BreakoutBricklet::get_identity function and the IpConnection::get_enumerate_callback_receiver callback of the IP Connection have a device_identifier parameter to specify the Brick's or Bricklet's type.

pub const Xmc1400BreakoutBricklet::DEVICE_DISPLAY_NAME

This constant represents the human readable name of a XMC1400 Breakout Bricklet.