Hi All Just an update note in case anybody else has trouble upgrading to T2 (I suppose it's the T1 dinosaurs finding evolution has problems - starting from scratch is easier).
I took a clean machine and built the tools from scratch and then UPGRADED cygwin to the latest and it worked. This was recommended to me early on - but I guess I was following the instructions. So to repeat my experience .... the instructions at http://www.tinyos.net/tinyos-2.x/doc/html/upgrade-tinyos.html - failed on three separate machines, and don't work in a Vista environment. I've looked for a way to push some notes into the Wiki on this, but doesn't seem to be open to that. Some information from investigations CYGWIN doesn't support Vista - with a fair number of cygwin users talking about lack of support. There is a Microsoft Virtual Machine that is being released - its currently at 1.0 so someone could be trail blazer who tries it on Vista and can migrate cygwin to it. In the process of finding out about Cygwin - as a few people reminded me - be careful of multiple Cygwins on the same machine. Cygwin faq recommends working with a "mount and unmount" as a way of repointing cygwin's working directory. I didn't try it, but so long as there is only one ACTIVE cygwin at any one time seems to be OK to have copies of the toolchain around (while trying to get a working toolchain) My method with a working T1 structure, was to rename it to another directory - C:\tinyos\cygwin\opt\tinyos-1.x.. --> C:\tinyos\cygwin-T1copy\opt\tinyos-1.x\.. copy in the working verified cygwin toolchain to c:tinyos\cygwin\.. - verify the operation for T1 and T2 by compiling Blink, and then copied in the working ..\tinyos-1.x\.. directories. I've also taken the Vanderbilt Iris toolchain for the ATmega1281 http://www.isis.vanderbilt.edu/projects/NEST/tinyos-2.x-iris/doc/html/instal l-tinyos-iris.html and it works nicely. Thanks for all the work explaining it from Vanderbilt In the process I've also beefed up on the WinAVr toolchain which fits in with AVR studio /JTAG symbolic emulator. Very nice. Has anybody got the nesC output so that it can be fed into the AVR studio. Even if it could just be used for integration testing of a subsystem it would be really nice to be able to have a pure 'C' output that can be fed into a symbolic environment. Just an idea Neil -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Hancock Sent: Friday, March 21, 2008 1:12 PM To: 'Janos Sallai' Cc: [email protected] Subject: RE: [Tinyos-help] RE: TinyOS 2.0 upgrade Hello Janos Thankyou again for the suggestion, I've looked at the registry keys and I'm not seeing anything that makes it look like there is any unusual dependencies. So I'm sharing my experience with the whole list in trying to get a set of T2 tools working. I've used a clean Windows XP machine install, and the tutorial as defined still fails for me. I've tried doing it on Vista Business machine using latest cygwin (1.5.25-11), and cygwin setup fails - not compatible yet with Vista I think. Sorry for beating this - but I don't have a T2 environment - and somehow I sense it is a thorny issue. Well there is an idea for Wmware for Putty/samba share from Ariel Mauricio Nunez Gomez, so I guess next step is to try that route again. Many thanks Neil Hancock More details .... So going back to your registry suggestion, I have been through the upgrade using the cygwin.com/setup - so if it needed an extra flag it would have put it in at that time. There is no downgrade concept in cygwin, only forward motion. I hear you when you say multiple cygwins is not recommended - but the reality of software engineering is we need to be able to define setups were we can switch between - the whole reason Vmware is making a hit. Since I need a working machine, I can't afford to delete my current environment until I have a new stable working environment - so I need to be able to switch between setups somehow - or buy a whole new machine for the T2 environment. So on your criteria for my XP machine 1) consistent cygwin.dll and other cygwin related dlls YES I believe I have that 2) don't just rename/move the directories, but also save/restore the registry keys related to cygwin (at least HKLM/SOFTWARE/Cygnus Solutions) No dependency that I can see of in " HKLM/SOFTWARE/Cygnus Solutions" Cygwin doesn't state it support Windwos Vista, so I guess there are a whole can of worms with the Windows Vista environment, I tried using my windows vista machine. When I try to run the cygwin.com/setup (v 2.573.2.2) on Vista it has an AppCrash and fails with "Setup.exe has stopped working" So at great expense (future liabilities) I borrowed my wifes computer while she was out. This has never seen cygwin/tinyos/jdk on it before. I installed cygwin-1.2a.tgz, jdk-6u5-windows-i586-p.exe & tinyos tools per http://www.tinyos.net/tinyos-2.x/doc/html/upgrade-tinyos.html selecting nesc-1.2.8a-1.cygwin.i386.rpm I initially installed cygwin at c:\cygwin and then realized the mistake, moved it to c:\tinyos\cygwin - and reinstalled setup from cygwin-1.2.a and with the new location specified Same result - kaput - nesc1 failed, " point basename could not be located in the dll cygwin1.dll" (So what is the difference with the unrecommended nesc-1.2.8b-1.cygwin.i386.rpm) And then the machine's owner returned .... so haven't tried the latest cygwin. BTW: Running total on the upgrade tutorial is about 16hrs. -----Original Message----- From: Janos Sallai [mailto:[EMAIL PROTECTED] Sent: Thursday, March 20, 2008 2:40 PM To: Neil Hancock; [email protected] Subject: RE: [Tinyos-help] RE: TinyOS 2.0 upgrade Neil, If you want to switch between multiple cygwin trees, there are a couple of things to keep in mind: - always make sure that the cygwin.dll on the path (and other cygwin related dlls) is the one in the cygwin tree that you are using - don't just rename/move the directories, but also save/restore the registry keys related to cygwin (at least HKLM/SOFTWARE/Cygnus Solutions) But still, as I wrote in my previous mail, having multiple cygwin installations on the same PC is not recommended. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Hancock Sent: Thursday, March 20, 2008 4:19 PM To: [email protected] Subject: [Tinyos-help] RE: TinyOS 2.0 upgrade Hi Janos Thanks for the reply - I forgot to mention - I tried going to the latest Cygwin, having setup.exe download it from the cygwin.com/setup.exe, but the environment didn't even come up. I'm very uncomfortable with the lack of visible versioning. My experience is that you need to have a baseline to test everything against. Occasionally after some testing, the baseline is moved up. Since you say that should work, and looking at cygwin.com there is a 2008-Mar-09 Cygwin DLL 1.5.25-11 release that perhaps I should bring it up. My environment I have one cygwin tree that I work in c:\tinyos\cygwin\..... but I've rename trees into this space for testing/coding in earnest. After the rename I reboot so that the first invocation is fresh. I've got older copies as c:\tinyos\cygwin-T1.1.15works\.. as well tested working arrangements... gotta be able to go back to a known working environment. I've got a newer tree as c:\tinyos\cygwin-T2.0tools When I switch environments I rename the directory structure to c:\tinyos\cygwin\... I could move them to another disk if that is likely to be interfering somehow... but rename is much nicer. I have upgrade the Java to the latest jdk1.6.0_05 - but I don't think that should affect TinyOS compiler should it. So here is my T2 environment - the latest tools, and configured for the tinyos-1.x tree. When I compile tinyos-1.x/apps/Blink with make mica2 And it fails with a windowlet Nesc1.exe - Entry point not found The procedure entry point basename could not be located in the dynanmic link library cygwin1.dll So any thoughts Many thanks Neil Hancock -----Message----- Janos Sallai sallai at isis.vanderbilt.edu Thu Mar 20 11:19:39 PDT 2008 It's a good practice to upgrade cygwin to the latest release when you upgrade from T1 to T2. Newer versions of the cygwin.dll are backwards compatible with the older ones, so the incompatibility issues you're facing would go away. Also, always make sure that you have only one cygwin tree installed on your computer, otherwise things can (and will) break... Janos -----Original Message----- From: Neil Hancock [mailto:[EMAIL PROTECTED] Sent: Thursday, March 20, 2008 10:58 AM To: '[email protected]' Subject: TinyOS 2.0 upgrade Hi All I'm wondering if anybody else has had problems upgrading from TinyOS 1.1.15 - and I can't find any recent suggestions on this topic in the archives. I've been running with the latest cygwin based environment from the pre-2.0 and which has been stable for the last 2+ years. I have a well beaten up windows workstation XP PROF with the latest updates and a laptop with Vista Business .. I followed the Cygwin Tutorial instructions on upgrading http://www.tinyos.net/tinyos-2.x/doc/html/upgrade-tinyos.html - when it came to install the tinyos-tools-1.2.4-2.cygwin.i386.rpm I got Giveio-install.exe complaining about "entry point_getreent could not be located in the dll cygwin1.dll" . I reinstalled the reference cygwin a couple of times and couldn't get past this - something really wrong in my setup that the install isn't fixing. So then I attempted a clean install of the reference tools - renaming my old c:\tinyos\cygwin and letting it build c:\tinyos\cygwin\... tool chain. So now I have TinyOs 2.0 tools. On adding my TinyOs tree (1.1.15) and knitting it into the tools it then started to compile my tree, hurrah .. but ended up with Nesc1.exe - Entry Point Not Found " The procedure entry point basename could not be located in the dll cygwn1.dll By this time - I'd taken at least 8 hours to get here. So is anybody using the Cygwin tools as per the tutorial.? Any suggestions as to where I should start. Is this supported under windows Vista. I tried to put an environment on my Vista portable a couple of months ago, and Cygwin didn't want to run on it from what I remember. So I tried the UbunTos route - thanks for Kevin Klueska 's good instructions and setting up the basic model - and after another 4 hours managed to get 2.0 App Blink to compile - Vmware/XP Prof and VmPlayer/Vista Business- but the environment isn't connected in with Windows - and I'm going to have trouble with the Windows tool chain - so I'm not seeing this as a viable option. So know I've downgraded my XP workstation (switched out my directories) back to the one where I rebuilt to the recommended Cygwin - and been running this for a week. Whats interesting is that it fails after about 20 compiles - kaput, does something weird, and requires a windows reboot. This has happened about 5 times in the last week . So the recommended Cygwin environment supplied is slightly different and less stable than the environment derived from following the Tinyos 1.1.15 upgrade path. Many thanks for any help Neil Hancock _______________________________________________ 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 _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
