Ok, my bad, I found out what went wrong with my board: I forgot to erase the flash and bring back the SAM-BA program on it. Once I did this the board was recognized by Windows as the mentionned-above GPS camera. Sorry for that!

For my understanding, why do you want to use Samba?
Is not a JTAG programming tool such as Segger's J-Flash (which works with SAM-ICE) a better solution?
I found that the SAMBA 32-bit driver caused a lot of blue screens, so we are not using it in production.
Is this a known problem or has it been fixed lately?

I don't have theses problems, and I'm working with SAM-BA because I don't have any JTAG programming tool. My dev kit cost me enough, and for the moment I don't have much money to put in this project! I bought the kit for my own free time at home. Maybe later I'll think about buying a JTAG, though

In USB a product ID and a vendor ID are unique to a device. Eg a company will buy a set of IDs and they will be theirs to keep.

My question therefore is have Atmel stolen a VID PID from a GPS camera. Or has Microsoft added a device which has stolen Atmels IDs. Someone has dropped the ball here.

A good reason to use the USB bootloader is that you do not need a JTAG tool. Customers would much rather plug a device into USB then mess about with JTAG programming tools. Especially if they are non-technical.

Hello! I found a document regarding "GPS Camera Driver". Solution described there worked for me, but I have 32-bit OS.

http://www.bipom.com/documents/boards/g ... 0Guide.pdf

I was unable to get the GPS camera driver to work for me on Windows 7 64bit.

I have now got sam-ba to work though - using the approach in post 3 here: http://www.avrfreaks.net/index.php?name ... c&p=649123

Download that .inf, change the PID to match the eval board, and install - giving a new virtual com port. Then use sam-ba over this port.

Thats right, the atm6124_cdc.inf will not work in 64bit OS because the .inf does not have the NTamd64 sections.

The VID/PID in the .inf must be made to match exactly or it will be ignored. But there are two options "USB\VID_03EB&PID_6124&REV_0110", and another without the REV_0110.

After i installed driver, and com port appeared, i tried to run sam-ba_cdc_2.9.xp_vista.exe, but this process just hung after i selected the correct com port and ev board type.
I was able to connect to the board using another XP computer with sam-ba-2.8, on that it is \usb\ARM0

I found a good solution (and explanation) to the 64-bit CDC driver issue here:

http://blogs.6bit.com/josh/2009/10/usb- ... t-windows/

SAM-BA is up and running on 64-bit Win 7

Wish Atmel would update their INF file .... it's as simple as that.