Error 12340002 using STM DFU DLL's SelectCurrentConfiguration

[roger239955_stm1]

Using the STM DFU DLL's to load firmware onto some 3rd party custom hardware, we have to call  SelectCurrentConfiguaration becuase the bootloader in the hardware requires this before it allows the STM32F4xx ROM to be written to

Normally this works OK.  However users in Turkey have reported Error 1234002 when this call is made , and they are unable to install new firmware.

This problem only seems to affect Windows computers which were installed with the Turkish locale.

Setting the Turkish locale on a English or even German  version of Windows, does not cause the problem.

But on PC's with Turkish as the initial / default locale, adding the english locale and switching to that locale to install firmware seems to fix the problem.

Is this a know problem with the DFU DLL's ??

[roger239955_stm1]

Just in case anyone else has this problem.

You need to set the application locale / cultural setting to English / USA . Probably any English cultural configuation would be OK, but US English definitely works

I've no idea why the STM DFU dll gives and error when calling set config when the language is set to Turkish and I don't have time to debug into the dll

[Peter BENSCH]

The DFU DLLs were part of the package STSW-STM32080, which is now no longer recommended for new designs. The DLL has an error offset called STDFU_ERROR_OFFSET = 0x12340000 and the difference 2 denotes the error STDFU_BADPARAMETER.

Instead of this package, the STM32CubeProg is recommended, where either its CLI or alternatively its CubeProgrammer_API.dll can perhaps replace the DFU DLL in your application.

Hope that helps?

Regards
/Peter

[roger239955_stm1]

Thanks.

Does the CubeProgrammer_API.dll have the same API as the old STDFU.dll and STTubeDevice30.dll

I also don't see any information files related to distribution of the DLL's in the installation files.
Unlike the old version which had STM_License_SLA0044.txt  which allows distribution

I doubt it would be economic, for us to rewrite the loader part of our application, as the work-around by setting the locale / cultural settings of the loader thread has fixed the problem.