Safety Certified FreeRTOS #906
Assignees
Labels
roadmap
An feature currently on the roadmap
Comments
laroche
pushed a commit
to laroche/FreeRTOS-Kernel
that referenced
this issue
Apr 18, 2024
1. miss debug info in assembly code
RISC-V-spike-htif_GCC
LDFLAGS add arch and abi info for linker
for riscv64-unknown-elf multilib, if there is no arch and abi
info, will link to default lib and have below error
target emulation `elf32-littleriscv' does not match `elf64-littleriscv'
use CFLAGS to replace ASFLAGS when compile assembly code
because DEBUG flag is added in CFLAGS, if we use ASFLAGS to compile
assembly code, there is no debug info in assembly code objfile
2. binutils 2.39 ld warn 'has a LOAD segment with RWX permissions'
RISC-V-Qemu-virt_GCC
RISC-V-spike-htif_GCC
RISC-V_RV32_QEMU_VIRT_GCC
3. fix build fail
RISC-V_RV32_QEMU_VIRT_GCC
Signed-off-by: Eric Chan <e14002270@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The FreeRTOS kernel will be assessed, and certified for functional safety compliance under IEC 61508. With the safety-compliant kernel, FreeRTOS developers will be able to more easily build and test systems that require safety certification. The kernel, matched with an MCU, provides a foundation upon which applications, devices, and systems can be built following functional safety standards and certified by authorized vendors. IEC 61508 is a base functional safety standard used across industries, and upon which other standards are derived to meet the safety needs of industrial, automotive, robotics, medical, and other applications.
The text was updated successfully, but these errors were encountered: