[U-Boot-Users] u-boot on a dbau1000
hello,
I just tried to load a compiled u-boot image on a dbau1000 devel board. but as it seems that quite at the beginning of loading the image via tftp the whole system froze. accidentally I also did this with the other boot rom, so prolly both are busted. the number display on the board shows a "02" whatever that means. I couldn't find documentation what this should actually mean. I assume that it means, more or less, that I busted the system. is there anything I can do right now to resurrect the boot rom, like resetting it to factory defaults, whatsoever? or more or less the last option I have is to call AMD?
the other technical question I'ld like to get some enlightenment is, why the system freezes or like, why is the boot rom busted just when doing a load? is load doing more than just moving the image into the ram? which is so far my understanding what load does. maybe I omitted something in the docs ... any hints, answers are greatly appreciated :).
the u-boot version in question is 1.1.1 but I had to made some changes to the source so that it compiles, like finding functions in start.S and the like. I wonder if the setup as it is shipped in 1.1.1 and cvs is supposed to work or how much hacking should be put in there that it is compileable.
regards, Othmar
In message 20040624214603.GB1989@tron.at you wrote:
I just tried to load a compiled u-boot image on a dbau1000 devel board. but as it seems that quite at the beginning of loading the image via tftp the whole system froze. accidentally I also did this with the other boot rom, so prolly both are busted. the
You seem to love the risk....
number display on the board shows a "02" whatever that means. I couldn't find documentation what this should actually mean. I assume that it means, more or less, that I busted the system.
Right.
is there anything I can do right now to resurrect the boot rom, like resetting it to factory defaults, whatsoever? or more or less the last option I have is to call AMD?
Attach your JTAG debugger, and erase and reprogram the flash.
the other technical question I'ld like to get some enlightenment is, why the system freezes or like, why is the boot rom busted just when doing a load? is load doing more than just moving the
Probably because you were doing something wrong? Sorry, but with your vague description nearly everything may have been wrong.
the u-boot version in question is 1.1.1 but I had to made some changes to the source so that it compiles, like finding functions in start.S and the like. I wonder if the setup as it is shipped
Sounds as is your toolchain is VERY broken. You should not expect that a system which required such severe changes will atually work.
in 1.1.1 and cvs is supposed to work or how much hacking should be put in there that it is compileable.
No changes are necessary. It compiles fine.
Best regards,
Wolfgang Denk
morning,
On Fri, Jun 25, 2004 at 12:56:18AM +0200, Wolfgang Denk wrote:
I just tried to load a compiled u-boot image on a dbau1000 devel board. but as it seems that quite at the beginning of loading the image via tftp the whole system froze. accidentally I also did this with the other boot rom, so prolly both are busted. the
You seem to love the risk....
usually not *shrug* ....
the other technical question I'ld like to get some enlightenment is, why the system freezes or like, why is the boot rom busted just when doing a load? is load doing more than just moving the
Probably because you were doing something wrong? Sorry, but with your vague description nearly everything may have been wrong.
well, yes, I didn't mention the code changes in detail. but actually the toolchains works for other programs, so wonder what might be wrong *sigh*. but I will recheck on that. maybe I was just a bit too ignorant about what I was doing..
the u-boot version in question is 1.1.1 but I had to made some changes to the source so that it compiles, like finding functions in start.S and the like. I wonder if the setup as it is shipped
Sounds as is your toolchain is VERY broken. You should not expect that a system which required such severe changes will atually work.
well, afaik -mcpu=4kc isn't used that often at least when I compiled code usually -march=mips32 is used. and the compiler has quite a strange prefix mips4kc- (or so, it's just from top of my head).
in 1.1.1 and cvs is supposed to work or how much hacking should be put in there that it is compileable.
No changes are necessary. It compiles fine.
aha, was your toolchain self compiled or premade and from somewhere?
thanks Othmar
In message 20040625055507.GA1927@tron.at you wrote:
No changes are necessary. It compiles fine.
aha, was your toolchain self compiled or premade and from somewhere?
We use the ELDK. And yes, this is premade :-)
Best regards,
Wolfgang Denk
participants (2)
-
Othmar Pasteka -
Wolfgang Denk