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] [December 2010 Threads] wrong behaviour of *pxPortInitialiseStack()Posted by Markus Krug on December 29, 2010 Hello,
I found a problem with the initialization of the initial values for each Task in the *pxPortInitialiseStack() function. The problem occured on a HCS12 Board that had a hard wired high value on the XIRQ (external interrupt) pin. The above mentioned function sets the CCR register for every task to a value that will unmask the external interrupt as soon as the task becomes running. Because of the special hardware setup of my board that setting of the CCR register in the *pxPortInitialiseStack() leads immidiately to jump to the ISR of the XIRQ and no chance to get out of this anymore. Even worse the corresponding X-Bit in the CCR Register can not be set again after it had cleared once during runtime. I wonder if the behaviour of *pxPortInitialiseStack() should be generally changed so that the X of the HCS12 will not be cleared by FreeRTOS. Probably other microcontrollers will have a similiar behaviour. Any thoughts ?
Best Regards Markus
RE: wrong behaviour of *pxPortInitialiseStack()Posted by Dave on December 29, 2010 I think there is something about this in the bug tracker.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|