Working with Generated Fixed-Point Files
This example shows how to work with the files generated during floating-point to fixed-point conversion.
This tutorial uses a simple filter implemented in floating-point and an associated testbench to illustrate the file structure of the generated fixed-point code.
design_name = 'mlhdlc_filter'; testbench_name = 'mlhdlc_filter_tb';
MATLAB Design: mlhdlc_filter
MATLAB testbench: mlhdlc_filter_tb
Simulate the Design
Simulate the design with the testbench prior to code generation to make sure there are no runtime errors.
Create a New HDL Coder™ Project
To create a new project, enter the following command:
coder -hdlcoder -new flt2fix_project
Next, add the file 'mlhdlc_filter' to the project as the MATLAB Function and 'mlhdlc_filter_tb' as the MATLAB Test Bench.
Refer to Get Started with MATLAB to HDL Workflow for a more complete tutorial on creating and populating MATLAB HDL Coder projects.
Fixed-Point Code Generation Workflow
Perform the following tasks in preparation for the fixed-point code generation step:
Click the Workflow Advisor button to launch the Workflow Advisor.
Convert to fixed-point at build timefor the option Fixed-point conversion.
Right-click the Fixed-Point Conversion step and select Run to Selected Task to execute the instrumented floating-point simulation.
Refer to Floating-Point to Fixed-Point Conversion for a more complete tutorial on these steps.
Floating-Point Design Structure
The original floating-point design and testbench have the following relationship.
For floating-point to fixed-point conversion, the following requirements apply to the original design and the testbench:
The testbench 'mlhdlc_filter_tb.m' (1) must be a script or a function with no inputs. The test bench can have local helper functions that take inputs.
The design 'mlhdlc_filter.m' (2) must be a function.
There must be at least one call to the design from the testbench. All call sites contribute when determining the proposed fixed-point types.
Both the design and testbench can call other sub-functions within the file or other functions on the MATLAB path. Functions that exist within matlab/toolbox are not converted to fixed-point.
In the current example, the MATLAB testbench 'mlhdlc_filter_tb' has a single call to the design function 'mlhdlc_filter'. The testbench calls the design with floating-point inputs and accumulates the floating-point results for plotting.
During the type validation step, fixed-point code is generated for this design and compiled to verify that there are no errors when applying the types. The output files will have the following structure.
The following steps are performed during fixed-point type validation process:
The design file 'mlhdlc_filter.m' is converted to fixed-point to generate fixed-point MATLAB code, 'mlhdlc_filter_fixpt.m' (3).
All user-written functions called in the floating-point design are converted to fixed point and included in the generated design file.
A new design wrapper file is created, called 'mlhdlc_filter_wrapper_fixpt.m' (2). This file converts the floating-point data values supplied by the testbench to the fixed-point types determined for the design inputs during the conversion step. These fixed point values are fed into the converted fixed-point design, 'mlhdlc_filter_fixpt.m'.
'mlhdlc_filter_fixpt.m' will be used for HDL code generation.
All the generated fixed-point files are stored in the output directory 'codegen/mlhdlc_filter/fixpt'.
Click the links to the generated code in the Workflow Advisor log Window to examine the generated fixed-point design and wrapper.