From: dbrazeau <dbrazeau1024@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] How do you print/view avaliable devices?
Date: Fri, 14 Aug 2009 10:55:54 -0700 (PDT) [thread overview]
Message-ID: <24975978.post@talk.nabble.com> (raw)
In-Reply-To: <20090814174252.8B1CC833DBD2@gemini.denx.de>
Ok. Thanks for your input.
wd wrote:
>
> Dear dbrazeau,
>
> In message <24975016.post@talk.nabble.com> you wrote:
>>
>> I actually tried used ace as well, since I saw it being used in some of
>> the
>> environment variables. Unfortunately that didn't work either, but had a
>> different error.
>>
>> fatload ace 0 0x1000000 /mnt-xsa/kdiags.katmai.img
>> reading /mnt-xsa/kdiags.katmai.img
>>
>> ** Unable to read "/mnt-xsa/kdiags.katmai.img" from ace 0:1 **
>>
>> This error made it sound like the file wasn't even in the flash so id did
>> an
>> fatls
>
> Indeed.
>
>> => fatls ace 0 /mnt-xsa/
>> ./
>> ../
>> 1378602 kernel.img
>> 19783883 ramdisk.img
>>
>> 2 file(s), 2 dir(s)
>>
>> Yep, not even there.
>
> Right. I have to admit that I really don;t understand why you wnt into
> such adventures as trying to use a phantasy device name (xsa) after
> verifying that the file you were looking for was not even present on
> the CompactFlash card you are using.
>
>> Now I tried transferring the program image via tftp a running it but it
>> fails with an illegal instruction. Here is the output:
>>
>> tftp 0x100000 kdiags.katmai.img
> ...
>> Bytes transferred = 893996 (da42c hex)
>
> So this works perfectly fine.
>
>> => go 0x100000
>> ## Starting application at 0x00100000 ...
>> NIP: 00100004 XER: 00000000 LR: 1FF75C9C REGS: 1fe64cb8 TRAP: 0700 DEAR:
> ...
>> I have also tried "go 0x100004" but that didn't work either. Am I doing
>> something wrong? Any Ideas? Thanks for you help.
>
> Well, the Kozio diagnostics software is aproprietary package, and if
> you cannot find out how it's working from the documentation provided
> by Kozio you should please contacxt Kozio support.
>
> As mentioned before, it's a closed-source proprietary tool and we
> have zero information about how to run it.
>
> Best regards,
>
> Wolfgang Denk
>
> --
> DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
> I have made mistakes, but have never made the mistake of claiming I
> never made one. - James G. Bennet
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
>
--
View this message in context: http://www.nabble.com/How-do-you-print-view-avaliable-devices--tp24943649p24975978.html
Sent from the Uboot - Users mailing list archive at Nabble.com.
prev parent reply other threads:[~2009-08-14 17:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 23:10 [U-Boot] How do you print/view avaliable devices? dbrazeau
2009-08-13 11:35 ` Detlev Zundel
2009-08-13 15:57 ` dbrazeau
2009-08-14 15:09 ` Detlev Zundel
2009-08-14 15:56 ` dbrazeau
2009-08-14 16:26 ` Stefan Roese
2009-08-14 16:54 ` dbrazeau
2009-08-14 17:42 ` Wolfgang Denk
2009-08-14 17:55 ` dbrazeau [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=24975978.post@talk.nabble.com \
--to=dbrazeau1024@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