Hi Jason, this is a tricky problem! What program are you using to do the Xmodem transfer? We use minicom at 115200 baud. Perhaps the clock is going out of sync?
Regards Alec All, I'm currently troubleshooting a bad roach1 board, and I thought I'd ask for some advice about the problems I'm seeing. The board seems to be bricked. It doesn't do anything on power up. So, I attached our wiggler and it appears to successfully run the macro loadram_rinit_auto.mac. However, I don't get the funky "S" character on hyperterm after the macro completes. Instead, it displays multiple strings of hex numbers. For grins, I tried to send the uboot file (uboot-2010-07-15-r3231-dram) via xmodem even though I didn't get the "S" character. It seems to transmit fine for the first 257K of 384K, then it stalls out badly. The transfer doesn't fail (according to hyperterm), but the rate drops way down to almost a stop. I looked at the RS232 lines with a scope and the signal levels look ok for the first 257K, but at that point transmission does indeed stop. Seems like the first issue is that I'm not getting the "S" character, so maybe something's going on with the macro execution...? I checked all the PPC clocks and they look ok. They are identical to those compared to a good roach1 board. Has anyone else ever had this problem? Any ideas on what could be going on? Thanks in advance! Jason
