Hi Chris, not sure what version of TinyOS and avr-gcc you are using, but it is clear that whatever version you have it is not using the new make system. Please try with:
https://github.com/tinyos/tinyos-main and avr-gcc 4.8.1 You should see something like this: vlahan@vlahan-ThinkPad-X1-Carbon:~/os/tinyos-main/apps/Blink$ make mica2 [INFO] compiling BlinkAppC to a mica2 binary nescc -o build/mica2/main.exe -Os -gcc=avr-gcc -Wnesc-all -fnesc-include=tos -fnesc-scheduler=TinySchedulerC,TinySchedulerC.TaskBasic,TaskBasic,TaskBasic,runTask,postTask -fnesc-cfile=build/mica2/app.c -fnesc-separator=__ -I/home/vlahan/os/tinyos-main/tos/platforms/mica2 -I/home/vlahan/os/tinyos-main/tos/platforms/mica -I/home/vlahan/os/tinyos-main/tos/platforms/mica2/chips/cc1000 -I/home/vlahan/os/tinyos-main/tos/chips/cc1000 -I/home/vlahan/os/tinyos-main/tos/platforms/mica2/chips/at45db -I/home/vlahan/os/tinyos-main/tos/platforms/mica/chips/at45db -I/home/vlahan/os/tinyos-main/tos/chips/at45db -I/home/vlahan/os/tinyos-main/tos/chips/atm128 -I/home/vlahan/os/tinyos-main/tos/chips/atm128/adc -I/home/vlahan/os/tinyos-main/tos/chips/atm128/i2c -I/home/vlahan/os/tinyos-main/tos/chips/atm128/pins -I/home/vlahan/os/tinyos-main/tos/chips/atm128/spi -I/home/vlahan/os/tinyos-main/tos/chips/atm128/timer -I/home/vlahan/os/tinyos-main/tos/lib/timer -I/home/vlahan/os/tinyos-main/tos/lib/serial -I/home/vlahan/os/tinyos-main/tos/lib/power -mmcu=atmega128 -fnesc-target=avr -fnesc-no-debug -DPLATFORM_MICA2 -Wall -Wshadow --param max-inline-insns-single=100000 -Wno-unused-but-set-variable -Wno-enum-compare -I/home/vlahan/os/tinyos-main/tos/system -I/home/vlahan/os/tinyos-main/tos/types -I/home/vlahan/os/tinyos-main/tos/interfaces -DIDENT_APPNAME=\"BlinkAppC\" -DIDENT_USERNAME=\"vlahan\" -DIDENT_HOSTNAME=\"vlahan-ThinkPad\" -DIDENT_USERHASH=0xcba3fc9cL -DIDENT_TIMESTAMP=0x56d6ca3dL -DIDENT_UIDHASH=0x8f1c6111L -fnesc-dump=wiring -fnesc-dump='interfaces(!abstract())' -fnesc-dump='referenced(interfacedefs, components)' -fnesc-dumpfile=build/mica2/wiring-check.xml BlinkAppC.nc -lm [INFO] script 2174 bytes in ROM 52 bytes in RAM [INFO] size (toolchain): text data bss dec hex filename 2174 0 52 2226 8b2 build/mica2/main.exe [INFO] generating symbol table [INFO] generating listing [INFO] creating srec file [INFO] creating ihex file [INFO] writing TOS image [INFO] writing TOS buildinfo [INFO] running the wiring check On Fri, Feb 12, 2016 at 4:43 AM Chris Nicholas <chrisgnicho...@att.net> wrote: > hmm - just trying to follow along the first tutorial: > > http://tinyos.stanford.edu/tinyos-wiki/index.php/Getting_Started_with_TinyOS > > root@cgn-VirtualBox:/usr/src/tinyos/apps/Blink# make mica2 > > mkdir -p build/mica2 > compiling BlinkAppC to a mica2 binary > ncc -o build/mica2/main.exe -Os -fnesc-separator=__ -Wall -Wshadow > -Wnesc-all -target=mica2 -fnesc-cfile=build/mica2/app.c -board=micasb > -DDEFINED_TOS_AM_GROUP=0x22 --param max-inline-insns-single=100000 > -DIDENT_APPNAME=\"BlinkAppC\" -DIDENT_USERNAME=\"root\" > -DIDENT_HOSTNAME=\"cgn-VirtualBox\" -DIDENT_USERHASH=0x5536ffb7L > -DIDENT_TIMESTAMP=0x56bd4f1dL -DIDENT_UIDHASH=0x61630383L > -fnesc-dump=wiring -fnesc-dump='interfaces(!abstract())' > -fnesc-dump='referenced(interfacedefs, components)' > -fnesc-dumpfile=build/mica2/wiring-check.xml BlinkAppC.nc -lm > /usr/src/tinyos/tos/chips/atm128/McuSleepC.nc:66:15: error: variable > ‘McuSleepC__atm128PowerBits’ must be const in order to be put into > read-only section by means of ‘__attribute__((progmem))’ > const_uint8_t atm128PowerBits[ATM128_POWER_DOWN + 1] = { > ^ > make: *** [exe0] Error 1 > > (sigh) > > Chris > > On Thursday, February 11, 2016 12:15 PM, Chris Nicholas < > chrisgnicho...@att.net> wrote: > > > Hi - I just installed the Debian packages on my MAC VirtualBox, and > getting psyched to build and install the examples on an Atmega 256, and > order the right low-power radio stuff to get collection tree protocol > working. > > I really want to try to port that to run over HAM radio at ~1200 baud FSK > 1/2 duplex ... does that sound feasible? > > Any words of wisdom, caution, etc on how best to go about this greatly > appreciated. And anyone here in the SF Bay/East Bay area that might be > available for a visit in 'high def' just to get my toolchain working, that > can be bribed with their favorite beer or otherwise, sought as well... > > thanks! > Chris > > >
_______________________________________________ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
