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

Groups > comp.lang.forth > #38915 > unrolled thread

Talking to an Embedded Target with Mecrisp

Back to article view | Back to comp.lang.forth

Contents

  Talking to an Embedded Target with Mecrisp rickman <gnuarm@gmail.com> - 2015-05-09 16:59 -0400
    Re: Talking to an Embedded Target with Mecrisp albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-05-09 22:16 +0000
    Re: Talking to an Embedded Target with Mecrisp rickman <gnuarm@gmail.com> - 2015-05-09 18:27 -0400
    Re: Talking to an Embedded Target with Mecrisp "Elizabeth D. Rather" <erather@forth.com> - 2015-05-09 13:31 -1000
      Re: Talking to an Embedded Target with Mecrisp Matthias Koch <matthias.koch@hot.uni-hannover.de> - 2015-05-12 16:26 +0200
        Re: Talking to an Embedded Target with Mecrisp albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-05-12 17:08 +0000
    Re: Talking to an Embedded Target with Mecrisp Bernd Paysan <bernd.paysan@gmx.de> - 2015-05-10 02:06 +0200
      Re: Talking to an Embedded Target with Mecrisp rickman <gnuarm@gmail.com> - 2015-05-09 22:35 -0400

#38915 — Talking to an Embedded Target with Mecrisp

I have an embedded ARM board running Mecrisp.  Because installing the 
driver on a PC was rather ugly I installed it on a raspberry pi.  I can 
talk to the pi through SSH from a PC.  I run microcom on the pi to talk 
to the embedded board over a USB virtual serial port.  That's all great.

But I can't figure out how to get the files into the compiler.  Normally 
a Forth tool uses a command to load files, but this target has no file 
system.  The command line can be used to load code, but it seems 
definitions must all be on one line.

Ignoring the single line definition issue, neither of the tools I am 
using (Putty on the PC and microcom on the rPi) have a facility to send 
files into the command line.  When I use copy and paste there seem to be 
overrun errors and some of the text is lost.

Mecrisp doesn't have much of a following yet so I am not finding a lot 
on the web on how others have used this tool.  I did manage to find one 
site where someone changed the character sent by CR to a CR rather than 
a LF, but I worked around that problem some time back.  Even then the 
guts of his info was moved to another web site and that one is gone.

I have code to test.  I just wish I could test it.  :(

-- 

Rick

[toc] | [next] | [standalone]

#38917

In article <milscu$hj2$1@dont-email.me>, rickman  <gnuarm@gmail.com> wrote:
>I have an embedded ARM board running Mecrisp.  Because installing the
>driver on a PC was rather ugly I installed it on a raspberry pi.  I can
>talk to the pi through SSH from a PC.  I run microcom on the pi to talk
>to the embedded board over a USB virtual serial port.  That's all great.
>
>But I can't figure out how to get the files into the compiler.  Normally
>a Forth tool uses a command to load files, but this target has no file
>system.  The command line can be used to load code, but it seems
>definitions must all be on one line.

That is pretty essential. For the Launchpad I've made a simple Forth
communication program, that works nice with a version of noforth that
I modified to use a handshake. New versions of noforth have a handshake
that work with the communication programs designed for the German forth
4e4th.
You can upload files, but you can also drop a file onto the console
window, and cut and paste into the console window. And still use
the command history and command editing from windows, or linux.
I would have published it, but like all communications programs it is
unreliable.

The essential point is, you get nowhere without knowing something about
your boards communication protocol.  An exception are sophisticated
programs like Kermit with decades of debugging behind them. Kermit
can do everything you want and get sitations under control after
I've messed up with other programs. It has those provisions for
crappy boards, where the last resort is to send files
then wait for a zillion ms after each line to make sure there
was enough time to compile it.
I can't believe you make due with a simplistic program like microcom,
while well-known established communication programs are available for
the Raspberry pi, like kermit and minicom.

>
>Ignoring the single line definition issue, neither of the tools I am
>using (Putty on the PC and microcom on the rPi) have a facility to send
>files into the command line.  When I use copy and paste there seem to be
>overrun errors and some of the text is lost.

Of course. If you can't tell your communication program to wait after
each line, just junk it.

>
>Mecrisp doesn't have much of a following yet so I am not finding a lot
>on the web on how others have used this tool.  I did manage to find one
>site where someone changed the character sent by CR to a CR rather than
>a LF, but I worked around that problem some time back.  Even then the
>guts of his info was moved to another web site and that one is gone.
>
>I have code to test.  I just wish I could test it.  :(

You're not alone. Our experience with lots of single board computers
in the Dutch forth gg is that nearly everybody has to experiment with
communication programs until they find something that works on their
computer.
>
>--
>
>Rick
-- 
Albert van der Horst, UTRECHT,THE NETHERLANDS
Economic growth -- being exponential -- ultimately falters.
albert@spe&ar&c.xs4all.nl &=n http://home.hccnet.nl/a.w.m.van.der.horst

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

#38918

On 5/9/2015 4:59 PM, rickman wrote:
> I have an embedded ARM board running Mecrisp.  Because installing the
> driver on a PC was rather ugly I installed it on a raspberry pi.  I can
> talk to the pi through SSH from a PC.  I run microcom on the pi to talk
> to the embedded board over a USB virtual serial port.  That's all great.
>
> But I can't figure out how to get the files into the compiler.  Normally
> a Forth tool uses a command to load files, but this target has no file
> system.  The command line can be used to load code, but it seems
> definitions must all be on one line.
>
> Ignoring the single line definition issue, neither of the tools I am
> using (Putty on the PC and microcom on the rPi) have a facility to send
> files into the command line.  When I use copy and paste there seem to be
> overrun errors and some of the text is lost.
>
> Mecrisp doesn't have much of a following yet so I am not finding a lot
> on the web on how others have used this tool.  I did manage to find one
> site where someone changed the character sent by CR to a CR rather than
> a LF, but I worked around that problem some time back.  Even then the
> guts of his info was moved to another web site and that one is gone.
>
> I have code to test.  I just wish I could test it.  :(

Shoot.  I have been beating my head on this one all day and I finally 
found it.  On typing some definitions manually on the Mecrisp command 
line I found it does let you spread word definitions over multiple 
lines.  So I dug into the settings on the Putty program and found 
something called "Drag and Drop" settings.  Seems if I drag the file 
over the Putty window it sends the file with a programmable inter-line 
delay.

So I have some basic compilation capability working from a PC through 
the rPi and likely can have it working on the rPi if I use Putty or 
Extra-Putty.

I am going to look at e4thcom next.  That is supposed to run on both the 
rPi and the PC.  I just don't know if it supports SSH which would be 
needed on the PC.  But I suppose I can run it on the rPi and continue 
using Putty on the PC.

-- 

Rick

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

#38919

On 5/9/15 10:59 AM, rickman wrote:
> I have an embedded ARM board running Mecrisp.  Because installing the
> driver on a PC was rather ugly I installed it on a raspberry pi.  I can
> talk to the pi through SSH from a PC.  I run microcom on the pi to talk
> to the embedded board over a USB virtual serial port.  That's all great.
>
> But I can't figure out how to get the files into the compiler.  Normally
> a Forth tool uses a command to load files, but this target has no file
> system.  The command line can be used to load code, but it seems
> definitions must all be on one line.
>
> Ignoring the single line definition issue, neither of the tools I am
> using (Putty on the PC and microcom on the rPi) have a facility to send
> files into the command line.  When I use copy and paste there seem to be
> overrun errors and some of the text is lost.
>
> Mecrisp doesn't have much of a following yet so I am not finding a lot
> on the web on how others have used this tool.  I did manage to find one
> site where someone changed the character sent by CR to a CR rather than
> a LF, but I worked around that problem some time back.  Even then the
> guts of his info was moved to another web site and that one is gone.
>
> I have code to test.  I just wish I could test it.  :(
>

You have neatly summed up the reason why many people prefer an 
interactive cross-compiler :-)

Cheers,
Elizabeth

-- 
==================================================
Elizabeth D. Rather   (US & Canada)   800-55-FORTH
FORTH Inc.                         +1 310.999.6784
5959 West Century Blvd. Suite 700
Los Angeles, CA 90045
http://www.forth.com

"Forth-based products and Services for real-time
applications since 1973."
==================================================

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

#39022

> You have neatly summed up the reason why many people prefer an 
> interactive cross-compiler :-)
> 
> Cheers,
> Elizabeth
> 

Dear Elizabeth,

mostly I wish for an interface with interlocked handshake like IEEE-488/GPIB we still have in lab equipment to become standard again. It would relief us of all terminal timing issues :-) I am sure you implemented such a thing on top of the internal communication line between host and target.

Matthias

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

#39034

In article <mit2j2$pp4$1@newsserver.rrzn.uni-hannover.de>,
Matthias Koch  <matthias.koch@hot.uni-hannover.de> wrote:
>
>> You have neatly summed up the reason why many people prefer an
>> interactive cross-compiler :-)
>>
>> Cheers,
>> Elizabeth
>>
>
>Dear Elizabeth,
>
>mostly I wish for an interface with interlocked handshake like IEEE-488/GPIB we still have in lab
>equipment to become standard again. It would relief us of all terminal timing issues :-) I am sure
>you implemented such a thing on top of the internal communication line between host and target.

O the good old 6809. The companion chip for serial communication ACIA allows
for a key and emit in a couple of assembler words.

>
>Matthias
-- 
Albert van der Horst, UTRECHT,THE NETHERLANDS
Economic growth -- being exponential -- ultimately falters.
albert@spe&ar&c.xs4all.nl &=n http://home.hccnet.nl/a.w.m.van.der.horst

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

#38921

rickman wrote:

> I have an embedded ARM board running Mecrisp.  Because installing the
> driver on a PC was rather ugly I installed it on a raspberry pi.  I can
> talk to the pi through SSH from a PC.  I run microcom on the pi to talk
> to the embedded board over a USB virtual serial port.  That's all great.
> 
> But I can't figure out how to get the files into the compiler.  Normally
> a Forth tool uses a command to load files, but this target has no file
> system.  The command line can be used to load code, but it seems
> definitions must all be on one line.
> 
> Ignoring the single line definition issue, neither of the tools I am
> using (Putty on the PC and microcom on the rPi) have a facility to send
> files into the command line.  When I use copy and paste there seem to be
> overrun errors and some of the text is lost.
> 
> Mecrisp doesn't have much of a following yet so I am not finding a lot
> on the web on how others have used this tool.  I did manage to find one
> site where someone changed the character sent by CR to a CR rather than
> a LF, but I worked around that problem some time back.  Even then the
> guts of his info was moved to another web site and that one is gone.
> 
> I have code to test.  I just wish I could test it.  :(

I use picocom for Mecrisp, in that form:

picocom -b 115200 /dev/ttyACM0 --imap lfcrlf,crcrlf --omap delbs,crlf --
send-cmd "ascii-xfr -s -l 50 -n"

You'll find that invocation in the "terminal" script in the same place where 
you find your binary to flash the device.

picocom alloes sending files with ctrl-a ctrl-s.  Just enter the file name, 
that will work.

-- 
Bernd Paysan
"If you want it done right, you have to do it yourself"
net2o ID: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ*
http://bernd-paysan.de/

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

#38923

On 5/9/2015 8:06 PM, Bernd Paysan wrote:
> rickman wrote:
>
>> I have an embedded ARM board running Mecrisp.  Because installing the
>> driver on a PC was rather ugly I installed it on a raspberry pi.  I can
>> talk to the pi through SSH from a PC.  I run microcom on the pi to talk
>> to the embedded board over a USB virtual serial port.  That's all great.
>>
>> But I can't figure out how to get the files into the compiler.  Normally
>> a Forth tool uses a command to load files, but this target has no file
>> system.  The command line can be used to load code, but it seems
>> definitions must all be on one line.
>>
>> Ignoring the single line definition issue, neither of the tools I am
>> using (Putty on the PC and microcom on the rPi) have a facility to send
>> files into the command line.  When I use copy and paste there seem to be
>> overrun errors and some of the text is lost.
>>
>> Mecrisp doesn't have much of a following yet so I am not finding a lot
>> on the web on how others have used this tool.  I did manage to find one
>> site where someone changed the character sent by CR to a CR rather than
>> a LF, but I worked around that problem some time back.  Even then the
>> guts of his info was moved to another web site and that one is gone.
>>
>> I have code to test.  I just wish I could test it.  :(
>
> I use picocom for Mecrisp, in that form:
>
> picocom -b 115200 /dev/ttyACM0 --imap lfcrlf,crcrlf --omap delbs,crlf --
> send-cmd "ascii-xfr -s -l 50 -n"
>
> You'll find that invocation in the "terminal" script in the same place where
> you find your binary to flash the device.
>
> picocom alloes sending files with ctrl-a ctrl-s.  Just enter the file name,
> that will work.

I tried picocom on the pi but it just locked up.  Not sure what was wrong.

-- 

Rick

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.forth

csiph-web