Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.arch.embedded > #20606 > unrolled thread
| Started by | rickman <gnuarm@gmail.com> |
|---|---|
| First post | 2015-04-02 21:08 -0400 |
| Last post | 2015-04-16 16:18 -0700 |
| Articles | 20 on this page of 123 — 26 participants |
Back to article view | Back to comp.arch.embedded
Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-02 21:08 -0400
Re: Mecrisp on the TI Stellaris Launchpad sbattazzo@gmail.com - 2015-04-13 16:18 -0700
Re: Mecrisp on the TI Stellaris Launchpad sbattazzo@gmail.com - 2015-04-13 16:25 -0700
Re: Mecrisp on the TI Stellaris Launchpad sbattazzo@gmail.com - 2015-04-13 16:33 -0700
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-13 21:45 -0400
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-13 21:47 -0400
Re: Mecrisp on the TI Stellaris Launchpad sbattazzo@gmail.com - 2015-04-14 07:33 -0700
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-14 14:38 -0400
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-16 14:24 -0700
Re: Mecrisp on the TI Stellaris Launchpad Paul Rubin <no.email@nospam.invalid> - 2015-04-16 15:11 -0700
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-16 23:37 -0400
Re: Mecrisp on the TI Stellaris Launchpad Paul Rubin <no.email@nospam.invalid> - 2015-04-16 20:59 -0700
Re: Mecrisp on the TI Stellaris Launchpad Mel Wilson <mwilson@the-wire.com> - 2015-04-17 13:16 +0000
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-17 00:19 -0400
Re: Mecrisp on the TI Stellaris Launchpad Paul Rubin <no.email@nospam.invalid> - 2015-04-16 21:56 -0700
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-17 14:47 -0400
WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking rickman <gnuarm@gmail.com> - 2015-04-17 15:12 -0400
Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking Martin Gregorie <martin@address-in-sig.invalid> - 2015-04-17 20:14 +0000
Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking rickman <gnuarm@gmail.com> - 2015-04-17 16:59 -0400
Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking David Brown <david.brown@hesbynett.no> - 2015-04-18 10:00 +0200
Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking rickman <gnuarm@gmail.com> - 2015-04-18 09:32 -0400
Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking Martin Gregorie <martin@address-in-sig.invalid> - 2015-04-18 15:15 +0000
Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking rickman <gnuarm@gmail.com> - 2015-04-18 11:31 -0400
Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking Niklas Holsti <niklas.holsti@tidorum.invalid> - 2015-04-18 19:21 +0300
Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking rickman <gnuarm@gmail.com> - 2015-04-19 16:39 -0400
Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking Alan Adams <alan@adamshome.org.uk> - 2015-04-18 18:52 +0100
Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking "Rod Pemberton" <bork@lllljunkqwer.cpm> - 2015-04-18 18:55 -0400
Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking The Natural Philosopher <tnp@invalid.invalid> - 2015-04-19 09:13 +0100
Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking Dimiter_Popoff <dp@tgi-sci.com> - 2015-04-19 13:22 +0300
Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking David Brown <david.brown@hesbynett.no> - 2015-04-19 22:09 +0200
Re: Mecrisp on the TI Stellaris Launchpad mm0fmf <none@mailinator.com> - 2015-04-17 21:15 +0100
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-17 17:02 -0400
Re: Mecrisp on the TI Stellaris Launchpad mm0fmf <none@mailinator.com> - 2015-04-18 17:06 +0100
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-19 16:57 -0400
Re: Mecrisp on the TI Stellaris Launchpad Alan Adams <alan@adamshome.org.uk> - 2015-04-20 09:33 +0100
Re: Mecrisp on the TI Stellaris Launchpad mm0fmf <none@mailinator.com> - 2015-04-20 18:03 +0100
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-21 01:16 -0400
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-17 20:20 -0400
Re: Mecrisp on the TI Stellaris Launchpad Paul Rubin <no.email@nospam.invalid> - 2015-04-17 17:24 -0700
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-17 20:40 -0400
Re: Mecrisp on the TI Stellaris Launchpad Paul Rubin <no.email@nospam.invalid> - 2015-04-17 17:57 -0700
Re: Mecrisp on the TI Stellaris Launchpad Mel Wilson <mwilson@the-wire.com> - 2015-04-18 02:14 +0000
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-18 02:05 -0400
Re: Mecrisp on the TI Stellaris Launchpad David Brown <david.brown@hesbynett.no> - 2015-04-18 10:16 +0200
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-18 09:56 -0400
Re: Mecrisp on the TI Stellaris Launchpad David Brown <david.brown@hesbynett.no> - 2015-04-18 17:46 +0200
USB serial ports, was: Re: Mecrisp on the TI Stellaris Launchpad Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> - 2015-04-18 18:34 +0000
Re: Mecrisp on the TI Stellaris Launchpad David Brown <david.brown@hesbynett.no> - 2015-04-18 10:04 +0200
Re: Mecrisp on the TI Stellaris Launchpad Jan Coombs <Jan-54 <jenfhaomndgfwutc@murmic.plus.com>> - 2015-04-18 09:38 +0100
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-18 11:04 -0400
Re: Mecrisp on the TI Stellaris Launchpad David Brown <david.brown@hesbynett.no> - 2015-04-18 17:54 +0200
Re: Mecrisp on the TI Stellaris Launchpad hal-usenet@ip-64-139-1-69.sjc.megapath.net (Hal Murray) - 2015-04-18 15:36 -0500
Re: Mecrisp on the TI Stellaris Launchpad Theo Markettos <theom+news@chiark.greenend.org.uk> - 2015-04-23 07:59 +0100
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-25 14:35 -0400
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-25 15:44 -0400
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-05-08 12:00 -0400
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-05-10 03:36 -0400
Re: Mecrisp on the TI Stellaris Launchpad Theo Markettos <theom+news@chiark.greenend.org.uk> - 2015-05-10 10:32 +0100
Re: Mecrisp on the TI Stellaris Launchpad Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2015-05-10 12:56 +0300
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-05-10 10:48 -0400
Re: Mecrisp on the TI Stellaris Launchpad The Natural Philosopher <tnp@invalid.invalid> - 2015-05-10 16:05 +0100
Re: Mecrisp on the TI Stellaris Launchpad Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> - 2015-05-10 23:26 +0000
Re: Mecrisp on the TI Stellaris Launchpad Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> - 2015-05-10 09:37 +0000
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-05-10 11:16 -0400
Re: Mecrisp on the TI Stellaris Launchpad Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> - 2015-05-10 23:42 +0000
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-05-11 02:17 -0400
Re: Mecrisp on the TI Stellaris Launchpad albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-05-10 11:41 +0000
Re: Mecrisp on the TI Stellaris Launchpad Theo Markettos <theom+news@chiark.greenend.org.uk> - 2015-05-10 16:56 +0100
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-05-10 13:01 -0400
Re: Mecrisp on the TI Stellaris Launchpad lasselangwadtchristensen@gmail.com - 2015-04-18 12:13 -0700
Re: Mecrisp on the TI Stellaris Launchpad stephen@mpeforth.com (Stephen Pelc) - 2015-04-18 19:22 +0000
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-19 17:04 -0400
Re: Mecrisp on the TI Stellaris Launchpad Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2015-04-20 13:24 +0300
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-22 13:23 -0400
Re: Mecrisp on the TI Stellaris Launchpad Dimiter_Popoff <dp@tgi-sci.com> - 2015-04-22 20:44 +0300
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-22 13:51 -0400
Re: Mecrisp on the TI Stellaris Launchpad Waldek Hebisch <hebisch@math.uni.wroc.pl> - 2015-04-22 19:10 +0000
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-22 15:31 -0400
Re: Mecrisp on the TI Stellaris Launchpad Waldek Hebisch <hebisch@math.uni.wroc.pl> - 2015-04-23 02:08 +0000
Re: Mecrisp on the TI Stellaris Launchpad Waldek Hebisch <hebisch@math.uni.wroc.pl> - 2015-04-24 02:52 +0000
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-25 14:40 -0400
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-25 15:42 -0400
Re: Mecrisp on the TI Stellaris Launchpad sbattazzo@gmail.com - 2015-04-21 09:34 -0700
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-22 14:57 -0400
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-22 15:35 -0400
Re: Mecrisp on the TI Stellaris Launchpad albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-04-17 10:52 +0000
Re: Mecrisp on the TI Stellaris Launchpad Dimiter_Popoff <dp@tgi-sci.com> - 2015-04-17 14:05 +0300
Re: Mecrisp on the TI Stellaris Launchpad Paul Rubin <no.email@nospam.invalid> - 2015-04-17 07:56 -0700
Re: Mecrisp on the TI Stellaris Launchpad David Brown <david.brown@hesbynett.no> - 2015-04-17 17:26 +0200
Re: Mecrisp on the TI Stellaris Launchpad glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-04-17 17:01 +0000
Re: Mecrisp on the TI Stellaris Launchpad Blajrs Jrolrsen <boegre@no.com> - 2015-04-17 13:36 +0000
Re: Mecrisp on the TI Stellaris Launchpad anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-17 14:42 +0000
Re: Mecrisp on the TI Stellaris Launchpad Hans-Bernhard Bröker <HBBroeker@t-online.de> - 2015-04-18 00:25 +0200
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-17 20:03 -0400
Re: Mecrisp on the TI Stellaris Launchpad Paul Rubin <no.email@nospam.invalid> - 2015-04-17 17:14 -0700
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-17 20:26 -0400
Re: Mecrisp on the TI Stellaris Launchpad Paul Rubin <no.email@nospam.invalid> - 2015-04-17 17:32 -0700
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-17 20:47 -0400
Re: Mecrisp on the TI Stellaris Launchpad albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-04-18 08:47 +0000
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-18 11:19 -0400
Re: Mecrisp on the TI Stellaris Launchpad albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-04-18 15:52 +0000
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-19 17:07 -0400
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-06-09 03:04 -0400
Re: Mecrisp on the TI Stellaris Launchpad Robert Wessel <robertwessel2@yahoo.com> - 2015-04-18 00:11 -0500
Re: Mecrisp on the TI Stellaris Launchpad David Brown <david.brown@hesbynett.no> - 2015-04-18 10:32 +0200
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-18 11:26 -0400
Re: Mecrisp on the TI Stellaris Launchpad David Brown <david.brown@hesbynett.no> - 2015-04-18 17:57 +0200
Re: Mecrisp on the TI Stellaris Launchpad Paul Rubin <no.email@nospam.invalid> - 2015-04-18 09:42 -0700
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-19 17:11 -0400
Re: Mecrisp on the TI Stellaris Launchpad Hans-Bernhard Bröker <HBBroeker@t-online.de> - 2015-04-18 12:19 +0200
Re: Mecrisp on the TI Stellaris Launchpad Dimiter_Popoff <dp@tgi-sci.com> - 2015-04-18 15:16 +0300
Re: Mecrisp on the TI Stellaris Launchpad David Brown <david.brown@hesbynett.no> - 2015-04-18 19:57 +0200
Re: Mecrisp on the TI Stellaris Launchpad Dimiter_Popoff <dp@tgi-sci.com> - 2015-04-18 23:11 +0300
Re: Mecrisp on the TI Stellaris Launchpad David Brown <david.brown@hesbynett.no> - 2015-04-19 21:32 +0200
Re: Mecrisp on the TI Stellaris Launchpad Dimiter_Popoff <dp@tgi-sci.com> - 2015-04-19 23:04 +0300
Re: Mecrisp on the TI Stellaris Launchpad anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-18 09:15 +0000
Re: Mecrisp on the TI Stellaris Launchpad David Brown <david.brown@hesbynett.no> - 2015-04-18 12:17 +0200
Re: Mecrisp on the TI Stellaris Launchpad anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-18 13:08 +0000
Re: Mecrisp on the TI Stellaris Launchpad David Brown <david.brown@hesbynett.no> - 2015-04-18 20:17 +0200
Re: Mecrisp on the TI Stellaris Launchpad anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-20 15:33 +0000
Re: Mecrisp on the TI Stellaris Launchpad rickman <gnuarm@gmail.com> - 2015-04-17 14:52 -0400
Re: Mecrisp on the TI Stellaris Launchpad albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-04-17 20:06 +0000
Re: Mecrisp on the TI Stellaris Launchpad lasselangwadtchristensen@gmail.com - 2015-04-16 16:18 -0700
Page 1 of 7 [1] 2 3 4 5 6 7 Next page →
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2015-04-02 21:08 -0400 |
| Subject | Mecrisp on the TI Stellaris Launchpad |
| Message-ID | <mfkp4c$s28$1@dont-email.me> |
I am trying out Mecrisp on a TI Stellaris Launchpad I have had for sometime. This is a program to be loaded onto the Launchpad over the debug USB port using the on board debugger chip. The Mecrisp instructions are shown here... ;------------------------------------------------------------------------------ Hardware and configuration for LM4F120 and TM4C123: ;------------------------------------------------------------------------------ Connect your cable to the Debug-USB-Port, set "PWR SELECT" switch to DEBUG and close VDD jumper. Flashing is possible with lm4flash: https://github.com/utzig/lm4tools On startup, this runs with internal PIOSC at 16 MHz, which is specified +-3% over whole temperature range. I can figure out the switch part and I found the debug port. But I am stumped with the lm4flash tool. I managed to download the directory from github, but I don't see an executable, only sources. Clearly I am expected to be able to compile C code on the PC, but it has likely been a decade since I've done that. I don't even have a C compiler on this machine. I guess the idea is that anyone wanting to use this flashing tool would be doing C development and so would be familiar with how to compile the sources. I really don't want to have to figure out where to get C tools for the PC and how to get them running. Heck, it might be easier in the long run to transcribe the program into Forth and run it that way. 800 line of source counting white space, but few comments... oh, the code uses libusb-1.0 for USB. I don't know how to deal with that. Crap... -- Rick
[toc] | [next] | [standalone]
| From | sbattazzo@gmail.com |
|---|---|
| Date | 2015-04-13 16:18 -0700 |
| Message-ID | <51cc1808-8727-4694-b94a-ee9d08209da4@googlegroups.com> |
| In reply to | #20606 |
On Thursday, April 2, 2015 at 6:08:24 PM UTC-7, rickman wrote: > I am trying out Mecrisp on a TI Stellaris Launchpad I have had for > sometime. This is a program to be loaded onto the Launchpad over the > debug USB port using the on board debugger chip. The Mecrisp > instructions are shown here... > > ;------------------------------------------------------------------------------ > Hardware and configuration for LM4F120 and TM4C123: > ;------------------------------------------------------------------------------ > Connect your cable to the Debug-USB-Port, > set "PWR SELECT" switch to DEBUG and > close VDD jumper. > > Flashing is possible with lm4flash: > https://github.com/utzig/lm4tools > > On startup, this runs with internal PIOSC at 16 MHz, > which is specified +-3% over whole temperature range. > > I can figure out the switch part and I found the debug port. But I am > stumped with the lm4flash tool. I managed to download the directory > from github, but I don't see an executable, only sources. Clearly I am > expected to be able to compile C code on the PC, but it has likely been > a decade since I've done that. I don't even have a C compiler on this > machine. > > I guess the idea is that anyone wanting to use this flashing tool would > be doing C development and so would be familiar with how to compile the > sources. I really don't want to have to figure out where to get C tools > for the PC and how to get them running. Heck, it might be easier in the > long run to transcribe the program into Forth and run it that way. 800 > line of source counting white space, but few comments... oh, the code > uses libusb-1.0 for USB. I don't know how to deal with that. Crap... > > -- > > Rick Should be very easy to take care of, unless you are hoping to do this on Windows. Assuming you are on Linux and depending which distro you use, either apt-get or yum install libusb-dev and type make from the lm4flash directory off of the github. That should pretty much be all!
[toc] | [prev] | [next] | [standalone]
| From | sbattazzo@gmail.com |
|---|---|
| Date | 2015-04-13 16:25 -0700 |
| Message-ID | <7510283a-ae20-40ce-87f9-6ee97e5b7565@googlegroups.com> |
| In reply to | #20649 |
On Monday, April 13, 2015 at 4:18:08 PM UTC-7, sbat...@gmail.com wrote: > On Thursday, April 2, 2015 at 6:08:24 PM UTC-7, rickman wrote: > > I am trying out Mecrisp on a TI Stellaris Launchpad I have had for > > sometime. This is a program to be loaded onto the Launchpad over the > > debug USB port using the on board debugger chip. The Mecrisp > > instructions are shown here... > > > > ;------------------------------------------------------------------------------ > > Hardware and configuration for LM4F120 and TM4C123: > > ;------------------------------------------------------------------------------ > > Connect your cable to the Debug-USB-Port, > > set "PWR SELECT" switch to DEBUG and > > close VDD jumper. > > > > Flashing is possible with lm4flash: > > https://github.com/utzig/lm4tools > > > > On startup, this runs with internal PIOSC at 16 MHz, > > which is specified +-3% over whole temperature range. > > > > I can figure out the switch part and I found the debug port. But I am > > stumped with the lm4flash tool. I managed to download the directory > > from github, but I don't see an executable, only sources. Clearly I am > > expected to be able to compile C code on the PC, but it has likely been > > a decade since I've done that. I don't even have a C compiler on this > > machine. > > > > I guess the idea is that anyone wanting to use this flashing tool would > > be doing C development and so would be familiar with how to compile the > > sources. I really don't want to have to figure out where to get C tools > > for the PC and how to get them running. Heck, it might be easier in the > > long run to transcribe the program into Forth and run it that way. 800 > > line of source counting white space, but few comments... oh, the code > > uses libusb-1.0 for USB. I don't know how to deal with that. Crap... > > > > -- > > > > Rick > > Should be very easy to take care of, unless you are hoping to do this on Windows. > Assuming you are on Linux and depending which distro you use, either apt-get or yum install libusb-dev and type make from the lm4flash directory off of the github. That should pretty much be all! OK I gave it a quick try on my Ubuntu vm out of curiosity. I already had the libusb-dev package installed, but the makefile is actually set up to depend on the 1.0 specific version of that package. Turns out that's fixed by just doing "sudo apt-get install libusb-1.0-0-dev" which took just a few seconds to do, then typing "make" worked out of the box with the makefile from that repository. Hope that helps! I highly doubt it would work under Windows but I imagine you can use another flasher utility (with an exe out of the box) in place of lm4flash in that case. Steve
[toc] | [prev] | [next] | [standalone]
| From | sbattazzo@gmail.com |
|---|---|
| Date | 2015-04-13 16:33 -0700 |
| Message-ID | <c46ca115-10e2-45ea-b0f9-dfd5f7d078b5@googlegroups.com> |
| In reply to | #20650 |
On Monday, April 13, 2015 at 4:25:56 PM UTC-7, sbat...@gmail.com wrote: > On Monday, April 13, 2015 at 4:18:08 PM UTC-7, sbat...@gmail.com wrote: > > On Thursday, April 2, 2015 at 6:08:24 PM UTC-7, rickman wrote: > > > I am trying out Mecrisp on a TI Stellaris Launchpad I have had for > > > sometime. This is a program to be loaded onto the Launchpad over the > > > debug USB port using the on board debugger chip. The Mecrisp > > > instructions are shown here... > > > > > > ;------------------------------------------------------------------------------ > > > Hardware and configuration for LM4F120 and TM4C123: > > > ;------------------------------------------------------------------------------ > > > Connect your cable to the Debug-USB-Port, > > > set "PWR SELECT" switch to DEBUG and > > > close VDD jumper. > > > > > > Flashing is possible with lm4flash: > > > https://github.com/utzig/lm4tools > > > > > > On startup, this runs with internal PIOSC at 16 MHz, > > > which is specified +-3% over whole temperature range. > > > > > > I can figure out the switch part and I found the debug port. But I am > > > stumped with the lm4flash tool. I managed to download the directory > > > from github, but I don't see an executable, only sources. Clearly I am > > > expected to be able to compile C code on the PC, but it has likely been > > > a decade since I've done that. I don't even have a C compiler on this > > > machine. > > > > > > I guess the idea is that anyone wanting to use this flashing tool would > > > be doing C development and so would be familiar with how to compile the > > > sources. I really don't want to have to figure out where to get C tools > > > for the PC and how to get them running. Heck, it might be easier in the > > > long run to transcribe the program into Forth and run it that way. 800 > > > line of source counting white space, but few comments... oh, the code > > > uses libusb-1.0 for USB. I don't know how to deal with that. Crap... > > > > > > -- > > > > > > Rick > > Last reply to this thread.. if you're on Windows it looks like TI provides what you need here: http://www.ti.com/tool/LMFLASHPROGRAMMER I'd be more than willing to bet it can accomplish the same task, though it's TI proprietary rather than open source for Linux. Whoever wrote up the instructions for that Mecrisp just probably hasn't tried it out or thought about .
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2015-04-13 21:45 -0400 |
| Message-ID | <mghre4$2b2$1@dont-email.me> |
| In reply to | #20651 |
On 4/13/2015 7:33 PM, sbattazzo@gmail.com wrote: > On Monday, April 13, 2015 at 4:25:56 PM UTC-7, sbat...@gmail.com wrote: >> On Monday, April 13, 2015 at 4:18:08 PM UTC-7, sbat...@gmail.com wrote: >>> On Thursday, April 2, 2015 at 6:08:24 PM UTC-7, rickman wrote: >>>> I am trying out Mecrisp on a TI Stellaris Launchpad I have had for >>>> sometime. This is a program to be loaded onto the Launchpad over the >>>> debug USB port using the on board debugger chip. The Mecrisp >>>> instructions are shown here... >>>> >>>> ;------------------------------------------------------------------------------ >>>> Hardware and configuration for LM4F120 and TM4C123: >>>> ;------------------------------------------------------------------------------ >>>> Connect your cable to the Debug-USB-Port, >>>> set "PWR SELECT" switch to DEBUG and >>>> close VDD jumper. >>>> >>>> Flashing is possible with lm4flash: >>>> https://github.com/utzig/lm4tools >>>> >>>> On startup, this runs with internal PIOSC at 16 MHz, >>>> which is specified +-3% over whole temperature range. >>>> >>>> I can figure out the switch part and I found the debug port. But I am >>>> stumped with the lm4flash tool. I managed to download the directory >>>> from github, but I don't see an executable, only sources. Clearly I am >>>> expected to be able to compile C code on the PC, but it has likely been >>>> a decade since I've done that. I don't even have a C compiler on this >>>> machine. >>>> >>>> I guess the idea is that anyone wanting to use this flashing tool would >>>> be doing C development and so would be familiar with how to compile the >>>> sources. I really don't want to have to figure out where to get C tools >>>> for the PC and how to get them running. Heck, it might be easier in the >>>> long run to transcribe the program into Forth and run it that way. 800 >>>> line of source counting white space, but few comments... oh, the code >>>> uses libusb-1.0 for USB. I don't know how to deal with that. Crap... >>>> >>>> -- >>>> >>>> Rick >>> > > Last reply to this thread.. if you're on Windows it looks like TI provides what you need here: http://www.ti.com/tool/LMFLASHPROGRAMMER > > I'd be more than willing to bet it can accomplish the same task, though it's TI proprietary rather than open source for Linux. Whoever wrote up the instructions for that Mecrisp just probably hasn't tried it out or thought about . Yes, I'm on windows and have downloaded the TI tool, but not yet tried to use it. I would like to run this on a raspberry pi as it is much smaller and suits my lab use better in some respects. I will try installing lm4flash the way you describe. There is a bit of irony in that to use a Forth tool I need to understand how to compile a C program. lol I am rather weary of learning all the ins and outs of complex tool, never knowing for sure what they are doing or if I am using them correctly. That's the main motivator for using Forth on this target. I'm trying to implement a rather simple function and would like to have a simple tool. Even once I get this installed on the host machine and I get Mecrisp installed on the target, I will still need to learn the details of using Mecrisp. At least then I am learning something I expect to use many times in the future. I plan to help with the documentation of Mecrisp. I think that is the big weakness of most open source tools, rather limited docs. -- Rick
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2015-04-13 21:47 -0400 |
| Message-ID | <mghrhp$2b3$1@dont-email.me> |
| In reply to | #20652 |
On 4/13/2015 9:45 PM, rickman wrote: > On 4/13/2015 7:33 PM, sbattazzo@gmail.com wrote: >> On Monday, April 13, 2015 at 4:25:56 PM UTC-7, sbat...@gmail.com wrote: >>> On Monday, April 13, 2015 at 4:18:08 PM UTC-7, sbat...@gmail.com wrote: >>>> On Thursday, April 2, 2015 at 6:08:24 PM UTC-7, rickman wrote: >>>>> I am trying out Mecrisp on a TI Stellaris Launchpad I have had for >>>>> sometime. This is a program to be loaded onto the Launchpad over the >>>>> debug USB port using the on board debugger chip. The Mecrisp >>>>> instructions are shown here... >>>>> >>>>> ;------------------------------------------------------------------------------ >>>>> >>>>> Hardware and configuration for LM4F120 and TM4C123: >>>>> ;------------------------------------------------------------------------------ >>>>> >>>>> Connect your cable to the Debug-USB-Port, >>>>> set "PWR SELECT" switch to DEBUG and >>>>> close VDD jumper. >>>>> >>>>> Flashing is possible with lm4flash: >>>>> https://github.com/utzig/lm4tools >>>>> >>>>> On startup, this runs with internal PIOSC at 16 MHz, >>>>> which is specified +-3% over whole temperature range. >>>>> >>>>> I can figure out the switch part and I found the debug port. But I am >>>>> stumped with the lm4flash tool. I managed to download the directory >>>>> from github, but I don't see an executable, only sources. Clearly >>>>> I am >>>>> expected to be able to compile C code on the PC, but it has likely >>>>> been >>>>> a decade since I've done that. I don't even have a C compiler on this >>>>> machine. >>>>> >>>>> I guess the idea is that anyone wanting to use this flashing tool >>>>> would >>>>> be doing C development and so would be familiar with how to compile >>>>> the >>>>> sources. I really don't want to have to figure out where to get C >>>>> tools >>>>> for the PC and how to get them running. Heck, it might be easier >>>>> in the >>>>> long run to transcribe the program into Forth and run it that way. >>>>> 800 >>>>> line of source counting white space, but few comments... oh, the code >>>>> uses libusb-1.0 for USB. I don't know how to deal with that. Crap... >>>>> >>>>> -- >>>>> >>>>> Rick >>>> >> >> Last reply to this thread.. if you're on Windows it looks like TI >> provides what you need here: http://www.ti.com/tool/LMFLASHPROGRAMMER >> >> I'd be more than willing to bet it can accomplish the same task, >> though it's TI proprietary rather than open source for Linux. Whoever >> wrote up the instructions for that Mecrisp just probably hasn't tried >> it out or thought about . > > Yes, I'm on windows and have downloaded the TI tool, but not yet tried > to use it. I would like to run this on a raspberry pi as it is much > smaller and in some respects suits my lab use better than a PC. I will try > installing lm4flash the way you describe. > > There is a bit of irony in that to use a Forth tool I need to understand > how to compile a C program. lol I am rather weary of learning all the > ins and outs of complex tool, never knowing for sure what they are doing > or if I am using them correctly. That's the main motivator for using > Forth on this target. I'm trying to implement a rather simple function > and would like to have a simple tool. Even once I get this installed on > the host machine and I get Mecrisp installed on the target, I will still > need to learn the details of using Mecrisp. At least then I am learning > something I expect to use many times in the future. I plan to help with > the documentation of Mecrisp. I think that is the big weakness of most > open source tools, rather limited docs. Oh, I forgot to say thanks. Thanks :) -- Rick
[toc] | [prev] | [next] | [standalone]
| From | sbattazzo@gmail.com |
|---|---|
| Date | 2015-04-14 07:33 -0700 |
| Message-ID | <7d1d9121-8a54-4763-800a-1217d535cfae@googlegroups.com> |
| In reply to | #20653 |
> > Oh, I forgot to say thanks. Thanks :) > > -- > > Rick Sure thing! That's how open source software tends to be a lot of the time, it is built for Linux or similar, and comes with a makefile, maybe a configure script, and not a lot of documentation. If you're on Linux, the C compiler is already there 99% of the time (Raspberry Pi should have a compiler on board as well) so as long as you have the library sources you need you can usually get away with just typing "make" and when you get an error, somebody on one of the Linux forums or stackoverflow has probably asked about it already.
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2015-04-14 14:38 -0400 |
| Message-ID | <mgjmps$jed$1@dont-email.me> |
| In reply to | #20654 |
On 4/14/2015 10:33 AM, sbattazzo@gmail.com wrote: > >> >> Oh, I forgot to say thanks. Thanks :) >> >> -- >> >> Rick > > Sure thing! > > That's how open source software tends to be a lot of the time, it is built for Linux or similar, and comes with a makefile, maybe a configure script, and not a lot of documentation. If you're on Linux, the C compiler is already there 99% of the time (Raspberry Pi should have a compiler on board as well) so as long as you have the library sources you need you can usually get away with just typing "make" and when you get an error, somebody on one of the Linux forums or stackoverflow has probably asked about it already. Yeah, the rPi was an afterthought. I get tired of lugging my laptop around and there really isn't a lot of space on the work bench. Trouble with the pi is that it is far too slow for useful for web browsing. When I have a problem I still have to go back to the laptop to research it and possibly download something that then has to be transferred to the pi by sneaker net. I guess in theory they could be networked. I had that working on my old Win2K PCs some years back, thanks to World of Windows Networking (which appears to have been sold and is no longer very useful). But with Vista and now Win8 I can't get any of my PCs to talk to each other. Compared to the average person I am very computer literate, but when it comes to dealing with Microsoft, I just can't keep up with them breaking everything all the time. -- Rick
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2015-04-16 14:24 -0700 |
| Message-ID | <ec2dd465-48dc-49fa-8584-8fa1183ebbc8@googlegroups.com> |
| In reply to | #20649 |
On Monday, April 13, 2015 at 7:18:08 PM UTC-4, sbat...@gmail.com wrote: > On Thursday, April 2, 2015 at 6:08:24 PM UTC-7, rickman wrote: > > I am trying out Mecrisp on a TI Stellaris Launchpad I have had for > > sometime. This is a program to be loaded onto the Launchpad over the > > debug USB port using the on board debugger chip. The Mecrisp > > instructions are shown here... > > > > ;------------------------------------------------------------------------------ > > Hardware and configuration for LM4F120 and TM4C123: > > ;------------------------------------------------------------------------------ > > Connect your cable to the Debug-USB-Port, > > set "PWR SELECT" switch to DEBUG and > > close VDD jumper. > > > > Flashing is possible with lm4flash: > > https://github.com/utzig/lm4tools > > > > On startup, this runs with internal PIOSC at 16 MHz, > > which is specified +-3% over whole temperature range. > > > > I can figure out the switch part and I found the debug port. But I am > > stumped with the lm4flash tool. I managed to download the directory > > from github, but I don't see an executable, only sources. Clearly I am > > expected to be able to compile C code on the PC, but it has likely been > > a decade since I've done that. I don't even have a C compiler on this > > machine. > > > > I guess the idea is that anyone wanting to use this flashing tool would > > be doing C development and so would be familiar with how to compile the > > sources. I really don't want to have to figure out where to get C tools > > for the PC and how to get them running. Heck, it might be easier in the > > long run to transcribe the program into Forth and run it that way. 800 > > line of source counting white space, but few comments... oh, the code > > uses libusb-1.0 for USB. I don't know how to deal with that. Crap... > > > > -- > > > > Rick > > Should be very easy to take care of, unless you are hoping to do this on Windows. > Assuming you are on Linux and depending which distro you use, either apt-get or yum install libusb-dev and type make from the lm4flash directory off of the github. That should pretty much be all! I took the 5 minutes to do this today... well, more like 15 with me stumbling around Linux on the rPi. I did manage to get lm4flash to compile, but I can't seem to figure out how to run it. I type lm4flash at the command line, but it says "command not found". The file has no visible extension. Is that expected? What am I missing?
[toc] | [prev] | [next] | [standalone]
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Date | 2015-04-16 15:11 -0700 |
| Message-ID | <87618vyb8d.fsf@jester.gateway.pace.com> |
| In reply to | #20659 |
rickman <gnuarm@gmail.com> writes: > compile, but I can't seem to figure out how to run it. I type > lm4flash at the command line, but it says "command not found". The > file has no visible extension. Is that expected? What am I missing? Try ./lm4flash
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2015-04-16 23:37 -0400 |
| Message-ID | <mgpv33$469$1@dont-email.me> |
| In reply to | #20660 |
On 4/16/2015 6:11 PM, Paul Rubin wrote: > rickman <gnuarm@gmail.com> writes: >> compile, but I can't seem to figure out how to run it. I type >> lm4flash at the command line, but it says "command not found". The >> file has no visible extension. Is that expected? What am I missing? > > Try ./lm4flash Yes, I figured that out. It seems the current working directory is not considered under Linux for finding executables... really!? I got things working to the point that I could run the program with the binary file and used the -v and -E options. I get an error message saying "Unable to find any ICDI devices". I am having to share the USB port between the launchpad and the mouse. I can't think that is the problem though. I set up the command, unplug the mouse, plug in the launchpad, give it a few seconds and hit return to run the programmer. I'm using the debug port on the launchpad, the switch is set to debug (otherwise it wouldn't have power). The RGB LED will cycle the colors, but as soon as I hit any key on the keyboard it turns Green and after a pause resumes the color cycle. I find that odd since the keyboard is on the rPi on the other port. I can't imagine the power on the USB port is not sufficient to power this dongle. I have a powered hub on order, but it won't be here for a week or two. I'm hoping this is not the problem. -- Rick
[toc] | [prev] | [next] | [standalone]
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Date | 2015-04-16 20:59 -0700 |
| Message-ID | <87lhhrwgkf.fsf@jester.gateway.pace.com> |
| In reply to | #20662 |
rickman <gnuarm@gmail.com> writes: > Yes, I figured that out. It seems the current working directory is > not considered under Linux for finding executables... really!? Yes, it's so that if you type something like "ls" in a directory, you get the normal system ls instead of a possibly malicious one that was sitting in the directory. I guess this was more of an issue in the timesharing era.
[toc] | [prev] | [next] | [standalone]
| From | Mel Wilson <mwilson@the-wire.com> |
|---|---|
| Date | 2015-04-17 13:16 +0000 |
| Message-ID | <mgr12k$gue$1@dont-email.me> |
| In reply to | #20663 |
On Thu, 16 Apr 2015 20:59:28 -0700, Paul Rubin wrote: > rickman <gnuarm@gmail.com> writes: >> Yes, I figured that out. It seems the current working directory is not >> considered under Linux for finding executables... really!? > > Yes, it's so that if you type something like "ls" in a directory, you > get the normal system ls instead of a possibly malicious one that was > sitting in the directory. I guess this was more of an issue in the > timesharing era. If you must have this, you can get it with a command like (the bash version here) PATH+=:. which makes the current directory, whatever it is or will be, the last directory searched for commands. I never do this. I like the predictability. "./" is always available.
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2015-04-17 00:19 -0400 |
| Message-ID | <mgq1j5$b0a$1@dont-email.me> |
| In reply to | #20662 |
On 4/16/2015 11:37 PM, rickman wrote: > On 4/16/2015 6:11 PM, Paul Rubin wrote: >> rickman <gnuarm@gmail.com> writes: >>> compile, but I can't seem to figure out how to run it. I type >>> lm4flash at the command line, but it says "command not found". The >>> file has no visible extension. Is that expected? What am I missing? >> >> Try ./lm4flash > > Yes, I figured that out. It seems the current working directory is not > considered under Linux for finding executables... really!? > > I got things working to the point that I could run the program with the > binary file and used the -v and -E options. I get an error message > saying "Unable to find any ICDI devices". > > I am having to share the USB port between the launchpad and the mouse. I > can't think that is the problem though. I set up the command, unplug > the mouse, plug in the launchpad, give it a few seconds and hit return > to run the programmer. I'm using the debug port on the launchpad, the > switch is set to debug (otherwise it wouldn't have power). The RGB LED > will cycle the colors, but as soon as I hit any key on the keyboard it > turns Green and after a pause resumes the color cycle. I find that odd > since the keyboard is on the rPi on the other port. I can't imagine the > power on the USB port is not sufficient to power this dongle. > > I have a powered hub on order, but it won't be here for a week or two. > I'm hoping this is not the problem. I think that is the problem. I found mention of a program, lsusb, which lists the USB devices. 1st time the launchpad didn't show up, 2nd time it did, 3rd time it didn't. 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. This time when I ran the lm4flash command it seemed to work. Maybe on the higher current side the meter was dropping enough voltage that it was less than marginal. Now at least it has a shot at working and clearly I need a powered hub for anything on the rPi USB ports. Seems they did a poor job on power distribution on the original design. The rPi 2 model B is supposed to be better. It can also be used for real PC work... like web browsing. Now I have to figure out how to get a terminal emulator working on the rPi. Can't be too hard... I just have to research it on my laptop rather than on the rPi. -- Rick
[toc] | [prev] | [next] | [standalone]
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Date | 2015-04-16 21:56 -0700 |
| Message-ID | <87h9sfwdy1.fsf@jester.gateway.pace.com> |
| In reply to | #20664 |
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.
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2015-04-17 14:47 -0400 |
| Message-ID | <mgrket$1d0$1@dont-email.me> |
| In reply to | #20665 |
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. -- Rick
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2015-04-17 15:12 -0400 |
| Subject | WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking |
| Message-ID | <mgrlsi$6ss$1@dont-email.me> |
| In reply to | #20674 |
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.
--
Rick
[toc] | [prev] | [next] | [standalone]
| From | Martin Gregorie <martin@address-in-sig.invalid> |
|---|---|
| Date | 2015-04-17 20:14 +0000 |
| Subject | Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking |
| Message-ID | <mgrpjr$ilp$1@dont-email.me> |
| In reply to | #20676 |
On Fri, 17 Apr 2015 15:12:13 -0400, rickman wrote: > 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. > This has been rewrapped by Pan because it needed to add "> " at the beginning of each line, but as received, your appended text was wrapped at between 71 and 74 characters. I think it wraps whenever the next word would make the line longer that 74 chars, which is a bit odd seeing that you set the limit at 72. The last word at the end of each line in the para were: that Anyone you at now. -- martin@ | Martin Gregorie gregorie. | Essex, UK org |
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2015-04-17 16:59 -0400 |
| Subject | Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking |
| Message-ID | <mgrs5s$um9$1@dont-email.me> |
| In reply to | #20680 |
On 4/17/2015 4:14 PM, Martin Gregorie wrote: > On Fri, 17 Apr 2015 15:12:13 -0400, rickman wrote: > >> 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. >> > This has been rewrapped by Pan because it needed to add "> " at the > beginning of each line, but as received, your appended text was wrapped > at between 71 and 74 characters. I think it wraps whenever the next word > would make the line longer that 74 chars, which is a bit odd seeing that > you set the limit at 72. The last word at the end of each line in the > para were: > > that > Anyone > you > at > now. Thanks. The 72 columns was just my recollection. I can't find the setting now. -- Rick
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2015-04-18 10:00 +0200 |
| Subject | Re: WAS: Mecrisp on the TI Stellaris Launchpad IS: Thunderbird Line Breaking |
| Message-ID | <mgt2sp$6s0$1@dont-email.me> |
| In reply to | #20676 |
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.
[toc] | [prev] | [next] | [standalone]
Page 1 of 7 [1] 2 3 4 5 6 7 Next page →
Back to top | Article view | comp.arch.embedded
csiph-web