linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Jongmin Yoon" <blueguy@blueguy.sarang.net>
To: <linuxppc-embedded@ozlabs.org>
Subject: I'm in troube to port linux on 405ep
Date: Fri, 20 Jan 2006 22:52:42 +0900	[thread overview]
Message-ID: <002d01c61dc8$c90572c0$efb079d2@Thinkpad> (raw)

[-- Attachment #1: Type: text/plain, Size: 3540 bytes --]

Hello, there,

 

Now, I’m in trouble with porting Linux to AMCC PPC405EP.

I think u-boot was ported successfully, So, I compile linux kernel 2.6.14 with crosstool-0.38

 

Here is a capture of my terminial

 

=> tftp 200000 uImage

ENET Speed is 10 Mbps - HALF duplex connection

TFTP from server 192.168.10.100; our IP address is 192.168.10.99

Filename 'uImage'.

Load address: 0x200000

Loading: T invalid RARP header

#################################################################

         #################################################################

         #################################################################

         ################

done

Bytes transferred = 1075636 (1069b4 hex)

=> bootm 200000

## Booting image at 00200000 ...

   Image Name:   Linux-2.6.14-kodicom

   Created:      2006-01-20  13:37:31 UTC

   Image Type:   PowerPC Linux Kernel Image (gzip compressed)

   Data Size:    1075572 Bytes =  1 MB

   Load Address: 00000000

   Entry Point:  00000000

   Verifying Checksum ... OK

   Uncompressing Kernel Image ... OK

## Transferring control to Linux (at address 00000000) ...

Starting kernel...

id mach(): done

MMU:enter

MMU:hw init

MMU:mapin

MMUetio

MMU:exit

setup_arch: enter

setup_arch: bootmem

ocp: exit

arch: exit

@

@

@

@

@

@

@

|^_���^_^_��~L~L~@p^_p^_�^_~L|�~L�^\|^_�|�^_^\p�^_?�^_~@~@|~L^_~L||

^_8~�^_|^_|^_^_^G|^_|^_8|^\~@|^_~L~L��c|~C^_�|�^_�~L�^\|^_�|�|

^_^\?�^_8�^_~@����|~Lp^\~L~@|c�~Lp^_c~@~L|p~@p|~C|�~C|^C�^_^\p��~@|

p~L|����|~C|^_�~@~L|pp��|p^C~L|^_������~L~L~Cp|�^_^\p|cp�~C|^_

|�^C�|^_^G|��~Lp^_|^_|~@|^C~L|~C|||�|^C�^\|^_?~^_8|^Cp|c~@^_^\?pp

^\�^_~@^_^\?�|||~L|^\|�c|~@~L|^_?�^_|��|�|~L|^_�p^C~L|^_���^_^_

��~L~L�p|�^C���p^C~L|^_|p������~L~L�|c��~@|p�p|^_|~L��^_p^_|

|�||^\~L|^_������~L~L�~C~L�^\||~L����|~L|^_|^_�|~@�p~@|�|~L�^\\

�|�|�^_�|^_|^_^_~L~@~@|~C|^_�~@�~L|p��p||^_|~@|�^_8~~L�|p|^C

~L|^_^\?��~@�~C|||^_|^_~L||~C|p|c|���|~C|p~L�~@||��|�p|��p�|�p�||

�^\�������|����^_~@�|��^_�������^_~@�|�^_~@�^_~@��~~

L|~L|�p~L|~L|^_^G~L|~L|^_�^C~L|^_|p������~L~L~L~C~@~@|p|^_|||^_^\~@||

^Cp��^_^_~L��^_8p|~C|^_^_||^\��p~@|�|^_^G|�~L�^\p��~@��||�~@|�

p�~C|�~L�^_cp^C~L|^_|p��^_^_��~L~L�||�^_�|~@|^_^_p�|�|^_||^_~Lp||

p~@�~L|�~L|^_�p~@�c�|~C||�c|p�|^\?~c^_p^C~L|^_���^_^_��~L~L~@~@|c|||

~@|^\|p|��^_|^_^_�^_|||~@|^Cp��~L�p~L�|^_8p|~C|~L�^_|^\�|��|

��^_|p|�|cp|^\�~L|~@^_^\?~@���|p�p�|�~L�^_|~Cp^C~L|^_���^_^_��

~L~L~C|||^_8~^_^_~L^_~@�^_|^_^_�^_|||^_^\~@|^Cp��~L�p~L��^_8p|~C|^_^_|

|^\��||�~@|^_|^_^G~@�cp|^\�~@|~@�|~L|~L||�|��~C~@|c|^_cp^C~L|^_||

p������~L~L~Lp^_^_~L|^_|p|~Cp���|�|�|�p��~C|^_|�^\~@|^_^_^_^^

G��~@||�p|�cp||^_^_~@|^_^\|�|~@�c|�~L||p��~@����^_^\�||�p

��^_p^_~@|��|����|~L|^_^_~L|^_p~Cp^C~L

 

 

I don’t know what’s wrong… 

Is there anybody to give me some advises?

 

 

Regards,

I


[-- Attachment #2: Type: text/html, Size: 70698 bytes --]

             reply	other threads:[~2006-01-20 14:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-20 13:52 Jongmin Yoon [this message]
2006-01-20 15:52 ` I'm in troube to port linux on 405ep Mark Chambers

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='002d01c61dc8$c90572c0$efb079d2@Thinkpad' \
    --to=blueguy@blueguy.sarang.net \
    --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).