Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #37861 > unrolled thread
| Started by | rickman <gnuarm@gmail.com> |
|---|---|
| First post | 2015-04-02 21:08 -0400 |
| Last post | 2015-04-17 20:06 +0000 |
| Articles | 20 on this page of 102 — 24 participants |
Back to article view | Back to comp.lang.forth
Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-02 21:08 -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 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 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 Mark Wills <markwills1970@gmail.com> - 2015-05-10 08:55 -0700
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-05-10 13:13 -0400
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-05-10 15:34 -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 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 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
Page 2 of 6 — ← Prev page 1 [2] 3 4 5 6 Next page →
| From | Dimiter_Popoff <dp@tgi-sci.com> |
|---|---|
| Date | 2015-04-19 13:22 +0300 |
| Subject | Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking |
| Message-ID | <mgvvii$hm4$1@dont-email.me> |
| In reply to | #38362 |
On 19.4.2015 г. 01:55, Rod Pemberton wrote: > On Sat, 18 Apr 2015 09:32:24 -0400, rickman <gnuarm@gmail.com> wrote: >> On 4/18/2015 4:00 AM, David Brown wrote: > >>> So your posts from Thunderbird are absolutely fine. >> >> Thanks for the info. It's good to know this is correct. There is one >> nut case in the Forth group who replies to my posts with a bit of boiler >> plate added saying my lines were not wrapped correctly and he rewrapped >> them for me, lol. > > That guy may be a nut, but he's *correct* about your lines. > > Your lines aren't wrapped correctly for Usenet. Don't know about nutcase but his lines here seem quite correct to me. I checked a few messages at a glance and examined in detail one (I think it was his second one). His lines are well within 72 characters. The quoted lines are left alone; some of them are much longer than they should be but this has been the fault of *their* poster, not Ricks. If someone has the expectation people will edit the line length of everything they quote.... well, this is unrealistic to say the least. Dimiter
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2015-04-19 22:09 +0200 |
| Subject | Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking |
| Message-ID | <mh11v9$jti$1@dont-email.me> |
| In reply to | #38371 |
On 19/04/15 12:22, Dimiter_Popoff wrote: > On 19.4.2015 г. 01:55, Rod Pemberton wrote: >> On Sat, 18 Apr 2015 09:32:24 -0400, rickman <gnuarm@gmail.com> wrote: >>> On 4/18/2015 4:00 AM, David Brown wrote: >> >>>> So your posts from Thunderbird are absolutely fine. >>> >>> Thanks for the info. It's good to know this is correct. There is one >>> nut case in the Forth group who replies to my posts with a bit of boiler >>> plate added saying my lines were not wrapped correctly and he rewrapped >>> them for me, lol. >> >> That guy may be a nut, but he's *correct* about your lines. >> >> Your lines aren't wrapped correctly for Usenet. > > Don't know about nutcase but his lines here seem quite correct to me. > I checked a few messages at a glance and examined in detail one (I think > it was his second one). > His lines are well within 72 characters. The quoted lines are left > alone; some of them are much longer than they should be but this > has been the fault of *their* poster, not Ricks. If someone has > the expectation people will edit the line length of everything > they quote.... well, this is unrealistic to say the least. > > Dimiter > Other than that, the only difference I see between the lines in my and Rick's posts, and Rod's posts, is that Thunderbird has spaces at the end of the lines, while Rod's do not. (Nor do yourrs, Dimiter.) I suspect that Thunderbird uses these spaces to identify wrapped paragraphs, which it can then re-wrap to the window width for display in Thunderbird (but not for posting). It could also be that there is a difference in the line ending characters, but it would surprise me if a Usenet client is fussy about the line endings it accepts.
[toc] | [prev] | [next] | [standalone]
| From | mm0fmf <none@mailinator.com> |
|---|---|
| Date | 2015-04-17 21:15 +0100 |
| Message-ID | <RRdYw.257010$Zf4.118346@fx22.am4> |
| In reply to | #38289 |
On 17/04/2015 19:47, rickman wrote: > On 4/17/2015 12:56 AM, Paul Rubin wrote: >> rickman <gnuarm@gmail.com> writes: >>> I was using a gadget to measure the voltage and current going into the >>> rPi. That side is at 5.25 volts give or take with around 400 mA of >>> current. I moved the meter to the launchpad and the output on the USB >>> port is only 4.95 volts. >> >> I remember reading somewhere (probably adafruit.com) that you should use >> a pretty beefy 5V power supply with the rpi especially if it's under any >> type of load. They actually tweak their rpi power supplies to deliver >> 5.25 volts to compensate for some inevitable sag. >> >> I don't remember hearing that the USB ports themselves are out of spec >> but it's possible. Despite popular misconception USB ports are only >> supposed to be able to deliver 100 mA unless they grant the client >> "permission" to draw more (up to 500ma), through a power negotiation >> protocol that's part of USB. Most x86 motherboards can deliver 500 mA >> with no problem, so lots of badly designed client devices just assume >> the power is available, and try to draw it without bothering with the >> protocol. Maybe something like that is going on here. > > I'm not 100% certain of this, but I believe the rPi runs input power > through a Polyfuse which does have some noticeable resistance and so > voltage droop. I've cross-posted this to the rPi group to see if anyone > will confirm it. > When in doubt check the spec... USB2.0 ports are 5v +/- 5% so 4.75V to 5.25V between the pins on the connector. 4.95 is almost perfectly in the middle.
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2015-04-17 17:02 -0400 |
| Message-ID | <mgrsbf$um9$2@dont-email.me> |
| In reply to | #38293 |
On 4/17/2015 4:15 PM, mm0fmf wrote: > On 17/04/2015 19:47, rickman wrote: >> On 4/17/2015 12:56 AM, Paul Rubin wrote: >>> rickman <gnuarm@gmail.com> writes: >>>> I was using a gadget to measure the voltage and current going into the >>>> rPi. That side is at 5.25 volts give or take with around 400 mA of >>>> current. I moved the meter to the launchpad and the output on the USB >>>> port is only 4.95 volts. >>> >>> I remember reading somewhere (probably adafruit.com) that you should use >>> a pretty beefy 5V power supply with the rpi especially if it's under any >>> type of load. They actually tweak their rpi power supplies to deliver >>> 5.25 volts to compensate for some inevitable sag. >>> >>> I don't remember hearing that the USB ports themselves are out of spec >>> but it's possible. Despite popular misconception USB ports are only >>> supposed to be able to deliver 100 mA unless they grant the client >>> "permission" to draw more (up to 500ma), through a power negotiation >>> protocol that's part of USB. Most x86 motherboards can deliver 500 mA >>> with no problem, so lots of badly designed client devices just assume >>> the power is available, and try to draw it without bothering with the >>> protocol. Maybe something like that is going on here. >> >> I'm not 100% certain of this, but I believe the rPi runs input power >> through a Polyfuse which does have some noticeable resistance and so >> voltage droop. I've cross-posted this to the rPi group to see if anyone >> will confirm it. >> > > When in doubt check the spec... USB2.0 ports are 5v +/- 5% so 4.75V to > 5.25V between the pins on the connector. > > 4.95 is almost perfectly in the middle. I never said that measurement was out of spec. I was commenting on the facts that there is a quarter volt lost across the rPi and that the launchpad seems to reset when I type on the USB keyboard. Maybe it's not voltage related, but the quarter volt drop is unexpected and there are plenty of cases where even an older mouse, like the one I have, can't be powered through the rPi. -- Rick
[toc] | [prev] | [next] | [standalone]
| From | mm0fmf <none@mailinator.com> |
|---|---|
| Date | 2015-04-18 17:06 +0100 |
| Message-ID | <2ivYw.272005$JH2.257361@fx11.am4> |
| In reply to | #38300 |
On 17/04/2015 22:02, rickman wrote: > I was commenting on the facts that there is a quarter volt lost across > the rPi It doesn't matter how much "is lost" because the final voltage is within spec. I don't know about the hub and PHY on the Pi, but all the PHYs we produce have the ability to disable VBUS on each port and can signal over current conditions. When a device pulls too much current you signal the USB MAC and it tells the PHY to kill VBUS. The missing volts will be loss in the PHY VBUS switch most likely. I don't work with our PHYs directly but only with the USB MACs we produce so I can't recall off the top of my head if the over current is as programmable as the current the device claims during enumeration. Devices specify their max current requirements in multiples of 2mA units. Before enumeration, the spec allows 100mA and I'm fairly sure our PHYs will signal over current if something tries to draw much more than 100mA. Once enumerated, again I'm fairly sure the over current level is programmable. > and that the launchpad seems to reset when I type on the USB > keyboard. If the launchpad lies during enumeration then this can happen. It's not helped by the early Pi hardware being a bit more than flakey. > Maybe it's not voltage related, but the quarter volt drop is > unexpected Not when you know there are switches between the power rail and VBUS as previously stated. >and there are plenty of cases where even an older mouse, like > the one I have, can't be powered through the rPi. I have lots of devices that work perfectly with a Pi as long as they are connected before the Pi (model B, 512M) is booted. Plugging them in once booted normally results in a crash. Which is a shame as USB is designed to be hot-pluggable. I should really say that I am shocked, nay stunned to find that a £30 single board PC which can be battery powered that runs Linux and provides a metric shit-load of IO in addition to Ethernet and USB has a number of gotchas and issues. ;-)
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2015-04-19 16:57 -0400 |
| Message-ID | <mh14qa$u9a$1@dont-email.me> |
| In reply to | #38352 |
On 4/18/2015 12:06 PM, mm0fmf wrote: > On 17/04/2015 22:02, rickman wrote: >> I was commenting on the facts that there is a quarter volt lost across >> the rPi > > It doesn't matter how much "is lost" because the final voltage is within > spec. You are confused. The only reason why the output voltage is in spec is because the input voltage is well above the nominal voltage required on the input. With another power module the output voltage would be outside of spec and even now, the output is not able to supply much current. Connect a device that draws more current and the voltage sags more. This is not so much about the USB spec as it is the design of the rPi which creates a lot of voltage drop on what should be very nearly a wire with nominal resistance. > I don't know about the hub and PHY on the Pi, but all the PHYs we > produce have the ability to disable VBUS on each port and can signal > over current conditions. When a device pulls too much current you signal > the USB MAC and it tells the PHY to kill VBUS. The missing volts will be > loss in the PHY VBUS switch most likely. Such a switch would typically have a resistance of low mOhms and create a correspondingly low voltage drop... much less than the 0.25 volts we are seeing in the rPi. > I don't work with our PHYs directly but only with the USB MACs we > produce so I can't recall off the top of my head if the over current is > as programmable as the current the device claims during enumeration. > Devices specify their max current requirements in multiples of 2mA > units. Before enumeration, the spec allows 100mA and I'm fairly sure our > PHYs will signal over current if something tries to draw much more than > 100mA. Once enumerated, again I'm fairly sure the over current level is > programmable. > >> and that the launchpad seems to reset when I type on the USB >> keyboard. > > If the launchpad lies during enumeration then this can happen. It's not > helped by the early Pi hardware being a bit more than flakey. Bingo. >> Maybe it's not voltage related, but the quarter volt drop is >> unexpected > > Not when you know there are switches between the power rail and VBUS as > previously stated. The rPi does not have switches in the power path I believe. But if it does, they should be designed for a much lower voltage drop than a quarter volt, hence the problem. >> and there are plenty of cases where even an older mouse, like >> the one I have, can't be powered through the rPi. > > I have lots of devices that work perfectly with a Pi as long as they are > connected before the Pi (model B, 512M) is booted. Plugging them in once > booted normally results in a crash. Which is a shame as USB is designed > to be hot-pluggable. > > I should really say that I am shocked, nay stunned to find that a £30 > single board PC which can be battery powered that runs Linux and > provides a metric shit-load of IO in addition to Ethernet and USB has a > number of gotchas and issues. ;-) I find your description of the rPi to be interesting. Battery powered is a bit tongue in cheek as this level device is on par with phones and tablets which can't be away from a power plug for hours rather than days. I think of "battery powered" as describing equipment that can be left unattended for many days without an external power source. But whatever, one man's battery is another man's RTG. lol Enjoy -- Rick
[toc] | [prev] | [next] | [standalone]
| From | Alan Adams <alan@adamshome.org.uk> |
|---|---|
| Date | 2015-04-20 09:33 +0100 |
| Message-ID | <e10132b754.Alan.Adams@iyonix.adamshome.org.uk> |
| In reply to | #38391 |
In message <mh14qa$u9a$1@dont-email.me>
rickman <gnuarm@gmail.com> wrote:
> On 4/18/2015 12:06 PM, mm0fmf wrote:
>> On 17/04/2015 22:02, rickman wrote:
>>> I was commenting on the facts that there is a quarter volt lost across
>>> the rPi
>>
>> It doesn't matter how much "is lost" because the final voltage is within
>> spec.
> You are confused. The only reason why the output voltage is in spec is
> because the input voltage is well above the nominal voltage required on
> the input. With another power module the output voltage would be
> outside of spec and even now, the output is not able to supply much
> current. Connect a device that draws more current and the voltage sags
> more.
> This is not so much about the USB spec as it is the design of the rPi
> which creates a lot of voltage drop on what should be very nearly a wire
> with nominal resistance.
and to make it worse, and fluctuations in the current drawn will
produce fluctuations in the voltage. Checking with an oscilloscope is
the only realistic way to see whether this is affecting the problem.
>> I don't know about the hub and PHY on the Pi, but all the PHYs we
>> produce have the ability to disable VBUS on each port and can signal
>> over current conditions. When a device pulls too much current you signal
>> the USB MAC and it tells the PHY to kill VBUS. The missing volts will be
>> loss in the PHY VBUS switch most likely.
> Such a switch would typically have a resistance of low mOhms and create
> a correspondingly low voltage drop... much less than the 0.25 volts we
> are seeing in the rPi.
>> I don't work with our PHYs directly but only with the USB MACs we
>> produce so I can't recall off the top of my head if the over current is
>> as programmable as the current the device claims during enumeration.
>> Devices specify their max current requirements in multiples of 2mA
>> units. Before enumeration, the spec allows 100mA and I'm fairly sure our
>> PHYs will signal over current if something tries to draw much more than
>> 100mA. Once enumerated, again I'm fairly sure the over current level is
>> programmable.
>>
>>> and that the launchpad seems to reset when I type on the USB
>>> keyboard.
>>
>> If the launchpad lies during enumeration then this can happen. It's not
>> helped by the early Pi hardware being a bit more than flakey.
> Bingo.
>>> Maybe it's not voltage related, but the quarter volt drop is
>>> unexpected
>>
>> Not when you know there are switches between the power rail and VBUS as
>> previously stated.
> The rPi does not have switches in the power path I believe. But if it
> does, they should be designed for a much lower voltage drop than a
> quarter volt, hence the problem.
>>> and there are plenty of cases where even an older mouse, like
>>> the one I have, can't be powered through the rPi.
>>
>> I have lots of devices that work perfectly with a Pi as long as they are
>> connected before the Pi (model B, 512M) is booted. Plugging them in once
>> booted normally results in a crash. Which is a shame as USB is designed
>> to be hot-pluggable.
>>
>> I should really say that I am shocked, nay stunned to find that a £30
>> single board PC which can be battery powered that runs Linux and
>> provides a metric shit-load of IO in addition to Ethernet and USB has a
>> number of gotchas and issues. ;-)
> I find your description of the rPi to be interesting. Battery powered
> is a bit tongue in cheek as this level device is on par with phones and
> tablets which can't be away from a power plug for hours rather than
> days. I think of "battery powered" as describing equipment that can be
> left unattended for many days without an external power source. But
> whatever, one man's battery is another man's RTG. lol
> Enjoy
--
Alan Adams, from Northamptonshire
alan@adamshome.org.uk
http://www.nckc.org.uk/
[toc] | [prev] | [next] | [standalone]
| From | mm0fmf <none@mailinator.com> |
|---|---|
| Date | 2015-04-20 18:03 +0100 |
| Message-ID | <qjaZw.248088$9c1.102235@fx41.am4> |
| In reply to | #38391 |
On 19/04/2015 21:57, rickman wrote: > > The rPi does not have switches in the power path I believe. Dear rickman, having studied many of your posts I have come to the conlusion that you don't read what people write and have significantly less comprehension regarding hardware and software in reality than you believe you have. And so, given I have fewer tomorrows than yesterdays, I shall let you stew in your own piss from now on rather than trying to help you. *plink*
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2015-04-21 01:16 -0400 |
| Message-ID | <mh4me3$jo9$1@dont-email.me> |
| In reply to | #38420 |
On 4/20/2015 1:03 PM, mm0fmf wrote: > On 19/04/2015 21:57, rickman wrote: >> >> The rPi does not have switches in the power path I believe. > > Dear rickman, having studied many of your posts I have come to the > conlusion that you don't read what people write and have significantly > less comprehension regarding hardware and software in reality than you > believe you have. > > And so, given I have fewer tomorrows than yesterdays, I shall let you > stew in your own piss from now on rather than trying to help you. > > *plink* No need to have a pissing contest with anyone, but I don't actually recall your posts attempting to be helpful. Rather you tried to tell me the voltage on the USB ports were "in spec" when that was not the issue being discussed. plonk yourself, lol -- Rick
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2015-04-17 20:20 -0400 |
| Message-ID | <mgs7uk$75f$1@dont-email.me> |
| In reply to | #38289 |
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. 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? -- Rick
[toc] | [prev] | [next] | [standalone]
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Date | 2015-04-17 17:24 -0700 |
| Message-ID | <87sibyuvuq.fsf@jester.gateway.pace.com> |
| In reply to | #38309 |
rickman <gnuarm@gmail.com> writes: > 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? Do "ls /dev/tty*" and it should give you a list of possible devices where the port is. Do you use irc? You can probably get quicker help on the #raspberrypi Freenode channel.
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2015-04-17 20:40 -0400 |
| Message-ID | <mgs93g$a1u$1@dont-email.me> |
| In reply to | #38310 |
On 4/17/2015 8:24 PM, Paul Rubin wrote: > rickman <gnuarm@gmail.com> writes: >> 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? > > Do "ls /dev/tty*" and it should give you a list of possible devices > where the port is. That gives me a list of tty, tty0 through tty63, ttyAMA0 and ttyprintk. The list is the same if the device is plugged in or not. Of course, I don't know for sure what the board should do, but my understanding is one port is for use as a debugger and this port is for use as a UART interface to the target MCU. I had found a web page where they were developing on this target under Linux. I'll go back to that to look for info. But I think it was more debugger oriented. Trouble is most of these pages are from experienced users and they have long ago forgotten all the small stumbling blocks to getting started. > Do you use irc? You can probably get quicker help on the #raspberrypi > Freenode channel. 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. One of my problems is there really isn't room for the pi, the laptop and all the other misc stuff on my work table at the moment. Maybe I need to just work remotely from the laptop. That would solve my lack of a USB hub as well. I have to unplug the mouse to plug in the launchpad. -- Rick
[toc] | [prev] | [next] | [standalone]
| 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 | #38313 |
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 | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2015-04-18 10:04 +0200 |
| Message-ID | <mgt34l$7l2$1@dont-email.me> |
| In reply to | #38309 |
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 | #38309 |
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 | #38329 |
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 | #38344 |
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 | #38344 |
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 | #38344 |
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 | #38528 |
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]
Page 2 of 6 — ← Prev page 1 [2] 3 4 5 6 Next page →
Back to top | Article view | comp.lang.forth
csiph-web