From: Jakob Viketoft <linux@viketoft.se>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Adding functionality to u-boot...
Date: Wed, 28 May 2008 12:58:39 +0200 [thread overview]
Message-ID: <483D3ADF.3050802@viketoft.se> (raw)
Hello!
I'm using u-boot 1.1.6 on a custom PCB of ours when we are prototyping
some hardware. I would like to transfer files over the ethernet to and
from the card using tftp and it seemed natural trying to use the
built-in u-boot functionality for this.
I have written a tftpwrite function which works well from command line
in much the same way as tftpboot (but in the other direction of course).
Now, I would like to call this function from my stand-alone program to
transfer files to and from memory regions which I specify.
To make things as easy as possible, I have created a TftpPut and TftpGet
function which takes arguments as filename, load address and size and
then set the "usual" variables used by existing function TftpStart and
newly written TftpWrite.
I have added TftpPut and TftpGet to _exports.h and I can compile and
link my stand-alone program to this customized version of u-boot.
However, the function doesn't seem to actually be called. As far as I
can see, the calls to TftpPut and TftpGet look much the same as the
u-boot built-in printf call (which works perfectly). If I "go" to the
address of the function TftpPut or TftpGet directly from the u-boot
prompt, I can see that it works as expected, but why can't I call it
from my stand-alone program?
Are there any more steps I have to do to make the new functions play
nicely with the rest of u-boot, or can anyone think of any other thing
which could be causing the problem? I don't get any errors, it just seem
that the functions are either never actually called or disregarded
somehow when supposed to be taken care of by u-boot...
Best regards,
/Jakob
reply other threads:[~2008-05-28 10:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=483D3ADF.3050802@viketoft.se \
--to=linux@viketoft.se \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox