RIOT-OS/RIOT
RIOT-OS/RIOT
1
0
Fork 0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2025-01-18 12:52:44 +01:00
Code Releases Activity
3aaea1a74e
RIOT/cpu/msp430/Kconfig

61 lines
1.4 KiB
Plaintext
Raw Normal View History

gnrc/pktbuf : Set Kconfig defaults and conditions Set Kconfig defaults for CPU and conditions to avoid conflict with CFLAGS Co-authored-by: Leandro Lanzieri <leandro.lanzieri@haw-hamburg.de>
2020-05-12 19:34:05 +02:00
# Copyright (c) 2020 Freie Universitaet Berlin
cpu/msp430_common: Add Kconfig symbols Also specify CPU_ARCH and CPU_CORE in Makefile.features.
2020-06-24 09:26:05 +02:00
# 2020 HAW Hamburg
gnrc/pktbuf : Set Kconfig defaults and conditions Set Kconfig defaults for CPU and conditions to avoid conflict with CFLAGS Co-authored-by: Leandro Lanzieri <leandro.lanzieri@haw-hamburg.de>
2020-05-12 19:34:05 +02:00
#
# This file is subject to the terms and conditions of the GNU Lesser
# General Public License v2.1. See the file LICENSE in the top level
# directory for more details.
#
cpu/msp430_common: Add Kconfig symbols Also specify CPU_ARCH and CPU_CORE in Makefile.features.
2020-06-24 09:26:05 +02:00
config CPU_ARCH_MSP430
bool
cpu/msp430: reorganize code RIOT supports two distinct families of the MSP430: The [MSP430 x1xx] MCU family and the [MSP430 F2xx/G2xx] MCU family. For both incompatible MCU families the code was located in the msp430fxyz folder, resulting in case of the UART driver in particularly bizarre code looking roughly like this: #ifndef UART_USE_USCI /* implementation of x1xx peripheral ... */ #else /* implementation of F2xx/G2xx peripheral ... */ #endif /* zero shared code between both variants */ This splits the peripheral drivers for USCI and USART serial IP blocks into separate files and relocates everything in cpu/msp430, similar to how cpu/stm32 is organized. [MSP430 x1xx]: https://www.ti.com/lit/ug/slau049f/slau049f.pdf [MSP430 F2xx/G2xx]: https://www.ti.com/lit/ug/slau144k/slau144k.pdf
2023-06-13 15:56:24 +02:00
imply MODULE_NEWLIB_NANO
cpu/msp430_common: Add Kconfig symbols Also specify CPU_ARCH and CPU_CORE in Makefile.features.
2020-06-24 09:26:05 +02:00
select HAS_ARCH_16BIT
select HAS_ARCH_MSP430
cpu/msp430: reorganize code RIOT supports two distinct families of the MSP430: The [MSP430 x1xx] MCU family and the [MSP430 F2xx/G2xx] MCU family. For both incompatible MCU families the code was located in the msp430fxyz folder, resulting in case of the UART driver in particularly bizarre code looking roughly like this: #ifndef UART_USE_USCI /* implementation of x1xx peripheral ... */ #else /* implementation of F2xx/G2xx peripheral ... */ #endif /* zero shared code between both variants */ This splits the peripheral drivers for USCI and USART serial IP blocks into separate files and relocates everything in cpu/msp430, similar to how cpu/stm32 is organized. [MSP430 x1xx]: https://www.ti.com/lit/ug/slau049f/slau049f.pdf [MSP430 F2xx/G2xx]: https://www.ti.com/lit/ug/slau144k/slau144k.pdf
2023-06-13 15:56:24 +02:00
select HAS_CPU_MSP430
cpu/msp430_common/kconfig: add dbgpin feature
2021-02-15 11:24:20 +01:00
select HAS_DBGPIN
cpu/msp430: reorganize code RIOT supports two distinct families of the MSP430: The [MSP430 x1xx] MCU family and the [MSP430 F2xx/G2xx] MCU family. For both incompatible MCU families the code was located in the msp430fxyz folder, resulting in case of the UART driver in particularly bizarre code looking roughly like this: #ifndef UART_USE_USCI /* implementation of x1xx peripheral ... */ #else /* implementation of F2xx/G2xx peripheral ... */ #endif /* zero shared code between both variants */ This splits the peripheral drivers for USCI and USART serial IP blocks into separate files and relocates everything in cpu/msp430, similar to how cpu/stm32 is organized. [MSP430 x1xx]: https://www.ti.com/lit/ug/slau049f/slau049f.pdf [MSP430 F2xx/G2xx]: https://www.ti.com/lit/ug/slau144k/slau144k.pdf
2023-06-13 15:56:24 +02:00
select HAS_NEWLIB
cpu/msp430_common: Add Kconfig symbols Also specify CPU_ARCH and CPU_CORE in Makefile.features.
2020-06-24 09:26:05 +02:00
select HAS_PERIPH_FLASHPAGE
periph/flashpage: Add _in_address_space feature
2022-03-17 19:45:54 +01:00
select HAS_PERIPH_FLASHPAGE_IN_ADDRESS_SPACE
msp430: Adapt to flashpage/flashpage_pagewise API
2020-11-09 16:44:29 +01:00
select HAS_PERIPH_FLASHPAGE_PAGEWISE
cpu/msp430_common: Add Kconfig symbols Also specify CPU_ARCH and CPU_CORE in Makefile.features.
2020-06-24 09:26:05 +02:00
select HAS_PERIPH_PM
cpu/msp430: improve periph_timer - add support for multiple timers - add support for selecting clock source in the board's `periph_conf.h` - add support for the prescaler - implement `periph_timer_query_freqs` - add a second timer to all MSP430 boards - the first timer is fast ticking, high-power - the second is slow ticking, low-power
2023-12-06 20:33:41 +01:00
select HAS_PERIPH_TIMER_QUERY_FREQS
cpu/msp430: reorganize code RIOT supports two distinct families of the MSP430: The [MSP430 x1xx] MCU family and the [MSP430 F2xx/G2xx] MCU family. For both incompatible MCU families the code was located in the msp430fxyz folder, resulting in case of the UART driver in particularly bizarre code looking roughly like this: #ifndef UART_USE_USCI /* implementation of x1xx peripheral ... */ #else /* implementation of F2xx/G2xx peripheral ... */ #endif /* zero shared code between both variants */ This splits the peripheral drivers for USCI and USART serial IP blocks into separate files and relocates everything in cpu/msp430, similar to how cpu/stm32 is organized. [MSP430 x1xx]: https://www.ti.com/lit/ug/slau049f/slau049f.pdf [MSP430 F2xx/G2xx]: https://www.ti.com/lit/ug/slau144k/slau144k.pdf
2023-06-13 15:56:24 +02:00
select MODULE_MALLOC_THREAD_SAFE if TEST_KCONFIG
config HAS_CPU_MSP430
bool
help
Indicates that an 'MSP430' CPU is being used.
cpu/msp430_common: Add Kconfig symbols Also specify CPU_ARCH and CPU_CORE in Makefile.features.
2020-06-24 09:26:05 +02:00
cpu/msp430: reorganize code RIOT supports two distinct families of the MSP430: The [MSP430 x1xx] MCU family and the [MSP430 F2xx/G2xx] MCU family. For both incompatible MCU families the code was located in the msp430fxyz folder, resulting in case of the UART driver in particularly bizarre code looking roughly like this: #ifndef UART_USE_USCI /* implementation of x1xx peripheral ... */ #else /* implementation of F2xx/G2xx peripheral ... */ #endif /* zero shared code between both variants */ This splits the peripheral drivers for USCI and USART serial IP blocks into separate files and relocates everything in cpu/msp430, similar to how cpu/stm32 is organized. [MSP430 x1xx]: https://www.ti.com/lit/ug/slau049f/slau049f.pdf [MSP430 F2xx/G2xx]: https://www.ti.com/lit/ug/slau144k/slau144k.pdf
2023-06-13 15:56:24 +02:00
config CPU_MSP430
cpu/msp430_common: Add Kconfig symbols Also specify CPU_ARCH and CPU_CORE in Makefile.features.
2020-06-24 09:26:05 +02:00
bool
select CPU_ARCH_MSP430
cpu/msp430: reorganize code RIOT supports two distinct families of the MSP430: The [MSP430 x1xx] MCU family and the [MSP430 F2xx/G2xx] MCU family. For both incompatible MCU families the code was located in the msp430fxyz folder, resulting in case of the UART driver in particularly bizarre code looking roughly like this: #ifndef UART_USE_USCI /* implementation of x1xx peripheral ... */ #else /* implementation of F2xx/G2xx peripheral ... */ #endif /* zero shared code between both variants */ This splits the peripheral drivers for USCI and USART serial IP blocks into separate files and relocates everything in cpu/msp430, similar to how cpu/stm32 is organized. [MSP430 x1xx]: https://www.ti.com/lit/ug/slau049f/slau049f.pdf [MSP430 F2xx/G2xx]: https://www.ti.com/lit/ug/slau144k/slau144k.pdf
2023-06-13 15:56:24 +02:00
choice LIBC_IMPLEMENTATION
default MODULE_NEWLIB
endchoice
cpu/msp430_common: Add Kconfig symbols Also specify CPU_ARCH and CPU_CORE in Makefile.features.
2020-06-24 09:26:05 +02:00
## Common CPU symbols
config CPU_ARCH
cpu/msp430: reorganize code RIOT supports two distinct families of the MSP430: The [MSP430 x1xx] MCU family and the [MSP430 F2xx/G2xx] MCU family. For both incompatible MCU families the code was located in the msp430fxyz folder, resulting in case of the UART driver in particularly bizarre code looking roughly like this: #ifndef UART_USE_USCI /* implementation of x1xx peripheral ... */ #else /* implementation of F2xx/G2xx peripheral ... */ #endif /* zero shared code between both variants */ This splits the peripheral drivers for USCI and USART serial IP blocks into separate files and relocates everything in cpu/msp430, similar to how cpu/stm32 is organized. [MSP430 x1xx]: https://www.ti.com/lit/ug/slau049f/slau049f.pdf [MSP430 F2xx/G2xx]: https://www.ti.com/lit/ug/slau144k/slau144k.pdf
2023-06-13 15:56:24 +02:00
default "msp430" if CPU_MSP430
config CPU
default "msp430" if CPU_MSP430
cpu/msp430_common: Add Kconfig symbols Also specify CPU_ARCH and CPU_CORE in Makefile.features.
2020-06-24 09:26:05 +02:00
config CPU_CORE
cpu/msp430: reorganize code RIOT supports two distinct families of the MSP430: The [MSP430 x1xx] MCU family and the [MSP430 F2xx/G2xx] MCU family. For both incompatible MCU families the code was located in the msp430fxyz folder, resulting in case of the UART driver in particularly bizarre code looking roughly like this: #ifndef UART_USE_USCI /* implementation of x1xx peripheral ... */ #else /* implementation of F2xx/G2xx peripheral ... */ #endif /* zero shared code between both variants */ This splits the peripheral drivers for USCI and USART serial IP blocks into separate files and relocates everything in cpu/msp430, similar to how cpu/stm32 is organized. [MSP430 x1xx]: https://www.ti.com/lit/ug/slau049f/slau049f.pdf [MSP430 F2xx/G2xx]: https://www.ti.com/lit/ug/slau144k/slau144k.pdf
2023-06-13 15:56:24 +02:00
default "msp430" if CPU_MSP430
cpu/msp430_common: Add Kconfig symbols Also specify CPU_ARCH and CPU_CORE in Makefile.features.
2020-06-24 09:26:05 +02:00
## Definition of specific features
config HAS_ARCH_MSP430
bool
help
Indicates that the current architecture is MSP430.
## Specific default configuration values
gnrc/pktbuf : Set Kconfig defaults and conditions Set Kconfig defaults for CPU and conditions to avoid conflict with CFLAGS Co-authored-by: Leandro Lanzieri <leandro.lanzieri@haw-hamburg.de>
2020-05-12 19:34:05 +02:00
config GNRC_PKTBUF_SIZE
default 2560
treewide: change prefix for generated Kconfig symbols. This changes the prefixes of the symbols generated from USEMODULE and USEPKG variables. The changes are as follow: KCONFIG_MODULE_ => KCONFIG_USEMODULE_ KCONFIG_PKG_ => KCONFIG_USEPKG_ MODULE_ => USEMODULE_ PKG_ => USEPKG_
2020-08-31 09:33:35 +02:00
depends on KCONFIG_USEMODULE_GNRC_PKTBUF_STATIC
cpu/msp430: reorganize code RIOT supports two distinct families of the MSP430: The [MSP430 x1xx] MCU family and the [MSP430 F2xx/G2xx] MCU family. For both incompatible MCU families the code was located in the msp430fxyz folder, resulting in case of the UART driver in particularly bizarre code looking roughly like this: #ifndef UART_USE_USCI /* implementation of x1xx peripheral ... */ #else /* implementation of F2xx/G2xx peripheral ... */ #endif /* zero shared code between both variants */ This splits the peripheral drivers for USCI and USART serial IP blocks into separate files and relocates everything in cpu/msp430, similar to how cpu/stm32 is organized. [MSP430 x1xx]: https://www.ti.com/lit/ug/slau049f/slau049f.pdf [MSP430 F2xx/G2xx]: https://www.ti.com/lit/ug/slau144k/slau144k.pdf
2023-06-13 15:56:24 +02:00
source "$(RIOTCPU)/msp430/periph/Kconfig"
source "$(RIOTCPU)/msp430/kconfigs/x1xx/Kconfig"
source "$(RIOTCPU)/msp430/kconfigs/f2xx_g2xx/Kconfig"
Copy Permalink