Why no header with ID Codes and ROM constants

[Uwe Bonnes]

Posted on October 13, 2016 at 16:47

Hello,

why are ID Codes and ROM calibration values like TS_CAL1 not available in the device headers? This make writing portable code harder. Bye #id #calibration #device-headers

[Nesrine M_O]

Posted on October 13, 2016 at 17:30

Hi bonnes.uwe,

Could you please clarify a bit more your suggestion? 

•What are you using as STM32 product?

•In witch firmware do you think this is missing?

-Syrine-

[Uwe Bonnes]

Posted on October 14, 2016 at 13:59

I use a lot of STM32 devices,  mostly as Nucleo and Discovery Board and some devices  (F303/F373) on ''production boards''. I use and work on the STM32 branch of the ''Ethernut NutOS'' http://ethernut.de in SVN head from https://svn.code.sf.net/p/ethernut/code. The library is based on the device headers, like stm32f303xc.h, imported from the Cube headers.

None of the Cube headers defines the Device IDs. For some device families , the device ID can be found in cube file as comment like in ./STM32Cube_FW_F3_V1.6.0/Drivers/STM32F3xx_HAL_Driver/Inc/stm32f3xx_ll_system.h:  * @note For STM32F373xx and STM32F378xx devices, the device ID is 0x432 For F2/4/F7 no stm32XXxx_ll_system.h file is provided and Device ID has to be extracted from zillions of different reference manual. Similar adresses of the factory calibration block items are not given consistant. E.g. for the temperatur sensor calibration, some stm32XXxx_ll_adc.h list the address of TS_CAL1 but again not consistantfor all families. Having this information in the device headers stm32Xyyyxx.h would be a good thing.