Linux flashing tools - Revision history

Fede.tft at 07:58, 10 May 2026

2026-05-10T07:58:08Z

← Older revision		Revision as of 07:58, 10 May 2026
Line 116:		Line 116:

	Please replace main.bin with image.bin if you're using processes.		Please replace main.bin with image.bin if you're using processes.

			'''Note:''' these chips have a quirk where once you first attach a debugger, power saving states don't work anymore until the next powercycle. There is a workaround in the ''exit_debug_mode'' function, to be called through gdb to end a debugging session [[https://github.com/fedetft/miosix-kernel/blob/master/miosix/arch/board/nrf52840_generic/openocd.cfg]]

	= ATsam Microcontrollers =		= ATsam Microcontrollers =

Fede.tft at 07:52, 10 May 2026

2026-05-10T07:52:42Z

← Older revision		Revision as of 07:52, 10 May 2026
Line 121:		Line 121:
	== Flashing through gdb/openocd ==		== Flashing through gdb/openocd ==

	'''Warning:''' these chips come from the factory a bootloader in the FLASH memory. This means it's possible to accidentally overwrite the bootloader. The bootloader is stored from address 0x0 to 0x4000.		'''Warning:''' these chips come from the factory with a bootloader in the FLASH memory. This means it's possible to accidentally overwrite the bootloader. The bootloader is stored from address 0x0 to 0x4000.

	TODO this needs better documenting, the short version is to type in a gdb session		TODO this needs better documenting, the short version is to type in a gdb session
Line 137:		Line 137:
	TODO document using lrzsz to talk to the serial bootloader		TODO document using lrzsz to talk to the serial bootloader

	'''Warning:''' these chips come from the factory a bootloader in the FLASH memory. This means it's possible to accidentally overwrite the bootloader.		'''Warning:''' these chips come from the factory with a bootloader in the FLASH memory. This means it's possible to accidentally overwrite the bootloader.

	= LPC2000 Microcontrollers =		= LPC2000 Microcontrollers =

Fede.tft at 07:51, 10 May 2026

2026-05-10T07:51:40Z

← Older revision		Revision as of 07:51, 10 May 2026
Line 120:		Line 120:

	== Flashing through gdb/openocd ==		== Flashing through gdb/openocd ==

			'''Warning:''' these chips come from the factory a bootloader in the FLASH memory. This means it's possible to accidentally overwrite the bootloader. The bootloader is stored from address 0x0 to 0x4000.

	TODO this needs better documenting, the short version is to type in a gdb session		TODO this needs better documenting, the short version is to type in a gdb session
Line 134:		Line 136:

	TODO document using lrzsz to talk to the serial bootloader		TODO document using lrzsz to talk to the serial bootloader

			'''Warning:''' these chips come from the factory a bootloader in the FLASH memory. This means it's possible to accidentally overwrite the bootloader.

	= LPC2000 Microcontrollers =		= LPC2000 Microcontrollers =

Fede.tft at 23:07, 9 May 2026

2026-05-09T23:07:49Z

← Older revision		Revision as of 23:07, 9 May 2026
Line 96:		Line 96:
	Older distros may not have it in their repos. In this case you'll need to compile it from sources.		Older distros may not have it in their repos. In this case you'll need to compile it from sources.

	To use this flashing tool, you'll need to interact with your board to start the bootloader. This does not happen by default, and requires to tie the BOOT pin high while sending a RUN pulse (RP2040 microcontrollers call their RESET pin RUN, go figure...). Annoyingly, official boards from Raspberry Pi only have a BOOT ~~butting~~, and lack a reset button, so you'll either need to		To use this flashing tool, you'll need to interact with your board to start the bootloader. This does not happen by default, and requires to tie the BOOT pin high while sending a RUN pulse (RP2040 microcontrollers call their RESET pin RUN, go figure...). Annoyingly, official boards from Raspberry Pi only have a BOOT button, and lack a reset button, so you'll either need to
	* solder a pushbutton between RUN and GND		* solder a pushbutton between RUN and GND
	* disconnect and reconnect power while holding the BOOT button every time you want to flash the microcontroller		* disconnect and reconnect power while holding the BOOT button every time you want to flash the microcontroller

Fede.tft at 23:06, 9 May 2026

2026-05-09T23:06:57Z

← Older revision		Revision as of 23:06, 9 May 2026
Line 96:		Line 96:
	Older distros may not have it in their repos. In this case you'll need to compile it from sources.		Older distros may not have it in their repos. In this case you'll need to compile it from sources.

	To use this flashing tool, you'll need to interact with your board to start the ~~STM32~~ bootloader. This does not happen by default, and requires to tie the BOOT pin high while sending a RUN pulse (RP2040 microcontrollers call their RESET pin RUN). Annoyingly, official boards from Raspberry Pi only have a BOOT butting, and lack a reset button, so you'll either need to		To use this flashing tool, you'll need to interact with your board to start the bootloader. This does not happen by default, and requires to tie the BOOT pin high while sending a RUN pulse (RP2040 microcontrollers call their RESET pin RUN, go figure...). Annoyingly, official boards from Raspberry Pi only have a BOOT butting, and lack a reset button, so you'll either need to
	* solder a pushbutton between RUN and GND		* solder a pushbutton between RUN and GND
	* disconnect and reconnect power while holding the BOOT button every time you want to flash the microcontroller		* disconnect and reconnect power while holding the BOOT button every time you want to flash the microcontroller

Fede.tft at 23:05, 9 May 2026

2026-05-09T23:05:58Z

← Older revision		Revision as of 23:05, 9 May 2026
Line 91:		Line 91:

	<source lang="bash">		<source lang="bash">
	sudo apt install ~~lpc21isp~~		sudo apt install picotool
	</source>		</source>

Fede.tft at 23:05, 9 May 2026

2026-05-09T23:05:06Z

← Older revision		Revision as of 23:05, 9 May 2026
Line 61:		Line 61:
	An useful tool, with a GUI, sadly unmaintained. This section is kept for reference, and should development of this tool restart.		An useful tool, with a GUI, sadly unmaintained. This section is kept for reference, and should development of this tool restart.

	[https://code.google.com/p/qstlink2 QSTLink2]. It has a GUI but the precompiled ppa is no longer updated for the latest Ubuntu releases. The installation on Ubuntu/Debian requires to add a ''ppa'' and install it via ''apt-get''. Also, it is ~~recomended~~ to install the udev rules, which allow QSTLink2 to connect to the USB port without the need to run it from root.		[https://code.google.com/p/qstlink2 QSTLink2]. It has a GUI but the precompiled ppa is no longer updated for the latest Ubuntu releases. The installation on Ubuntu/Debian requires to add a ''ppa'' and install it via ''apt-get''. Also, it is recommended to install the udev rules, which allow QSTLink2 to connect to the USB port without the need to run it from root.

	<source lang="bash">		<source lang="bash">

Fede.tft at 23:04, 9 May 2026

2026-05-09T23:04:25Z

← Older revision		Revision as of 23:04, 9 May 2026
Line 59:		Line 59:
	== QSTLink2 ==		== QSTLink2 ==

	An useful tool, ~~wit~~ a GUI, sadly unmaintained. This section is kept for reference, and should development of this tool restart.		An useful tool, with a GUI, sadly unmaintained. This section is kept for reference, and should development of this tool restart.

	[https://code.google.com/p/qstlink2 QSTLink2]. It has a GUI but the precompiled ppa is no longer updated for the latest Ubuntu releases. The installation on Ubuntu/Debian requires to add a ''ppa'' and install it via ''apt-get''. Also, it is recomended to install the udev rules, which allow QSTLink2 to connect to the USB port without the need to run it from root.		[https://code.google.com/p/qstlink2 QSTLink2]. It has a GUI but the precompiled ppa is no longer updated for the latest Ubuntu releases. The installation on Ubuntu/Debian requires to add a ''ppa'' and install it via ''apt-get''. Also, it is recomended to install the udev rules, which allow QSTLink2 to connect to the USB port without the need to run it from root.

Fede.tft at 23:02, 9 May 2026

2026-05-09T23:02:19Z

← Older revision		Revision as of 23:02, 9 May 2026
Line 1:		Line 1:
	For boards officially supported by the Miosix kernel, the build system includes a ''make program'' rule to easily flash the kernel (and application). If you use ''make program'', the choice of which flashing tool to use has been made by whoever contributed the port. If you don't have the required tool, ''make program'' will fail with an error related to not finding the required flashing tool.		For most boards officially supported by the Miosix kernel, the build system includes a ''make program'' rule to easily flash the kernel (and application). If you use ''make program'', the choice of which flashing tool to use has been made by whoever contributed the port. If you don't have the required tool, ''make program'' will fail with an error related to not finding the required flashing tool.

	Using ''make program'' is only a convenience, not a necessity. Miosix can work with any flashing utility that accepts as input raw binary files. If you prefer to use another flashing program, just directly run your flashing program passing it the appropriate ''.bin'' file (the name is main.bin if you're '''not''' using processes, or image.bin if you are using processes).		Using ''make program'' is only a convenience, not a necessity. Miosix can work with any flashing utility that accepts as input raw binary files. If you prefer to use another flashing program, just directly run your flashing program passing it the appropriate ''.bin'' file (the name is main.bin if you're '''not''' using processes, or image.bin if you are using processes).

Fede.tft: Created page with "For boards officially supported by the Miosix kernel, the build system includes a ''make program'' rule to easily flash the kernel (and application). If you use ''make program'', the choice of which flashing tool to use has been made by whoever contributed the port. If you don't have the required tool, ''make program'' will fail with an error related to not finding the required flashing tool. Using ''make program'' is only a convenience, not a necessity. Miosix can work..."

2026-05-09T23:01:25Z

Created page with "For boards officially supported by the Miosix kernel, the build system includes a ''make program'' rule to easily flash the kernel (and application). If you use ''make program'', the choice of which flashing tool to use has been made by whoever contributed the port. If you don't have the required tool, ''make program'' will fail with an error related to not finding the required flashing tool. Using ''make program'' is only a convenience, not a necessity. Miosix can work..."

New page

For boards officially supported by the Miosix kernel, the build system includes a ''make program'' rule to easily flash the kernel (and application). If you use ''make program'', the choice of which flashing tool to use has been made by whoever contributed the port. If you don't have the required tool, ''make program'' will fail with an error related to not finding the required flashing tool.

Using ''make program'' is only a convenience, not a necessity. Miosix can work with any flashing utility that accepts as input raw binary files. If you prefer to use another flashing program, just directly run your flashing program passing it the appropriate ''.bin'' file (the name is main.bin if you're '''not''' using processes, or image.bin if you are using processes).

Following is a list of suggestions for the most common microcontrollers used with Miosix.

= STM32 microcontrollers =

== st-flash ==

A popular choice for STM32 development boards that have an embedded STLink USB programmer/debugger, such as discovery and nucleo boards. To install it on Debian/Ubuntu run:

<source lang="bash">
sudo apt install stlink-tools
</source>

You'll need to connect the development board to your computer with an USB cable that will both provide power and allow programming. No user interaction on the board is required to enter programming mode.

== dfu-util ==

This tool allows to program STM32 microcontrollers that have an USB bootloaders (roughly speaking, from STM32F2 onward). This tool is used for some third party development boards (such as the blackpill boards), but is also a convenient choice if you design your own boards.

To install it on Debian/Ubuntu run:

<source lang="bash">
sudo apt install dfu-util
</source>

To use this flashing tool, you'll need to interact with your board to start the STM32 bootloader. This does not happen by default, and usually requires to tie the BOOT0 pin high while sending a RESET pulse. If you do so correctly, the microcontroller will show up when doing an ''lsusb'' as an STM32 in DFU mode:

<source>
Bus 001 Device 011: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
</source>

== stm32flash ==

This tool allows to program STM32 microcontrollers using the serial bootloader, which is supported by every STM32. It is also the slowest option, though.

To install it on Debian/Ubuntu run:

<source lang="bash">
sudo apt install stm32flash
</source>

To use this flashing tool, you'll need to interact with your board to start the STM32 bootloader. This does not happen by default, and usually requires to tie the BOOT0 pin high while sending a RESET pulse.

== Flashing through gdb/openocd ==

TODO this needs better documenting, the short version is to type in a gdb session

<source>
del break
monitor reset halt
monitor flash write_image erase main.bin 0x08000000
</source>

Please replace main.bin with image.bin if you're using processes.

== QSTLink2 ==

An useful tool, wit a GUI, sadly unmaintained. This section is kept for reference, and should development of this tool restart.

[https://code.google.com/p/qstlink2 QSTLink2]. It has a GUI but the precompiled ppa is no longer updated for the latest Ubuntu releases. The installation on Ubuntu/Debian requires to add a ''ppa'' and install it via ''apt-get''. Also, it is recomended to install the udev rules, which allow QSTLink2 to connect to the USB port without the need to run it from root.

<source lang="bash">
sudo add-apt-repository ppa:fpoussin/ppa
sudo apt-get update
sudo apt-get install qstlink2
wget https://raw.githubusercontent.com/mobyfab/QStlink2/master/res/49-stlinkv2.rules
sudo mv 49-stlinkv2.rules /etc/udev/rules.d
sudo chown root:root /etc/udev/rules.d/49-stlinkv2.rules
</source>

If a PPA of QStlink2 is not available for your platform, you can compile the stable version V1.2.3 in this way

<source lang="bash">
git clone https://github.com/fpoussin/QStlink2.git
cd QStlink2
git checkout v1.2.3
git submodule update --init
qmake -qt=qt5
make
sudo make install
</source>

= RP2040 Microcontrollers =

== picotool ==

A tool for flashing RP2040 microcontrollers through USB. To install it on Debian/Ubuntu run:

<source lang="bash">
sudo apt install lpc21isp
</source>

Older distros may not have it in their repos. In this case you'll need to compile it from sources.

To use this flashing tool, you'll need to interact with your board to start the STM32 bootloader. This does not happen by default, and requires to tie the BOOT pin high while sending a RUN pulse (RP2040 microcontrollers call their RESET pin RUN). Annoyingly, official boards from Raspberry Pi only have a BOOT butting, and lack a reset button, so you'll either need to
* solder a pushbutton between RUN and GND
* disconnect and reconnect power while holding the BOOT button every time you want to flash the microcontroller
* get creative shorting RUN and GND with tweezers or a short piece of wire

Unofficial boards, such as those from waveshare don't have this issue.

= Nordic nRF Microcontrollers =

== Flashing through gdb/openocd ==

TODO this needs better documenting, the short version is to type in a gdb session

<source>
del break
monitor reset halt
monitor flash write_image erase main.bin 0x0
</source>

Please replace main.bin with image.bin if you're using processes.

= ATsam Microcontrollers =

== Flashing through gdb/openocd ==

TODO this needs better documenting, the short version is to type in a gdb session

<source>
del break
monitor reset halt
monitor flash write_image erase main.bin 0x4000
</source>

Please replace main.bin with image.bin if you're using processes.

= EFM32 Micocontrollers =

TODO document using lrzsz to talk to the serial bootloader

= LPC2000 Microcontrollers =

== lpc21isp ==

A tool to program LPC2000 microcontrollers using their serial bootloader. To install it on Debian/Ubuntu run:

<source lang="bash">
sudo apt install lpc21isp
</source>

This tool was included in older versions of the Miosix Toolchain, as the LPC2138 was the first microcontoller supported by Miosix.