From: "Thomas Maenner" <tmaenner@aehr.com>
To: "Wolfgang Denk" <wd@denx.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: TQM 860L, 64MB RAM, ELDK4.1, TQM860L, Kernel 2.6.19
Date: Thu, 22 Mar 2007 08:01:44 -0700 [thread overview]
Message-ID: <f001edbb0703220801m68622465j397a007bb85570cd@mail.gmail.com> (raw)
In-Reply-To: <20070322074052.34DD535260B@atlas.denx.de>
Thanks Wolfgang for your reply,
You're right, I can not really tell, whether it's frozen since I don't
have a BDM...
I'll try the console command you suggested, which I haven't had to use
before (U-boot 1.1.2 and older, Kernel 2.4, older ELDK)
Thanks
Tom
On 3/22/07, Wolfgang Denk <wd@denx.de> wrote:
> In message <200703212044.40611.tmaenner@aehr.com> you wrote:
> >
> > need from the experts on the list again.
> > The CPU freezes after the ramdisk gets loaded!
>
> Does it really freeze? I mean, did you verify this witha BDM
> debugger, or do you just see no further output on the console? Note
> that these are two fundamentally different things...
>
> > u-boot environment:
> > => printenv
> > bootcmd=run flash_self
> > bootdelay=5
> > baudrate=115200
> > loads_echo=1
> > preboot=echo;echo TQ-Module Bootloader for ABTS;echo Type "run flash_nfs" to
> > mount root filesystem over NFS;echo
> > netdev=eth0
> > nfsargs=setenv bootargs root=/dev/nfs rw nfsroot=${serverip}:${rootpath}
> > addip=setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:
> > ${netmask}:${hostname}:${netdev}:off panic=1
> > flash_nfs=run nfsargs addip;bootm ${kernel_addr}
> > flash_self=run ramargs addip;bootm ${kernel_addr} ${ramdisk_addr}
> > net_nfs=tftp 200000 ${bootfile};run nfsargs addip;bootm
> > rootpath=/opt/eldk/ppc_8xx
> > kernel_addr=40040000
> > serial#=TQM860LDDBA3-P80.210 11090659
> > ethaddr=00:D0:93:04:DC:1B
> > eth1addr=00:D0:93:04:DC:1B
> > ethprime=FEC ETHERNET
> > bootfile=/TQM860L/uImage
> > fileaddr=100000
> > ramdisk_addr=40200000
> > ramargs=setenv bootargs ramdisk_size=6144 root=/dev/ram rw
> > initrd_high=30000000
> > stdin=serial
> > stdout=serial
> > stderr=serial
> > ethact=FEC ETHERNET
> > bootcount=39
>
> I don't see you passing any console=ttyCPM0 argument here?
>
> Best regards,
>
> Wolfgang Denk
>
> --
> DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
> Office: Kirchenstr. 5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
> Not one hundred percent efficient, of course ... but nothing ever is.
> -- Kirk, "Metamorphosis", stardate 3219.8
>
--
Thomas Maenner
Engineering Project Manager
AEHR Test Systems
400 Kato Terrace
Fremont, CA 94539
Phone: +1-510-623-9400x323
Cell: +1-925-389-6653
Fax: +1-510-623-9450
E-Mail: mailto:tmaenner@aehr.com
next prev parent reply other threads:[~2007-03-22 15:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 3:44 TQM 860L, 64MB RAM, ELDK4.1, TQM860L, Kernel 2.6.19 Thomas Maenner
2007-03-22 7:40 ` Wolfgang Denk
2007-03-22 15:01 ` Thomas Maenner [this message]
2007-03-22 21:10 ` Thomas Maenner
2007-03-22 21:26 ` Wolfgang Denk
2007-03-23 11:19 ` Ralph Hempel
2007-03-23 13:27 ` Wolfgang Denk
2007-03-23 17:29 ` Thomas Maenner
2007-03-25 19:35 ` Wolfgang Denk
2007-03-23 17:26 ` Thomas Maenner
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=f001edbb0703220801m68622465j397a007bb85570cd@mail.gmail.com \
--to=tmaenner@aehr.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=wd@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;
as well as URLs for NNTP newsgroup(s).