2019-08-22 06:29 AM
For each microprocessor of the ST series - there is public documentation in PDF format, for example DS10916 (pages 76-87). I want to make my own format for describing AFxx contact states. When you try to convert a table from PDF to text or Excel tables, there are errors that need to be fixed, they turn out to be unreasonably many. Size of the description in the format of structures - takes 2500 lines for the body on 208 feet. For this reason, manual labor is not desirable, it’s easier for me to write a small program for converting data. But the data for this work should not have errors. I am in search of this data.
Yes, I have a little time to invent a new bike, but I don’t have time to fix all the data conversion errors.
zap_gpio.G.pin14.v_af11_eth_mii_rmii_txd1.s100Mgz.pull_up.open_drain.lock_on
In this form, the structure element gets into the macro, where it is converted to the text version, the text is analyzed, and the 32bit control number is formatted for the function of setting one contact. During compilation, the macro is fully executed by GCC on a large machine. The firmware gets read data on the offset and call the function to set up one contact - only two commands in assembler.
2019-08-22 10:40 AM
For providing Pin- and Dma-Mux headers, I use the XML description in the StcubeMX device description and warp these files with python helpers to headers as in
https://sourceforge.net/p/ethernut/code/HEAD/tree/trunk/nut/include/arch/cm3/stm/generated/
You find the python scripts in
https://sourceforge.net/p/ethernut/code/HEAD/tree/trunk/nut/tools/helpers/stm32/
2019-08-22 03:06 PM
Pages linked to other pages ... Not available to me at this stage.
https://bitbucket.org/AVI-crak/system_f746/src/default/testing.h