Thanks for your help Jeff. I finally got it installed over the weekend. Had to install the LibUSB Filter Driver to allow AVRDUDE to talk to the AVRISPmk2, since the Atmel Studio drivers apparently changed at some point and prevent AVRDUDE from being able to find the USB device, even if Atmel Studio is not running. Embedded drivers: WinUSB v6.1.7600.16385, libusb-win32 v188.8.131.52, libusbK v184.108.40.206 & usbser (native). Libusb is a C library that provides generic access to USB devices. It is intended to be used by developers to facilitate the production of applications that communicate with USB hardware. It is portable: Using a single cross-platform API, it provides access to USB devices on Linux, macOS, Windows, etc. LibusbK is a complete driver/library solution for vendor class usb device interfaces. If you are a usb developers or usb device manufacturer seeking a driver solution for a new USB widget then libusbK could be for you. LibusbK encompasses a 100% WinUSB compatible api/funtion set. All WinUSB power/pipe polices are fully supported by the libusbK. The package provides the installation files for Microsoft WinUSB Device Driver version 220.127.116.11. In order to manually update your driver, follow the steps below (the next steps): 1. Go to Device Manager (right click on My Computer, choose Manage and then find Device Manager in the left panel) 2.
This tool simplifies installation of the USB drivers for Libusb and FTDI D2XX drivers for your devices. Simply select the device from the list, right-click, select the desired driver type and the tool will do the rest. No need to modify INF files, no need to click through multiple stages of Device Wizard, just one click and your drivers are installed!
You can download the USB driver tool here: UsbDriverTool.exe
UsbDriverTool is free for commercial and non-commercial use.After this successful transfer of the DMR database, the RT3 / MD380 could now decodeany of the 49000 DMR-IDs in the database into callsign and operator name.
The journey of exploring the 'Experimental' firmware continues on DL4YHF's Retevis RT3 / Tytera MD380 page .
Switching from the default USB driver ('STTub30' for the Retevis/Tytera CPS) to libusbIf you frequently switch between the normal CPS ('Customer Programming Software') and the MD380-Tools, consider touse Zadig to switch from the 'STTub30' driver (which appears as 'STM Device in DFU Mode' in the device manager)to the libusb driver (or similar driver compatible with the MD380-Tools). Zadig can install or replace the currently selected driver with just a few mouse clicks.
- Connect the radio to the USB port and turn it on (normally, not in firmware-update mode)
- In Zadig's 'Options' menu, select 'List All Devices'
- In the drop-down list, select 'Patched MD380' (see screenshot in the next chapter)
- In the field right next to the green arrow, select 'libusb-win32 (latest version)'
- Click 'Replace Driver' and wait until done.
'Switching back' to the default USB driver (for the Retevis / Tytera CPS)Occasionally, I wanted to edit the codeplug with the original Retevis (or Tytera) CPS under windows.After installing libusb_win32 (or similar), this didn't work anymore, since the USB device(the 'Patched MD380') was now occupied by the libusb_win32 'driver' !
Unfortunately there is no way to switch back (via Zadig) to the 'original' driver.
Remember which driver was in use
See Full List On Nuget.orgbefore installing libusb_xyz ? Here the screenshot (in Zadig)before
Download Libusb.org Usb Devices Driver Windows 7switching to one of the possible drivers for the MD380-Tools:
('STTub30' was the driver installed by the Retevis CPS, in December 2016)
Since it's not possible to 'switch back' to the original driver with Zadig, I had to use the following stepsunder Windows 8.1 to get the original USB drivers back:
- Open the Device Manager ('Start'..'Control Panel', etc etc etc or simply run 'mmc devmgmt.msc')
- In this case, the 'Patched MD380' was listed under 'libusb-win32 Usb Devices'
- RIGHT CLICK on it, select 'Uninstall' / 'Deinstallieren' ... but hold on, DON'T PROCEED TOO QUICK !
- Make sure 'Delete the driver software for this device' is checked
(on a german PC: Haken vor 'Die Treibersoftware für dieses Gerät löschen')
- Turn the radio off and on again (or disconnect from / reconnect to USB).
Only because we've deleted the driver software,
windows will NOT immediately re-install the libusb_win32 driver (or whatever we installed via Zadig & Co) !
- If the 'Patched MD380' still appears as another 'libusb' device or similar outside the 'USB-Controller' list, repeat the above step (uninstall + delete driver).
- Sooner or later, windows surrenders, and the 'STM Device in DFU Mode' appears in under 'USB-Controller' again.
Dr Zadig would then identify the current driver for our 'Patched MD380' as 'STTub30', as it was after a clean install of the CPS (see screenshot further above). Anything else causes the Retevis/Tytera CPS not to recognize the radio, because it can only talk to the 'STTub30' driver.