gnupic: Help with pic over usb


Previous by date: 18 Feb 2011 23:58:00 -0000 Re: Moving from PIC16 to PIC18 Adding chip to gpasm and picp, captain.deadly.gmail.com
Next by date: 18 Feb 2011 23:58:00 -0000 pic reset?, John Pritchard
Previous in thread: 18 Feb 2011 23:58:00 -0000 Re: Help with pic over usb, Peter Stuge
Next in thread:

Subject: Re: Help with pic over usb
From: John Maxwell ####@####.####
Date: 18 Feb 2011 23:58:00 -0000
Message-Id: <1298073478.6833.0@deepthought.jmaxhome.com>

On 02/14/11 07:46:28, Anne Vanhoest wrote:
> But how
> do I
> get "any terminal emulator" to connect to the virtual com port?
> 

Linux includes drivers for most (I'm tempted to say "all", because I've 
never found an exception, but that'd be begging for trouble) devices 
which conform to the USB CDC (the USB sub-spec for com port-like 
devices)

Plugging in a such a device usually results in a new device file 
showing up on the machine. Typical filenames are /dev/ttyUSB0 or
/dev/ttyUSB1 or the like.

To find out for sure whether your Linux box is noticing the PIC32 board 
and setting things up properly, do a tail -f on /var/log/messages, and 
then plug the device in. You should see a flurry of messages indicating 
that Linux has seen the new device, and (hopefully) what device file 
it's accessible as.

Given that all of the above works, just tell minicom to use /dev/
ttyUSB0 (substitute appropriate terminal program and device file, of 
course) as its communications port.

-John

--
John Maxwell  KB3VLL  ####@####.####

Exit ramps - suburban America's skid pads.

Previous by date: 18 Feb 2011 23:58:00 -0000 Re: Moving from PIC16 to PIC18 Adding chip to gpasm and picp, captain.deadly.gmail.com
Next by date: 18 Feb 2011 23:58:00 -0000 pic reset?, John Pritchard
Previous in thread: 18 Feb 2011 23:58:00 -0000 Re: Help with pic over usb, Peter Stuge
Next in thread:


Powered by ezmlm-browse 0.20.