Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.arch.embedded > #20606 > unrolled thread

Mecrisp on the TI Stellaris Launchpad

Started byrickman <gnuarm@gmail.com>
First post2015-04-02 21:08 -0400
Last post2015-04-16 16:18 -0700
Articles 20 on this page of 123 — 26 participants

Back to article view | Back to comp.arch.embedded


Contents

  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 2 of 7 — ← Prev page 1 [2] 3 4 5 6 7  Next page →


#20709 — Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking

Fromrickman <gnuarm@gmail.com>
Date2015-04-18 09:32 -0400
SubjectRe: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking
Message-ID<mgtmbd$582$1@dont-email.me>
In reply to#20697
On 4/18/2015 4:00 AM, David Brown wrote:
> On 17/04/15 21:12, rickman wrote:
>> On 4/17/2015 2:47 PM, 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.
>>
>> I'm appending this OT post because I don't often look at my own posts,
>> but did this one.  I'm using Thunderbird and it seems to do odd things
>> with line breaking.
>>
>> It is common that I reply to ("Followup" in T-bird parlance) a post only
>> to find quoted lines extending off the page.  Ok, so T-bird doesn't
>> always figure out that it needs to wrap lines for display.
>>
>> But looking at my own post, I see the lines wrapping, but at the edge of
>> the screen, not at the 72 column point where line breaks should be
>> inserted when sending a message.  Changing the size of the window
>> confirms this.
>>
>> Then to make it even more confusing, in this reply it would appear that
>> line breaks are inserted in the quoted text!  WTF????!!!!  Anyone
>> understand how T-bird handles the line breaks, word wrap features?  Do
>> you see my posts with line breaks at 72 columns?  I have that turned
>> on... at least I thought I did.  I can't find the setting now.
>>
>
> Thunderbird is wrapping your lines perfectly well - you can see this by
> using ctrl-U to see the "source" of the posts.
>
> But Thunderbird re-wraps for display - if the lines in a post are not
> quoted, and appear to be a line-wrapped paragraph, it re-wraps then to
> the width of the window.  I am somewhat in two minds as to whether this
> is a good thing or a bad thing, but I haven't tried to turn it off.
>
> 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.

But that doesn't explain the issue I have where quoted text in the 
window for composing messages often is not wrapped and runs off the edge 
of the window.  Any idea what causes that?  It makes it very hard to see 
what I am replying to.  This message seems to be just fine, I suppose 
because the lines *are* wrapped.  Looking at my post from April 16 at 
5:24 PM I see my lines are *not* wrapped.  I see in the source the = 
char at the end of each line which I assume means a continuation. 
Strange...  This seems to not be wrapped in the composition window when 
replying.

-- 

Rick

[toc] | [prev] | [next] | [standalone]


#20712 — Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking

FromMartin Gregorie <martin@address-in-sig.invalid>
Date2015-04-18 15:15 +0000
SubjectRe: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking
Message-ID<mgtsep$ri3$1@dont-email.me>
In reply to#20709
On Sat, 18 Apr 2015 09:32:24 -0400, rickman wrote:

> But that doesn't explain the issue I have where quoted text in the
> window for composing messages often is not wrapped and runs off the edge
> of the window.  Any idea what causes that?
>
I some NNTP clients don't seem wrap outgoing lines, But I don't know 
which ones they are.

Pan has the ability to display incoming messages as they were received or 
after wrapping them, which is quite useful. 

Wrapping is useful if long lines are received, but it can mess up lines 
which start with hyphens or asterisks because it thinks that means 'join 
to preceding line' rather than 'another item in the list'. Hitting 'w' 
toggles between wrap and no-wrap so either way the fix is instant.
 

-- 
martin@   | Martin Gregorie
gregorie. | Essex, UK
org       |

[toc] | [prev] | [next] | [standalone]


#20715 — Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking

Fromrickman <gnuarm@gmail.com>
Date2015-04-18 11:31 -0400
SubjectRe: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking
Message-ID<mgttb9$23f$1@dont-email.me>
In reply to#20712
On 4/18/2015 11:15 AM, Martin Gregorie wrote:
> On Sat, 18 Apr 2015 09:32:24 -0400, rickman wrote:
>
>> But that doesn't explain the issue I have where quoted text in the
>> window for composing messages often is not wrapped and runs off the edge
>> of the window.  Any idea what causes that?
>>
> I some NNTP clients don't seem wrap outgoing lines, But I don't know
> which ones they are.
>
> Pan has the ability to display incoming messages as they were received or
> after wrapping them, which is quite useful.
>
> Wrapping is useful if long lines are received, but it can mess up lines
> which start with hyphens or asterisks because it thinks that means 'join
> to preceding line' rather than 'another item in the list'. Hitting 'w'
> toggles between wrap and no-wrap so either way the fix is instant.

I don't wish to belabor this too much.  It is off topic and I just 
thought someone with Thunderbird experience might have a quick answer. 
This issue is not on reading messages, that always wraps lines so they 
are viewable.  It is the quoted text in the reply that will not be 
wrapped if it is not broken in the received message.  Very odd....

-- 

Rick

[toc] | [prev] | [next] | [standalone]


#20721 — Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking

FromNiklas Holsti <niklas.holsti@tidorum.invalid>
Date2015-04-18 19:21 +0300
SubjectRe: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking
Message-ID<cpfekcF7nfaU1@mid.individual.net>
In reply to#20709
On 15-04-18 16:32 , rickman wrote:

> But that doesn't explain the issue I have where quoted text in the
> window for composing messages often is not wrapped and runs off the edge
> of the window.

That occasionally happens with Thunderbird for me, too.

> Any idea what causes that?

No, I don't.

> It makes it very hard to see what I am replying to.

Yes. But there is a useful menu command Edit->Rewrap which wraps the 
quoted text.

-- 
Niklas Holsti
Tidorum Ltd
niklas holsti tidorum fi
       .      @       .

[toc] | [prev] | [next] | [standalone]


#20745 — Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking

Fromrickman <gnuarm@gmail.com>
Date2015-04-19 16:39 -0400
SubjectRe: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking
Message-ID<mh13p1$qgf$1@dont-email.me>
In reply to#20721
On 4/18/2015 12:21 PM, Niklas Holsti wrote:
> On 15-04-18 16:32 , rickman wrote:
>
>> But that doesn't explain the issue I have where quoted text in the
>> window for composing messages often is not wrapped and runs off the edge
>> of the window.
>
> That occasionally happens with Thunderbird for me, too.
>
>> Any idea what causes that?
>
> No, I don't.
>
>> It makes it very hard to see what I am replying to.
>
> Yes. But there is a useful menu command Edit->Rewrap which wraps the
> quoted text.

Thanks, that will make me happier.

-- 

Rick

[toc] | [prev] | [next] | [standalone]


#20723 — Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking

FromAlan Adams <alan@adamshome.org.uk>
Date2015-04-18 18:52 +0100
SubjectRe: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking
Message-ID<a4795db654.Alan.Adams@iyonix.adamshome.org.uk>
In reply to#20709
In message <mgtmbd$582$1@dont-email.me>
          rickman <gnuarm@gmail.com> wrote:

> On 4/18/2015 4:00 AM, David Brown wrote:
>> On 17/04/15 21:12, rickman wrote:
>>> On 4/17/2015 2:47 PM, rickman wrote:
>>>> On 4/17/2015 12:56 AM, Paul Rubin wrote:
>>>>> rickman <gnuarm@gmail.com> writes:
<snip>

>>
>> But Thunderbird re-wraps for display - if the lines in a post are not
>> quoted, and appear to be a line-wrapped paragraph, it re-wraps then to
>> the width of the window.  I am somewhat in two minds as to whether this
>> is a good thing or a bad thing, but I haven't tried to turn it off.
>>
>> 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.

> But that doesn't explain the issue I have where quoted text in the
> window for composing messages often is not wrapped and runs off the edge
> of the window.  Any idea what causes that?  It makes it very hard to see
> what I am replying to.  This message seems to be just fine, I suppose
> because the lines *are* wrapped.  Looking at my post from April 16 at
> 5:24 PM I see my lines are *not* wrapped.  I see in the source the =
> char at the end of each line which I assume means a continuation.
> Strange...  This seems to not be wrapped in the composition window when
> replying.

The = at the end of each line means that the message was sent using 
"quoted-printable" encoding, but has not been decoded correctly. This 
might be a problem at your end, but more likely means that along the 
line the descriptor which identified the encoding has been lost, 
replaced or mangled.

-- 
Alan Adams, from Northamptonshire
alan@adamshome.org.uk
http://www.nckc.org.uk/

[toc] | [prev] | [next] | [standalone]


#20732 — Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking

From"Rod Pemberton" <bork@lllljunkqwer.cpm>
Date2015-04-18 18:55 -0400
SubjectRe: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking
Message-ID<op.xxa8mkiowa0t4m@localhost>
In reply to#20709
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.  This is not a Google
Group.

Your lines should hard wrap with a newline, i.e., ASCII CR LF per spec.,
at 72 characters or so.  Either your Usenet reader has a setting to do
this, or you must manually hit return before 72 characters.  I.e., on
my browser, I had to enter newlines above or it would be one single line.

In this thread, Usenet text wrapping for posts by "rickman" and by
"David Brown" are incorrect.


Rod Pemberton

-- 
Cars kill more people than guns in the U.S.
Yet, no one is trying to take away your car.

[toc] | [prev] | [next] | [standalone]


#20734 — Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking

FromThe Natural Philosopher <tnp@invalid.invalid>
Date2015-04-19 09:13 +0100
SubjectRe: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking
Message-ID<mgvo3o$20k$2@news.albasani.net>
In reply to#20732
On 18/04/15 23: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.  This is not a Google
> Group.
>
> Your lines should hard wrap with a newline, i.e., ASCII CR LF per spec.,
> at 72 characters or so.  Either your Usenet reader has a setting to do
> this, or you must manually hit return before 72 characters.  I.e., on
> my browser, I had to enter newlines above or it would be one single line.
>
> In this thread, Usenet text wrapping for posts by "rickman" and by
> "David Brown" are incorrect.
>
Thunderbird has a 'rewrap text' option that does this.


>
> Rod Pemberton
>


-- 
Everything you read in newspapers is absolutely true, except for the 
rare story of which you happen to have first-hand knowledge. – Erwin Knoll

[toc] | [prev] | [next] | [standalone]


#20735 — Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking

FromDimiter_Popoff <dp@tgi-sci.com>
Date2015-04-19 13:22 +0300
SubjectRe: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking
Message-ID<mgvvii$hm4$1@dont-email.me>
In reply to#20732
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]


#20743 — Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking

FromDavid Brown <david.brown@hesbynett.no>
Date2015-04-19 22:09 +0200
SubjectRe: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking
Message-ID<mh11v9$jti$1@dont-email.me>
In reply to#20735
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]


#20679

Frommm0fmf <none@mailinator.com>
Date2015-04-17 21:15 +0100
Message-ID<RRdYw.257010$Zf4.118346@fx22.am4>
In reply to#20674
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]


#20682

Fromrickman <gnuarm@gmail.com>
Date2015-04-17 17:02 -0400
Message-ID<mgrsbf$um9$2@dont-email.me>
In reply to#20679
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]


#20720

Frommm0fmf <none@mailinator.com>
Date2015-04-18 17:06 +0100
Message-ID<2ivYw.272005$JH2.257361@fx11.am4>
In reply to#20682
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]


#20747

Fromrickman <gnuarm@gmail.com>
Date2015-04-19 16:57 -0400
Message-ID<mh14qa$u9a$1@dont-email.me>
In reply to#20720
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]


#20750

FromAlan Adams <alan@adamshome.org.uk>
Date2015-04-20 09:33 +0100
Message-ID<e10132b754.Alan.Adams@iyonix.adamshome.org.uk>
In reply to#20747
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]


#20757

Frommm0fmf <none@mailinator.com>
Date2015-04-20 18:03 +0100
Message-ID<qjaZw.248088$9c1.102235@fx41.am4>
In reply to#20747
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]


#20763

Fromrickman <gnuarm@gmail.com>
Date2015-04-21 01:16 -0400
Message-ID<mh4me3$jo9$1@dont-email.me>
In reply to#20757
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]


#20687

Fromrickman <gnuarm@gmail.com>
Date2015-04-17 20:20 -0400
Message-ID<mgs7uk$75f$1@dont-email.me>
In reply to#20674
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]


#20688

FromPaul Rubin <no.email@nospam.invalid>
Date2015-04-17 17:24 -0700
Message-ID<87sibyuvuq.fsf@jester.gateway.pace.com>
In reply to#20687
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]


#20691

Fromrickman <gnuarm@gmail.com>
Date2015-04-17 20:40 -0400
Message-ID<mgs93g$a1u$1@dont-email.me>
In reply to#20688
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]


Page 2 of 7 — ← Prev page 1 [2] 3 4 5 6 7  Next page →

Back to top | Article view | comp.arch.embedded


csiph-web