All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan <dgisselq@verizon.net>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] Data transfer from de0-nano board to Laptop/PC
Date: Fri, 30 Sep 2016 07:38:23 -0400	[thread overview]
Message-ID: <1475235503.4153.197.camel@jericho> (raw)
In-Reply-To: <0c7aa936-9e06-58b5-d42d-0ff83d475e67@embecosm.com>

FTP?  Does that work over a uart?

My thought would've been to try a serial line protocol, such as xmodem?
Try "man sx", or the similar "man rx" for the support programs you would
need.  If you go this road, you can even 'tar' and 'gzip' the files you
need to send.

Alternatively, since the file being transferred is text, why not just
"cat" it across the interface, and save it in the PC?  You can use
"script" for this purpose, or if you are using something like minicom to
talk to the UART, you can direct minicom to save it's output.

Dan


On Fri, 2016-09-30 at 08:14 +0100, Jeremy Bennett wrote:

> On 29/09/16 20:22, Manaar Alam wrote:
> > Hello,
> > 
> > Is there any way to copy any text file, generated by a C program
> > running on openrisc linux on de0-nano board, into my Laptop/PC?
> > 
> > I will be highly obliged with any kind of help.
> 
> Hi Manaar,
> 
> If you build your linux with FTP, you can use that in principle to
> talk across the UART.  You'd have to look up exactly how to configure
> that.
> 
> If you are running the Linux gdbserver and connecting to that from
> GDB, you will also be able to suck data off using GDB. I've never
> tried connecting GDB, but it should work over the serial link you use
> for telnet.
> 
> Once you find out how, it would be helpful if you could share it here.
> I'm sure you won't be the first person wanting to do this.
> 
> Best wishes,
> 
> 
> Jeremy
> 
> 
> > 
> > Thank you
> > 
> > -- *Manaar Alam,* Junior Research Fellow, Secured Embedded
> > Architecture Laboratory (SEAL), Department of Computer Science and
> > Engineering, Indian Institute of Technology, Kharagpur, West
> > Bengal, India.
> > 
> > 
> > _______________________________________________ OpenRISC mailing
> > list OpenRISC at lists.librecores.org 
> > https://lists.librecores.org/listinfo/openrisc
> > 
> 
> 
> _______________________________________________
> OpenRISC mailing list
> OpenRISC at lists.librecores.org
> https://lists.librecores.org/listinfo/openrisc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.librecores.org/pipermail/openrisc/attachments/20160930/946ac481/attachment.html>

  reply	other threads:[~2016-09-30 11:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-29 19:22 [OpenRISC] Data transfer from de0-nano board to Laptop/PC Manaar Alam
2016-09-30  7:14 ` Jeremy Bennett
2016-09-30 11:38   ` Dan [this message]
2016-09-30 12:17     ` Jeremy Bennett

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1475235503.4153.197.camel@jericho \
    --to=dgisselq@verizon.net \
    --cc=openrisc@lists.librecores.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.