public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot 1.2.0 -> 1.3.4 migration
Date: Mon, 08 Sep 2008 22:11:18 -0400	[thread overview]
Message-ID: <48C5DB46.1080509@gmail.com> (raw)
In-Reply-To: <4f13832e0809080710i5ed4784ck3a49eed2c3f98b5d@mail.gmail.com>

Alexander Danilov wrote:
> My bsp for u-boot 1.2.0 for AMCC PPC440EPx custom board works. I've
> moved all bsp code to current u-boot version (1.3.4). All works fine
> but I am getting program check exception when sending or receiving
> packet over ethernet (EMAC0).
> I've tryed to debug it but ethernet works when bdm connected.
> What was changed in ethernet code for ppc4xx after 1.2.0?

What initialization does your BDM debugger do that your start up code 
does not do?

I don't know what BDM you are using and am not very familiar with the 
4xx family, but Best Practices is to create a minimal BDM config and use 
that, especially when things work with the BDM plugged in but not when 
running bare.

If that doesn't help, git bisect.

HTH,
gvb

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-08 14:10 [U-Boot] u-boot 1.2.0 -> 1.3.4 migration Alexander Danilov
2008-09-09  2:11 ` Jerry Van Baren [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=48C5DB46.1080509@gmail.com \
    --to=gvb.uboot@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