The problem lies in when the board is connected without pressing the bind pin so the board can be configured. To me, and I may be wrong, seeing as the board is being seen and able to be flashed with firmware when in DFU mode, that part is all working as it should. I realse that this must be very frustrating for you seeing as my knowledge of all this is so basic but I am explaining it in the best way that I can. How do I access ST's DFU Manager? In regard to ''When Windows claims it can't find it, what VID/PID is the Unknown device reporting?'' what is VID/PID please.ĭo those match the one's Zadig was using?'' from my extremely rudimentary uderstanding, Zadig is just replacing the STM Driver with the WinUSB one. ''Can ST's DFU Manager software see the board?'' Sorry to sound clueless but all I know about this is what I have been asked to do to get the board flashed and configured by the developer. As for the ST Driver finding the board in DFU mode I am not sure because the developer asked that it be replaced with the WinUSB Driver. Therefore the instructions are good and the WinUSB driver that Zadig replaces the ST Driver with is also sound. My friend with the same problem is also using the same OS. I have these issues on mu 32bit W7 PC but my PC at home running the same OS works perfectly. The instructions are working for everyone that I know of other than myself and another friend.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |