Integer to Bit Converter

R2026b

Map vector of integers to vector of bits

• 

Integer to Bit Converter block

To add a block to a model, double-click the canvas and start typing the block name. Then, select the block from the list.

Libraries:
Simulink / Logic and Bit Operations

Description

The Integer to Bit Converter block maps each integer (or fixed-point value) in the input vector to a group of bits in the output vector.

This block is single-rate and single-channel. The block maps each integer value (or stored integer when you use a fixed point input) to a group of M bits, using the selection for the Output bit order to determine the most significant bit. The resulting output vector length is M times the input vector length.

Ports

Input

In — Input signal

integer | column vector of integers

Input signal, specified as an integer or a length N column vector of integers.

If M is specified by the Number of bits per integer(M) parameter:

• When the Number of bits per integer parameter is set to Unsigned, input values must be integers in the range [0, (2^M – 1)].

• When the Number of bits per integer parameter is set to Signed, input values must be integers in the range [(–2^M-1), (2^{M – 1} – 1)].

During simulation, the block performs a run-time check and issues an error if any input value is outside of the appropriate range. When the block generates code, it does not perform this run-time check.

Data Types: double

Output

Out — Output signal

bit scalar | column vector of bits

Output signal, returned as a scalar or column vector of bits of length M·N.

Parameters

Number of bits per integer(M) — Number of bits per integer

3 (default) | integer in the range [1, 32]

Number of input bits mapped to each integer in the input, specified as an integer in the range [1, 32].

Programmatic Use

Block Parameter: nbits

Type: character vector

Values: integer in the range [1, 32]

Default: '3'

Treat input values as — Treat input values as

Unsigned (default) | Signed

Indicate if the integer value input ranges should be treated as signed or unsigned.

Programmatic Use

Block Parameter: signedInputValues

Type: character vector

Values: 'Unsigned' | 'Signed'

Default: 'Unsigned'

Output bit order — Output bit order

MSB first (default) | LSB first

Define whether the first bit of the output signal is the most significant bit (MSB) or the least significant bit (LSB).

Programmatic Use

Block Parameter: bitOrder

Type: character vector

Values: 'MSB first' | 'LSB first'

Default: 'MSB first'

Output data type — Output data type

Inherit via internal rule (default) | Smallest unsigned integer | Same as input | double | single | int8 | uint8 | int16 | uint16 | int32 | uint32 | boolean

Specify the data type of the output bits. You can choose one of the following Output data type options:

• Inherit via internal rule –– The block determines the output data type based on the input data type.

  • If the input signal is floating-point (either single or double), the output data type is the same as the input data type.

  • If the input data type is not floating-point, the output data type is determined as if the parameter is set to Smallest integer.

• Smallest integer ––The block selects the output data type based on settings used in the Hardware Implementation Pane of the Configuration Parameters dialog box.

  • If you select ASIC/FPGA for the device vendor, the output data type is the ideal one-bit size (ufix1).

  • For all other device vendor selections, the output data type is an unsigned integer with the smallest available word length, as defined in the Hardware Implementation settings (for example, uint8)

• Same as input

• double

• single

• uint8

• uint16

• uint32

Programmatic Use

Block Parameter: outDtype

Type: character vector

Values: 'Inherit via internal rule' | 'Smallest unsigned integer' | 'Same as input' | 'double' | 'single' | 'int8' | 'uint8' | 'int16' | 'uint16' | 'int32' | 'uint32'| 'boolean'

Default: 'Inherit via internal rule'

Block Characteristics

Data Types	Boolean | double | fixed pointa | integer | single
Direct Feedthrough	no
Multidimensional Signals	no
Variable-Size Signals	yes
Zero-Crossing Detection	no
a ufix(1) only at the output when ASIC/FPGA is selected in the Hardware Implementation Pane.

Programmatic Use: Add Block

To add the block programmatically, use the add_block function with one of these library block paths as the source.

"simulink/Logic and Bit Operations/Integer to Bit Converter"

Example: add_block("simulink/Logic and Bit Operations/Integer to Bit Converter","myModel/myBlock",MakeNameUnique="on")

Extended Capabilities

C/C++ Code Generation
Generate C and C++ code using Simulink® Coder™.

HDL Code Generation

Generate VHDL, Verilog and SystemVerilog code for FPGA and ASIC designs using HDL Coder™.

HDL Coder™ provides additional configuration options that affect HDL implementation and synthesized logic.

HDL Architecture

This block has one default HDL architecture.

HDL Block Properties

General
ConstrainedOutputPipeline	Number of registers to place at the outputs by moving existing delays in the design. Distributed pipelining does not redistribute these registers. The default value is 0. For more details, see ConstrainedOutputPipeline (HDL Coder).
InputPipeline	Number of input pipeline stages to insert in the generated code. Distributed pipelining and constrained output pipelining can move these registers. The default value is 0. For more details, see InputPipeline (HDL Coder).
OutputPipeline	Number of output pipeline stages to insert in the generated code. Distributed pipelining and constrained output pipelining can move these registers. The default value is 0. For more details, see OutputPipeline (HDL Coder).
SynthesisAttributes	Specifies the synthesis attributes for the blocks and block output signals in the model. The generated HDL code contains these attributes. For more information, see SynthesisAttributes (HDL Coder).

Native Floating Point
LatencyStrategy	Specify whether to map the blocks in your design to MAX, MIN, CUSTOM, or ZERO latency for floating-point types. See LatencyStrategy (HDL Coder).
CustomLatency	When LatencyStrategy is set to CUSTOM and use this property to specify a custom latency value between ZERO and MAX. See NFPCustomLatency (HDL Coder).

Data Type Support

The block supports these data types for HDL code generation:

Input Port	Dimension	Fixed-Point	Floating-Point	Built-in Integers	Bus	Boolean	Complex Signal
In	Scalar Vector	Yes	Single Double	Yes	Yes	Yes	No

Latency Details

The block uses multicycle implementations to introduce additional latency in the generated code. To see the added latency, view the generated model or validation model. See Generated Model and Validation Model (HDL Coder).

Floating-Point Latency

Architecture	Floating-Point Type	Latency Strategy	Latency (in cycles)	Custom Latency Support
default	Single	Min	6	Yes
		Max	6
	Double	Min	3
		Max	6

Restrictions

• Matrix input is not supported.

Version History

Introduced before R2006a

R2026a: Specify synthesis attributes for blocks and block output signals

Use the SynthesisAttributes HDL block property to specify the synthesis attributes for the block and its output signals. HDL Coder includes these attributes in the generated HDL code.

R2022a: Integer to Bit Converter Block Added to Simulink Logic and Bit Operations Library

The Integer to Bit Converter block has been added from the Communications Toolbox > Utility Blocks library to the Simulink > Logic and Bit Operations library. All existing models continue to work.