Searching \ for '[PIC] Wisp628 and xwisp2w Problem' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/microchip/devprogs.htm?key=wisp
Search entire site for: 'Wisp628 and xwisp2w Problem'.

Exact match. Not showing close matches.
PICList Thread
'[PIC] Wisp628 and xwisp2w Problem'
2006\06\23@090658 by Victor Fraenckel

flavicon
face
I am attempting to program a 16F876A project with the Wisp628 programmer
driven by xwisp2w  from http://www.robh.nl/ The '628 is connected to my
computer through a FT232RL serial to USB connection. The device manager
shows this serial port to be COM3. The .BAT file command I am using to
run is xwisp2w is "com3 baud 9600 go %1" where %1 is the name of the
.HEX file I wish to use.  When running xwisp2w it immediately errors
"Command 'com3' unknown or not currently implemented" also "xwisp2
failed after 0.08 seconds, rc 36". I have had good luck running this
combination with a true serial port, but that one stopped functioning.

I am assuming the the program does not function properly using the USB
to Serial interface. I cannot see at the above web site where to e-mail
robh.nl to get suggestions. Anyone here have any?

Any enlightenment will be appreciated.

Vic
--

*____________________________________________________________________________________________*

*Victor Fraenckel
KC2GUI
victorf ATSIGN windreader DOT com**
*



2006\06\23@092452 by Wouter van Ooijen

face picon face
> I cannot see at the above web site where
> to e-mail
> robh.nl to get suggestions. Anyone here have any?

Rob is spam_OUTrobTakeThisOuTspamrobh.nl, but I think he will be listening here too.

I have never used xwisp2, but you might try 'port com3' instead of
'com3'.

You could also try my xwisp.

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: http://www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: http://www.voti.nl/hvu


2006\06\23@094417 by Xiaofan Chen

face picon face
On 6/23/06, Victor Fraenckel <.....victorfKILLspamspam@spam@windreader.com> wrote:
> I am attempting to program a 16F876A project with the Wisp628 programmer
> driven by xwisp2w  from http://www.robh.nl/ The '628 is connected to my
> computer through a FT232RL serial to USB connection. The device manager
> shows this serial port to be COM3. The .BAT file command I am using to
> run is xwisp2w is "com3 baud 9600 go %1" where %1 is the name of the
> .HEX file I wish to use.  When running xwisp2w it immediately errors
> "Command 'com3' unknown or not currently implemented" also "xwisp2
> failed after 0.08 seconds, rc 36". I have had good luck running this
> combination with a true serial port, but that one stopped functioning.
>
> I am assuming the the program does not function properly using the USB
> to Serial interface. I cannot see at the above web site where to e-mail
> robh.nl to get suggestions. Anyone here have any?
>

Output from xwsip2:

>>>  (-) not yet supported, (+) fully supported with Wisp628 firmware 1.10
>>> See below some examples of command lines:
>>> (press 'Enter' to continue):

Flash file 'abc.hex' using a Wisp628 on COM1 or /dev/ttyS0:

> xwisp2 abc           {first serial port is default, 'go' can be left out}

Flash file 'abc.hex' using a Wisp628 on COM3 or /dev/ttyS3:

> xwisp2 port 3 go abc {'go' must be specified in this case}

The environment variable 'XWISP2' may be set to customise XWisp2 for daily use.

xwisp2 terminated successfully in 5.19 seconds

2006\06\23@095007 by Dave Lag

picon face
Victor Fraenckel wrote:
> I am attempting to program a 16F876A project with the Wisp628 programmer
> driven by xwisp2w  from http://www.robh.nl/ The '628 is connected to my
> computer through a FT232RL serial to USB connection. The device manager
> shows this serial port to be COM3. The .BAT file command I am using to
> run is xwisp2w is "com3 baud 9600 go %1" where %1 is the name of the
> .HEX file I wish to use.  
>
> Any enlightenment will be appreciated.
>
> Vic

Missing a space I believe
eg:
xwisp2w port 4 read  readtemp.hex

2006\06\23@170839 by Victor Fraenckel

flavicon
face
Thanks for the suggestion concerning using port rather than comX. I
modified my batch file which now reads:

xwisp2w port 3 baud 9600 go %1

Now I am getting the following error:

xwisp2 version 1.9.0 for Windows (Apr 08 2006, Open Watcom C 1.40)
File sensorboard.hex loaded and is Intel Hex format conforming
SendReceiveSlow read timeout, 0 bytes received
SendReceiveSlow read timeout, 0 bytes received
Failed to activate Wbus device, not connected?
xwisp2 failed after 1.30 seconds, rc 23!

Does the RS232 side of the converter have to supply other than RXD, TXD
and ground to the Wisp628? The FT232RL can supply  most of the standard
RS232 signals but I am only using RXD and TXD.

I am getting the feeling that xwisp2w is not going to hack it with the
USB>Serial connection. If Rob is listening here, would he like to
comment on my problem?

Any further enlightenment will be appreciated.

Vic

*____________________________________________________________________________________________*

*Victor Fraenckel
KC2GUI
victorf ATSIGN windreader DOT com**


*


2006\06\24@030633 by Wouter van Ooijen

face picon face
> I am getting the feeling that xwisp2w is not going to hack it
> with the
> USB>Serial connection. If Rob is listening here, would he like to
> comment on my problem?

I dunno about the xwisp2w specifics, but XWisp on XP works OK with the
usb-serial converters I tried (in fact these converters work better than
the flaky serial port on my PC).

Wisp628 uses only gnd, tx, rx. But The PC-side drivers might insist on
handshake.

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: http://www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: http://www.voti.nl/hvu


2006\06\24@131503 by Jan-Erik Soderholm

face picon face
Victor Fraenckel wrote :

> The Wisp628 is connected to my computer through a FT232RL
> serial to USB connection.

Is that some home-built "hack" ?
Or is it one of the many USB/serial converters available ?
I have run all my Wisp628's using a cheap USB/serial converter
all the time without any problem at all.

> xwisp2w is "com3 baud 9600 go %1"...

(Other have commented on "com3"...)
Why do you need the "baud xxx" parameter ?

> I have had good luck running this
> combination with a true serial port,...

Using the same "...comx..." syntax ?

> I cannot see at the above web site where
> to e-mail robh.nl to get suggestions.

You've got an error in the syntax and you're using an
USB/serial converter of unknown origin, I'm not sure
how much "support" you can ask on that. I do not this
is a problem with XWisp2 as such...


Best Regards,
Jan-Erik.



2006\06\24@145513 by Victor Fraenckel

flavicon
face
Jan-Erik Soderholm wrote:
>Is that some home-built "hack" ?
>Or is it one of the many USB/serial converters available ?

Go here and enlighten yourself:

http://www.sparkfun.com/commerce/product_info.php?products_id=718

>Why do you need the "baud xxx" parameter ?

To set the baud rate to 9600 because I wanted to. It worked well for me when I had a real serial port.

>You've got an error in the syntax

No syntax error. Try envoking xwisp2w -? and closely reading the help you see. comX is a valid command. The device manager shows the USB converter to be com3. I have since changed that to port 3 as suggested by some on this list. Since my original posting, I have posted another one outlining my latest command line and results of using it.

>USB/serial converter of unknown origin,

previously commented on

>I'm not sure how much "support" you can ask on that. I do not think
>is a problem with XWisp2 as such...

I never implied that there was a problem with XWisp2. I was merely asking if using a usb to serial converter might be a problem. I was hoping someone had a work-around.

Thanks for your response.

Vic

*____________________________________________________________________________________________*

*Victor Fraenckel
KC2GUI
victorf ATSIGN windreader DOT com**


*


2006\06\24@171115 by Jan-Erik Söderholm XA (TN/PAC)jan-erik.xa.soderholmn/a

flavicon
Victor Fraenckel wrote :

>
> Go here and enlighten yourself:
>
> http://www.sparkfun.com/commerce/product_info.php?products_id=718

OK, fine. More of a "demo/test" board. Try with a complete
adapter using standard connectors and all that. The ones you
can buy in any PC/computer store.

>
> >Why do you need the "baud xxx" parameter ?
>
> To set the baud rate to 9600 because I wanted to.

OK, the programming will only go slower, maybe that's
what you "want". I seldom uses the "baud" command but
let XWsip2/Wisp628 handle the speed changes.

> No syntax error. Try envoking xwisp2w -? and closely reading
> the help you see. comX is a valid command.

OK, I always use the "port x" syntax. Sorry about that...

B.t.w, the "usage" command examples you can see on the last of
the XWisp2 help page are actualy mine... :-) I did the first
OS/2 -> Win32 port of XWisp2, but Rob H have since then taken
over that...


> I have since changed that
> to port 3 as suggested by some on this list. Since my
> original posting, I have posted another one outlining my
> latest command line and results of using it.

And I seems to remember that they showed that XWisp2 *does*
find the port but you get some communication error, right ?

> I was merely asking if using a usb to serial converter might
> be a problem.

No, not in general. Most (all?) converters does work OK, as
far as I've heard.

Best Regards,
Jan-Erik.

2006\06\24@171254 by Jan-Erik Soderholm

face picon face
(This was first sent from a wrong mail account, resending
from the correct account. Sorry if it gets doubled...)




Victor Fraenckel wrote :

>
> Go here and enlighten yourself:
>
> http://www.sparkfun.com/commerce/product_info.php?products_id=718

OK, fine. More of a "demo/test" board. Try with a complete
adapter using standard connectors and all that. The ones you
can buy in any PC/computer store.

>
> >Why do you need the "baud xxx" parameter ?
>
> To set the baud rate to 9600 because I wanted to.

OK, the programming will only go slower, maybe that's
what you "want". I seldom uses the "baud" command but
let XWsip2/Wisp628 handle the speed changes.

> No syntax error. Try envoking xwisp2w -? and closely reading
> the help you see. comX is a valid command.

OK, I always use the "port x" syntax. Sorry about that...

B.t.w, the "usage" command examples you can see on the last of
the XWisp2 help page are actualy mine... :-) I did the first
OS/2 -> Win32 port of XWisp2, but Rob H have since then taken
over that...


> I have since changed that
> to port 3 as suggested by some on this list. Since my
> original posting, I have posted another one outlining my
> latest command line and results of using it.

And I seems to remember that they showed that XWisp2 *does*
find the port but you get some communication error, right ?

> I was merely asking if using a usb to serial converter might
> be a problem.

No, not in general. Most (all?) converters does work OK, as
far as I've heard.

Best Regards,
Jan-Erik.



2006\06\25@111413 by Xiaofan Chen

face picon face
On 6/25/06, Victor Fraenckel <victorfspamKILLspamwindreader.com> wrote:

> >Why do you need the "baud xxx" parameter ?
>
> To set the baud rate to 9600 because I wanted to. It worked well for me when I
> had a real serial port.

Try to delete the "baud xxx" option and see if it is oaky. I remember
once I have problem with baud rate switching under Windows XP.

> I never implied that there was a problem with XWisp2. I was merely asking if
> using a usb to serial converter might be a problem. I was hoping someone
> had a work-around.
>

Yes it is said that some usb to serial converters can cause a problem.
Try to use a shorter cable as well. Please try to add bypass
capacitors across Vdd and GND as well.

By the way, are you using the latest firmware version
(WISP628 firmware version 1.10a) which comes with the v1.90 package?

Regards,
Xiaofan

More... (looser matching)
- Last day of these posts
- In 2006 , 2007 only
- Today
- New search...