![]() the 'work around' is to find alternative more reliable upload means including manually. ![]() It is convenient but that if one runs into 'driver problems'. ![]() The resetting provides some convenience as otherwise you would just need to press that reset button manually.Īfter resetting it calls dfu-util in the 'good old' maple way to upload the firmware. Note that this 'resetting' has nothing to do with that 'old' maple/stm32duino libmaple dfu bootloader. It is an old maple magic that's still there today That java-loader magic is simply that it sends a DTR 1EAF command to the sketch and the sketch / core triggers a reset. i'm not too sure if this is indeed the symptom, but accordingly such behaviors can happen in windows. that driver may keep thinking that it is still connected even if the board is already disconnected. if you unplug your blue pill without 'informing' windows, and your driver is after all 'hogging' that port e.g. those may cause other woes related to the usb-ports. Windows has various 'gotchas' such as that it may 'hog' drivers etc. In case anyone is looking for a release 'jssc.jar', and messing with windows sources and drivers is 'too intimidating' (it may not work even if you try), i think processing uses jssc.jar, so you may be able to find something there. Or you can try with the updated open sourced tools like dfu-util, st-link, stm32 loader etcĪ main thing you may want to first try if you insist on 'integrated' flashing is perhaps to update that jssc.jar with an updated release jar. The alternatives are to do that upload manually. never! whatever java distributions you are using. This is a likely potential trouble spot that will not go away. The minefields are actually the windows dll interfacing the c libraries to the actual windows serial drivers dll. Rather, you probably would want to try using a updated release of jssc in the earlier link or literally build it from source. If you are willing to go the distance i'd guess you could try to rebuild that java-loader.jar as the source code is there. This is apparently used by processing and that java-loader is apparently written in processing. If i'm not wrong jssc is actually a serial driver / connector library I think these problems may have something to do with the dicey windows dll environment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |