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] [November 2006 Threads] HS08 Port H register stacking problemPosted by Nobody/Anonymous on November 11, 2006 The pshh asm instruction should follow psha to be consistent with portRESTORE_CONTEXT and the pxPortInitialiseStack function's context restore unstacking order. For example, this incorrect order caused obvious issues with the H:X register pair (HS08 parameter passing convention only) being passed the correct 16-bit pointer address through pvParameters during the first call to the created task after the scheduler is started. The code in question is shown below.
#define portSAVE_CONTEXT()\ {\ extern volatile void * pxCurrentTCB;\ extern volatile unsigned portBASE_TYPE uxCriticalNesting;\ \ __asm( "pshh" );/* Save H context */ \ __asm( "lda uxCriticalNesting" );\ __asm( "psha" );\
RE: HS08 Port H register stacking problemPosted by Nobody/Anonymous on November 11, 2006 Where did you get the code from? There is not an official HS08 port as far as I know. I cannot find the code you highlight in the download. ???
RE: HS08 Port H register stacking problemPosted by Nobody/Anonymous on November 11, 2006 Here's the link:
http://forums.freescale.com/attachments/freescale/8BITCOMM/2709/1/FreeRTOS_HC(S)
RE: HS08 Port H register stacking problemPosted by Nobody/Anonymous on November 11, 2006 Can you write on that forum or to the author of the port?
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|