linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Julien Eyries <julien.eyries@thales-bm.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: MBX boot loader on a MPC8260 custom board
Date: Thu, 21 Mar 2002 11:53:23 +0100	[thread overview]
Message-ID: <3C99BBA3.8090703@thales-bm.com> (raw)


hi all ,

we have here a custom MPC8260 board (4 Mo flash, 32 Mo SDRAM,200 Mhz
MPC8260) and we want to use the HardHat linux from Montavista.
we are also using BDI-2000 probe (from ABATRON) .

the kernel we have build is based on the ADS8260 board which is quite
similar to our board.

the boot-loader we use is the "mbx" boot loader which come with the
Linux kernel tree.

the problem i have is :
- we load the file "zvmlinux.mbx" using the BDI2000 probe
- we take control over the MPC8260 with "ppc_82xx-gdb zvmlinux.mbx" and
"target remote xx.xx.xx.xx:2001"
- we do some "stepi" and the code runs, entering function
"decompress_kernel", then "serial_init" .
- at some point in this function "serial_init" , the PC (program
counter) begins to count downwards !!! for exemple ( 0x400000 ...
0x3ffffc ... 0x3fff8 ...  )

another point is: when debugging C source code (in emacs + gdb),
we can see that the programms jumps from one point to another (some
times backward) , not following the logical flow of the C source code
.Is that normal ????

what could be the reason of such behaviour ???
does someone here have an idea for our problem ?????


any help is welcome,
greetings,



--
Julien Eyries
R&D engineer
Thales Broadcast & Multimedia (ex-thomcast)
email: julien.eyries@thales-bm.com
fax: 33(0) 1 34 90 31 10
tel: 33(0) 1 34 90 31 01


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2002-03-21 10:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-21 10:53 Julien Eyries [this message]
2002-03-21 11:18 ` MBX boot loader on a MPC8260 custom board Wolfgang Denk
2002-03-21 15:30   ` Julien Eyries

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=3C99BBA3.8090703@thales-bm.com \
    --to=julien.eyries@thales-bm.com \
    --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).