 Hello, and welcome to this presentation of the STM32 QBMX Code Generation Tool. It covers the main features of this tool, which is used to configure and generate code, compile and debug, and estimate power consumption for the STM32 family of microcontrollers. While this presentation is specifically about the STM32 MP1 microprocessor, STM32 QBMX is a common platform to the whole STM32 family. However, the feature set available for an MPU-class device is different. The STM32 QBMX application helps developers using STM32 microcontrollers through a user interface that guides the initial configuration of a firmware project. It provides the means to configure pin assignments, the clocked tree, integrated peripherals, and simulate the power consumption of the resulting project. It uses a rich library of data from the STM32 microcontroller portfolio. The application is intended to ease the initial phase of development by helping developers select the best product with regards to features and power. The user interface is built around a natural workflow of choosing a suitable MCU, selecting the required peripherals, and assigning pin configurations. The power consumption calculator aids in designing an efficient system. Finally, the project initialization code can be generated and potentially regenerated while keeping the user code intact. Download the STM32 QBMX installer for free from the ST website and install it. Then set your preferences in the settings menu. One menu for the updater and library download, Alt plus S, the other menu for code generation and integration with development tool chains, Alt plus P. Once this setup is completed, a new project can be created. If the internet connection is configured correctly, the tool can update itself as well as the code libraries used for generating the project workspaces. Use the install new libraries option, Alt plus U, to download additional STM32 cube libraries, or retrieve older versions for interoperability reasons. However, note that the STM32 QBMX tool is not tested with all historical library releases, and new library releases may not work correctly with old tool versions. The MCU selector window will come up after selecting the new project option. If the user knows which MCU to use, it can be found quickly. If not, the available products can be filtered based on the specific requirements. The next step is to select the peripherals to be used and, where applicable, assign pins to their inputs and outputs. Independent GPIOs can also be configured. Signals are assigned to default pins, but they can be transferred to alternate locations, which are displayed by control clicking on the pin. For example, when the I2C1 peripheral is enabled, the tool automatically assigns it to the default pins. The tool automatically takes into account most bonds between the peripherals and software components it manages. As more pins are reserved for their alternate functions, the choice of remaining configurations for other peripherals decreases. The limitations are indicated by icon changes on other peripheral nodes. Left-click on the pin to display its alternate functions. Right-click on the pin to name or select the pin assignment. If a pinout is selected without a particular peripheral enabled, or if there is any other problem with the pinout, the pin turns orange instead of green. There are different possible states for peripheral modes. Dimmed. The mode is not available because it requires another mode to be set. Place the mouse pointer over the dimmed mode to see the reason. It may require a disabled clock source or may have other peripheral dependencies. Yellow. The mode is available with limitations because some options are blocked by conflicts. For example, the use art may not be configured to synchronous mode because all the selectable clock pins are taken. Red. Signals required for this mode cannot be mapped to the pinout. This may occur, for example, if a crucial signal has all its alternate pins used by other peripherals. Signals can be set or moved directly from the pinout view. Click on the pin to display the list of possible signals and select one. This works for GPIOs which have no peripherals assigned. To see alternate pins for a signal, hold the control key and click on the signal. You can then drag and drop the signal to the new pin while holding the control key. It is not necessary to manually set all unused pins to analog. There is a semi-automated step that does this. When configuring a peripheral, most important is to decide what boot step and arm core it is assigned to. That determines what code is generated for it. Not all IPs are available for each mode. The dialogue window shows basic parameters, dependencies, and constraints. Simple dropdown menus are used when applicable. Interrupts priorities can only be set in the NVIC settings tab. The peripheral window can only be used to enable or disable each interrupt. The DMA settings tab contains all the parameters for DMA requests relevant for initialization, but runtime parameters, such as start address, are not managed here. GPIO settings tab is used to define GPIO parameters and features, pin filtering, and the possibility to label each signal for easy identification. A central location with an easy to understand overview of available and enabled interrupts, along with their priorities, is another advantage of STM32 Cube MX. This window is used to enable interrupts for selected peripherals and to configure the priorities. Select the tab for the corresponding DMA channel and click the add button to add a DMA request for the specified peripherals. Verify all configuration options. Note that this configures a DMA channel, but does not fully describe a DMA transfer. This must be done in the application code. The GPIO tab in the pin configuration window facilitates the configuration and initialization settings for each pin. Each pin is listed in table format, which provides an overview of the pin configuration along with its user label. Sort, search, and apply modifications to selected pins using dropdown menus. Default values assigned by the tool are safe, but may not work with certain peripheral configurations. Check that the GPIO speed selected by the tool is sufficient for the peripheral communication speed and that an internal pull-up is selected where needed. To assign the settings faster, try selecting groups of pins rather than configuring pins individually. Use tabs to get pin groups dedicated to specific peripherals. Note that settings applied during initialization can be modified during runtime, but that is outside the scope of the STM32 Cube MX tool. Each middleware software component has options that are different, but they are all presented in a similar fashion, giving easy access to initialization options and providing informative descriptions. The configuration tab of the main window provides an overview of all the configurable hardware and software components that STM32 Cube MX can help set up. Each button with access to configuration options is displayed with a small icon indicating the configuration state. The default state is not configured. Clicking on a button for a peripheral or middleware displays its configuration options. Even when configured correctly, further modifications are possible. Warning signs provide notifications about incorrect configurations and the peripheral will not work if code is generated in this state. Critical errors are represented by a red X and the configuration must be modified to continue. To add more peripherals and components, return to the Pinout tab. The Clock Configuration tab provides a schematic overview of the clock paths, along with all clock sources, dividers, and multipliers. Actual clock speeds are visible. Active and enabled clock signals are highlighted in blue. Drop-down menus and buttons serve to modify the actual clock configuration. If a configured value is out of bounds, it immediately turns red to highlight a problem. It also works the other way. Enter the required clock speed in a blue frame and the software will attempt to reconfigure multipliers and dividers to provide the requested value. Right-click on a clock value in blue to lock it to prevent modifications. When all inputs, outputs, and peripherals are configured, the code is ready to be generated. First, check the settings in the Project menu of the main window. STM32 Cube HAL Initialization Code is generated for the ARM M-Core, DTS for the ARM Application Core. One of the several supported development tools can be selected to take over the generated project, including tool chains from Keele, IAR, and Atalic. User code must be kept between the constraints of the user code comment blocks in order for the initialization settings to be modified using STM32 Cube MX without affecting the custom code. This window is available when saving the project, save as. The tool chain folder refers to where the workspace for the tool chain will be placed, not the actual tool chain application location. A limited version of this dialog window is also available using the Alt plus P shortcut to display project settings. The STM32 Cube HAL library may be associated with the project in different ways. Select the copy option if the project should be migrated as a compact package, or if there is a need to customize the library code. Keeping the library in the original location makes it easier to share the latest version of the library among several projects. It can also generate the initialization code for all peripherals together in the STM32 MP1XX HAL MSP.C file, or generate one file per peripheral. Options to backup or delete old files are a matter of the preferred workflow. Keep in mind that the options are tied to the regeneration function. This is also where the keep user code when regenerating option is enabled. The set all free pins as analog setting helps lower power consumption, but if the SWD JTAG interface is not specifically selected in the pinout tab, this option will disable the debug interface. Full assert enables checking the parameters passed to the HAL functions and may help reveal some bugs in the user code without an excess debugging effort. The user interface is a great tool. It is a universal assistant for all STM32 microcontrollers. However, it cannot tackle all the details of each product while providing a useful overview of the diversified STM32 portfolio. In case of doubt, please refer to the reference manual or data sheet for more detailed and accurate information. Do not hesitate to read the application notes and examples to learn more. It is common practice to start an application with STM32 cube MX to quickly get a prototype working and then modify the code when dynamic changes are needed, typically to support a different clock or a new GPIO configuration in the same application. If the user wrote the code within the user areas defined by the STM32 cube MX generator, it is possible to revert to the initial STM32 cube MX setup when some modifications are needed at the top level of user interface. This typically involves adding GPIO pin configurations, selecting another clock, or changing the NVIC priority, for example. When developing embedded applications, low power consumption is often the primary design goal. Extracting power consumption levels from data sheets is a time-consuming and tedious job. The power consumption calculator attempts to simplify this task by exporting referenced values from the data sheet to a smart graphic tool, producing informative estimates from configurable use cases. For external memory timing settings, an automated DDR memory tester is also available. The power consumption calculator can estimate the battery lifetime used as either main or supplementary power supplies. Sequences can easily be imported and exported. Illegal state transitions are detected too. It is even possible to compare sequence executions of two different MCUs or MPUs and generate a report. The power consumption calculator is the fourth tab in the STM32 cube MX main window. The window is divided into several panes. The general configuration pane summarizes the typical operating conditions and the MCU type currently selected. The second pane displays the simulation sequence and its controls. There is no button to execute the simulation. The results are available instantaneously. The general PCC configuration pane is mostly informative, summarizing the selected MCU and the default power source. Parameters such as temperature and voltage may even be defined depending on the MCU selected and the available power consumption data. The battery selection pane is used to select or define a battery type. The battery source is optional and, if defined, may be used in only selected sequence steps, simulating a device that works both independently and connected to an external power source. Information and help sections include useful notes for the user. The sequence table defines a series of steps with different durations and configurations. Its length is virtually unlimited. Sequences can be loaded, modified and reused. Individual steps can be duplicated and repositioned within the sequence using the user interface. If enabled, all state transitions are checked against basic validity rules to prevent illegal jumps in frequency or power ranges. Problematic steps are instantly highlighted in the sequence table. Click the show log button to display a detailed explanation. The compare feature displays a comparison of the power and performance in the current scenario with a saved sequence. Different configurations, including different MCUs, can be evaluated against each other. A power step can be added or edited in this dialogue window. If the transition checker is enabled, it will preset the new step with allowed values. The power step is determined by several characteristics, with the power mode being the most important. The availability and characteristics of each power mode are described in the specific reference manual or data sheet. Power mode selection has the most significant impact on the availability of other settings, interfaces and power performance balance. The voltage regulator sets the core voltage. At lower voltages, the system clock frequency is limited, but the power consumption is often dramatically reduced. Refer to the data sheet for more details. The address from which the instruction is fetched and the related settings can also influence the power consumption and available clock speeds. The supply voltage for which power consumption is calculated. Use the nearest possible value if the actual voltage is not available. The last option is present to exclude cases when the device is, for example, connected to the USB in battery drain mode. To learn more about power modes, refer to the system power control module training presentation. The power consumption calculator features powerful presentation tools. Click on the EXT display button to display the report in a separate window. There are many different ways available to plot the current consumption estimates in graphical form. The default method is based on the power step sequence and the consumption over time. Alternatively, the percentage of energy spent in different modes can be charted. The pie chart may show the share of each mode or split to only display run and low power modes. It is also possible to split the power consumption of peripherals and plot their power requirements in a graph. You can plot digital peripherals only, analog peripherals only or a mixed view with both. The following three slides are a brief introduction to a new STM32 CubeMX feature. So far, specific to the STM32 MP1-MPU. It is the ability to configure, test, and fine-tune a connection to a standard external DDR memory. The following three slides are a brief introduction to a new STM32 CubeMX feature. So far, specific to the STM32 MP1-MPU. It is the ability to configure, test, and fine-tune a connection to a standard external DDR memory. Unlike the other function of the STM32 CubeMX, the DDR test configuration requires a physical board connection and a binary to load. A basic U-boot SPL binary image is available in the starter package. The connection may be a simple ST-Link virtual COM port or VCP when a discovery board is used. To test a user-specific board, the default port used by the U-boot SPL for connection is the UART4 port. This function provides easy means to execute various tests to detect and identify possible failures in the dynamic memory. Both basis and stress tests are available in the U-boot SPL and executable from the STM32 CubeMX suite. The DDR tuning is a semi-automated process used to determine fine settings of the DDR memory interface and compensate for unequal route length and other factors. See application notes AN5168 and AN5122 for further details. A more detailed description is also available in the STM32 CubeMX documentation. A file with the extension .IOC contains the static initialization settings. The power sequence is saved using the .PCS extension. A PDF report is generated along with simplified text and a separate JPEG image file with pinout. For more information about using the STM32 CubeMX code generation tool, the documents listed in this slide are available for download on www.st.com. Thank you.