There are 3 layers for how this works. The Application (CPS or firmware loader), the Dynamic Link Libraries provided by STM to interface to the driver and the driver installed by Windows (which is also from STM)SA0BUX wrote: ↑Mon Jul 31, 2023 4:31 amNeither I have any knowledge about windows (driver) debugging, I did some debugging inside Solaris years ago.
But It's positive that we now know when this error occur and how to workaround it.
I never had any thought that such locale settings could affect this.
As the Baofeng loader includes the DLL files, then the Baofeng loader probably uses them to interface to the driver.
If I have time I may try setting one of my PC's to Turkish language and see which DLL API call is failing, but it would be very difficult to go much further.
STM provide the source code to their DLL's, so in theory it would be possible to debug inside the DLL to understand why their are causing an 'exception'
But this would take many hours of work, and I have a lot of other things I need to do related to the firmware and CPS.
And it seems that the problem with the Turkish language can be fixed by simply switching the PC language to English when using the firmware loader in the CPS.
Actually, there may be a workaround by the CPS changing the language paramaters under which it runs
e.g.
Code: Select all
System.Globalization.CultureInfo ci = new System.Globalization.CultureInfo("en-US");
System.Threading.Thread.CurrentThread.CurrentCulture = ci;