MikeB wrote: ↑Thu Oct 31, 2019 12:08 am
Do you know what file the bootloader is in? Or is it the one that was on the radio when you first got it?
When in the bootloader, and you plug in the USB cable, do you hear the "USB device connected" tones? If so, can you tell what device is now connected?
If the bootloader presents hard drives, then there should not be any driver problem as hard drives use a standard, built in driver.
eepskye searches for a hard drive with a specific volume label. It actually allows for two different labels as openTx used a different name.
I am clearly in over my head in this.
When I got the T16, I installed JumperTx and later Open Tx with companion.
So the bootloader would either have been there originally or only after I installed STM32 with Zadig.
As far as I can tell, STM32 sits in Windows\System32\DiverStore\FileRepository.
I do not know the name of any other pertinent bootloader. Can you tell me what to look for?
When starting in BL mode (trims inwards) it shows HORUS BOOTLOADER with options to: "Write Firmware or Exit or Plug in USB Cable for mass storage"
At the bottom of the screen it says "Current Firmware: no version found"
With the USB plugged in it says "USB connected" and I get the sound.
Now, in the File Explorer, I see an F: drive with Firmware.bin and Firmware.txt and a drive E: with a whole series of folders starting with Crossfire, Firmware, etc...
The Firmware folder contains the t16_rom.bin which I put there directly on the SD card..
This for me is the same as I got when running OpenTx. At least The PC now sees the SD card.
Now, how do I make eepskye see the Tx?
Hope this helps.
I really appreciate your help.