After spending the time (and money) on getting the BDI2000 and u-boot working on the DBAU1500 board, our hardware guys finally delivered me a couple of our own design boards with Au1500 processors on them. I connected the BDI2000 to one of our boards, and when it wouldn't erase the flash and after a call to the HW engineer, found out that it has a different flash. OK, changed the flash type to the correct one, and also the bus width was changed to 16 as opposed to the 32 on the DBAU1500. The BDI will now erase and program the flash, but u-boot won't come up. After a bit of digging I found that after an erase the flash looks like this:
BDI>md 0xbfc00000 bfc00000 : 0000ffff 0000ffff 0000ffff 0000ffff ................ bfc00010 : 0000ffff 0000ffff 0000ffff 0000ffff ................ bfc00020 : 0000ffff 0000ffff 0000ffff 0000ffff ................ bfc00030 : 0000ffff 0000ffff 0000ffff 0000ffff ................
and on, and on.....
Does anyone have any idea what could cause this? Our HW guy is pouring over the schematics trying to find something, but I want to make sure it isn't something stupid I did on the BDI2000 config.
Ed Okerson