Turn off the power to the ODrive and set the DIP switch back to RUN mode. I suspect the V2.1 stuff will also work with the older V2. I'd start by using the ST-LINK Utilities, make sure you update the firmware, and then use the V2 or V2.1 driver package as appropriate, and the 32-bit or 64-bit installer depending on your version of Windows. Congratulations your ODrive should now be flashed you can now quit DfuSeDemo. The V2.1 drivers are for the mbed enabled version of the ST-LINK. If you get a warning that it’s not possible to check that it’s the correct device type: click yes to continue. Locate the ODriveFirmware.dfu we made before. In the bottom right section called “Upgrade or Verify Action” click the button “Choose…”. 
You can simply delete the file C:WindowsSystem32driverslibusb0.sys.
If, after doing the above step, the ODrive still installs itself as a libusb device in Device Manager, you can try to delete the libusb driver (this is OK, since we can use Zadig to install it again). We need to set it back to the original driver. If it doesn’t appear, it may be because the driver is set to libusb by Zadig. In the top left it should now be connected to “STM Device in DFU Mode”. Force the ODrive into DFU mode, as per the instructions above “How to force DFU mode”. Launch DfuSeDemo.exe which probably got added to the start menu as “DfuSeDemo”. Note that the success message has a warning sign for some reason… Save the output file as ODriveFirmware.dfu. Leave all the other settings as default and click the “Generate…” button. 
Click the button that says “S19 or Hex…”, find the ODriveFirmware.hex file you built or downloaded.Select “I want to GENERATE a DFU file from S19, HEX or BIN files”, press OK.After installing the tool, launch DfuFileMgr.exe which probably got added to the start menu as “Dfu file manager”.Unfortunately they make you create a login to download.
0 kommentar(er)
