manual:ports
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
manual:ports [2019/08/09 12:13] voorburg [Available Ports] |
manual:ports [2020/03/09 12:50] voorburg |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Port Specifics ====== | ====== Port Specifics ====== | ||
| - | |||
| - | |||
| The bootloader program is always present in non-volatile memory of the microcontroller. This means that after programming the user's program, there are altogether two programs present. Both programs need to be able to activate each other and they typically share resources such as the interrupt vector table. | The bootloader program is always present in non-volatile memory of the microcontroller. This means that after programming the user's program, there are altogether two programs present. Both programs need to be able to activate each other and they typically share resources such as the interrupt vector table. | ||
| - | |||
| - | |||
| How this is handled by both the bootloader and the user's program for a specific port is described in this part of the manual. | How this is handled by both the bootloader and the user's program for a specific port is described in this part of the manual. | ||
| + | Note that the OpenBLT bootloader includes a microcontroller port template. Using this template as a starting point you can easily add support for a new microcontroller family yourself. Refer to [[https://www.feaser.com/en/blog/?p=352|this blog article]] for more details. | ||
| ===== Available Ports ===== | ===== Available Ports ===== | ||
manual/ports.txt ยท Last modified: 2023/11/10 18:23 by voorburg
Page Tools
