ATm32U4DFU Drivers

Go To Last Post
6 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

When I try to upgrade my mEDBG firmware, the application restarts the board into DFU mode, but Windows doesn't load the ATm32U4DFU driver.

 

I looked in my Atmel Studio folder for the driver, but I don't see any inf files for anything other than the Jungo stuff, which I gather isn't the right driver for this device.

 

I tried downloading driver-atmel-installer-x64-7.0.305.msi and driver-atmel-bundle-7.0.666.exe and AtmelStudioUSB-7.0.31.exe, and driver-libusb0-installer-x64-7.0.305.msi and none of them work -- the exe files fail and rollback, and the MSI files either appear to do nothing, or they produce the error message "The specified account already exists"

 

Which drivers should I use for ATm32U4DFU?

 

I'm on Windows 10 build 14291

 

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Forgive me if I am wrong, but I don't know what product this is? Do you mean you're using an Atmega32U4 in DFU (Device firmware update) mode?

 

If this is the case you must realise that the chip itself has a usb component but not an internal usb driver. As such, you either have to write one or get a USB library, upload the hex to the device, then use their windows driver to talk to their atmega usb driver.

 

An example of this would be for the Arduino Pro Micro. I havn't had experience with their software, but you should be able to upload a bootloader initially and go from there. Else you could look at other projects like Teensy "http://www.pjrc.com/teensy/usb_s..." based on the avr family. Teensy comes with a windows driver so you can mount a serial port if thats what you're after as well.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

This is for an ATmega328P Xplained Mini dev board. I'm talking about the mEDBUG firmware running on the on-board debugger (re-read my initial post, please).

 

hen I try to use the board with Atmel Studio 7.0, it complains about the version 1.0 firmware on the board. It tries to update the firmware by (I gather) rebooting the debugger MCU into a DFU mode. The MCU instantiates itself in Windows as a "ATm32U4DFU" in Device Manager, but no drivers are loaded, thus the atfw tool obviously can't communicate with it and send it the new firmware it needs. So the operation fails. I can unplug the board and plug it back in to reset it back into mEDBUG mode, but without loading the Windows drivers for the device when it's in bootloader mode, I'm not sure how it'd ever be able to update its own firmware.

 

I'm having the same problem as mentioned here:

https://www.avrfreaks.net/forum/e...

 

So, I followed along with the supposed solution, but whenever I try to install any of those driver packages, it fails (as I mentioned in my initial post).

 

I hope that's more clear?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I was able to get it working. I stumbled upon a sketchy download link to "ATm32U4DFU Driver" (http://www.driverscape.com/files...). It wasn't signed, so I had to reboot into test-signing mode. When Atmel Studio's firmware updating utility rebooted the Xplained Mini into DFU mode for the firmware update, I installed the driver in Device Manager manually. It then worked fine and updated the firmware.

 

This obviously isn't a very good solution. I see that the libusb0 drivers are in the "Drivers" folder inside Atmel Studio, but there aren't any INF files in there. What gives? How is a user supposed to manually install those drivers if necessary? Please make sure the appropriate INFs are located in the Drivers folder for the next release of Atmel Studio.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

All the inf files are installed by default in the driver catalogue. No te that there's a separate MSI that deploys these infs and preregisters them in the PNP system. If you have installed Atmel Studio in another location before, then the inf files may still be at that location.

Also, doing a repair of the USB bundle (available on gallery.Atmel.com) should reregister them in the PNP system.

If the driver doesn't bind , you should be able to just choose update driver, and go to the choose from list option and it should be one of the compatible driver listed there.

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I have had a similar problem.

I was using Atmel Studio 6.2 Service pack 2

I was able to program the Atmega328P-XMINI in Windows XP with Service Pack 3

The following items showed up in the Device Manager:

Under Ports COM & LPT

mEDBG Virtual COM Port (COM 5)

Under Serial Bus controllers

USB Composite Device

 

1. Now all of sudden Atmel Studio 6.2 forces me to upgrade the Firmware in the Atmega328P-XMINI

    It will disconnect from the Atmega328P-XMINI if I don't upgrade the firmware.

    After upgrading the Firmware for the Atmega328P-XMINI Atmel Studio 6.2 no longer can communicate with the board.

    I have contacted Atmel and sent them many emails describing the problem.

    I Installed FLIP version 3.4.7 and this utility will find the DFU Atmega32U4.

   After the Firmware upgrade to the Atmega328P-XMIN both entries in PORTS and USB have disappeared.

   Now then the Atmega328P-XMIN is plugged in i get the following in Device manager:

   XMOS Devices\ATmega32U4

 

2. I have asked Atmel if the problem is that Atmel Studio 6.2 does not support DFU programming.

    All I get in response to my question is a request to reinstall Atmel Studio 6.2. This I have done three times,again the same problem.

    They should not have forced the user to upgrade the firmware for the Atmega328P-XMINI.

     Atmel is now following the same route that Microsoft follows. This is the reason that I don't use any form of Windows for development.

     Windows has been a pain from day one.

     Is this the result of Microchip buying out Atmel?

 

  3. I have asked Atmel How I can restore the original Firmware, they have refused to give me this information!

       Using FLIP I find that there appears some protection mechanism placed in the Bootloader preventing you from upload the contents of the EEPROM used to store the Bootloader.

       I don't know if it is possible to use the JTAG interface on the AVR Dragon to remove that bit that is set in the Bootloader.

 

4. The other problem that is now occurring is that when ever I start Atmel Stuidio 6.2 I receive the following error:

     Windows - Fatal Application Exit

     WinDriver - This is an unregistered copy,available for 30 day evaluation period. You have 23 day left.

    Please note: I have removed Atmel Studio 6.2 each time all with any files that has to do with Atmel Studio along with all USB drivers that were install with Atmel Studio including the WinDriver.

    Each time its the same problem.

 

5. It appears that the latest version of Arduino support programming the Atmega328P-XMIN. Until I get a new board with the original fiirmware on it I can't confirm this.