AVR ATMega 2560 USB driver error - windows

I have an issue while installing drivers for the ATMega 2560. I downloaded the drivers from the ATMEL website, no issues during installation, but once small window pops up it gives me an error that the drivers are not compatible with x64 operating systems, although a lot of my colleagues are using x64. If you need I can take a snip of the error message.
P.S. Forgot to mention I`m using x64 Windows 8.1, with the latest updates installed and Atmel Studio 6.2.1153

I had the same problem recently and many of the driver links on the Atmel and other sites are for old versions of the driver. If you install the Atmel Software Framework you'll find signed drivers in a location similar to the following:
C:\Program Files (x86)\Atmel\Atmel USB Drivers\inf\atmel_devices_cdc\atmel_devices_cdc.inf
C:\Program Files (x86)\Atmel\Atmel USB Drivers\inf\atmel_devices_cdc\atmelinf.cat
Supported Windows versions are listed as Windows 2000, XP, Vista, 7 and 8 (x32 and x64) and I've confirmed it works fine on Windows 8.1 x64 as well. I've assumed you're using a CDC class driver but there are also updated drivers for the DFU bootloader if that's what you're after.

Related

Kernel Driver Procedure Not Found

I have recently developed and tested a kernel driver in windows using visual studio. The Driver itself is nothing but a notifier which prints info about created processes. I have already tested the code on a Windows 10 x64 machine by putting the Windows 10 x64 VM into test mode and installing the driver as a service. It works just as it should.
However I want to test this driver code on multiple windows os versions. The problem is whenever I follow the same steps on Windows 2012 Server R2 x64, Windows 7 x64, Windows 8.1 x64 all of them throw the same error.
Procedure Not Found Error:127
You are most likely calling a function that is not available on older versions of Windows.
Open the driver in Dependency Walker on one of the systems where it fails.

How to simulate sensors with Visual Studio 2015 and Windows 10?

I'm trying to develop a simple Windows 10 app and I wanted to simulate a Pedometer for testing. How can I do that? And what about other type of sensors, can I simulate them too?
Ok I found a solution.
Microsoft provides sample drivers here and there you can find sensors folder. So download what you need, compile and deploy.
To compile you need Windows Driver Kit.
If you're deploying to a x64 machine the drivers has to be signed. I had trouble signing the drivers so I booted Windows 10 with no driver signature enforcement and deployed the driver using DevCon. Check the driver INF once compiled to see the installation instructions.

CUDA in Windows XP Embedded

I want to do CUDA programming in Windows XP Embedded OS with graphics card Quadro 600. The CUDA SDK i want to use is 4.0. I searched NVIDIA driver for Windows XP Embedded, but i didn't find it in the nvidia driver download site. Where do i get the nvidia driver for Windows XP Embedded OS.
How can I run the CUDA application in that machine.?
Please help..
Have you tried installing the regular Windows XP driver from NVidia for your card? XP Embedded is just a componentized version of Windows XP, where you can leave out OS components that you aren't using. It's not a different kernel like Windows CE. As far as I know, it's just the normal XP kernel, so normal XP drivers should work, unless NVidia is doing something to prevent that. It's also possible, of course, that necessary components were left out of your Windows image by whoever built the XP Embedded image that you're using.

Why does installing a device driver from a virtual drive fail in Windows 7?

I have a driver that needs to be installed from a virtual drive. I am able to install this driver (*.sys) from the normal directory, but when I try to install it from a virtual drive it does not happen. Is there any constraint on installing Windows device drivers from virtual drives?
I think installing drivers from virtual drives on Windows XP is possible.
I am using Windows 7, both x86 and x64 versions.
If you're using two different bit versions of windows from your actual windows and your virtual machine. Say that in your virtual machine is windows x64 and your actual windows is x86. The 64 bit version of the driver would not be compatible with the 32 bit version of windows.
After a hell lot of effort, I found that Antivirus is the issue. The setup should not give any error while installing. Please run as administrator when you run the setup and turn off antivirus if any.
Turning vmci0 value to false is not at all a good approach

WinUSB failing on non-development computers

Good afternoon,
WinUSB is working well on the development computer that I am using (Win XP SP3). I am able to download new firmware to the Cypress FX2, and then connect to the new USB device once it 'renumerates'. However, if I've tried the same code with the WinUSB driver on a few other computers (Win XP SP3, Win7 x64) and they both returned the error "A device attached to the system is not functioning." when trying to use CreateFile to get a handle to the USB device.
The devicePath was found successfully, so I'm not sure why it cannot connect to the device. Furthermore, the device manager states that my device is working properly. I'm curious if I'm missing something when compiling the code? I would guess that my development computer has something installed on it that the other computers do not? Or perhaps it's a power setting and the device is going to sleep (although I've fooled around with the Power Options on each computer to no avail).
Does anyone have any ideas? I've compiled under Visual Studio 2008, and have installed the Microsoft C++ 2008 Redistributable Package on the computers that I've tested on.
Thanks,
Giawa
Solved: The GUID that my driver was using was shared with another device on the system, which was returned instead of my device. The device just happened to not be installed on my computer. I've generated a new GUID and everything seems to work now.
Giawa

Resources