I too have not been able to program micaz's after upgrading to 1.1.14
as per the instructions on the TOS page that is now lost to my bookmarks...
I over-loaded the cygwin upgrade and then overloaded the TOS 1.1.14 onto
my working 1.1.7 system (all this in hopes that my micaz communication
problems would "just go away", which they didn't...more later...).

I had a bit of trouble with the TOS rpm because it refused to admit that
I had nesc 1.1 installed so I had to use -nodeps to get it to DWIW. Also
once the dust was clear, the platform/micaz/HPLPowerManagementM.nc file
was still there and caused compile problems -- doing some code archeology
I think I determined that the file is superceeded by that in the mica(noZ)
directory (and accessed through the usual inexplicable and undocumented
TOS include process sub( if the "inexplicable and undocumented" part is
an oversight on my part please someone tell me where to look )end-sub ).

Luckily, I kept a full copy of my working 1.1.7 system, which STILL works
fine. What's more I can program mica2's in the new system just fine.

The micaz symptom is as described before, (by turning on -v=4) I see that
no reply is received from the target and the uisp hangs waiting.

I was happy to see that Michael Smith had a ready answer: use /dev/ttySn
however I get:

    Error: No such file or directory
     -> /dev/ttyS3

(I'm using a USB converter that resides at COM3 on my WINXP box). The whole
/dev/trick thing on Widows has always been a mystery to me, but it has on
occasion JustWorked(TM), before.

I suspect that there is some disagreement on the actual startup message
sequence for the micaz, but I don't know where to look for the specs...
anybody else know?

So, anyway, is the real answer to use 1.1.10 instead? Is there anyone out there
who can vouch for it working correctly? Should I bother, or just stick to 1.1.7?

MS

ps...see my next post for micaz comm problems...



Sam Pierson wrote:
I apologize for not editing subject on the previous email!

On 1/9/06, Sam Pierson <[EMAIL PROTECTED]> wrote:

I tried all of the following suggestions, and the same problem arises.
I installed tinyos 1.1.11 because I had the install shield version and
it seems to be much cleaner than installing 1.1.0 and then upgrading
via RPM to 1.1.10.  I could only find the January cvs release of 1.1.10.

The programming board does not respond to /dev/ttyS0 and hangs
again when I try to manually use uisp as below.  I know that my
programming board is on COM1.

Is there any other step I can take?

Thanks,


Date: Fri, 6 Jan 2006 13:52:18 -0800
From: "Mike Smith" <[EMAIL PROTECTED]>
Subject: [Tinyos-help] trouble uploading to mica z
To: <[email protected]>
Message-ID:
       <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"

Sam,



Crossbow currently supports TinyOS 1.1.10 for the use of our software
applications.  There are several bugs in the more recent versions and
although we continue to test some of the newest versions we think it is
important to have a stable version to work from.  In response to your
questions, please consider the following possibilities:



1)       Make sure that your SW2 switch is in the OFF position on the
MIB510 at all times and make sure that the green LED is lit.

2)       In version 1.1.11 and higher you will need to type "make micaz
install mib510,/dev/ttyS0" for COM1,  "ttyS1" for COM2 the first time
you attempt to install to the mote.  If you don't do this, you can hang
the COM port which prevents further communication.  Simply reboot the
computer and try the command line above if you have a frozen COM port

3)       Your output should look like this:



uisp -dprog=mib510 -dserial=com1 --wr_fuse_h=0xd8 -dpart=ATmega128



The -dprog indicates you are using the MIB510 and the -dserial output
indicates your COM port.  If the -dprog output states "dapa", this means
you are trying to access the parallel port which will result in a series
of flash errors.

Sincerely,

Michael Smith
Application Engineer/Tech Support
Crossbow Technology, Inc.




--
Sam Pierson

_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to