From: Wolfgang Denk <wd@denx.de>
To: ASchreckenberg@dspace.de
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Debugger Problems
Date: Mon, 06 Nov 2000 13:34:33 +0100 [thread overview]
Message-ID: <200011061234.eA6CYXd00907@denx.local.net> (raw)
In-Reply-To: Your message of "Mon, 06 Nov 2000 12:53:58 +0100." <3A069BD6.9F63FF6C@dspace.de>
In message <3A069BD6.9F63FF6C@dspace.de> Andreas Schreckenberg wrote:
>
> Our board contains a MPC750-466 MHz CPU, it's no embedded system in the
Why not? You can build an Embedded System around any CPU :-)
> There is no firmware. The board has flash memory and jumps directly to
> ram after reset.
> Can I use ppcboot for my board ?
Yes, sure. You will have to make some modifications, of course. So
far nobody ported it to a 750 board yet.
> I thought it's only for special TQM8xx boards.
No. We have support for several MPX8xx and IBM 40x based systems:
TQM823L, TQM850L, TQM855L, TQM860L, ETX094, ADCIOP, CPCI405, COGENT,
FADS, SPD823TS, FPS850L, MBX, SM850, IVMS8. There are some other
systems, where I have received success reports from the developers
who ported PPCBoot to their systems, but I never received patches.
Ports for MPC82xx systems are in the works.
> Perhaps I have read not enough about ppcboot... :-)
Definitely :-)
> I want to build a kernel and boot via ramdisk support, the board communicates
> with a serial port.
That's fine. You could use the serial port to download a Linux kernel
image (using S-Records and/or kermit binary protocol).
> I want to download my code via JTAG/BDM as a raw binary or elf file in the ram memory.
> (there are problems with elf and EST, because the EST debugger handles
> the kernel and ramdisk sections not correct, bin2bin which I found in
> the mailinglist seems to fix this for .bin files.)
> Finally all the stuff should be burned into flash.
That's fine. Just get working tools.
> I turn on the MMU and jump via an rfi instruction.
> (first init the srr0/srr1 registers) then the debugger confuses this situation
> and shows wrong code in the disassemby window.
>
> Is there any workaround availible ?
> Or is there no chance to use the EST Debugger with virtual memory ?
Sorry, I can't help here. We didn't buy this device exactly because
of this problem (and because of the price).
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
"Unix is simple, but it takes a genius to understand the simplicity."
- Dennis Ritchie
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-11-06 12:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-06 8:47 Debugger Problems Andreas Schreckenberg
2000-11-06 9:39 ` Wolfgang Denk
[not found] ` <3A069BD6.9F63FF6C@dspace.de>
2000-11-06 12:34 ` Wolfgang Denk [this message]
2000-11-06 13:06 ` Jerry Van Baren
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=200011061234.eA6CYXd00907@denx.local.net \
--to=wd@denx.de \
--cc=ASchreckenberg@dspace.de \
--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).