We’re designing a new product using the STM32L151ZE microcontroller. We’ve been doing some tests with the NUCLEO-L152RE dev board and everything has been good so far. Now, we want to move on to the final microprocessor and we realized that it is not present in the device list. I would like to know what are the steps to “create” my own board device in the mbed OS file system so we can stil use all the libraries and developments made so far.
Many thanks for your time. Best regards,
To be able to do and maintain official supported board you have to be a Partner. You can still use your own board.
You can fork, customize and build DAPLink for your purposes. We have mechanisms to let developers to detect their custom platform using the
mbed ls mock feature for their development:
This file has been truncated.
# Development moved
The development of Mbed LS has been moved into the [mbed-os-tools](../../src/mbed_os_tools) package. You can continue to use this module for legacy reasons, however all further development should be continued in the new package.
# Mbed LS
Mbed LS is a Python (2 and 3) module that detects and lists Mbed Enabled devices connected to the host computer. The Mbed OS team publishes Mbed LS on PyPI. It works on all major operating systems (Windows, Linux and Mac OS X).
It provides the following information for all connected boards in a console (terminal) output:
- Mbed OS platform name.
- Mount point (MSD or disk).
- Serial port.
You can also create configuration for a custom platform:
This file has been truncated.
# Using Mbed OS on a custom board
When designing a custom microcontroller board to run Mbed OS, you may need to make software customizations for the unique design choices you have made for your new board, such as clocking, pin connections and peripheral use. You can accomplish this by adding configuration and source files to an Mbed OS-based application project without the need to modify files within Mbed OS, itself. You can add a file named `custom_targets.json` to your project, which can store your custom target configurations. If your board is based on an existing Mbed Enabled microcontroller, you can simply extend that board configuration without the need to implement all the files yourself.
This tutorial covers the most common methods used to create a custom port of Mbed OS when starting from an existing Mbed Enabled board. For detailed information on how to create a port from scratch, go to the [Mbed Porting guide](../porting/index.html). Additionally, not all possible aspects of target configuration are covered. For detailed information on all the ways you can configure targets, go to [adding and configuring targets](../reference/adding-and-configuring-targets.html).
## Extending an existing MCU target configuration
Consider a situation in which you are creating a new board based on an existing Mbed Enabled board. This tutorial lists the steps to create the software for a new board we will call `ImaginaryBoard`. This board is based on [DISCO-L475VG-IOT01A](https://os.mbed.com/platforms/ST-Discovery-L475E-IOT01A/). It shares most of the features of DISCO-L475VG-IOT01A, but it does not use `AnalogOut`, `AnalogIn`, `CAN` or `USB`. Some pins are connected differently on the new board.
Follow these steps to create a custom port for Mbed OS:
1. [Install Mbed CLI](../tools/installation-and-setup.html) if you don't already have it.
1. (Optional) Create a new Mbed program (for example, `mbed-os-imaginary-port`).
If you don't already have an Mbed program on your computer, run this Mbed CLI command in a command terminal:
And for the specifics about adding support for a new board based on STM32 please visit: