FreeRTOS Support Archive
The 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.
This is a read only archive of threads posted to the FreeRTOS support forum.
The archive is updated every week, so will not always contain the very latest posts.
Use these archive pages to search previous posts. Use the Live FreeRTOS Forum
link to reply to a post, or start a new support thread.
[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [August 2014 Threads]
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
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.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.