The latest version of the Atmel SAM-BA tool (v2.11) for the first time supports the 64-bit version of Windows 7.
This is something we like a lot, because nowadays evermore laptops and deskstops come with the 64-bit edition of Windows 7. Good work, Atmel!
Unfortunately, the SAM-BA tool seems to have a flaw when running under this edition of Windows 7; it takes several minutes(!)
to start up and show the initial dialog window to the user. (= window for selection of communications device and target board).
As no hour-glass is shown during this period of time, the user has the impression that SAM-BA has crashed/hang up.
Note that we have seen this behaviour now on several (Dell) laptops with Windows 7 - 64 bit edition.
We have never seen this with any PC running the 32-bit edition of Windows 7 or with any PC running Windows XP. (even when using same target board)
So it really looks like a '64-bit-only' problem.
Let me know if you experienced the same and if you know of a work-around for this problem...

What chip/board?
What connectivity mode? USB/Serial/JTAG

The SAM-ICE/J-LINK works well on the 9260/9G20 with Win7 Pro 64-Bit, with 2.11. If you want to edit the TCL files, I'd generally recommend NOT installing under "Program Files"

2.10 did go out-to-lunch on this box, ie it looked like nothing was running, it would never connect, but would error out if you disconnected it.

Running it under Virtual PC (XP) might be a workable.

Target is AT91SAM7XC512.
Connectivity: I have tried USB, JTAG (SAM-ICE) and real COM port (through PC-Card extension module, laptop does not have one itself). All interfaces have the same problem...

Hi

I try to use SAM-BA v2.11 in 32-bit windows 7 .

I instal this and load the bootloader .

Then i run the sam-ba v2.11 and chosse my target (at91sam7x256) then click on connect button , the current window close but ever open any window to send file to target ! why ?

Of curse i can send file (*.bin) to target wth previos version (sam-ba v2.9) but i have problem with this version .

Thanks.
Mojtaba

I'm having the same problem (long delay before SAM-BA GUI shows up) with AT91SAM9261 rev A silicon. Rev B silicon (only checked with AT91SAM9261S), the GUI never even shows up.

I can see in device manager that the CDC driver shows up pretty much instantly after I put the device in SAM-BA Boot mode.

Is there any new information regarding win 7 64-bit and SAM-BA?

I can confirm this problem with a 64-bit windows 7, targeting a SAM9x5EK. I haven't found any solutions yet, beside using a 32-bit computer..