From: "Shen Rong" <rshen@udtech.com.cn>
To: "Jason Park" <jason@amadeus.kist.re.kr>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: How do you change the program counter (PC)
Date: Fri, 24 Jan 2003 11:02:58 +0800 [thread overview]
Message-ID: <025b01c2c355$199c8600$e600a8c0@udtech.net> (raw)
In-Reply-To: 001701c2c33f$298715f0$5e207aa1@fish
> now, i want to test and check whether the ppcboot loader will work properly
> before i overwrite the planetcore bootloader code. how can i change the PC
> (which states 0xfff0 0100 when i type "info" at the BDI prompt)...
go 0xffc00100
or
ti 0xffc00100
> also, whats the main difference between the 3 files created by ppcboot.
> (ELF, BIN, SREC) besides size.. is there an advantage/disadvantage using
> one over the other? is it dependant on the debugger?
ELF: portable binary format, which has program headers/sections and others
information. You can't excute the ELF file directly. It needs intepreter(or named
loader) to load it to proper memory address. BDI can do it. But remember not to
program it to flash for excuting directly.
BIN: pure binary format, which has nothing but cpu instrctions(and data). If you
want to program it to flash, it's the proper choise.
SREC: (I am not much sure) It seems an old format used mostly by motorola.
It's like BIN format, but has other information used for downloading. It seems
some bootloaders need SREC format for downloading.
Don't trust me. For ELF & SREC, you can download the specification if you do
have interesting, and for BIN file, you do can disassemble it if you really want
to know what's in it (of course, ELF format is the best choise for disassembling).
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-01-24 3:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 0:25 How do you change the program counter (PC) Jason Park
2003-01-24 3:02 ` Shen Rong [this message]
2003-01-24 8:33 ` Jason Park
2003-01-24 8:56 ` Shen Rong
2003-01-24 13:20 ` Kenneth Johansson
-- strict thread matches above, loose matches on Subject: below --
2003-01-24 16:58 erik.teose
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='025b01c2c355$199c8600$e600a8c0@udtech.net' \
--to=rshen@udtech.com.cn \
--cc=jason@amadeus.kist.re.kr \
--cc=linuxppc-embedded@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).