From: "Jason Park" <jason@amadeus.kist.re.kr>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Problem with BDI2000 flash programming
Date: Thu, 23 Jan 2003 09:20:12 +0900 [thread overview]
Message-ID: <003201c2c275$45a441b0$5e207aa1@fish> (raw)
hi, im new to this email list.. but i am having some problems with my board
and don't know where to turn.
target board: ep8260
host distribution: redhat 8.0 (with powerpc cross compilers)
debugger: BDI2000
problem: trying to burn a PPCBOOT image into the flash memory at location
0xFF10 0000
setting up the initial bdi configurations.. i get the following output:
[root@FISH gdbcop21]# ./bdisetup -v -s
BDI Type : BDI2000 Rev.C (SN: 94406634)
Loader : V1.05
Firmware : V1.14 bdiGDB for PPC6xx/PPC7xx
Logic : V1.02 PPC6xx/PPC7xx
MAC : 00-40-49-fa-40-66
IP Addr : 161.122.32.98
Subnet : 255.255.255.0
Gateway : 161.122.32.1
Host IP : 161.122.32.94
Config : ep8260.cfg.init
everything looks normal to me... i have the ep8260.cfg.init file in the
/tftpboot directory. so at this point i will connect to the board with
telnet.
# telnet 161.122.32.98
Trying 161.122.32.98...
Connected to 161.122.32.98.
Escape character is '^]'.
BDI Debugger for Embedded PowerPC
=================================
PHYS <address> converts an effective to a physical address
****
****
other stuff here..
****
****
QUIT terminate the Telnet session
bdi2000>
since there is not error outputting that it cannot find the original
configuration file ep8260.cfg.init, i conclude that tftp worked properly.
i can read the flash memory, including the existing bootloader i got from
embedded planet. (planetcore at location 0xFFF0 000)
Now i place ppcboot.bin into the /tftpboot directory, and after checking
whats in memory location 0xFF10 0000 (there is nothing there), i proceed
to try and write into the flash:
bdi2000>prog 0xFF100000 ppcboot.bin bin
Programming ppcboot.bin , please wait ....
# Cannot open program file on host
bdi2000>
this is what i can't figure out. i think that it must be a problem
with the hosts tftp configuration, but i did check the tftp server several
times, even connected it to other computers and swapping files. could there
be a setting i missed in the BDI2000?
also.. i was wondering if there was more detailed documentation on using
the BDI2000 besides the manual that came with the prooduct and WD's PPCBoot
and Linux Guide.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-01-23 0:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 0:20 Jason Park [this message]
2003-01-23 0:46 ` Problem with BDI2000 flash programming Vladimir Gurevich
-- strict thread matches above, loose matches on Subject: below --
2003-01-23 0:30 Rod Boyce
2003-01-23 2:28 ` Jason Park
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='003201c2c275$45a441b0$5e207aa1@fish' \
--to=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).