I've resurrected a project which runs on an AT91SAM9261-EK evaluation board, however my development PC has changed from Windows 7 32bit to Windows 7 64bit (also different hardware).

After a lot of issues with SAM-BA not working in CDC mode, and non-CDC mode no longer possible in 64bit mode, I found a suggestion that using XP Mode in Windows 7 may solve it. (XP Mode is basically a virtual machine running XP).

I've got SAM-BA 2.10 running in XP Mode, and connecting to the evaluation kit via non-CDC mode. Applications that were built months ago and ran successfully in SDRAM are no longer working (board seems to hang). If I run them in SRAM they appear to work.

When I use the "Compare sent file with memory" it reports that they're different - even for the SRAM version which seemed to work. I've sent the .bin file to the board using SAM-BA and then immediately read it back again. What I see when I manually compare the sent and received files is that there appears to be 2 blocks of code which have moved. I'll try to explain (for SDRAM file):

0x0000 to 0x0FFF are identical.
0x1000 to 0x2FFF of received file originates from 0xE000 to 0xFFFF in sent file.
There is another swap elsewhere in the file, but it's hard to describe exactly in words.

Has anyone else seen this? I would imagine that this kind of corruption would explain why it's not working. I see a similar corruption in the SRAM application, but it occurs 0x1000 to 0x1FFFF at the first point.

I'm suspecting that SAM-BA is at fault. Does this sound right? Likely to be a XP Mode issue, or just SAM-BA in general? Any suggestions?

Thanks

David