RIOT-OS/RIOT
RIOT-OS/RIOT
1
0
Fork 0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2024-12-29 04:50:03 +01:00
Code Releases Activity
c507ebff43
RIOT/cpu/fe310/Makefile.features

13 lines
369 B
Makefile
Raw Normal View History

cpu/fe310: add CPU_CORE information
2021-09-22 15:51:54 +02:00
CPU_CORE := rv32imac
cpu/fe310: add RISC-V cpu FE310 New CPU FE310 from SiFive based on RISC-V architecture build: add makefile for RISC-V builds Makefile for builds using RISC-V tools
2018-04-16 19:03:33 +02:00
FEATURES_PROVIDED += periph_cpuid
cpu/fe310: provide gpio feature at cpu level
2019-12-05 14:05:17 +01:00
FEATURES_PROVIDED += periph_gpio periph_gpio_irq
cpu/fe310: add RISC-V cpu FE310 New CPU FE310 from SiFive based on RISC-V architecture build: add makefile for RISC-V builds Makefile for builds using RISC-V tools
2018-04-16 19:03:33 +02:00
FEATURES_PROVIDED += periph_pm
cpu/riscv: Add PMP driver
2023-06-06 17:30:51 +02:00
FEATURES_PROVIDED += periph_pmp
cpu/riscv_common: only select PLIC for fe310 Not every RISC-V implements that interrupt controller, gd32v uses CLIC instead.
2021-08-25 10:49:47 +02:00
FEATURES_PROVIDED += periph_plic
cpu: add periph_rtt_overflow feature The RTT overflow callback is not available on all RTT implementations. This means it is either a no-op or `rtt_set_overflow_cb()` is a no-op or it will overwrite the alarm set with `rtt_set_alarm()`. This adds a feature to indicate that proper overflow reporting is available.
2021-01-13 20:48:29 +01:00
FEATURES_PROVIDED += periph_rtt_overflow
drivers/periph/rtt: add periph_rtt_set_counter feature Some periph_rtt implementations do not provide `rtt_set_counter()`. This adds `periph_rtt_set_counter` as feature to allow testing for its availability. The feature is provided at CPU level if periph_rtt is provided by the board for all CPUs implementing `rtt_set_counter()`.
2021-03-03 17:05:35 +01:00
FEATURES_PROVIDED += periph_rtt_set_counter
cpu/fe310: implement driver for watchdog
2019-11-07 14:12:07 +01:00
FEATURES_PROVIDED += periph_wdt
cpu/fe310: blacklist picolibc on CI The RISC-V toolchain in riotdocker has issues with picolibc and will still include newlib headers. This leads to conflicts like ``` In file included from [01m[Knanostubs.c:22[m[K: [01m[K/usr/local/picolibc/riscv-none-embed/include/stdio.h:270:23:[m[K [01;31m[Kerror: [m[Kconflicting types for '[01m[K__FILE[m[K' typedef struct __file [01;31m[K__FILE[m[K; [01;31m[K^~~~~~[m[K In file included from [01m[K/opt/gnu-mcu-eclipse/riscv-none-gcc/8.2.0-2.2-20190521-0004/riscv-none-embed/include/reent.h:93[m[K, from [01m[Knanostubs.c:20[m[K: [01m[K/opt/gnu-mcu-eclipse/riscv-none-gcc/8.2.0-2.2-20190521-0004/riscv-none-embed/include/sys/reent.h:287:26:[m[K [01;36m[Knote: [m[Kprevious declaration of '[01m[K__FILE[m[K' was here typedef struct __sFILE [01;36m[K__FILE[m[K; [01;36m[K^~~~~~[m[K ``` The problem does not occur when installing both the toolchain and picolibc directly from the Debian / Ubuntu repositories, but CI uses an older Ubuntu version that does not have those packages yet, so it builds them manually. Blacklist RISC-V until CI has been updated.
2020-10-14 11:08:36 +02:00
riscv_common: Refactor common fe310 code to riscv_common
2020-09-09 21:37:15 +02:00
include $(RIOTCPU)/riscv_common/Makefile.features
Copy Permalink