Quality RTOS & Embedded Software

 Real time embedded FreeRTOS RSS feed 
Quick Start Supported MCUs PDF Books Trace Tools Ecosystem TCP & FAT




Loading

Pic32

Posted by tlafleur on August 22, 2014

In the code for PIC32MZ in your 8.0.1 release, interrupts have an assembler wrapper to save the FreeRTOS state... But in the 1.0 release of Harmony, the assembler wrapper are gone....

So why the changes harmony? Is one method better or faster?

Will you update your demo code to include Harmony in the future?

Thanks


Pic32

Posted by rtel on August 22, 2014

If you don't use an interrupt wrapper then you have the standard interrupt entry/exit code generated by the compiler. That makes the code simple to write but also means potentially nested interrupts use the stack of whichever task was running when the interrupt occurred. That can consume a lot of RAM as each task must allocate enough RAM for an entire [potentially nested 6 deep] interrupt stack frame.

If you use a wrapper then you use the FreeRTOS interrupt entry code rather than the compiler's interrupt entry code. The FreeRTOS interrupt entry code handles interrupt nesting and switches to a dedicated interrupt/system stack on interrupt entry - meaning you can allocate a smaller stack to each task and save a lot of RAM.

Please see the documentation page for this port as you will find this information there: http://www.freertos.org/PIC32MZRTOSMIPS_M14K.html

Regards.


[ Back to the top ]    [ About FreeRTOS ]    [ Sitemap ]    [ ]




Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.

Latest News

FreeRTOS kernel V10 is available for immediate download. Now MIT licensed.


FreeRTOS Partners

ARM Connected RTOS partner for all ARM microcontroller cores

IAR Partner

Microchip Premier RTOS Partner

RTOS partner of NXP for all NXP ARM microcontrollers

STMicro RTOS partner supporting ARM7, ARM Cortex-M3, ARM Cortex-M4 and ARM Cortex-M0

Texas Instruments MCU Developer Network RTOS partner for ARM and MSP430 microcontrollers

OpenRTOS and SafeRTOS