Hello All, I am writing some NesC source code here I find the source coding is Correct. However, I cannot link and help to make the next step. This file is directly derived by Blink software, and can not be acquired from other sources. As far as I know and as I read through all of the source codes of TinyOS and NesC, I find the source code can be directly written by C# and DSP 56002 Motorola Assembly Language, which is the Basics of DSP Assembly published by my thesis advisor Professor Mohamond in IUPUI by the year 1995. He published a Book about this source coding style. /***************************************/ //Using C# //make the blink software ALLOW SOURCE CODING USING C# ALLOW PICC & CSS &RRK USING NAMESPACING CCS USING ULTRAEDIT &&MINGW PULT CCD FFG HHG FFC DDS CCV BBV MMN SET TOPOLOGY BLK END /**************************************/ and the compile the software and make it into a common mote in TINYOS suite. /*************************************/ // Using DSP Assembly //make the blink software multiple control multiple using ccs ddf ffg hhg biquad ffd ccv blk on fan off end
/*************************************/ can some one tell me why the compiling is OK and the compiler can support, however, why the hardware cannot work. An Feng [email protected] -----Original Message----- From: tinyos-help-request <[email protected]> To: tinyos-help <[email protected]> Sent: Sun, Feb 17, 2013 4:01 am Subject: Tinyos-help Digest, Vol 118, Issue 33 Send Tinyos-help mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of Tinyos-help digest..." Today's Topics: 1. Re: I2C read and write API (He Dajiang (I2R)) 2. Re: typedef + nx_intN_t = impossible?! (David Gay) 3. What is the number maximum of nodes that can support blip 2.0? ([email protected]) ---------------------------------------------------------------------- Message: 1 Date: Sat, 16 Feb 2013 03:01:42 +0000 From: "He Dajiang (I2R)" <[email protected]> Subject: Re: [Tinyos-help] I2C read and write API To: Andr?s B?r? <[email protected]>, Miklos Maroti <[email protected]> Cc: Tinyos-Help <[email protected]> Message-ID: <F726DEB3CA4E28449D635321F51C8A900FF29D@S3-EXCHMB07.shared-svc.local> Content-Type: text/plain; charset="iso-8859-1" Hi Andris, Thx for ur reply. The chip means MCU or sensor chip connected to MCU through I2C? My MCU is ATMEL Mega 128L, and my sensor chip is MPU9150 from InvenSense. The problem I encounter is: there are two device addresses on the sensor chip. The I2C driver works well with simple reading and writing to the main device address. In order for me to access register info on the other device, I need to set I2C by-pass on main address. If I set it wrongly, and when I use second device address to read register information, the I2C driver hangs like: I2CPacket.write()/read() == SUCCESS, but the I2CPacket.writeDone()/readDone() never got triggered. Best Regards dajiang ________________________________________ From: Andr?s B?r? [[email protected]] Sent: Friday, 15 February, 2013 4:02:35 PM To: Miklos Maroti Cc: Eric Decker; He Dajiang (I2R); Tinyos-Help Subject: Re: [Tinyos-help] I2C read and write API Hi Guys, No it doesn't have new implementation (but it will be soon). However, I fixed a lot of bugs in the atm128 i2c driver, trust me, it works. We're using it with a lot of chips. What is the chip you're trying to use? Andris Institute for Infocomm Research disclaimer: "This email is confidential and may be privileged. If you are not the intended recipient, please delete it and notify us immediately. Please do not copy or use it for any purpose, or disclose its contents to any other person. Thank you." ------------------------------ Message: 2 Date: Sat, 16 Feb 2013 00:14:53 -0800 From: David Gay <[email protected]> Subject: Re: [Tinyos-help] typedef + nx_intN_t = impossible?! To: Eric Decker <[email protected]> Cc: tinyos-help <[email protected]> Message-ID: <CALdFPO=lrx_j_xwdl7gs1pxv_17dnbzanezztxk7aava9ge...@mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" I'll look into it in a week or so... David On Feb 12, 2013 7:14 PM, "Eric Decker" <[email protected]> wrote: > > > Sigh. Would of been nice if we could have found a work around. > > File it as a bug against https://github.com/tinyos/nesc > > Maybe we can get David's attention. David? > > On Tue, Feb 12, 2013 at 3:48 AM, Johny Mattsson <[email protected]>wrote: > >> On 12 February 2013 13:31, Eric Decker <[email protected]> wrote: >> >>> First, the #define works because it is simple text substitution. So if >>> you look at the resultant app.c you will see >>> >>> error_t foo(nx_uint16_t val) >>> >>> when using the define. >>> >>> So of course it works. >>> >> >> I'd like to think so, but given that a plain typedef doesn't work in this >> situation, I wouldn't say "of course" - there could've been something wrong >> with using nx types as pass-by-value parameters, for example. :) >> >> >> If you compile Blink say for the telosb and then take a look at app.c you >>> can see where the nx types are defined. Search for nx_uint16. >>> >> >> I'll do you one better, I'll show you what's in the app.c from the >> minimal test case in my previous email: >> >> First there's the nx_uint16_t which is an innocuous enough packed struct: >> typedef struct { unsigned char nxdata[2]; } __attribute__((packed)) >> nx_uint16_t; >> >> Then there's an unused typedef of a __nesc_nxbase_nx_uint16_t whose use >> I'm not entirely clear on without delving into compiler internals: >> typedef uint16_t __nesc_nxbase_nx_uint16_t ; >> >> There is of course my typedef, looking as expected (module__type name): >> typedef nx_uint16_t TestNxTypedefP__my_type16_t; >> >> And then there's the weirdness of the function taking my typedef'd type >> as an argument: >> static inline error_t >> TestNxTypedefP__foo(TestNxTypedefP____nesc_nxbase_my_type16_t val); >> >> What I had expected to see here was: >> static inline error_t TestNxTypedefP__foo(TestNxTypedefP__my_type16_t >> val); >> >> >> It seems the compiler has an internal translation rule for nx types that >> translates them from the struct version to the "base" version. When >> compiling with the #define rather than the typedef, the function prototype >> looks like this: >> static inline error_t TestNxTypedefP__foo(__nesc_nxbase_nx_uint16_t >> val); >> >> >> To me this seems like a nesc issue (or at the very least a nesc >> documentation issue). >> Who/where do I bounce this to? Running nescc --help only points at the >> gcc bug reporting, which is clearly not applicable here. >> >> >> >>> Maybe adding a nx_ prefix to your type would help. >>> >> >> Tried that, it didn't help. >> >> >> Thanks, >> /Johny >> * >> * > > > > > -- > Eric B. Decker > Senior (over 50 :-) Researcher > > -------------- next part -------------- An HTML attachment was scrubbed... URL: https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20130216/4063adf5/attachment-0001.htm ------------------------------ Message: 3 Date: Sat, 16 Feb 2013 16:30:19 +0100 (CET) From: [email protected] Subject: [Tinyos-help] What is the number maximum of nodes that can support blip 2.0? To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain;charset=utf-8 Dear all. Someone have any idea about the maximum number of nodes that can support one sink mote (TelosB) using PppRouter and working with Blip 2.0? I've worked ok with one sink node and 3 sensor nodes. There is a limitant factor? Thanks in advance for your answer. Best regards, Alejandro. > This is actually for Muhammad but I only have Robin email directly. > > > On Wed, Feb 13, 2013 at 12:42 PM, Robin Martinjak <[email protected]> > wrote: > >> On Wed, Feb 13, 2013 at 10:46:29PM +0500, Muhammad Tayyeb wrote: >> > Hi, >> > I am new to TinyOS and implementing the tutorials. I am on Deluge T2 >> at >> the >> > moment. >> > > I am guessing that you are on cygwin. It would have been really helpful > if you had told us what system you are hosting your development > environment > on. > >> >> > When I run the command >> > >> > ./burn serial@/dev/ttyUSB0:115200 telosb >> > >> > I get the following error >> > >> > xubuntos@xubuntos-tinyos:/opt/tinyos-2.x/apps/tests/deluge/Blink$ >> ./burn >> > serial@/dev/ttyUSB0:115200 telosb >> > rm -rf build >> > rm: cannot remove `build/telosb/ident_flags.txt': Permission denied >> > rm: cannot remove `build/telosb/StorageVolumes.h': Permission denied >> > > what do the permissions look like for the install? > > >> > make: *** [clean] Error 1 >> > ============================ Compile and load Blink >> > ============================ >> > mkdir -p build/telosb >> > /bin/sh: cannot create build/telosb/ident_flags.txt: Permission denied >> >> You should copy the whole tinyos-2.x directory to somewhere in your >> user's $HOME if you want to build stuff. >> > > Gag. > > We haven't updated the install instructions but the new improved > mechansims > to get the release are as follows: > > cd ~ > mkdir -p w > cd w > git clone git://github.com/tinyos/tinyos-release.git > > The above will put the current tinyos release (2.1.2) into the directory > ~/w/tinyos-release > > you will have to tweak your environment variable appropriately. > > you will also need git, "apt-get install git-core" should do the trick.... > > But I am assuming that you are on Linux and I suspect that isn't true. > > Currently, we don't have cygwin rpms for the 4.6.3 builds So if you are > on cygwin, I'm not > sure what you can do. The problem you will also run into is 2.1.2 needs > 4.6.3. > > I would strongly encourage you to switch over to a Linux box (Debian or > Ubuntu). I originally started TinyOS development using a Cygwin host and > found it to be quite painful as well as problematic. At some point I got > fed up and switched over to Linux and haven't looked back. I do much of > the packaging for toolchains and tinyos and do not support the cygwin > rpms. > I support the debian archives. > > Also the TinyOS repository at Stanford is no longer actively maintained so > am hosting my work at tinyprod.net. See below. > > >> > >> > Your help will be much appreciated on the error "Couldn't execute >> > msp430-gcc" error. msp430-gss exe is present in its folder. >> > > running commands as root isn't recommended, you can really do damage if > you > screw something up. > > > did you install the msp430 toolchain (you need 4.6.3 which you can get > from > http://tinyprod.net/repos/debian/ > > you should be able to execute the command "msp430gcc --version" to make > sure that > > >> > >> >> You probably need to install additional packages. Search your package >> manager for "msp430" or so. >> > > > > >> >> >> -- >> O< ascii ribbon campaign - stop html mail - www.asciiribbon.org >> >> _______________________________________________ >> Tinyos-help mailing list >> [email protected] >> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >> > > > > -- > Eric B. Decker > Senior (over 50 :-) Researcher > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ------------------------------ _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help End of Tinyos-help Digest, Vol 118, Issue 33 ********************************************
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
