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


Groups > comp.lang.forth > #38923

Re: Talking to an Embedded Target with Mecrisp

From rickman <gnuarm@gmail.com>
Newsgroups comp.lang.forth
Subject Re: Talking to an Embedded Target with Mecrisp
Date 2015-05-09 22:35 -0400
Organization A noiseless patient Spider
Message-ID <mimg34$abo$1@dont-email.me> (permalink)
References <milscu$hj2$1@dont-email.me> <mim7c4$n7h$1@dont-email.me>

Show all headers | View raw


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

Back to comp.lang.forth | Previous | Next — Previous in thread | Find similar | Unroll thread


Thread

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

csiph-web