Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Safety Certified FreeRTOS #906

Open
amazonKamath opened this issue Nov 27, 2023 · 4 comments
Open

Safety Certified FreeRTOS #906

amazonKamath opened this issue Nov 27, 2023 · 4 comments
Assignees
@joshzarr
Labels
roadmap An feature currently on the roadmap

Comments

@amazonKamath
Copy link
Member

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.
@amazonKamath amazonKamath converted this from a draft issue Nov 27, 2023
@amazonKamath amazonKamath added the roadmap An feature currently on the roadmap label Nov 27, 2023
laroche pushed a commit to laroche/FreeRTOS-Kernel that referenced this issue Apr 18, 2024
@e14002270
risc-v: Fix build flags and linker scripts (FreeRTOS#906)
d60b34c 
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>
@BerndThie
Copy link

This is a very interesting topic!
When can we expect more information?

@archigup
Copy link
Member

Hi, this is actively being worked on. Is there particular information you are interested in?

@BerndThie
Copy link

BerndThie commented Jan 28, 2025 •
edited
Loading

Thanks for the fast reply! I'm interested in the SIL you are targeting and the timeline. When do you expect to go public with the safety certified FreeRTOS?

@joshzarr
Copy link
Member

Thank you for your interest in FreeRTOS!

We are currently working to certify FreeRTOS to IEC 61508 Systematic Capability 3 for use in systems up to SIL 3. Our plan is to have separate certificates for the FreeRTOS Kernel and individual FreeRTOS Ports. We are targeting submission of all documentation and test artifacts to our assessor for Q1 2025 and anticipate the certificate being granted in Q2 2025. Our first safety certified port will target the TI Hercules series of microcontrollers.

Once we have completed the certification process we will follow on with further announcements regarding the general availability of Safety Certified FreeRTOS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@joshzarr joshzarr

Labels
roadmap An feature currently on the roadmap
Projects
Roadmap
Status: 🏗 In Progress
Milestone
No milestone
Development

No branches or pull requests
4 participants
@archigup @BerndThie @amazonKamath @joshzarr