public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Graeme Russ <graeme.russ@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Help Request - Command parsing, find_cmd (), possible linker script problem
Date: Sun, 21 Sep 2008 12:22:23 +1000	[thread overview]
Message-ID: <48D5AFDF.3060709@gmail.com> (raw)
In-Reply-To: <48D586F2.2010505@gmail.com>

OK, I've had a closer look at u-boot.map and u-boot.bin...

The command table starts at offset 0x001268e into u-boot.bin and each
entry is 24 bytes. The first entry is:

001268e: 90 e0 04 38 02 00 00 00 00 00 00 00 86 08 04 38 98 e0 04 38 ba e0 04 38

Which decodes down to:

90 e0 04 38 => cmd_tbl_t->name
ASCII string at offset 0xe090 in u-boot.bin
"autoscr"

02 00 00 00 => cmd_tbl_t->maxargs
2

00 00 00 00 = cmd_tbl_t->repeatable
0

86 08 04 38 => cmd_tbl_t->cmd
u-boot.map => do_autoscript ()

98 e0 04 38 => cmd_tbl_t->usage
ASCII string at offset 0xe098 in u-boot.bin
"autoscr - run script from memory"

ba e0 04 38 => cmd_tbl_t->help
ASCII string at offset 0xe0ba in u-boot.bin
"[addr] - run script starting at addr - A valid autoscr header must be present"

So the table and all the references in it are valid and u-boot.map
suggest it should be located at 0x540, but what is this relative to,
and how does it end up there? I feel I'm getting closer, but missing
one tiny, but critical, bit of info.

Sorry if this all seems obvious, but this is the first time I've
dealt with data at such a low level

Regards,

Graeme

      reply	other threads:[~2008-09-21  2:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-20  6:56 [U-Boot] Help Request - Command parsing, find_cmd (), possible linker script problem Graeme Russ
2008-09-20 13:57 ` Jerry Van Baren
2008-09-20 23:27   ` Graeme Russ
2008-09-21  2:22     ` Graeme Russ [this message]

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=48D5AFDF.3060709@gmail.com \
    --to=graeme.russ@gmail.com \
    --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