Hi,
I'm getting an error using nesdoc on some apps and not others, hoping someone can give me a hint or at least confirm whether or not they see the same error. -- My setup -- I'm working with the latest TinyOS 2.1.2 code base. I started with a clean Ubuntu Server 14.04, installed packages nesc, tinyos-tools, avr-tinyos and msp430-46 from the tinyprod repositories, also installed python-dev and build-essential from the default Ubuntu repos, checked out the latest 2.1.2 code from github, set the required environment variables as per the wiki, and have been successfully building and installing apps onto MicaZ and TelosB for a few weeks now. -- The problem -- However when I try to generate documentation using nesdoc for *some* of the example apps (for example for the RadioSenseToLeds app) using either of the following commands from the application's directory: nesdoc -o doc -target=micaz RadioSenseToLedsAppC.nc or make micaz docs The only output I get is quite unhelpful: *** LOW POWER COMMUNICATIONS DISABLED ***" nesc1: output pipe has been closed Killed Strangely I don't get this error when running nesdoc on the RadioSenseToLedsC component, only on the RadioSenseToLedsAppC component. Some example apps seem to work fine with nesdoc, some don't. Some I have tried are: Blink - works Powerup - works BaseStation - doesn't work RadioCountToLeds - doesn't work Sense - works It seems to be any app with radio components that fail - I have a few of my own apps, and it's only ones which send packets I get this error. Possibly a coincidence but can anyone suggest why this might be? The only other thing I can think of is it's a gcc version thing, as the 'output pipe has been closed' appears to be a gcc error. When i run 'gcc --version' I get: gcc (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4 Is this version of gcc okay? I can build and install apps just fine, so I'm assuming it's okay. Or if someone can anyone just confirm to me that nesdoc *works for them* on the RadioCountToLeds app, at least that will help me narrow down the problem to something wrong with my setup, that would be great! I can only find about 10 lines of documentation for nesdoc on the TinyOS wiki and can't find any source code for it, so I'm a bit stuck here. Many many thanks James
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
