![]() (I've read a lot of places where people seem to have the mistaken impression that Zadig tells the board what mode to be in, or even that Zadig somehow tells dfu-util where to install the firmware). Windows doesn't know that 0xef98 and 0xef99 are even the same physical board - it relies entirely on this identifier (the USB VID/PID) to decide what to do. The driver that you install with Zadig tells Windows what to do when it detects a given device. Hopefuly Pycom is working on a solution definitely confirmed (with Pycom) now that the boards are faulty - unfortunately you'll need to get a replacement - I assume they'll announce something? To perform a proper firmware update I still have to press and hold the S1 button while connecting the Expansion Board. This program is Free Software and has ABSOLUTELY NO WARRANTYĭfu-util: Cannot open DFU device 04d8:ef99ĭfu-util: No DFU capable USB device available ![]() Interestingly, the device doesn't really seem to be in update mode, as trying to execute:Ĭopyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.Ĭopyright 2010-2016 Tormod Volden and Stefan Schmidt The part ef99 indicates firmware update mode as decribed here. If I now check my usb devices (on ubuntu) with lsubs it gives: Bus 001 Device 070: ID 04d8:ef99 Microchip Technology, Inc. The first thing I did after receiving the board was to execute the update. Unfortunately, I don't know if it was introduced by the firmware update or already existed before.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |