Hi, I am using freeRTOS.org version v6.0.0 under Code-Red Suite 3 NXP Edition on an LPC1768.  As part of the download, I also got the rtos.openrtos.viewer_1.0.10.jar and followed the document “OpenRTOS APPLICATION NOTE: #34-185-AN-001 – Installing and Using the OpenRTOS Eclipse Plug-In” to install the plug-in.  I then tried to view the Queue Table and Tasks Table.  I had success with the Tasks Table but not with the Queue Table; I then noticed that I needed to use the function vQueueAddToRegistry() after the** xQueueCreate()** function, which I did, but the Queue Table still does not show anything.  Does anyone know what might be wrong?  In particular, does this plugin work with freeRTOS or is it only for openRTOS?   Further, the application note mentions that a similar method may be followed for semaphores:…”The following description refers only to queue, but is equally applicable to binary semaphores, counting semaphores, mutex type semaphores and recursive semaphores”…. but I see no register function for each of these types of semaphores similar to xQueueAddToRegistry(), so how does one go about registering these semaphores and does the results appear under the Queue Table window as well?

Sorry for very quick responses: - yes it works with FreeRTOS as well.
- have you set configUSE_QUEUE_REGISTRY to 1?  This is needed in FreeRTOSConfig.h for the queue table to do anything.  I think it is explained in the application note.
- You can use the same function to register semaphores as queues. Regards.

There is no mention of the configUSE_QUEUE_REGISTRY in any of the documentation.  But you did point me in the right direction. The FreeRTOS Reference Manual mentions configQUEUE_REGISTRY_SIZE, and it works when set to a non-zero value.  Is it possible to view the tasks and queue tables in ‘real-time’ through a trace; right now, the values only update when we break the execution. Thanks!

My mistake, configQUEUE_REGISTRY_SIZE is the correct parameter.  The other one I made up. Regards.

Is it possible to view the tasks and queue tables in ‘real-time’ through a trace; right now, the values only update when we break the execution.

Real time trace is not currently an option – but watch this space. Regards.