Hello Keith,
On 07/09/2012 03:05 AM, Keith Amidon wrote:
> {-- Sun, 08 Jul 2012 20:01:02 +0200: Erich wrote: --}
>
>Erich> More info below ...
>>> I found a minor thing that puzzles me:
>>> |C| 11|\ PORTD 7 portpin: PD.7 ( define portD pin #7)
>>> |E| 12|\ PD.7 high ( turn por
{-- Sun, 08 Jul 2012 20:01:02 +0200: Erich wrote: --}
Erich> More info below ...
>> I found a minor thing that puzzles me:
>> |C| 11|\ PORTD 7 portpin: PD.7 ( define portD pin #7)
>> |E| 12|\ PD.7 high ( turn portD pin #7 on, i.e. set it high-level)
>> |E=Illegal nested comment
>> mak
Hi all,
>>
>>Matthias> I collect the changes in the repository at
>>Matthias>
>> http://amforth.svn.sourceforge.net/viewvc/amforth/trunk/tools/amforth-term.py?view=log
Just for the record: I renamed the tool to amforth-shell, You'll find it
here:
http://amforth.svn.sourceforge.net/viewv
More info below ...
> I found a minor thing that puzzles me:
>
> |I=mcudef
> |I=using device.py for atmega32
> |F=/home/ew/Forth/atmega/46_trunk-2/lib/bitnames.frt
> |C| 1|\ V 1.3 02.11.2007
> |W| 2|
> |C| 3|\ Code: Matthias Trute
> |C| 4|\ Text: M.Kalus
> |W| 5|
> |C| 6|\ A named port pin puts a
Hello Keith!
On 07/05/2012 06:29 PM, Keith Amidon wrote:
>
>Matthias> I collect the changes in the repository at
>Matthias>
> http://amforth.svn.sourceforge.net/viewvc/amforth/trunk/tools/amforth-term.py?view=log
>
I finally got around to try out the new upload tool.
The result is nothi
>
> Actually, my motivation was a lot simpler. I wasn't sure if the regular
> expression I use to match an error being indicated by the amforth
> interpreter really covered all cases. That expression (without the
> delimiting double quotes included below) is:
>
>" \?\? -\d+ \d+ \r\n> $"
{-- Tue, 03 Jul 2012 20:02:55 +0200: Matthias wrote: --}
Matthias> Editing the source files builds a rather high barrier for
Matthias> your excellent tool. For me your ideas sound like
Matthias> introducing concepts like Design By Contract
Matthias> (http://en.wikipedia.org/wiki/Design_by_
Hi Keith,
> Ah, I think this is working as I intended but the behavior may be
> somewhat surprising to others, I'm not sure. I made the assumption
> that well behaved upload files never generate output because in my
> use cases for the class I was helping develop they consisted of one
> of tw
.. edit at error line - it does not start automaticaly. I have to
open the editor with
#edit
as the user guide says :)
p.
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security a
Keith,
> 2) The feature of opening the editor to the line
> where an upload error
> occurred only works for editors for which the
> script knows the
> appropriate command line syntax.
the PN editor opens and jumps to the line with following command (ie
to the line 3)
C:\WinAVR\pn\pn.exe --line
Keith
> version of python didn't
> come with the required readline support.
I am using python 2.7, installed long time back. No idea where it
comes from :)
> 1) Pass an additional option to the script, for
> example
>
> "--editor=C:\WinAVR\pn\pn.exe"
Yes, it works, I did a .bat file where I
{-- Tue, 03 Jul 2012 11:23:56 +0200 (CEST): pito wrote: --}
pito> Hi Keith, I'm trying to run your script under winXP. I had to
pito> install "pyreadline-1.7.1.win32.exe" in order to get imported
pito> the readline.
Interesting. I wasn't aware that the Windows version of python didn't
co
a1284P)>
thnks,
pito
- PŮVODNÍ ZPRÁVA -
Od: "Keith Amidon"
Komu: "Matthias Trute"
Předmět: Re: [Amforth] New forth interaction script
Datum: 3.7.2012 - 3:18:51
> {-- Sat, 30 Jun 2012 15:54:09 +0200: Matthias
> wrote: --}
> >> Could you reply with an exam
{-- Sat, 30 Jun 2012 15:54:09 +0200: Matthias wrote: --}
>> Could you reply with an example showing the exact command line
>> options you are giving and the output you get when it does not
>> work.
Matthias>
Matthias> With the --no-error-on-output option everything works well.
Ah, I t
hi Keith,
> Could you reply with an example showing the exact command line options
> you are giving and the output you get when it does not work.
mt@ayla:amforth/tools$ ./amforth-term.py -p /dev/ttyUSB2 ./test.frt --debug
|a( )\n
|s( )\n->\r\n|\n-> ok\r\n|
|r( )> \r\n ok
|F=mcudef
|a(
{-- Fri, 29 Jun 2012 19:38:03 +0200: Matthias wrote: --}
Matthias> short: its a great tool, by far the best I know. I very much
Matthias> prefer it over my own upload script now :)
Thanks! I'm really glad to hear you like it.
Matthias> I have sometimes problems to get it starting, the op
Hi Keith,
> Returning after a month+ of being consumed by other things, I was
> wondering if anyone got a chance to take a look at the interaction
> script I sent to the list.
I did and I forgot to give you feedback :(
short: its a great tool, by far the best I know. I very much prefer
it over
{-- Tue, 08 May 2012 09:35:52 -0700: Keith wrote: --}
Keith> I've been helping to develop and conduct a class that
Keith> introduces kids to electronics, computer engineering, and
Keith> software development concepts using Arduino & ATMega
Keith> microcontrollers. We chose to use AMForth
I've been helping to develop and conduct a class that introduces kids to
electronics, computer engineering, and software development concepts
using Arduino & ATMega microcontrollers. We chose to use AMForth for a
part of the programming section of the class and were concerned the kids
would have t
19 matches
Mail list logo
