Hello UHF MD-380 owners... and MANY thanks to Travis and others on the team, for their programming efforts and for their countless hours they have put into this project!
I have been trying to understand why I was only able to perform a "make flashdb" one time under Windows and transfer the CSV file into the MD-380. Over the past month, I have tried many approaches to the way I installed then de-installed the USB driver, but with no success... until last weekend. I have been testing this on different Tytera radios, and I believe I have found a way to issue a "make flashdb" and reliably flash the 16MB SPI Flash in the UHF MD-380... via Windows.
I have performed this on 3 different MD-380s and repeated several updated CSV installs on each, running both the older (patched v2.032) and newer (patched D13.020) firmware versions. (Please note, I have skipped many steps and hopefully most users will follow what I am trying to state below.)
Normally, I would obtain either one of the following two responses when issuing a "./md380-tool spiflashid" command in a MINGW32 window:
# 1. SPI Flash ID: 10 dc 1 (...when patched firmware v2.032 is installed)
W25Q128FV 16MByte maybe
~ or ~
# 2. SPI Flash ID: 70 f1 1 (..when patched firmware vD13.020 is installed)
Unknown SPI Flash - please report can't program spi flash wrong flash type
I have found that unless you receive the following response, you will not be successful in erasing then writing to the SPI Flash:
SPI Flash ID: ef 40 18
As others have stated, they can not erase or write a new UsersCSV database to their MD-380 under Windows reliably. Here is the process that works for me under WinXP:
1. With either patched firmware v2.032 or D13.020 installed in your radio...
2. run Zadig, and install libusb-win32 (v184.108.40.206) or (libusb-win32 from: https://sourceforge.net/projects/libusb-win32/ as described in MD380tools / Windows-instructions.txt)
Once the driver is installed you will see that if you issue a ./md380-tool spiflashid command, you will received either a # 1 or #2 from the above responses.
3. Now, execute the "testlibusb-win.exe" file, then click on the Refresh button at the bottom of the popup window. (Note this file is located in the libusb-win32-bin-220.127.116.11\bin\x86 folder). Once you click on the Refresh button you will find that if you again issue a ./md380-tool spiflashid command in the MINGW32 window, you will receive the proper response from the radio:
SPI Flash ID: EF 40 18
Now you can issue a make flashdb and your CSV file will be properly installed into the SPI Flash. (remember to perform a "make clean all" in your md380tools/db folder, to update the "users.csv" file)
Note: I have just tested this process with the latest commit, 4779096 (2016-09-18) and it works flawlessly. I can not tell you why executing the "testlibusb-win.exe" file then clicking on the Refresh button changes the SPI Flash ID. Maybe it sets or resets the USB port parameters, thereby properly preparing it to accept data. (Also, I really like the new full screen CSV data display. It is much easier to read, than the original green pop-up window. I also like that the callsign is in a larger and bold font as well - thank you!)
I am writing this because I am sure the MD380tools group will see what is happening and use it to improve the repeatability for Windows users to reliably install the CSV files into the SPI Flash... :-)
Thank you again and take care,
73, N6YN - Ed