From: "Sangtae Ha" <stha@postech.edu>
To: "Alexander J" <Alexander.J@lntinfotech.com>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Linux Kernel Porting in PPC405GPr
Date: Fri, 28 Mar 2003 16:59:15 +0900 [thread overview]
Message-ID: <003901c2f500$0b077b40$a80e000a@JERRY> (raw)
In-Reply-To: OFF7149A9F.93AD1B92-ON65256CF7.0028C780@lntinfotech.com
please check bd_info first.
----- Original Message -----
From: "Alexander J" <Alexander.J@lntinfotech.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Sent: Friday, March 28, 2003 4:41 PM
Subject: Linux Kernel Porting in PPC405GPr
>
> Hi all,
>
> I have a PPC 405GPr target board loaded with the customized PPCboot 1.1.5.
> Now i am trying
> to load the linux kernel into the target but unsuccessful. Could anyone pl
> help?
>
> The following is the procedure which i have followed.
>
> .(a) Downloaded the Linux-2.4.18 from the net (No support for the built-in
> network card)
> (b)
> (c) The following changes are done in the main make file existing in the
> linux folder
> a. Changed the architecture as ARCH :- ppc
> b. Changed the cross compiler as CROSS COMPILE = powerpc-linux-
> (d) make menuconfig
> (e) make dep
> (f) make clean
> (g) make zImage. It created the image as zImage
> (h) Added the header to image using mkimage (mkimage -n xx -O linux - A
> ppc -a 0000 -e 0000 -d xx ) as described in the BSP.
> (i) Downloaded the image using the PPC monitor program tftpboot to the
> default location 0x1000000
> => tftp 1000000 vmlinux
> miiphy_read: addr[0x0] reg[0x1]
> read err 3
> a2: read: EMAC_STACR=0xffffc001, i=2
> miiphy_read: addr[0x0] reg[0x5]
> read err 3
> a2: read: EMAC_STACR=0xffffc005, i=2
> PHY speed1 read failed, assuming 10bT
> miiphy_read: addr[0x0] reg[0x5]
> read err 3
> a2: read: EMAC_STACR=0xffffc005, i=2
> PHY duplex read failed, assuming half duplex
> ENET Speed is 10 Mbps - HALF duplex connection
> ARP broadcast 1
> TFTP from server 107.108.204.207; our IP address is
> 107.108.204.104
> Filename 'vmlinux'.
> Load address: 0x1000000
> Loading:
> #################################################################
>
> #################################################################
> ###########################
> done
> Bytes transferred = 802132 (c3d54 hex)
>
> (j) run the command bootm 1000000, It printed the following
> => bootm 1000000
> ## Booting image at 01000000 ...
> Image Name: kernel_image
> Created: 2003-03-03 13:39:09 UTC
> Image Type: PowerPC Linux Kernel Image (uncompressed)
> Data Size: 802068 Bytes = 783 kB = 0 MB
> Load Address: 00000000
> Entry Point: 00000000
> Verifying Checksum ... OK
> Loading Kernel Image ... OK
>
> (k) After this, the PPC target system hangs forever.
>
>
> Any ideas or suggestions?
>
> Thanks in advance.
> Alex j
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-03-28 7:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 7:41 Linux Kernel Porting in PPC405GPr Alexander J
2003-03-28 7:59 ` Sangtae Ha [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-31 7:12 Laurent Mohin
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='003901c2f500$0b077b40$a80e000a@JERRY' \
--to=stha@postech.edu \
--cc=Alexander.J@lntinfotech.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).