[U-Boot-Users] BDI2000 not good for ARM946?
Hi,
I know this is out of the topic of this mailing list. But I really need some comments on this issue and I know that this probably is the best place to get a quick feedback for BDI2000 since a lot of ppl here use it.
Some people using BDI2000 to bring up ARM946 board have a little complaint that BDI2000 works flakey on their board. (It took them a week to figure out its configuration file and sometimes it just simply doesn't work.)
However my experience on ppc bring-up tells me that BDI2000 works perfectly. So I'm wondering if this is an individual case for ARM bring-up. Or BDI2000 for ARM is not as good as for PPC?
Please share your experience.
Best regards, -Shawn.
Dear Shawn,
in message c3d0340b040804134627e0e723@mail.gmail.com you wrote:
Some people using BDI2000 to bring up ARM946 board have a little complaint that BDI2000 works flakey on their board. (It took them a week to figure out its configuration file and sometimes it just simply doesn't work.)
It takes some understanding of the hardware to come up with a working BDI2000 configuration file. And of course the stability of the system BDI2000-target depends on _both_ components, the BDI2000 _and_ the target.
My guess is that these people have little experience and/or flakey target hardware.
However my experience on ppc bring-up tells me that BDI2000 works perfectly. So I'm wondering if this is an individual case for ARM bring-up. Or BDI2000 for ARM is not as good as for PPC?
We use the BDI2000 on PowerPC, MIPS and ARM. I remember only one case when a specific version of the firmware had problems (and this got replaced by Abatron within a few hours). In all other cases the BDi200 has proved to be absolutely reliable and stable. I see no difference whether on ARM, MIPS or PowerPC.
Best regards,
Wolfgang Denk
participants (2)
-
Shawn Jin -
Wolfgang Denk