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.
1679 Commits
99 Branches
41 Tags
26 MiB
Tree: 2194d447e9
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '2194d447e9'
${ noResults }
tinygo/targets/nrf52.json

17 lines
337 B
Raw Normal View History

targets: let specific targets inherit more general targets This avoids a ton of duplication and makes it easier to change a generic target (for example, the "cortex-m" target) for all boards that use it. Also, by making it possible to inherit properties from a parent target specification, it is easier to support out-of-tree boards that don't have to be updated so often. A target specification for a special-purpose board can simply inherit the specification of a supported chip and override the properites it needs to override (like the programming interface).
6 years ago
{
arm: make FPU configuraton consistent Eventually we might want to start using the FPU, but the easy option right now is to simply disable it everywhere. Previously, it depended on whether Clang was built as part of TinyGo or it was an external binary. By setting the floating point mode explicitly, such inconsistencies are avoided. This commit creates a new cortex-m4 target which can be the central place for setting FPU-related settings across all Cortex-M4 chips.
5 years ago
"inherits": ["cortex-m4"],
targets: let specific targets inherit more general targets This avoids a ton of duplication and makes it easier to change a generic target (for example, the "cortex-m" target) for all boards that use it. Also, by making it possible to inherit properties from a parent target specification, it is easier to support out-of-tree boards that don't have to be updated so often. A target specification for a special-purpose board can simply inherit the specification of a supported chip and override the properites it needs to override (like the programming interface).
6 years ago
"build-tags": ["nrf52", "nrf"],
all: compile and link using clang, where possible
6 years ago
"cflags": [
"-Qunused-arguments",
targets: let specific targets inherit more general targets This avoids a ton of duplication and makes it easier to change a generic target (for example, the "cortex-m" target) for all boards that use it. Also, by making it possible to inherit properties from a parent target specification, it is easier to support out-of-tree boards that don't have to be updated so often. A target specification for a special-purpose board can simply inherit the specification of a supported chip and override the properites it needs to override (like the programming interface).
6 years ago
"-DNRF52832_XXAA",
nrf: add support for SoftDevices to PCA10040 board
6 years ago
"-I{root}/lib/CMSIS/CMSIS/Include",
"-I{root}/lib/nrfx/mdk"
all: compile and link using clang, where possible
6 years ago
],
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/nrf52.ld",
all: compile and link using clang, where possible
6 years ago
"extra-files": [
targets: let specific targets inherit more general targets This avoids a ton of duplication and makes it easier to change a generic target (for example, the "cortex-m" target) for all boards that use it. Also, by making it possible to inherit properties from a parent target specification, it is easier to support out-of-tree boards that don't have to be updated so often. A target specification for a special-purpose board can simply inherit the specification of a supported chip and override the properites it needs to override (like the programming interface).
6 years ago
"lib/nrfx/mdk/system_nrf52.c",
"src/device/nrf/nrf52.s"
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
],
"openocd-target": "nrf51"
targets: let specific targets inherit more general targets This avoids a ton of duplication and makes it easier to change a generic target (for example, the "cortex-m" target) for all boards that use it. Also, by making it possible to inherit properties from a parent target specification, it is easier to support out-of-tree boards that don't have to be updated so often. A target specification for a special-purpose board can simply inherit the specification of a supported chip and override the properites it needs to override (like the programming interface).
6 years ago
}