github
/
tinygo
mirror of https://github.com/tinygo-org/tinygo.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1968 Commits
99 Branches
41 Tags
26 MiB
Tree: f23ba3b023
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'f23ba3b023'
${ noResults }
tinygo/targets/nucleo-f103rb.json

17 lines
413 B
Raw Normal View History

machine/stm32f103xx/nucleo-f103rb: add support for NUCLEO-F103RB STM32F1-based board Compared to the already supported stm32f103xx "bluepill" board this: - features 128 KiB flash memory size ("RB" suffix) instead of 64 KiB, see `targets/stm32f103rb.ld` - has onboard ST-LINK/V2-1 programmer and debugger requiring different OpenOCD configuration file - uses USART2 connected to ST-LINK/V2-1 debugger as virtual COM port over USB for `putchar()` - has a user-accessible button besides the reset button
5 years ago
{
"inherits": ["cortex-m"],
"llvm-target": "armv7m-none-eabi",
stm32: i2c implementation for F7, L5 and L4 MCUs
4 years ago
"build-tags": ["nucleof103rb", "stm32f103", "stm32f1","stm32"],
machine/stm32f103xx/nucleo-f103rb: add support for NUCLEO-F103RB STM32F1-based board Compared to the already supported stm32f103xx "bluepill" board this: - features 128 KiB flash memory size ("RB" suffix) instead of 64 KiB, see `targets/stm32f103rb.ld` - has onboard ST-LINK/V2-1 programmer and debugger requiring different OpenOCD configuration file - uses USART2 connected to ST-LINK/V2-1 debugger as virtual COM port over USB for `putchar()` - has a user-accessible button besides the reset button
5 years ago
"cflags": [
"--target=armv7m-none-eabi",
"-Qunused-arguments"
],
compileopts: add linkerscript key Setting the linker script as one property (instead of as part of the generic ldflags property) allows it to be overriden. This is important for the SoftDevice on Nordic chips, because the SoftDevice takes up a fixed part of the flash/RAM and the application must be flashed at a different position. With this linkerscript option, it is possible to create (for example) a pca10040-s132v6 that overrides the default linker script.
5 years ago
"linkerscript": "targets/stm32f103rb.ld",
machine/stm32f103xx/nucleo-f103rb: add support for NUCLEO-F103RB STM32F1-based board Compared to the already supported stm32f103xx "bluepill" board this: - features 128 KiB flash memory size ("RB" suffix) instead of 64 KiB, see `targets/stm32f103rb.ld` - has onboard ST-LINK/V2-1 programmer and debugger requiring different OpenOCD configuration file - uses USART2 connected to ST-LINK/V2-1 debugger as virtual COM port over USB for `putchar()` - has a user-accessible button besides the reset button
5 years ago
"extra-files": [
stm32: use stm32-rs SVDs which are of much higher quality This commit changes the number of wait states for the stm32f103 chip to 2 instead of 4. This gets it back in line with the datasheet, but it also has the side effect of breaking I2C. Therefore, another (seemingly unrelated) change is needed: the i2cTimeout constant must be increased to a higher value to adjust to the lower flash wait states - presumably because the lower number of wait states allows the chip to run code faster.
4 years ago
"src/device/stm32/stm32f103.s"
machine/stm32f103xx/nucleo-f103rb: add support for NUCLEO-F103RB STM32F1-based board Compared to the already supported stm32f103xx "bluepill" board this: - features 128 KiB flash memory size ("RB" suffix) instead of 64 KiB, see `targets/stm32f103rb.ld` - has onboard ST-LINK/V2-1 programmer and debugger requiring different OpenOCD configuration file - uses USART2 connected to ST-LINK/V2-1 debugger as virtual COM port over USB for `putchar()` - has a user-accessible button besides the reset button
5 years ago
],
targets: refactor flash/gdb target configuration Instead of specifying explicit commands, most of these commands have been replaced by more specific properties. This is work that will be necessary for an eventual -programmer flag to the compiler, with which it is possible to select which programmer to use to flash or debug a chip. That's not very useful for boards that already include a programmer or bootloader for that purpose, but is very useful for novel boards or single-purpose boards that are not already included in TinyGo.
5 years ago
"flash-method": "openocd",
"openocd-interface": "stlink-v2-1",
"openocd-target": "stm32f1x"
machine/stm32f103xx/nucleo-f103rb: add support for NUCLEO-F103RB STM32F1-based board Compared to the already supported stm32f103xx "bluepill" board this: - features 128 KiB flash memory size ("RB" suffix) instead of 64 KiB, see `targets/stm32f103rb.ld` - has onboard ST-LINK/V2-1 programmer and debugger requiring different OpenOCD configuration file - uses USART2 connected to ST-LINK/V2-1 debugger as virtual COM port over USB for `putchar()` - has a user-accessible button besides the reset button
5 years ago
}