Name |
Date |
Size |
#Lines |
LOC |
||
---|---|---|---|---|---|---|
.. | - | - | ||||
chip_specific_extensions/ | 18-Mar-2025 | - | 94 | 33 | ||
Documentation.url | D | 18-Mar-2025 | 139 | 6 | 5 | |
chip_extensions.cmake | D | 18-Mar-2025 | 829 | 17 | 15 | |
port.c | D | 18-Mar-2025 | 11 KiB | 242 | 109 | |
portASM.s | D | 18-Mar-2025 | 18 KiB | 400 | 211 | |
portContext.h | D | 18-Mar-2025 | 7.3 KiB | 190 | 127 | |
portmacro.h | D | 18-Mar-2025 | 7.9 KiB | 199 | 95 | |
readme.txt | D | 18-Mar-2025 | 1.2 KiB | 24 | 23 |
readme.txt
1/* 2 * The FreeRTOS kernel's RISC-V port is split between the the code that is 3 * common across all currently supported RISC-V chips (implementations of the 4 * RISC-V ISA), and code that tailors the port to a specific RISC-V chip: 5 * 6 * + FreeRTOS\Source\portable\GCC\RISC-V-RV32\portASM.S contains the code that 7 * is common to all currently supported RISC-V chips. There is only one 8 * portASM.S file because the same file is built for all RISC-V target chips. 9 * 10 * + Header files called freertos_risc_v_chip_specific_extensions.h contain the 11 * code that tailors the FreeRTOS kernel's RISC-V port to a specific RISC-V 12 * chip. There are multiple freertos_risc_v_chip_specific_extensions.h files 13 * as there are multiple RISC-V chip implementations. 14 * 15 * !!!NOTE!!! 16 * TAKE CARE TO INCLUDE THE CORRECT freertos_risc_v_chip_specific_extensions.h 17 * HEADER FILE FOR THE CHIP IN USE. This is done using the assembler's (not the 18 * compiler's!) include path. For example, if the chip in use includes a core 19 * local interrupter (CLINT) and does not include any chip specific register 20 * extensions then add the path below to the assembler's include path: 21 * FreeRTOS\Source\portable\GCC\RISC-V-RV32\chip_specific_extensions\RV32I_CLINT_no_extensions 22 * 23 */ 24