I’ve been using an older version of StateViewer (1.0.10) in an older version of Eclipse (Galileo).  Having just completed a project, I’m in the process of updating my toolset and have installed (on a different computer, but still Windows 7 / 64-bits) the latest Eclipse.  I also installed the latest StateViewer (2.0.6.201306030857) and am now rebuilding my project under this new environment.  The installation details indicate no problems and the Queue Table (DSF) and Task Table (DSF) show up with the proper column headers but are empty. I have had to make a few minor changes to the project code to get it to compile in the new environment but I can’t see where any of it would have had an effect – the vQueueAddToRegistry() entries are still there and configUSE_TRACE_FACILITY is set to 1.  I am using an older version of FreeRTOS (6.0.4) as that was what was available when I started the project.  Anyone have any thoughts on what I need to check to troubleshoot this? Thanks,
Dave

The plug-in is maintained by WITTENSTEIN high integrity systems.  Please contact them for advice. Regards.

Hi Dave,
I’m using Eclipse Kepler with 7.5.0, and it works with gdb:
http://mcuoneclipse.com/2013/08/04/diy-free-toolchain-for-kinetis-part-5-freertos-eclipse-kernel-awareness-with-gdb/
Have you set the queue registry size? Erich

Hi Erich,
Thanks for the response.  Yes, the queue registry size is set.  I also checked the error log and there is nothing in there to indicate any type of problem.  The link you provided looks good but I didn’t see anything in there that might give me any ideas.  I checked the WITTENSTEIN site and they do have a support forum but it looks like it’s only for customers with a product license. Dave

Hi Dave, I’m facing the same issue. Even though I configured the configQUEUEREGISTRYSIZE to 10 and set configUSETRACEFACILITY to 1, I’m not able to see anything in Task or Queue table. I’m using StateViewer 2.0.6 and FreeRTOS 7.0.2. Did you get any breakthrough? Mangesh

Hi Mangesh, I never got things going. I recently tried installing on a second computer that was running the same version of Eclipse and got exactly the same results. I really enjoyed using StateViewer before I upgraded to the latest Eclipse but, given a choice between the two, I’d rather be using the latest Eclipse. Dave

I managed to get mine partially working after similar symptoms. The key for me was to switch the Eclipse debugger invocation to use “GDB (DSF) Hardware Debugging Launcher”. It is the Eclipse default, but the toolchain setup instructions had instructed to change that (to get around some earlier bug). Open “Manage debug configurations” and the setting is at the end of the form, opens from the link “Select other”. I now have a weird symptom: the “Queue Table (DSF)” works well (after googling the instructions). But there are no tasks visible in the “Task Table (QSF)” view. Any ideas what could help? In the debugger instructions I can view for example the pxCurrentTCB content and see the task names there. I have not set up the run time statistics – but I suppose that is not required to get the basic information? Running on a Mac, Eclipse Kepler, latest StateViewer, openOCD and carlson-minot/crosscompilers/bin/arm-none-eabi-gdb Pertti

The remaining problems I had in the previous message were resolved after 1) upgrading to the latest FreeRTOS version, and 2) Upgrading all Eclipse components. Great tools, both the FreeRTOS and the StateViewer 🙂 Pertti