Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.arch.embedded > #20606 > unrolled thread
| Started by | rickman <gnuarm@gmail.com> |
|---|---|
| First post | 2015-04-02 21:08 -0400 |
| Last post | 2015-04-16 16:18 -0700 |
| Articles | 20 on this page of 123 — 26 participants |
Back to article view | Back to comp.arch.embedded
Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-02 21:08 -0400
Re: Mecrisp on the TI Stellaris Launchpad sbattazzo@gmail.com - 2015-04-13 16:18 -0700
Re: Mecrisp on the TI Stellaris Launchpad sbattazzo@gmail.com - 2015-04-13 16:25 -0700
Re: Mecrisp on the TI Stellaris Launchpad sbattazzo@gmail.com - 2015-04-13 16:33 -0700
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-13 21:45 -0400
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-13 21:47 -0400
Re: Mecrisp on the TI Stellaris Launchpad sbattazzo@gmail.com - 2015-04-14 07:33 -0700
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-14 14:38 -0400
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-16 14:24 -0700
Re: Mecrisp on the TI Stellaris Launchpad Paul Rubin <no.email@nospam.invalid> - 2015-04-16 15:11 -0700
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-16 23:37 -0400
Re: Mecrisp on the TI Stellaris Launchpad Paul Rubin <no.email@nospam.invalid> - 2015-04-16 20:59 -0700
Re: Mecrisp on the TI Stellaris Launchpad Mel Wilson <mwilson@the-wire.com> - 2015-04-17 13:16 +0000
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-17 00:19 -0400
Re: Mecrisp on the TI Stellaris Launchpad Paul Rubin <no.email@nospam.invalid> - 2015-04-16 21:56 -0700
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-17 14:47 -0400
WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking rickman <gnuarm@gmail.com> - 2015-04-17 15:12 -0400
Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking Martin Gregorie <martin@address-in-sig.invalid> - 2015-04-17 20:14 +0000
Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking rickman <gnuarm@gmail.com> - 2015-04-17 16:59 -0400
Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking David Brown <david.brown@hesbynett.no> - 2015-04-18 10:00 +0200
Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking rickman <gnuarm@gmail.com> - 2015-04-18 09:32 -0400
Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking Martin Gregorie <martin@address-in-sig.invalid> - 2015-04-18 15:15 +0000
Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking rickman <gnuarm@gmail.com> - 2015-04-18 11:31 -0400
Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking Niklas Holsti <niklas.holsti@tidorum.invalid> - 2015-04-18 19:21 +0300
Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking rickman <gnuarm@gmail.com> - 2015-04-19 16:39 -0400
Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking Alan Adams <alan@adamshome.org.uk> - 2015-04-18 18:52 +0100
Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking "Rod Pemberton" <bork@lllljunkqwer.cpm> - 2015-04-18 18:55 -0400
Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking The Natural Philosopher <tnp@invalid.invalid> - 2015-04-19 09:13 +0100
Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking Dimiter_Popoff <dp@tgi-sci.com> - 2015-04-19 13:22 +0300
Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking David Brown <david.brown@hesbynett.no> - 2015-04-19 22:09 +0200
Re: Mecrisp on the TI Stellaris Launchpad mm0fmf <none@mailinator.com> - 2015-04-17 21:15 +0100
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-17 17:02 -0400
Re: Mecrisp on the TI Stellaris Launchpad mm0fmf <none@mailinator.com> - 2015-04-18 17:06 +0100
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-19 16:57 -0400
Re: Mecrisp on the TI Stellaris Launchpad Alan Adams <alan@adamshome.org.uk> - 2015-04-20 09:33 +0100
Re: Mecrisp on the TI Stellaris Launchpad mm0fmf <none@mailinator.com> - 2015-04-20 18:03 +0100
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-21 01:16 -0400
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-17 20:20 -0400
Re: Mecrisp on the TI Stellaris Launchpad Paul Rubin <no.email@nospam.invalid> - 2015-04-17 17:24 -0700
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-17 20:40 -0400
Re: Mecrisp on the TI Stellaris Launchpad Paul Rubin <no.email@nospam.invalid> - 2015-04-17 17:57 -0700
Re: Mecrisp on the TI Stellaris Launchpad Mel Wilson <mwilson@the-wire.com> - 2015-04-18 02:14 +0000
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-18 02:05 -0400
Re: Mecrisp on the TI Stellaris Launchpad David Brown <david.brown@hesbynett.no> - 2015-04-18 10:16 +0200
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-18 09:56 -0400
Re: Mecrisp on the TI Stellaris Launchpad David Brown <david.brown@hesbynett.no> - 2015-04-18 17:46 +0200
USB serial ports, was: Re: Mecrisp on the TI Stellaris Launchpad Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> - 2015-04-18 18:34 +0000
Re: Mecrisp on the TI Stellaris Launchpad David Brown <david.brown@hesbynett.no> - 2015-04-18 10:04 +0200
Re: Mecrisp on the TI Stellaris Launchpad Jan Coombs <Jan-54 <jenfhaomndgfwutc@murmic.plus.com>> - 2015-04-18 09:38 +0100
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-18 11:04 -0400
Re: Mecrisp on the TI Stellaris Launchpad David Brown <david.brown@hesbynett.no> - 2015-04-18 17:54 +0200
Re: Mecrisp on the TI Stellaris Launchpad hal-usenet@ip-64-139-1-69.sjc.megapath.net (Hal Murray) - 2015-04-18 15:36 -0500
Re: Mecrisp on the TI Stellaris Launchpad Theo Markettos <theom+news@chiark.greenend.org.uk> - 2015-04-23 07:59 +0100
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-25 14:35 -0400
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-25 15:44 -0400
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-05-08 12:00 -0400
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-05-10 03:36 -0400
Re: Mecrisp on the TI Stellaris Launchpad Theo Markettos <theom+news@chiark.greenend.org.uk> - 2015-05-10 10:32 +0100
Re: Mecrisp on the TI Stellaris Launchpad Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2015-05-10 12:56 +0300
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-05-10 10:48 -0400
Re: Mecrisp on the TI Stellaris Launchpad The Natural Philosopher <tnp@invalid.invalid> - 2015-05-10 16:05 +0100
Re: Mecrisp on the TI Stellaris Launchpad Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> - 2015-05-10 23:26 +0000
Re: Mecrisp on the TI Stellaris Launchpad Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> - 2015-05-10 09:37 +0000
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-05-10 11:16 -0400
Re: Mecrisp on the TI Stellaris Launchpad Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> - 2015-05-10 23:42 +0000
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-05-11 02:17 -0400
Re: Mecrisp on the TI Stellaris Launchpad albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-05-10 11:41 +0000
Re: Mecrisp on the TI Stellaris Launchpad Theo Markettos <theom+news@chiark.greenend.org.uk> - 2015-05-10 16:56 +0100
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-05-10 13:01 -0400
Re: Mecrisp on the TI Stellaris Launchpad lasselangwadtchristensen@gmail.com - 2015-04-18 12:13 -0700
Re: Mecrisp on the TI Stellaris Launchpad stephen@mpeforth.com (Stephen Pelc) - 2015-04-18 19:22 +0000
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-19 17:04 -0400
Re: Mecrisp on the TI Stellaris Launchpad Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2015-04-20 13:24 +0300
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-22 13:23 -0400
Re: Mecrisp on the TI Stellaris Launchpad Dimiter_Popoff <dp@tgi-sci.com> - 2015-04-22 20:44 +0300
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-22 13:51 -0400
Re: Mecrisp on the TI Stellaris Launchpad Waldek Hebisch <hebisch@math.uni.wroc.pl> - 2015-04-22 19:10 +0000
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-22 15:31 -0400
Re: Mecrisp on the TI Stellaris Launchpad Waldek Hebisch <hebisch@math.uni.wroc.pl> - 2015-04-23 02:08 +0000
Re: Mecrisp on the TI Stellaris Launchpad Waldek Hebisch <hebisch@math.uni.wroc.pl> - 2015-04-24 02:52 +0000
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-25 14:40 -0400
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-25 15:42 -0400
Re: Mecrisp on the TI Stellaris Launchpad sbattazzo@gmail.com - 2015-04-21 09:34 -0700
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-22 14:57 -0400
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-22 15:35 -0400
Re: Mecrisp on the TI Stellaris Launchpad albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-04-17 10:52 +0000
Re: Mecrisp on the TI Stellaris Launchpad Dimiter_Popoff <dp@tgi-sci.com> - 2015-04-17 14:05 +0300
Re: Mecrisp on the TI Stellaris Launchpad Paul Rubin <no.email@nospam.invalid> - 2015-04-17 07:56 -0700
Re: Mecrisp on the TI Stellaris Launchpad David Brown <david.brown@hesbynett.no> - 2015-04-17 17:26 +0200
Re: Mecrisp on the TI Stellaris Launchpad glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-04-17 17:01 +0000
Re: Mecrisp on the TI Stellaris Launchpad Blajrs Jrolrsen <boegre@no.com> - 2015-04-17 13:36 +0000
Re: Mecrisp on the TI Stellaris Launchpad anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-17 14:42 +0000
Re: Mecrisp on the TI Stellaris Launchpad Hans-Bernhard Bröker <HBBroeker@t-online.de> - 2015-04-18 00:25 +0200
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-17 20:03 -0400
Re: Mecrisp on the TI Stellaris Launchpad Paul Rubin <no.email@nospam.invalid> - 2015-04-17 17:14 -0700
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-17 20:26 -0400
Re: Mecrisp on the TI Stellaris Launchpad Paul Rubin <no.email@nospam.invalid> - 2015-04-17 17:32 -0700
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-17 20:47 -0400
Re: Mecrisp on the TI Stellaris Launchpad albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-04-18 08:47 +0000
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-18 11:19 -0400
Re: Mecrisp on the TI Stellaris Launchpad albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-04-18 15:52 +0000
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-19 17:07 -0400
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-06-09 03:04 -0400
Re: Mecrisp on the TI Stellaris Launchpad Robert Wessel <robertwessel2@yahoo.com> - 2015-04-18 00:11 -0500
Re: Mecrisp on the TI Stellaris Launchpad David Brown <david.brown@hesbynett.no> - 2015-04-18 10:32 +0200
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-18 11:26 -0400
Re: Mecrisp on the TI Stellaris Launchpad David Brown <david.brown@hesbynett.no> - 2015-04-18 17:57 +0200
Re: Mecrisp on the TI Stellaris Launchpad Paul Rubin <no.email@nospam.invalid> - 2015-04-18 09:42 -0700
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-19 17:11 -0400
Re: Mecrisp on the TI Stellaris Launchpad Hans-Bernhard Bröker <HBBroeker@t-online.de> - 2015-04-18 12:19 +0200
Re: Mecrisp on the TI Stellaris Launchpad Dimiter_Popoff <dp@tgi-sci.com> - 2015-04-18 15:16 +0300
Re: Mecrisp on the TI Stellaris Launchpad David Brown <david.brown@hesbynett.no> - 2015-04-18 19:57 +0200
Re: Mecrisp on the TI Stellaris Launchpad Dimiter_Popoff <dp@tgi-sci.com> - 2015-04-18 23:11 +0300
Re: Mecrisp on the TI Stellaris Launchpad David Brown <david.brown@hesbynett.no> - 2015-04-19 21:32 +0200
Re: Mecrisp on the TI Stellaris Launchpad Dimiter_Popoff <dp@tgi-sci.com> - 2015-04-19 23:04 +0300
Re: Mecrisp on the TI Stellaris Launchpad anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-18 09:15 +0000
Re: Mecrisp on the TI Stellaris Launchpad David Brown <david.brown@hesbynett.no> - 2015-04-18 12:17 +0200
Re: Mecrisp on the TI Stellaris Launchpad anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-18 13:08 +0000
Re: Mecrisp on the TI Stellaris Launchpad David Brown <david.brown@hesbynett.no> - 2015-04-18 20:17 +0200
Re: Mecrisp on the TI Stellaris Launchpad anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-20 15:33 +0000
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-17 14:52 -0400
Re: Mecrisp on the TI Stellaris Launchpad albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-04-17 20:06 +0000
Re: Mecrisp on the TI Stellaris Launchpad lasselangwadtchristensen@gmail.com - 2015-04-16 16:18 -0700
Page 3 of 7 — ← Prev page 1 2 [3] 4 5 6 7 Next page →
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Date | 2015-04-17 17:57 -0700 |
| Message-ID | <87k2xauubq.fsf@jester.gateway.pace.com> |
| In reply to | #20691 |
rickman <gnuarm@gmail.com> writes: > I'm not familiar with irc. I think I tried it once a long time ago > and didn't get much traction with it. I'm expecting there should be > knowledgeable people in the rPi group. Usenet probably predates the rpi by too much. I'd suggest: download an irc client (xchat.org has a nice one), connect to irc.freenode.net and join the #raspberrypi channel. There are also some web based clients but I've always found them annoying to use.
[toc] | [prev] | [next] | [standalone]
| From | Mel Wilson <mwilson@the-wire.com> |
|---|---|
| Date | 2015-04-18 02:14 +0000 |
| Message-ID | <mgsemm$ans$1@dont-email.me> |
| In reply to | #20687 |
On Fri, 17 Apr 2015 20:20:30 -0400, rickman wrote: [ ... ] > Even once I get a terminal emulator running, I'm not sure how to find > the ID of the device I'll be talking to with it. It is a TI launchpad > with a USB emulated UART. These things are like falling off a rock in > the PC world... mainly because I've come up the learning curve and know > it. Will miniterm have the smarts to find the one serial port on the > machine or do I have to figure out the ID of this USB serial port and > tell it? What do you mean by USB emulated UART? When I plug one of my Sparkfun FTDI boards into a Pi, it shows up to lsusb as "0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC" and gets assigned to /dev/ttyUSB0. A different device, Arduino based, announces itself as "2341:0010 Arduino SA Mega 2560 (CDC ACM)" and gets assigned as /dev/ttyACM0. This is on a stock Raspbian distribution. The difference between the two is apparently that the FTDI emulates a UART, whereas the Arduino emulates a modem, and that's somehow recognized when they're establishing the USB connection. If the Launchpad is supporting serial/USB on its own, as the Arduino is doing, I'd suspect it's following one of these two regimes, but it's up to udev rules in the Raspbian configuration to know this, probably from the manufacturer and device codes. Hope this helps -- it's the limit of what I know.
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2015-04-18 02:05 -0400 |
| Message-ID | <mgss54$jhk$1@dont-email.me> |
| In reply to | #20694 |
On 4/17/2015 10:14 PM, Mel Wilson wrote: > On Fri, 17 Apr 2015 20:20:30 -0400, rickman wrote: > [ ... ] >> Even once I get a terminal emulator running, I'm not sure how to find >> the ID of the device I'll be talking to with it. It is a TI launchpad >> with a USB emulated UART. These things are like falling off a rock in >> the PC world... mainly because I've come up the learning curve and know >> it. Will miniterm have the smarts to find the one serial port on the >> machine or do I have to figure out the ID of this USB serial port and >> tell it? > > What do you mean by USB emulated UART? What do you call a UART on a USB port? These things are MCUs with a USB on one side and a UART on the hardware side. The software on the PC makes them look like a UART to the PC, but the PC is really talking over USB. > When I plug one of my Sparkfun > FTDI boards into a Pi, it shows up to lsusb as "0403:6001 Future > Technology Devices International, Ltd FT232 USB-Serial (UART) IC" and > gets assigned to /dev/ttyUSB0. The question is how do you know that? As I have said, I know how to do this stuff under Windows, but not under Linux. I've also posted that when I do an ls /dev/tty* I get a list of tty, tty0 through tty63, ttyAMA0 and ttyprintk. This list does not change when I plug the device in or unplug it. I also spent some time plugging in a number of USB UARTs and none of them showed up any differently this way. I did find one that crashes the rPi as soon as I plug it in. I expect this is part of the power issues the rPi has. > A different device, Arduino based, announces itself as "2341:0010 Arduino > SA Mega 2560 (CDC ACM)" and gets assigned as /dev/ttyACM0. This is on a > stock Raspbian distribution. What do you mean, "announces itself"? Where do you see that? > The difference between the two is apparently that the FTDI emulates a > UART, whereas the Arduino emulates a modem, and that's somehow recognized > when they're establishing the USB connection. I'm not totally clear on the difference. A modem is connected to the PC via a UART. To talk to a modem the software talks through the UART. I suppose there is the AT command protocol that is used to control the modem which has nothing to do with the UART. I guess the modem is like another layer on top of the UART although that assumes a smart modem as opposed to a dumb modem which just transmits the data it sees one bit at a time. > If the Launchpad is supporting serial/USB on its own, as the Arduino is > doing, I'd suspect it's following one of these two regimes, but it's up > to udev rules in the Raspbian configuration to know this, probably from > the manufacturer and device codes. Hope this helps -- it's the limit of > what I know. Thanks for the effort, but no, this has not helped. I understand modems and UARTs probably more than most people. I don't know much about Linux and I don't see anything here that explains that. I'm a complete noob at Linux, not computers. -- Rick
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2015-04-18 10:16 +0200 |
| Message-ID | <mgt3q7$9mt$1@dont-email.me> |
| In reply to | #20696 |
On 18/04/15 08:05, rickman wrote:
> On 4/17/2015 10:14 PM, Mel Wilson wrote:
>> On Fri, 17 Apr 2015 20:20:30 -0400, rickman wrote:
>> [ ... ]
>>> Even once I get a terminal emulator running, I'm not sure how to find
>>> the ID of the device I'll be talking to with it. It is a TI launchpad
>>> with a USB emulated UART. These things are like falling off a rock in
>>> the PC world... mainly because I've come up the learning curve and know
>>> it. Will miniterm have the smarts to find the one serial port on the
>>> machine or do I have to figure out the ID of this USB serial port and
>>> tell it?
>>
>> What do you mean by USB emulated UART?
>
> What do you call a UART on a USB port? These things are MCUs with a USB
> on one side and a UART on the hardware side. The software on the PC
> makes them look like a UART to the PC, but the PC is really talking over
> USB.
>
>
>> When I plug one of my Sparkfun
>> FTDI boards into a Pi, it shows up to lsusb as "0403:6001 Future
>> Technology Devices International, Ltd FT232 USB-Serial (UART) IC" and
>> gets assigned to /dev/ttyUSB0.
>
> The question is how do you know that? As I have said, I know how to do
> this stuff under Windows, but not under Linux.
>
> I've also posted that when I do an ls /dev/tty* I get a list of tty,
> tty0 through tty63, ttyAMA0 and ttyprintk. This list does not change
> when I plug the device in or unplug it. I also spent some time plugging
> in a number of USB UARTs and none of them showed up any differently this
> way. I did find one that crashes the rPi as soon as I plug it in. I
> expect this is part of the power issues the rPi has.
>
Once you have figured out what devices you are plugging in, and where
("lsusb" and "lsusb -v" are very handy), udev rules are your friend for
making it all consistent and easy to use.
This is from my "52-david.rules" file in /etc/udev/rules.d on my
development PC (the rules files are read in order, so the "52" is about
the middle) :
KERNEL=="ttyUSB*", DEVPATH=="*/usb2/2-1/2-1.1/2-1.1:1.0/*", SYMLINK +=
"ttySerial_hub1"
KERNEL=="ttyUSB*", DEVPATH=="*/usb2/2-1/2-1.2/2-1.2:1.0/*", SYMLINK +=
"ttySerial_hub2"
KERNEL=="ttyUSB*", DEVPATH=="*/usb2/2-1/2-1.3/2-1.3:1.0/*", SYMLINK +=
"ttySerial_hub3"
KERNEL=="ttyUSB*", DEVPATH=="*/usb2/2-1/2-1.4/2-1.4:1.0/*", SYMLINK +=
"ttySerial_hub4"
KERNEL == "ttyUSB*", ATTRS{idVendor} == "0403", ATTRS{idProduct} ==
"6001", \
ATTRS{serial} == "FTFLYG0L", SYMLINK += "ttySerial_ttl1"
ATTR{idVendor}=="0403", ATTR{idProduct}=="6001", \
ATTR{serial}=="FTUSV1RA", SYMLINK += "ttySerial_232"
The key points here are to give a list of identification checks (like
the ttyUSB kernel driver, used for FTDI devices, or the physical path
through hubs, or the serial numbers, vendor IDs, etc., of the device),
and then a list of commands. Typical commands change the permissions
(to make particular devices available to particular users), and SYMLINK
to make new symbolic links.
So with this setup, I have a four-port hub that I use to connect FTDI
serial ports - TTL, RS232, RS485, etc. When I connect then, the first
connected gets /dev/ttyUSB0, then the next gets /dev/ttyUSB1, etc.
Unlike Windows, the numbers are not tracked by serial number of the
device - this means the same devices entered in different orders get
different numbers. On the other hand, you don't end up with numbers
like COMM123 ...
With the udev rule above, the devices get additional names when plugged
into particular ports on the hub. This means that I always know exactly
which device is which, using those symbolic names. It doesn't matter if
/dev/ttySerial_hub2 points to /dev/ttyUSB0 - I know which port it is
attached to.
Another quick point - if you are working with serial ports, and you like
Python, don't forget that pyserial is your friend :-)
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2015-04-18 09:56 -0400 |
| Message-ID | <mgtno4$c77$1@dont-email.me> |
| In reply to | #20699 |
On 4/18/2015 4:16 AM, David Brown wrote:
>
> Once you have figured out what devices you are plugging in, and where
> ("lsusb" and "lsusb -v" are very handy), udev rules are your friend for
> making it all consistent and easy to use.
Ok, lsusb is helping. If I plug into the "device" port on the launchpad
*nothing* shows up. If I plug into the "debug" port it shows up as
dev1.7. This is on the same port that was showing a mouse as dev1.6.
But this is a start. I guess I was using the wrong port on the launchpad.
> This is from my "52-david.rules" file in /etc/udev/rules.d on my
> development PC (the rules files are read in order, so the "52" is about
> the middle) :
>
>
>
> KERNEL=="ttyUSB*", DEVPATH=="*/usb2/2-1/2-1.1/2-1.1:1.0/*", SYMLINK +=
> "ttySerial_hub1"
> KERNEL=="ttyUSB*", DEVPATH=="*/usb2/2-1/2-1.2/2-1.2:1.0/*", SYMLINK +=
> "ttySerial_hub2"
> KERNEL=="ttyUSB*", DEVPATH=="*/usb2/2-1/2-1.3/2-1.3:1.0/*", SYMLINK +=
> "ttySerial_hub3"
> KERNEL=="ttyUSB*", DEVPATH=="*/usb2/2-1/2-1.4/2-1.4:1.0/*", SYMLINK +=
> "ttySerial_hub4"
>
> KERNEL == "ttyUSB*", ATTRS{idVendor} == "0403", ATTRS{idProduct} ==
> "6001", \
> ATTRS{serial} == "FTFLYG0L", SYMLINK += "ttySerial_ttl1"
>
> ATTR{idVendor}=="0403", ATTR{idProduct}=="6001", \
> ATTR{serial}=="FTUSV1RA", SYMLINK += "ttySerial_232"
>
>
> The key points here are to give a list of identification checks (like
> the ttyUSB kernel driver, used for FTDI devices, or the physical path
> through hubs, or the serial numbers, vendor IDs, etc., of the device),
> and then a list of commands. Typical commands change the permissions
> (to make particular devices available to particular users), and SYMLINK
> to make new symbolic links.
I appreciate the help, but I don't understand much of this. Like I've
said, I'm a complete noob at Linux. Do I need to do any of this? There
is only one user, "raspberry".
> So with this setup, I have a four-port hub that I use to connect FTDI
> serial ports - TTL, RS232, RS485, etc. When I connect then, the first
> connected gets /dev/ttyUSB0, then the next gets /dev/ttyUSB1, etc.
> Unlike Windows, the numbers are not tracked by serial number of the
> device - this means the same devices entered in different orders get
> different numbers. On the other hand, you don't end up with numbers
> like COMM123 ...
>
> With the udev rule above, the devices get additional names when plugged
> into particular ports on the hub. This means that I always know exactly
> which device is which, using those symbolic names. It doesn't matter if
> /dev/ttySerial_hub2 points to /dev/ttyUSB0 - I know which port it is
> attached to.
But only if the devices are connected in the same order each time. I
noticed that when the mouse is plugged in it was port 1.6. When I
unplug it and use that port for the launchpad it becomes port 1.7. Is
that expected?
> Another quick point - if you are working with serial ports, and you like
> Python, don't forget that pyserial is your friend :-)
It may be my friend, but I can't figure out how to run it... Is that
what friends are about, hard to understand? I also can't figure out how
to run miniterm. Google searches... or more accurately a duckduckgo
search on miniterm I get all manner of links to pyserial and few, if
any, to miniterm. The noob factor is at work. I can download what
seems to be pyserial, but I can't figure out how to run it as an
application.
--
Rick
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2015-04-18 17:46 +0200 |
| Message-ID | <mgtu7k$577$1@dont-email.me> |
| In reply to | #20710 |
On 18/04/15 15:56, rickman wrote:
> On 4/18/2015 4:16 AM, David Brown wrote:
>>
>> Once you have figured out what devices you are plugging in, and where
>> ("lsusb" and "lsusb -v" are very handy), udev rules are your friend for
>> making it all consistent and easy to use.
>
> Ok, lsusb is helping. If I plug into the "device" port on the launchpad
> *nothing* shows up. If I plug into the "debug" port it shows up as
> dev1.7. This is on the same port that was showing a mouse as dev1.6.
> But this is a start. I guess I was using the wrong port on the launchpad.
>
>
>> This is from my "52-david.rules" file in /etc/udev/rules.d on my
>> development PC (the rules files are read in order, so the "52" is about
>> the middle) :
>>
>>
>>
>> KERNEL=="ttyUSB*", DEVPATH=="*/usb2/2-1/2-1.1/2-1.1:1.0/*", SYMLINK +=
>> "ttySerial_hub1"
>> KERNEL=="ttyUSB*", DEVPATH=="*/usb2/2-1/2-1.2/2-1.2:1.0/*", SYMLINK +=
>> "ttySerial_hub2"
>> KERNEL=="ttyUSB*", DEVPATH=="*/usb2/2-1/2-1.3/2-1.3:1.0/*", SYMLINK +=
>> "ttySerial_hub3"
>> KERNEL=="ttyUSB*", DEVPATH=="*/usb2/2-1/2-1.4/2-1.4:1.0/*", SYMLINK +=
>> "ttySerial_hub4"
>>
>> KERNEL == "ttyUSB*", ATTRS{idVendor} == "0403", ATTRS{idProduct} ==
>> "6001", \
>> ATTRS{serial} == "FTFLYG0L", SYMLINK += "ttySerial_ttl1"
>>
>> ATTR{idVendor}=="0403", ATTR{idProduct}=="6001", \
>> ATTR{serial}=="FTUSV1RA", SYMLINK += "ttySerial_232"
>>
>>
>> The key points here are to give a list of identification checks (like
>> the ttyUSB kernel driver, used for FTDI devices, or the physical path
>> through hubs, or the serial numbers, vendor IDs, etc., of the device),
>> and then a list of commands. Typical commands change the permissions
>> (to make particular devices available to particular users), and SYMLINK
>> to make new symbolic links.
>
> I appreciate the help, but I don't understand much of this. Like I've
> said, I'm a complete noob at Linux. Do I need to do any of this? There
> is only one user, "raspberry".
No, you certainly don't /need/ any of it. But it can sometimes make
life a little easier. If you only use one user, and have made sure that
it is in the right groups (typically "dialout" and/or "plugdev" -
details vary from distro to distro), then you will have full access to
the USB serial devices. If you have problems, you can also access the
port as "root". (Some people will call such advice blasphemy, but
sometimes it is simply easier to do things as root.)
Other than that, keep a note of this post. If you want to use more
devices in the future and get consistent names, then it will give you
clues - especially when combined with a google search for udev rules.
(Of course, you could also post again here.) Even if you don't need
these things now, it might be useful to know about them in the future.
>
>
>> So with this setup, I have a four-port hub that I use to connect FTDI
>> serial ports - TTL, RS232, RS485, etc. When I connect then, the first
>> connected gets /dev/ttyUSB0, then the next gets /dev/ttyUSB1, etc.
>> Unlike Windows, the numbers are not tracked by serial number of the
>> device - this means the same devices entered in different orders get
>> different numbers. On the other hand, you don't end up with numbers
>> like COMM123 ...
>>
>> With the udev rule above, the devices get additional names when plugged
>> into particular ports on the hub. This means that I always know exactly
>> which device is which, using those symbolic names. It doesn't matter if
>> /dev/ttySerial_hub2 points to /dev/ttyUSB0 - I know which port it is
>> attached to.
>
> But only if the devices are connected in the same order each time. I
> noticed that when the mouse is plugged in it was port 1.6. When I
> unplug it and use that port for the launchpad it becomes port 1.7. Is
> that expected?
Yes - some of the number in USB devices simply increments each time a
device is attached. The DEVPATH I used in the rules above does not act
like that - it is a tree based on the physical path through hubs, and is
thus completely independent of the ordering.
>
>
>> Another quick point - if you are working with serial ports, and you like
>> Python, don't forget that pyserial is your friend :-)
>
> It may be my friend, but I can't figure out how to run it... Is that
> what friends are about, hard to understand? I also can't figure out how
> to run miniterm. Google searches... or more accurately a duckduckgo
> search on miniterm I get all manner of links to pyserial and few, if
> any, to miniterm. The noob factor is at work. I can download what
> seems to be pyserial, but I can't figure out how to run it as an
> application.
>
pyserial is not an application - it is a library for Python. If you
have experience with Python programming (or /want/ experience with
Python programming - it's a nice high-level language, fully
cross-platform), then you should find pyserial quite easy to use. You
can try it on Windows first for familiarity - it works there too.
But if you haven't used Python, then pyserial is not your friend for now!
As I noted elsewhere, try "screen" rather than miniterm - "screen
/dev/ttyUSB0 115200" gets you connected at 115200 baud. Obviously
change the /dev/ttyUSB0 as needed.
[toc] | [prev] | [next] | [standalone]
| From | Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> |
|---|---|
| Date | 2015-04-18 18:34 +0000 |
| Subject | USB serial ports, was: Re: Mecrisp on the TI Stellaris Launchpad |
| Message-ID | <mgu844$dm6$1@dont-email.me> |
| In reply to | #20694 |
On 2015-04-17, Mel Wilson <mwilson@the-wire.com> wrote: > On Fri, 17 Apr 2015 20:20:30 -0400, rickman wrote: > [ ... ] >> Even once I get a terminal emulator running, I'm not sure how to find >> the ID of the device I'll be talking to with it. It is a TI launchpad >> with a USB emulated UART. These things are like falling off a rock in >> the PC world... mainly because I've come up the learning curve and know >> it. Will miniterm have the smarts to find the one serial port on the >> machine or do I have to figure out the ID of this USB serial port and >> tell it? > > What do you mean by USB emulated UART? When I plug one of my Sparkfun > FTDI boards into a Pi, it shows up to lsusb as "0403:6001 Future > Technology Devices International, Ltd FT232 USB-Serial (UART) IC" and > gets assigned to /dev/ttyUSB0. > A different device, Arduino based, announces itself as "2341:0010 Arduino > SA Mega 2560 (CDC ACM)" and gets assigned as /dev/ttyACM0. This is on a > stock Raspbian distribution. > The difference between the two is apparently that the FTDI emulates a > UART, whereas the Arduino emulates a modem, and that's somehow recognized > when they're establishing the USB connection. To expand on that: There's a standard for accessing serial ports on the USB specifications which is the CDC ACM specification. This is fully open and documented and many implementations exist (I did a simple version myself as a learning exercise a few years ago). However, as you say, it's targetted towards modems in it's model of operation although serial ports work just fine with it. However, the hardware flow control signals don't get directly passed through to the host (there's no direct handling of CTS for example). The way people like Microchip appear to handle this (in devices like the MCP2200) is to handle the flow control on the device itself. FTDI (and Prolific (PL-2303)) have their own closed USB protocol specifications for their own devices. These specifications are not available without signing an NDA (I know; in the case of FTDI I actually asked them about this). There are however drivers for these manufacturers in the Linux kernel and (as you have discovered) they show up in a different way to the standards compliant CDC ACM devices. As for how Linux knows the difference, the different types of USB serial ports are encoded differently in the configuration descriptors on the device (with the CDC ACM devices using configuration values assigned by the USB standards). Simon. -- Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP Microsoft: Bringing you 1980s technology to a 21st century world
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2015-04-18 10:04 +0200 |
| Message-ID | <mgt34l$7l2$1@dont-email.me> |
| In reply to | #20687 |
On 18/04/15 02:20, rickman wrote: > Now I am a bit stuck trying to get a serial port terminal emulation > running. It would appear that miniterm is the right program to use, but > while dealing with the slowness of the rPi when web browsing I have yet > to find it exactly. I thought I had found it at a site called Py > Serial. But I think what I downloaded with some sort of python wrapper > for miniterm. I'm not sure really. If you are running from X, then there are a few terminal editor programs (including putty, which might be familiar to you from windows). From the command line, I prefer to use "screen" for serial ports. I use "screen" at lot for other purposes (if you don't know it, look it up on google - it's very useful for getting lots of cli windows, but this is not the place for covering details). screen /dev/ttyUSB0 115200 > > Even once I get a terminal emulator running, I'm not sure how to find > the ID of the device I'll be talking to with it. It is a TI launchpad > with a USB emulated UART. These things are like falling off a rock in > the PC world... mainly because I've come up the learning curve and know > it. Will miniterm have the smarts to find the one serial port on the > machine or do I have to figure out the ID of this USB serial port and > tell it? >
[toc] | [prev] | [next] | [standalone]
| From | Jan Coombs <Jan-54 <jenfhaomndgfwutc@murmic.plus.com>> |
|---|---|
| Date | 2015-04-18 09:38 +0100 |
| Message-ID | <20150418093835.7ddd5a76@T60A> |
| In reply to | #20687 |
On Fri, 17 Apr 2015 20:20:30 -0400 rickman <gnuarm@gmail.com> wrote: > Now I am a bit stuck trying to get a serial port terminal emulation > running. It would appear that miniterm is the right program to use, but > while dealing with the slowness of the rPi when web browsing I have yet > to find it exactly. I thought I had found it at a site called Py > Serial. But I think what I downloaded with some sort of python wrapper > for miniterm. I'm not sure really. gtkterm is simple and capable, but can't find rPi to check this :( To install, type at terminal: sudo apt-get install gtkterm > Even once I get a terminal emulator running, I'm not sure how to find > the ID of the device I'll be talking to with it. It is a TI launchpad > with a USB emulated UART. These things are like falling off a rock in > the PC world... mainly because I've come up the learning curve and know > it. Will miniterm have the smarts to find the one serial port on the > machine or do I have to figure out the ID of this USB serial port and > tell it? In a terminal type: dmesg | tail and you will see the end of the system log. If you just plugged the USB, then you should see something like: "FTDI USB Serial Device converter now attached to ttyUSB1" For the above, the com port name/location is /dev/ttyUSB1 To access the comm ports as a regular user you might need to join the dialout group. To check current status type: groups To add user "rick" to dialout group, type at prompt either of these: (your user name might be "pi") sudo usermod -a -G dialout rick sudo adduser rick dialout Checked this on my desktop, so maybe not quite so. The rPi will run a number of linux systems, so if you have further problems say which version of linux it is running. uname -a I recently connected the little MSP430 launchpad board at work, and struggled. I could re-check this on Monday. Jan Coombs -- http://askubuntu.com/questions/112568/how-do-i-allow-a-non-default-user-to-use-serial-device-ttyusb0 email valid, else fix dots and hyphen jan4clf2014@murrayhyphenmicroftdotcodotuk
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2015-04-18 11:04 -0400 |
| Message-ID | <mgtro8$reh$1@dont-email.me> |
| In reply to | #20701 |
On 4/18/2015 4:38 AM, Jan Coombs <Jan-54 wrote: > On Fri, 17 Apr 2015 20:20:30 -0400 > rickman <gnuarm@gmail.com> wrote: > >> Now I am a bit stuck trying to get a serial port terminal emulation >> running. It would appear that miniterm is the right program to use, but >> while dealing with the slowness of the rPi when web browsing I have yet >> to find it exactly. I thought I had found it at a site called Py >> Serial. But I think what I downloaded with some sort of python wrapper >> for miniterm. I'm not sure really. > > gtkterm is simple and capable, but can't find rPi to check > this :( To install, type at terminal: > > sudo apt-get install gtkterm Sounded good, but didn't work. I am familiar with the "sudo apt-get install" thing. I think that was the first thing I learned a few weeks ago (or was it months?) when I first powered up the rPi. This time it says "Unable to locate package gtkterm". It would be so much easier if I could access newsgroups on the rPi. Oh well... >> Even once I get a terminal emulator running, I'm not sure how to find >> the ID of the device I'll be talking to with it. It is a TI launchpad >> with a USB emulated UART. These things are like falling off a rock in >> the PC world... mainly because I've come up the learning curve and know >> it. Will miniterm have the smarts to find the one serial port on the >> machine or do I have to figure out the ID of this USB serial port and >> tell it? > > In a terminal type: > > dmesg | tail > > and you will see the end of the system log. If you just > plugged the USB, then you should see something like: > > "FTDI USB Serial Device converter now attached to ttyUSB1" > > For the above, the com port name/location is /dev/ttyUSB1 Yeah, I've already figured out I was using the wrong port on the launchpad for the UART. Seems it is the same port as the debugger. So now I can see it. I have to switch it out with the mouse and every time the USB number increments. The mouse is now on port 1.8 lol. > To access the comm ports as a regular user you might need > to join the dialout group. To check current status type: > > groups > > To add user "rick" to dialout group, type at prompt either > of these: (your user name might be "pi") > > sudo usermod -a -G dialout rick > sudo adduser rick dialout Now I just need to figure out my user name. I haven't logged into this thing in months. I believe the default is raspberry. > Checked this on my desktop, so maybe not quite so. The > rPi will run a number of linux systems, so if you have > further problems say which version of linux it is running. > > uname -a > > I recently connected the little MSP430 launchpad board at > work, and struggled. I could re-check this on Monday. I'm running Raspbian. I think I have all the pieces now except a terminal emulator. When reading about miniterm it says it lets the command window handle ANSI code formatting and that window is called "terminal". I'm wondering if I need a terminal emulator at all. I guess the "terminal emulator" reroutes the keystrokes to the serial port output and the serial port input to the display. There would be no way to do that with pipes or such. That would allow me to control the command window from the serial port perhaps which is not what I need. -- Rick
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2015-04-18 17:54 +0200 |
| Message-ID | <mgtuli$6lh$1@dont-email.me> |
| In reply to | #20711 |
On 18/04/15 17:04, rickman wrote:
> On 4/18/2015 4:38 AM, Jan Coombs <Jan-54 wrote:
>> On Fri, 17 Apr 2015 20:20:30 -0400
>> rickman <gnuarm@gmail.com> wrote:
>>
>>> Now I am a bit stuck trying to get a serial port terminal emulation
>>> running. It would appear that miniterm is the right program to use, but
>>> while dealing with the slowness of the rPi when web browsing I have yet
>>> to find it exactly. I thought I had found it at a site called Py
>>> Serial. But I think what I downloaded with some sort of python wrapper
>>> for miniterm. I'm not sure really.
>>
>> gtkterm is simple and capable, but can't find rPi to check
>> this :( To install, type at terminal:
>>
>> sudo apt-get install gtkterm
>
> Sounded good, but didn't work. I am familiar with the "sudo apt-get
> install" thing. I think that was the first thing I learned a few weeks
> ago (or was it months?) when I first powered up the rPi. This time it
> says "Unable to locate package gtkterm".
Personally, I like to save a bit of "sudo" by doing "sudo su -" first,
to get a root login, and then just typing commands without the sudo stuff.
Make sure you have updated your repository lists ("apt-get update").
Then try a search ("apt-cache search gtkterm") - maybe it has a slightly
different name on your distro.
>
> It would be so much easier if I could access newsgroups on the rPi. Oh
> well...
>
>
>>> Even once I get a terminal emulator running, I'm not sure how to find
>>> the ID of the device I'll be talking to with it. It is a TI launchpad
>>> with a USB emulated UART. These things are like falling off a rock in
>>> the PC world... mainly because I've come up the learning curve and know
>>> it. Will miniterm have the smarts to find the one serial port on the
>>> machine or do I have to figure out the ID of this USB serial port and
>>> tell it?
>>
>> In a terminal type:
>>
>> dmesg | tail
>>
>> and you will see the end of the system log. If you just
>> plugged the USB, then you should see something like:
>>
>> "FTDI USB Serial Device converter now attached to ttyUSB1"
>>
>> For the above, the com port name/location is /dev/ttyUSB1
>
> Yeah, I've already figured out I was using the wrong port on the
> launchpad for the UART. Seems it is the same port as the debugger. So
> now I can see it.
>
> I have to switch it out with the mouse and every time the USB number
> increments. The mouse is now on port 1.8 lol.
Yes, but that number doesn't matter much - don't worry about it.
>
>
>> To access the comm ports as a regular user you might need
>> to join the dialout group. To check current status type:
>>
>> groups
>>
>> To add user "rick" to dialout group, type at prompt either
>> of these: (your user name might be "pi")
>>
>> sudo usermod -a -G dialout rick
>> sudo adduser rick dialout
>
> Now I just need to figure out my user name. I haven't logged into this
> thing in months. I believe the default is raspberry.
Use "whoami" to confirm that.
Also use "ls -l /dev/ttyUSB*" to confirm that the group you want is
"dialout" - distros vary on the details.
Note that you need to log out, then log in again, in order for the new
group membership to take effect.
>
>
>> Checked this on my desktop, so maybe not quite so. The
>> rPi will run a number of linux systems, so if you have
>> further problems say which version of linux it is running.
>>
>> uname -a
>>
>> I recently connected the little MSP430 launchpad board at
>> work, and struggled. I could re-check this on Monday.
>
> I'm running Raspbian. I think I have all the pieces now except a
> terminal emulator. When reading about miniterm it says it lets the
> command window handle ANSI code formatting and that window is called
> "terminal". I'm wondering if I need a terminal emulator at all. I
> guess the "terminal emulator" reroutes the keystrokes to the serial port
> output and the serial port input to the display. There would be no way
> to do that with pipes or such. That would allow me to control the
> command window from the serial port perhaps which is not what I need.
>
[toc] | [prev] | [next] | [standalone]
| From | hal-usenet@ip-64-139-1-69.sjc.megapath.net (Hal Murray) |
|---|---|
| Date | 2015-04-18 15:36 -0500 |
| Message-ID | <CfudnQaBSdLRXa_InZ2dnUU7-V-dnZ2d@megapath.net> |
| In reply to | #20711 |
In article <mgtro8$reh$1@dont-email.me>, rickman <gnuarm@gmail.com> writes: > Now I just need to figure out my user name. I haven't logged into this > thing in months. I believe the default is raspberry. What I do for things like that is keep a small text file with all the details I need. Often it's a command line that I can cut-paste when setting up a copy of the system. (or putting the system back together) You don't need the whole story, just enough to trigger your memory, or contain the magic phrase that will let man or google find it for you. If google finds multiple pages, I often save the URL with the one that had the answer I liked best. -- These are my opinions. I hate spam.
[toc] | [prev] | [next] | [standalone]
| From | Theo Markettos <theom+news@chiark.greenend.org.uk> |
|---|---|
| Date | 2015-04-23 07:59 +0100 |
| Message-ID | <kAD*vyItv@news.chiark.greenend.org.uk> |
| In reply to | #20711 |
In comp.sys.raspberry-pi rickman <gnuarm@gmail.com> wrote: > On 4/18/2015 4:38 AM, Jan Coombs <Jan-54 wrote: > > On Fri, 17 Apr 2015 20:20:30 -0400 > > rickman <gnuarm@gmail.com> wrote: > > > >> Now I am a bit stuck trying to get a serial port terminal emulation > >> running. It would appear that miniterm is the right program to use, but > >> while dealing with the slowness of the rPi when web browsing I have yet > >> to find it exactly. I thought I had found it at a site called Py > >> Serial. But I think what I downloaded with some sort of python wrapper > >> for miniterm. I'm not sure really. > > > > gtkterm is simple and capable, but can't find rPi to check > > this :( To install, type at terminal: > > > > sudo apt-get install gtkterm > > Sounded good, but didn't work. I am familiar with the "sudo apt-get > install" thing. I think that was the first thing I learned a few weeks > ago (or was it months?) when I first powered up the rPi. This time it > says "Unable to locate package gtkterm". I don't know gtkterm, but the 'canonical' package people often talk about is minicom (not miniterm as you mentioned). However it has an annoying 'curses' (DOS-style) GUI - I prefer picocom because it doesn't have menus on obscure keypresses to configure it, you just tell it the serial device on the command line and away you go: picocom -b 115200 /dev/ttyUSB0 > It would be so much easier if I could access newsgroups on the rPi. Oh > well... So do that then ;-) sudo apt-get install tin NNTPSERVER=nntp.aioe.org tin -r then hit shift-S and type the name of a newsgroup you want to subscribe to. Navigate with the arrow keys. You can of course set it up with your newsserver and name etc (look in ~/.tin/), but the above should work directly. 'Other newsreaders are available', as they say. > Now I just need to figure out my user name. I haven't logged into this > thing in months. I believe the default is raspberry. The default username is 'pi' and the password 'raspberry'. > I'm running Raspbian. I think I have all the pieces now except a > terminal emulator. When reading about miniterm it says it lets the > command window handle ANSI code formatting and that window is called > "terminal". I'm wondering if I need a terminal emulator at all. I > guess the "terminal emulator" reroutes the keystrokes to the serial port > output and the serial port input to the display. There would be no way > to do that with pipes or such. That would allow me to control the > command window from the serial port perhaps which is not what I need. You don't need a terminal emulator as such - the window that displays your session is already a terminal emulator. If it's on the Pi display then that could be a program like xterm or gnome-terminal, if you're using SSH then it could be a Windows program like PuTTY. That provides the terminal-to-pixels conversion, and then all you need to do is ensure that character stream that reaches it is in the right format. Typically this is done by propagating a TERM environment variable around (which SSH will do for you but picocom won't), for example TERM=vt100, so as long as whatever is outputting text know it's aiming for a vt100 it'll generate the right characters for PuTTY or whatever, even if they pass through three machines on the way. Anyway, for simple stuff you probably don't need to tell your heating controller or whatever to output vt100 codes - ASCII works just fine, the terminal settings only matter for things like cursor movement and graphics. So all you need is a program to display the traffic on the serial port - picocom or minicom will do, but they aren't 'terminal emulators' as such. Theo
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2015-04-25 14:35 -0400 |
| Message-ID | <mhgmo3$7lr$1@dont-email.me> |
| In reply to | #20785 |
On 4/23/2015 2:59 AM, Theo Markettos wrote: > In comp.sys.raspberry-pi rickman <gnuarm@gmail.com> wrote: >> On 4/18/2015 4:38 AM, Jan Coombs <Jan-54 wrote: >>> On Fri, 17 Apr 2015 20:20:30 -0400 >>> rickman <gnuarm@gmail.com> wrote: >>> >>>> Now I am a bit stuck trying to get a serial port terminal emulation >>>> running. It would appear that miniterm is the right program to use, but >>>> while dealing with the slowness of the rPi when web browsing I have yet >>>> to find it exactly. I thought I had found it at a site called Py >>>> Serial. But I think what I downloaded with some sort of python wrapper >>>> for miniterm. I'm not sure really. >>> >>> gtkterm is simple and capable, but can't find rPi to check >>> this :( To install, type at terminal: >>> >>> sudo apt-get install gtkterm >> >> Sounded good, but didn't work. I am familiar with the "sudo apt-get >> install" thing. I think that was the first thing I learned a few weeks >> ago (or was it months?) when I first powered up the rPi. This time it >> says "Unable to locate package gtkterm". > > I don't know gtkterm, but the 'canonical' package people often talk about is > minicom (not miniterm as you mentioned). However it has an annoying > 'curses' (DOS-style) GUI - I prefer picocom because it doesn't have menus on > obscure keypresses to configure it, you just tell it the > serial device on the command line and away you go: > picocom -b 115200 /dev/ttyUSB0 > >> It would be so much easier if I could access newsgroups on the rPi. Oh >> well... > > So do that then ;-) > > sudo apt-get install tin > NNTPSERVER=nntp.aioe.org tin -r > > then hit shift-S and type the name of a newsgroup you want to subscribe to. > Navigate with the arrow keys. You can of course set it up with your > newsserver and name etc (look in ~/.tin/), but the above should work > directly. > > 'Other newsreaders are available', as they say. > >> Now I just need to figure out my user name. I haven't logged into this >> thing in months. I believe the default is raspberry. > > The default username is 'pi' and the password 'raspberry'. > >> I'm running Raspbian. I think I have all the pieces now except a >> terminal emulator. When reading about miniterm it says it lets the >> command window handle ANSI code formatting and that window is called >> "terminal". I'm wondering if I need a terminal emulator at all. I >> guess the "terminal emulator" reroutes the keystrokes to the serial port >> output and the serial port input to the display. There would be no way >> to do that with pipes or such. That would allow me to control the >> command window from the serial port perhaps which is not what I need. > > You don't need a terminal emulator as such - the window that displays your > session is already a terminal emulator. If it's on the Pi display then that > could be a program like xterm or gnome-terminal, if you're using SSH then it > could be a Windows program like PuTTY. That provides the terminal-to-pixels > conversion, and then all you need to do is ensure that character stream that > reaches it is in the right format. Typically this is done by propagating a > TERM environment variable around (which SSH will do for you but picocom > won't), for example TERM=vt100, so as long as whatever is outputting text > know it's aiming for a vt100 it'll generate the right characters for PuTTY > or whatever, even if they pass through three machines on the way. > > Anyway, for simple stuff you probably don't need to tell your heating > controller or whatever to output vt100 codes - ASCII works just fine, the > terminal settings only matter for things like cursor movement and graphics. > > So all you need is a program to display the traffic on the serial port - > picocom or minicom will do, but they aren't 'terminal emulators' as such. I got minicom up (I was calling it miniterm, lol) but it doesn't seem to have a setting for translating LF to CR/LF. The Mecrisp app on the launchpad only sends LF. I also tried setting the "implicit CR on LF" option in Putty which doesn't do the trick either. Just to recap, I have the rPi running headless with the command line on the PC through SSH using Putty. The launchpad running Mecrisp is ttyACM0 on the rPi. Through the Putty session I am running minicom to the launchpad. Mecrisp seems to return "ok.<LF>" which marches across the Putty window until it wraps at the right margin. Any suggestions? -- Rick
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2015-04-25 15:44 -0400 |
| Message-ID | <mhgqo7$nne$2@dont-email.me> |
| In reply to | #20795 |
On 4/25/2015 2:35 PM, rickman wrote: > On 4/23/2015 2:59 AM, Theo Markettos wrote: >> In comp.sys.raspberry-pi rickman <gnuarm@gmail.com> wrote: >>> On 4/18/2015 4:38 AM, Jan Coombs <Jan-54 wrote: >>>> On Fri, 17 Apr 2015 20:20:30 -0400 >>>> rickman <gnuarm@gmail.com> wrote: >>>> >>>>> Now I am a bit stuck trying to get a serial port terminal emulation >>>>> running. It would appear that miniterm is the right program to >>>>> use, but >>>>> while dealing with the slowness of the rPi when web browsing I have >>>>> yet >>>>> to find it exactly. I thought I had found it at a site called Py >>>>> Serial. But I think what I downloaded with some sort of python >>>>> wrapper >>>>> for miniterm. I'm not sure really. >>>> >>>> gtkterm is simple and capable, but can't find rPi to check >>>> this :( To install, type at terminal: >>>> >>>> sudo apt-get install gtkterm >>> >>> Sounded good, but didn't work. I am familiar with the "sudo apt-get >>> install" thing. I think that was the first thing I learned a few weeks >>> ago (or was it months?) when I first powered up the rPi. This time it >>> says "Unable to locate package gtkterm". >> >> I don't know gtkterm, but the 'canonical' package people often talk >> about is >> minicom (not miniterm as you mentioned). However it has an annoying >> 'curses' (DOS-style) GUI - I prefer picocom because it doesn't have >> menus on >> obscure keypresses to configure it, you just tell it the >> serial device on the command line and away you go: >> picocom -b 115200 /dev/ttyUSB0 >> >>> It would be so much easier if I could access newsgroups on the rPi. Oh >>> well... >> >> So do that then ;-) >> >> sudo apt-get install tin >> NNTPSERVER=nntp.aioe.org tin -r >> >> then hit shift-S and type the name of a newsgroup you want to >> subscribe to. >> Navigate with the arrow keys. You can of course set it up with your >> newsserver and name etc (look in ~/.tin/), but the above should work >> directly. >> >> 'Other newsreaders are available', as they say. >> >>> Now I just need to figure out my user name. I haven't logged into this >>> thing in months. I believe the default is raspberry. >> >> The default username is 'pi' and the password 'raspberry'. >> >>> I'm running Raspbian. I think I have all the pieces now except a >>> terminal emulator. When reading about miniterm it says it lets the >>> command window handle ANSI code formatting and that window is called >>> "terminal". I'm wondering if I need a terminal emulator at all. I >>> guess the "terminal emulator" reroutes the keystrokes to the serial port >>> output and the serial port input to the display. There would be no way >>> to do that with pipes or such. That would allow me to control the >>> command window from the serial port perhaps which is not what I need. >> >> You don't need a terminal emulator as such - the window that displays >> your >> session is already a terminal emulator. If it's on the Pi display >> then that >> could be a program like xterm or gnome-terminal, if you're using SSH >> then it >> could be a Windows program like PuTTY. That provides the >> terminal-to-pixels >> conversion, and then all you need to do is ensure that character >> stream that >> reaches it is in the right format. Typically this is done by >> propagating a >> TERM environment variable around (which SSH will do for you but picocom >> won't), for example TERM=vt100, so as long as whatever is outputting text >> know it's aiming for a vt100 it'll generate the right characters for >> PuTTY >> or whatever, even if they pass through three machines on the way. >> >> Anyway, for simple stuff you probably don't need to tell your heating >> controller or whatever to output vt100 codes - ASCII works just fine, the >> terminal settings only matter for things like cursor movement and >> graphics. >> >> So all you need is a program to display the traffic on the serial port - >> picocom or minicom will do, but they aren't 'terminal emulators' as such. > > I got minicom up (I was calling it miniterm, lol) but it doesn't seem to > have a setting for translating LF to CR/LF. The Mecrisp app on the > launchpad only sends LF. > > I also tried setting the "implicit CR on LF" option in Putty which > doesn't do the trick either. > > Just to recap, I have the rPi running headless with the command line on > the PC through SSH using Putty. The launchpad running Mecrisp is > ttyACM0 on the rPi. Through the Putty session I am running minicom to > the launchpad. Mecrisp seems to return "ok.<LF>" which marches across > the Putty window until it wraps at the right margin. > > Any suggestions? Someone suggested using microcom which handles the LF with no CR issue and I am talking to Mecrisp finally. Now I just have to learn it. -- Rick
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2015-05-08 12:00 -0400 |
| Message-ID | <miimhe$ob0$1@dont-email.me> |
| In reply to | #20798 |
On 4/25/2015 3:44 PM, rickman wrote: > On 4/25/2015 2:35 PM, rickman wrote: >> >> Just to recap, I have the rPi running headless with the command line on >> the PC through SSH using Putty. The launchpad running Mecrisp is >> ttyACM0 on the rPi. Through the Putty session I am running minicom to >> the launchpad. Mecrisp seems to return "ok.<LF>" which marches across >> the Putty window until it wraps at the right margin. >> >> Any suggestions? > > Someone suggested using microcom which handles the LF with no CR issue > and I am talking to Mecrisp finally. Now I just have to learn it. A fair amount of water has fallen over the damn and I have made some progress on my project. The Forth compiler is installed on the target. Using microcom on the rPi and Extra-Putty on my PC I can talk to the Forth program from the PC. Microcom got me around the problem I had with minicom where I needed the LF from the target translated to CRLF. I have completed my hardware setup and have some software to test, but I can't figure out how to transmit a file to the target either from the rPi or from the PC. Microcom doesn't seem to have an option for sending a file to the target and Putty only seems to support X and Y modem, not a simple dump of a text file. I found picocom and installed it on the rPi, but when I run it I get the configuration info and "Terminal Ready", but none of the commands seem to work. The escape key is supposed to be Cntl-A but nothing I type gets a response. I have to kill the putty session. -- Rick
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2015-05-10 03:36 -0400 |
| Message-ID | <min1oo$lv5$1@dont-email.me> |
| In reply to | #20840 |
I took a few more steps today. I found that Mecrisp will accept definitions spread over multiple lines and that Putty has an option that lets you drag and drop a file to send it to the target. It doesn't work perfectly, but it works. Now I can run some source and test it. To get something working better I tried using e4thcom which knows about the command line prompt in mecrisp and can load a file to it. e4thcom installed ok but when I run it I get no response from the target. I am invoking with this command... e4thcom -t mecrisp -d ttyACM0 -b B9600 It reports this... /dev/ttyACM0 open, hdl=3 B9600 8N1 CLOCAL ONLCR but when e4thcom is exited stty returns this... speed 0 baud; rows 0; columns 0; line = 0; among other things. Why would the speed be set to zero? Even when I run microcom the target does not respond. I have to reboot which resets the target too. :( -- Rick
[toc] | [prev] | [next] | [standalone]
| From | Theo Markettos <theom+news@chiark.greenend.org.uk> |
|---|---|
| Date | 2015-05-10 10:32 +0100 |
| Message-ID | <lAD*SL8uv@news.chiark.greenend.org.uk> |
| In reply to | #20848 |
In comp.sys.raspberry-pi rickman <gnuarm@gmail.com> wrote: > To get something working better I tried using e4thcom which knows about > the command line prompt in mecrisp and can load a file to it. e4thcom > installed ok but when I run it I get no response from the target. I am > invoking with this command... > > e4thcom -t mecrisp -d ttyACM0 -b B9600 > > It reports this... > > /dev/ttyACM0 open, hdl=3 B9600 8N1 CLOCAL ONLCR > > but when e4thcom is exited stty returns this... > > speed 0 baud; rows 0; columns 0; line = 0; > > among other things. Why would the speed be set to zero? AIUI if you ask stty for speed, unless you give it a device name it'll return the speed of the terminal you're typing in at the moment. Terminal speed is, I think, supposed to be a hint to programs how much data they're likely to be able to output before the serial port gets congested. If connect to your Unix timesharing system via a VT100 then termcap will say it's at 9600 baud - not only do you need to configure the serial port but it could cause programs to adapt to the speed. This is all water under the 1970s bridge, so I'd imagine 'speed 0' means 'I don't care about that stuff any more'. > Even when I run microcom the target does not respond. I have to reboot > which resets the target too. :( Is it anything to do with CTS/RTS/DSR/DTR? A slow serial line getting wedged isn't uncommon if you're lacking flow control and doing bulk downloads. Theo
[toc] | [prev] | [next] | [standalone]
| From | Tauno Voipio <tauno.voipio@notused.fi.invalid> |
|---|---|
| Date | 2015-05-10 12:56 +0300 |
| Message-ID | <min9v3$ehp$1@dont-email.me> |
| In reply to | #20849 |
On 10.5.15 12:32, Theo Markettos wrote: > In comp.sys.raspberry-pi rickman <gnuarm@gmail.com> wrote: >> To get something working better I tried using e4thcom which knows about >> the command line prompt in mecrisp and can load a file to it. e4thcom >> installed ok but when I run it I get no response from the target. I am >> invoking with this command... >> >> e4thcom -t mecrisp -d ttyACM0 -b B9600 >> >> It reports this... >> >> /dev/ttyACM0 open, hdl=3 B9600 8N1 CLOCAL ONLCR >> >> but when e4thcom is exited stty returns this... >> >> speed 0 baud; rows 0; columns 0; line = 0; >> >> among other things. Why would the speed be set to zero? > > AIUI if you ask stty for speed, unless you give it a device name it'll > return the speed of the terminal you're typing in at the moment. Terminal > speed is, I think, supposed to be a hint to programs how much data they're > likely to be able to output before the serial port gets congested. If > connect to your Unix timesharing system via a VT100 then termcap will say > it's at 9600 baud - not only do you need to configure the serial port but it > could cause programs to adapt to the speed. This is all water under the > 1970s bridge, so I'd imagine 'speed 0' means 'I don't care about that > stuff any more'. > >> Even when I run microcom the target does not respond. I have to reboot >> which resets the target too. :( > > Is it anything to do with CTS/RTS/DSR/DTR? A slow serial line getting > wedged isn't uncommon if you're lacking flow control and doing bulk > downloads. > > Theo It could be software flow control, X-on, X-off getting wedged. -- -TV
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2015-05-10 10:48 -0400 |
| Message-ID | <minr1l$aaa$1@dont-email.me> |
| In reply to | #20849 |
On 5/10/2015 5:32 AM, Theo Markettos wrote: > In comp.sys.raspberry-pi rickman <gnuarm@gmail.com> wrote: >> To get something working better I tried using e4thcom which knows about >> the command line prompt in mecrisp and can load a file to it. e4thcom >> installed ok but when I run it I get no response from the target. I am >> invoking with this command... >> >> e4thcom -t mecrisp -d ttyACM0 -b B9600 >> >> It reports this... >> >> /dev/ttyACM0 open, hdl=3 B9600 8N1 CLOCAL ONLCR >> >> but when e4thcom is exited stty returns this... >> >> speed 0 baud; rows 0; columns 0; line = 0; >> >> among other things. Why would the speed be set to zero? > > AIUI if you ask stty for speed, unless you give it a device name it'll > return the speed of the terminal you're typing in at the moment. Terminal > speed is, I think, supposed to be a hint to programs how much data they're > likely to be able to output before the serial port gets congested. If > connect to your Unix timesharing system via a VT100 then termcap will say > it's at 9600 baud - not only do you need to configure the serial port but it > could cause programs to adapt to the speed. This is all water under the > 1970s bridge, so I'd imagine 'speed 0' means 'I don't care about that > stuff any more'. > >> Even when I run microcom the target does not respond. I have to reboot >> which resets the target too. :( > > Is it anything to do with CTS/RTS/DSR/DTR? A slow serial line getting > wedged isn't uncommon if you're lacking flow control and doing bulk > downloads. It appeared to be the speed. It seems there is some different handling of the tty settings in the two programs, microcom and e4thcom so that e4thcom leaves the port is a state that disrupts microcom. I set the data rate from stty and got microcom to work again. But now something else is messed up and even rebooting and cycling power won't fix it. I can get microcom to work, but the target won't respond unless I hit enter twice rapidly. 8-* This is getting to be rather frustrating. -- Rick
[toc] | [prev] | [next] | [standalone]
Page 3 of 7 — ← Prev page 1 2 [3] 4 5 6 7 Next page →
Back to top | Article view | comp.arch.embedded
csiph-web