ĭownload either OTX 2.2.4 (last from 2.2) Since bootloader can be normally flashed from OTX it self. You don't have bootloader yet - but it can show as mass storage. You have OTX 2.2.1 already installed (at least not FrOS) ![]() Obviously - I was too tired to think at all last night - might be no better now too - but I feel that I just couldn't "drive through" my thoughts last night. So this might be a "if nothing else" method.but perhaps wait for others more knowledgeable chime in on the validity. I know from the past that small version differences between older bootloader vs new OpenTx versions played well together. Then plug into USB if it does, and see if you can flash the main program from Companion. Then try the three finger salute to see if the bootloader comes up. Turn the power off after it returns to the file directory screen. Insert the card back into the radio (if needed), and then using the radio navigate to that file to flash the bootloader. As noted earlier save the "opentx-x10express-lua-noheli-ppmus-en.bin" (or whatever your variation is) to the firmware folder. Ummm - DANGER AHEAD.but perhaps you can download the latest and greatest 2.3.11 using Companion.and then copy that file to the SD card (either as a mass storage, or by moving the card to another card device). Companion says something such as "No compatible USB DFU Device Found". Unfortunately because it's not in bootloader mode it will not flash, or back up for that matter. Yes, if it's turned on it shows as "USB Mass Storage Device". I would try disabling, finding and deleting ( or renaming) the Guillemot driver files, so they can't re-install. Just have to figure out how to stop windows from undoing my driver update.any windows gurus know what's going on? Interestingly enough, in that 3 second or so window I was able to successfully do a backup of my radio firmware. (This is the exact same behavior I see with Zadig and Driver Fixer, just doing it manually) It stays that way for about 3 seconds and then reverts back to what you seen in the first photo. I did a manual driver update using the "STM32 BOOTLOADER" driver and it gives me what you see in the second photo I've attached. If I go into Device Manager I find my radio under "Sound, video and game controllers" as "Guillemot STM DFU Device" as seen in the attached photo. I will post an update once I have the "programmer".I tried a quick peck and nothing happens, press and hold and it turns on like normal.all holding the trim switches of course. ![]() Perhaps as the poster suggested the USB has been damaged, however the device is meant for low power RF purposes and even has a low power generator for measuring S21, I would be surprised if RF killed the USB, *but* you never know. I need to thoroughly read the datasheet for this device. The poster tells me this will make no difference, and he appears to be correct.Īnd yes I have been lazy. I did try heating up the package but with no success. Again a big guess is that the oscillator frequency might have drifted out of spec, as hinted at in the article. (*) Since there is no crystal on the PCB, I assume that it must be using the internal RC oscillator, which is possible factory calibrated. ![]() Push comes to shove I can remove the CPU and replace with a new one. Since it was "broken" he gave it to me, since I have an interest in microcontrollers and he thought that I might be able to "fix" it. ![]() This is an open source design, and since it's release much improved versions of firmware have been released, which is why my friend wanted to connect the device to USB. The original firmware is actually working. I hope that it might be possible to burn the firmware using this programmer, but I have no idea. Although I have familiarity with many different micros, I know virtually nothing about the STM32(*), so it will be a bit of a chance to learn. I have no idea if this will work, or even what the programmer can do. The SW pins are brought out to an edge connector. I have purchased a cheap gadget which apparently does SWD (OpenOCD programmer). Power State : D0 (supported: D0, D3, wake from D0)Ĭhild Device 1 : HID-konformes, vom Hersteller definiertes Gerätĭevice ID : HID\VID_0483&PID_572A\7&F3C2821&0&0000 Status : 0x0180600A (DN_DRIVER_LOADED, DN_STARTED, DN_DISABLEABLE, DN_REMOVABLE, DN_NT_ENUMERATOR, DN_NT_DRIVER) Manufacturer Info : (Standardsystemgeräte)Ĭapabilities : 0x94 (Removable, UniqueID, SurpriseRemovalOK) In that mode the USB device looks fine with STM VID (0483) and some PID 572A (read: communication/temp. Physically all should be well: There seems to be a demo programm running right after reset, that dimms and brightens the LED cyclically.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |