Dave,
I did a virgin git-clone this morning and got U-boot running on my MPC8349EMDS. I'm afraid there's nothing too exotic in the methods, though. Here's the sequence:
1. host$ cg-clone git://www.denx.de/git/u-boot.git 2. host$ make MPC8349EMDS_config 3. host$ make all 4. Cold boot board and BDI-2000 5. Program image: 8349>erase 0xfe000000 0x20000 2 Erasing flash at 0xfe000000 Erasing flash at 0xfe020000 Erasing flash passed 8349>prog 0xfe000000 mpc8349emds/u-boot.bin.0721 BIN Programming mpc8349emds/u-boot.bin.0721 , please wait .... Programming flash passed 8349>reset run
I checked all switches and jumpers on the board to make sure I hadn't changed anything. No dice.
Here's the [TARGET] portion of my BDI-2000 config file. This morning I didn't override the HRCW, but have played around with that in the past when things didn't do what I wanted:
[TARGET] CPUTYPE 8349 ;the CPU type JTAGCLOCK 0 ;use 16 MHz JTAG clock POWERUP 2000 ;start delay after power-up detected in ms WAKEUP 500 ;give reset time to complete STARTUP RESET ;halt immediately at the boot vector ;STARTUP RUN ;halt immediately at the boot vector ;RCW 0xb060a000 0x04040000 ; low boot memory, TSEC 1&2 GMII ;BOOTADDR 0xfff00100 ;boot address used for start-up break BOOTADDR 0x00000100 ;boot address used for start-up break BREAKMODE SOFT ;SOFT or HARD, HARD uses PPC hardware breakpoint ;STEPMODE HWBP ;TRACE or HWBP, HWBP uses a hardware breakpoint STEPMODE TRACE ;TRACE or HWBP, HWBP uses a hardware breakpoint MMU XLAT 0xc0000000 ;enable address translation PTBASE 0x000000f0 ;SIO 8023 115200
I suspect your config file has the high boot address, and that's why it's not working. Dave Liu hinted towards that, I believe.
Let me know if there's any other information you need.
regards, Ben