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 2010 Threads] Deadlock in prvAllocateTCBAndStackPosted by Yinxia ZHAO on August 20, 2010 memset( pxNewTCB->pxStack, tskSTACK_FILL_BYTE, usStackDepth * sizeof( portSTACK_TYPE ) );
I am using a simulator, is it possible that the memory in this simulator is not big enough so program goes into deadlock at this line?
RE: Deadlock in prvAllocateTCBAndStackPosted by Dave on August 20, 2010 A single line like this cannot deadlock. I think your definition of deadlock is not correct, unless you have seen something in the implementation of memset() (in its source code) that could.
People using simulators waste a lot of time on this forum. In addition you do not state which processor you are using, which compiler you are using, which simulator you are using, or what the problem you are experiencing is. Don't expect to get a solution.
RE: Deadlock in prvAllocateTCBAndStackPosted by Yinxia ZHAO on August 20, 2010 sorry.. I'm using simulator WSim, msp430-gcc, freeRTOS on wsn430 platform. I want to setup a peer communicating via MAC address on simulators WSim and WSNet. In fact there is a example given by http://senstools.gforge.inria.fr/doku.php?id=os:freertos:examples, 05_network_device and 06_coordinator, I tested it and failed. Now, I don't know where the problems come from, simulator, driver or system...
RE: Deadlock in prvAllocateTCBAndStackPosted by Richard Damon on August 20, 2010 First, "Deadlock" is a fairly specific term dealing with synchronization and is not applicable here. If by "Deadlock" you mean the program appears stuck here, note that memset can be a slow operation for a simulator, as it has in it a loop with a count equal to the number of entries to set.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|