|
|||||||||||||||
FreeRTOS Support ArchiveThe FreeRTOS support forum is used to obtain active support directly from Real Time Engineers Ltd. In return for using our top quality software and services for free, we request you play fair and do your bit to help others too! Sign up to receive notifications of new support topics then help where you can.
Loading
Identify current task after a crashPosted by Jack Peacock on October 4, 2007 Is there a specific global inside the RTOS where a crash handler for ARM aborts can identify which task was active when the exception occurred? Since this is a crash situation I don;t want to make any RTOS calls. The specific situation I'm trying to trace is where code jumps to non-existent memory, causing an ARM prefetch abort. The link address for the exception only tells me the bad address, not where the real error is located. Jack Peacock RE: Identify current task after a crashPosted by sotd on October 4, 2007 Look at pxCurrentTCB in your debugger. This will tell you the task that is currently running.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|
|||||||||||||||
NXP tweet showing LPC5500 (ARMv8-M Cortex-M33) running FreeRTOS.
Meet Richard Barry and learn about running FreeRTOS on RISC-V at FOSDEM 2019
Version 10.1.1 of the FreeRTOS kernel is available for immediate download. MIT licensed.
View a recording of the "OTA Update Security and Reliability" webinar, presented by TI and AWS.
FreeRTOS and other embedded software careers at AWS.
