[U-Boot] How do you print/view avaliable devices?
I am trying to run a standalone program from flash but I keep receiving ** Invalid boot device ** when I attempt to load it into memory. I think I'm just using the wrong device number. I was wondering if there was any way to print the devices that U-boot can see, so I can figure out dev:part numbers of my onboard flash and compact flash.
Hi dbrazeau,
I am trying to run a standalone program from flash but I keep receiving ** Invalid boot device ** when I attempt to load it into memory. I think I'm just using the wrong device number. I was wondering if there was any way to print the devices that U-boot can see, so I can figure out dev:part numbers of my onboard flash and compact flash.
Not understanding a word what you wrote, I needed a grep -r to find the message you were referring to. Now it seems that you try some filesystem access and it does not work. Although I still have no clue if you use USB, IDE, ATA or whatever...
May you please be so kind to show us what you try to do and what you would like to see instead? Actual session transcripts help a lot in such cases...
Thanks Detlev
This is the command I try to execute in the U-boot console: fatload xsa 0 0x1000000 /mnt-xsa/someprogram.img
output: ** Invalid boot device **
Detlev Zundel wrote:
Hi dbrazeau,
I am trying to run a standalone program from flash but I keep receiving ** Invalid boot device ** when I attempt to load it into memory. I think I'm just using the wrong device number. I was wondering if there was any way to print the devices that U-boot can see, so I can figure out dev:part numbers of my onboard flash and compact flash.
Not understanding a word what you wrote, I needed a grep -r to find the message you were referring to. Now it seems that you try some filesystem access and it does not work. Although I still have no clue if you use USB, IDE, ATA or whatever...
May you please be so kind to show us what you try to do and what you would like to see instead? Actual session transcripts help a lot in such cases...
Thanks Detlev
-- To you I'm an atheist; to God, I'm the Loyal Opposition. -- Woody Allen -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu@denx.de _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Hi dbrazeau,
This is the command I try to execute in the U-boot console: fatload xsa 0 0x1000000 /mnt-xsa/someprogram.img
output: ** Invalid boot device **
Do you pay for every character you send, or why are you so very restrictive in providing more information to your problem? Telling us on what platform you work, which U-Boot version etc. would go *a long way* in putting us into a better position to help you.
As "git grep xsa" yields no output I'm pretty sure that you try to do something which is not supported - at least in mainline.
What device exactly do you try to access?
Cheers Detlev
I working on the Katmai board. I'm trying to run a program in the 16MB boot flash. The user manual states the U-boot command to load Kozio diagnostics program is: => fatload xsa 0x1000000 /mnt-xsa/kdiags.katmai.img => bootm 0x1000000
This doesn't work as it does not define a device number, so I tried adding the device number with no luck. I'm using U-boot version 2009.06-rc1. Thanks.
Detlev Zundel wrote:
Hi dbrazeau,
This is the command I try to execute in the U-boot console: fatload xsa 0 0x1000000 /mnt-xsa/someprogram.img
output: ** Invalid boot device **
Do you pay for every character you send, or why are you so very restrictive in providing more information to your problem? Telling us on what platform you work, which U-Boot version etc. would go *a long way* in putting us into a better position to help you.
As "git grep xsa" yields no output I'm pretty sure that you try to do something which is not supported - at least in mainline.
What device exactly do you try to access?
Cheers Detlev
-- Insider comment on Microsoft releasing Linux Hyper-V driver code under GPLv2: "It looks like hell just froze over." -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu@denx.de _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
On Friday 14 August 2009 17:56:07 dbrazeau wrote:
I working on the Katmai board. I'm trying to run a program in the 16MB boot flash. The user manual states the U-boot command to load Kozio diagnostics program is: => fatload xsa 0x1000000 /mnt-xsa/kdiags.katmai.img
That's not boot flash but most likely a CompactFlash connected via the SystemACE. You should use "ace" instead of "xsa" here. Perhaps this will work.
Cheers, Stefan
-- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office@denx.de
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
fatls ace 0 / mnt-xsa/
0 file(s), 1 dir(s)
=> fatls ace 0 /mnt-xsa/ ./ ../ 1378602 kernel.img 19783883 ramdisk.img
2 file(s), 2 dir(s)
Yep, not even there.
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 Waiting for PHY auto negotiation to complete.... done ENET Speed is 1000 Mbps - FULL duplex connection (EMAC0) Using ppc_4xx_eth0 device TFTP from server 192.168.2.66; our IP address is 192.168.2.92 Filename 'kdiags.katmai.img'. Load address: 0x100000 Loading: ############################################################# done Bytes transferred = 893996 (da42c hex) => go 0x100000 ## Starting application at 0x00100000 ... NIP: 00100004 XER: 00000000 LR: 1FF75C9C REGS: 1fe64cb8 TRAP: 0700 DEAR: 0ECFC12 0 MSR: 00029000 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 00
GPR00: 1FF75D1C 1FE64DA8 1FE64F38 00000001 1FE693F4 1FE693F4 00000006 58AF5DD6 GPR08: 1FF6CD98 00000020 010F4471 09896800 28822F22 00100400 1FFB4400 00000000 GPR16: 1FFA8EA8 1FFAE7BC 00000000 00000000 00000000 00000000 00000000 00000000 GPR24: 00000000 1FE69340 00000000 00000000 1FE693F4 00100004 1FFB4A18 00000002 ** Illegal Instruction ** Call backtrace: 00100004 1FF75D1C 1FF871D0 1FF868DC 1FF86A4C 1FF896A8 1FF6C8E4 1FF6B6DC Program Check Exception
I have also tried "go 0x100004" but that didn't work either. Am I doing something wrong? Any Ideas? Thanks for you help.
Stefan Roese wrote:
On Friday 14 August 2009 17:56:07 dbrazeau wrote:
I working on the Katmai board. I'm trying to run a program in the 16MB boot flash. The user manual states the U-boot command to load Kozio diagnostics program is: => fatload xsa 0x1000000 /mnt-xsa/kdiags.katmai.img
That's not boot flash but most likely a CompactFlash connected via the SystemACE. You should use "ace" instead of "xsa" here. Perhaps this will work.
Cheers, Stefan
-- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office@denx.de _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
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
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@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@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
participants (4)
-
dbrazeau -
Detlev Zundel -
Stefan Roese -
Wolfgang Denk