linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: alayrac <christophe.alayrac@univ-orleans.fr>
To: linuxppc-embedded@ozlabs.org
Subject: ML403 UBOOT,  I2C and Linux boot problem
Date: Thu, 28 Sep 2006 18:10:30 +0200	[thread overview]
Message-ID: <1159459831.5737.3.camel@Serge-Linux> (raw)

I succeed to start u-boot on my ML403 board.

To do so I've dowloaded the ml403_emb_ref_ppc_81.zip from xilinx website
as well as u-boot.zip (from ml410 documentation on xilinx web site).

1) First you I've modifie the xparameters.h file in
u-boot/board/xilnx/ml403 directory to match hardware design of
ml403_emb...81 design.
(The memory mapping is different)

I now have u-boot working on ML403 but the IIC EEPROM can't be
accessed.

imd command (imd 50 10.2 10 )return error message, iprobe hang up and
saveenv did not save anything into I2C memory.

Does any one as any experience on that issue?

Note :To use I2C one should define either CONFIG_HARD_I2C or
CONFIG_SOFT_I2C, but Xilinx as writen function (i2c_read...) in
iic_addapter.c without using this macro.
Is it the right way?

2) If I manually load kernel uImage in memory (fatload ace 0 400000
linux/uboot.uImage) and then boot the kernel (bootm 400000) then the
process stop after 
Uncompressing Kernel Image ... Ok

Note: The kernel has been compiled with a command line to boot via NFS.
This image works properly if associated to bitsream in the ace file.
The kernel 2.4.26 has been patched for u-boot and recompiled with same
config (using mkimage to generate uImage)

Any suggestion?

3) The board did not start at powerup with that uboot ace file, the done
light did not go on, I need to press sysace rst button to start
properly.

Does any one face that cold start prolblem?

Thank in advance for any help

Chris

                 reply	other threads:[~2006-09-28 16:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1159459831.5737.3.camel@Serge-Linux \
    --to=christophe.alayrac@univ-orleans.fr \
    --cc=linuxppc-embedded@ozlabs.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).