After the Cygwin update, I managed to track down that uisp was apparently opening the port
but was unable to write to it (why? permissions?). Your mention of  /dev/ttyS0 get me to
wondering why there is no /dev device directory in the distribution.

Following the procedure given at:

Cygwin_project

and invoking the .bat and .sh script, I was able to then specify

    make mica2 install mib512,/dev/ttyS0

and get it to work. The perms were crw-rw-rw-   ttyS0.

First I upgraded to 1.1.8, which I have been using in my labs for a while and I knew
how it worked ... and it did.

Then upgraded nesc and TOS to 1.1.14 and it's still working (although I did have to
    fix the avr.rules to use environment variables as opposed to the command line spec
    for the MIB510).

Did I just get lucky, or is this likely to be the real answer to going above 1.1.10?

Thanks

--John Stone  [EMAIL PROTECTED]

Michael Schippling wrote:
I think we should all just face the fact that UISP serial port access
doesn't work, or work reliably, under the cygwin update. I thought
this update took place years ago (since I try not to use any version
of anything that is less than 5 years old...), but it's only recently
that I've seen questions and complaints flooding in to this list.

Xbow's solution was to replace COM1 with /dev/ttyS0 in the port
specification, but that seems to have minimal effect. Didn't work
for me in other words.

My solution was to back out the cygwin update and level off at TOS 1.1.10,
but I have also been able to compile later TOS code under my old env,
seemingly successfully.

I wonder if someone who knows something could tell us WHY the cygwin
update is necessary for post .10 TOS versions?

MS


John Stone wrote:
On Windows:

After a clean install of 1.1.0, the MIB510 worked as expected. I left everything
connected.

Then did the TOS specific Cygwin upgrade in preparation for loading 1.1.14 (and the nesc
upgrade). Rebooted and tried the make command again, with essentially the same results Affan
reports. It hangs.

Any help appreciated.

--John Stone

Michael Schippling wrote:

Anything you've changed since it all worked? upgrade, etc?

No other programs trying to get to the serial port, modem, etal?

Check that darn serial switch is OFF on the MIB, but I don't think
this affects the programming cycle.

Wiggle the wires...

Reboot? If it's Windows, it's the only way...
I have been told that later version of TOS (1.1.14 at least)
can hang the serial port if you don't use /dev/ttyN from the
start.

If you have a serial breakout box, see if there are any signals
actually on the wire. Can do this with a scope too.

Try to connect to some other serial device using hyperterm or
whatever terminal program you have.

MS





Affan Syed wrote:

Hello,
I seem to be getting this very basic programmer not responding error. I
have searched the mailng list for the solution but most of the issues
discussed have been b/c of a USB-serial conversion for the mib510
programming board. I have checked that the board is getting the power,
and even changed the programmer. It seems as if the issue might be with
the serial port, but I have used the same system earlier for programming
the nodes.
Here are the diagnostics that I tried:

[EMAIL PROTECTED] /opt/tinyos-1.x/apps/dtest

$ make mica2 reinstall
    installing mica2 binary
uisp -dprog=mib510 -dserial=/dev/ttyS0 -dpart=ATmega128 --wr_fuse_e=ff
--erase

Programmer is not responding.

make: *** [reinstall] Error 2

[EMAIL PROTECTED] /opt/tinyos-1.x/apps/dtest
$ uisp -dprog=mib510 -dserial=/dev/ttyS0 -dpart=ATmega128 --wr_fuse_e=ff
Programmer is not responding.

[EMAIL PROTECTED] /opt/tinyos-1.x/apps/dtest
$ uisp -dprog=mib510 -dserial=/dev/ttyS0 -dpart=ATmega128 --rd_fuse
Programmer is not responding.

Any clues on what might be the issue? Or how to further investigate this
issue.
Thankyou.
Best Regards,
Affan Syed.


_______________________________________________
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

_______________________________________________
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