cancel
Showing results for 
Search instead for 
Did you mean: 

Looking for registermap database to generate headers for SDCC

martonmiklos
Senior
Posted on June 12, 2017 at 10:36

Hello all,

I would like to generate register map definition header files preferably for all STM8 MCUs to for the SDCC project.

Is there any database (XML, MDB, whatever) from what I could generate it without hurting any license?

Thanks in advance!

#sdcc

Note: this post was migrated and contained many threaded conversations, some content may be missing.
23 REPLIES 23
Posted on June 23, 2017 at 15:22

Are not these bitfields specified in the datasheet?

Posted on June 23, 2017 at 15:29

Yes they are, but manually copying is error prone and time wasting. And it would be awesome to bundle headers for all STM8 MCUs with the SDCC:

martonmiklos
Senior
Posted on July 06, 2017 at 14:37

Bump!

I would be satisfied with a 'no we cannot provide such a material', 'or we need some time to work on it' kind of answers too.

Posted on July 06, 2017 at 16:50

It is primarily a user forum, so perhaps you're just in the wrong venue to pose such questions. An engineering or sales contact within ST would be the way to go.

Synthesize what you need from what is available. At some point people from IAR, ST, or where ever type stuff in, be resourceful. Typical sources would be assembler .INC files and .H files. The XML type files often come from a post-processing of user generated tables.

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..
Posted on July 07, 2017 at 08:25

Yeah I know this is an user forum, but sometimes ST employees used to comment here. Unfortunately I do not have engineering/sales contact with ST.

I can synthesize what I need from the IAR SFR files, but doing that would violate the IAR license terms. I have already found renamed registers in those files, so saying that I have typed the generated headers by hand from the datasheets is not an option.

Posted on July 07, 2017 at 21:28

Clive, this is a community forum, on an ST Microelectronics server, created to deal with the problems users are facing in using their microcontrollers.  It is just common sense to provide complete header files for their microcontrollers - as long as those bitfields exist and they are referring those in their datasheets. As long as they sell those, they are required to offer the best support possible. We have the right to complain on the user form first.

Miklos, there is no

'no we cannot provide such a material', only a temporary '

or we need some time to work on it

' and after that, they are forced to comply.

'

Synthesize what you need from what is available

' - I assure you that ST.M. knows exactly.
martonmiklos
Senior
Posted on June 11, 2018 at 11:35

Hi ST Folks,

I have started to discuss this matter with one of your colleague, but I cannot reach out him recently.

According to our last mail change he started an internal discussion about this.

I would deeply appreciate if someone from ST could ask around the output of this internal discussion and let me know the results.

Thanks in advance!

Posted on June 11, 2018 at 12:13

the ST person may have ceased communications for a reason.

I think you may want to think about the possibility of repurposing the stock header files for your compiler, by either making it compilable under SDCC, or to generate your own header files from them. all the information is there anyway.

Posted on June 11, 2018 at 12:59

Please compare the attached files (iostm8sh shipped with the Cosmic, STM8S103F.h shipped with STVD, and iostm8s003k3 generated

https://github.com/martonmiklos/iarSTM8sfr2cosmic

from the IAR registermaps). If you see the difference you will understand the reason why I want to get registermaps definition.

As I have mentioned above generating the headers from the files shipped with IAR and using with non IAR tools explicitly forbidden by the IAR license agreement.

Believe me I am not whinning here for nothing. Having good header files is essential for embedded development:

https://jaycarlson.net/microcontrollers/#headers

And at the another hand the STVD debug view got more readable this way:

0690X0000060BcoQAE.png

________________

Attachments :

iostm8s103.h.zip : https://st--c.eu10.content.force.com/sfc/dist/version/download/?oid=00Db0000000YtG6&ids=0680X000006HxWp&d=%2Fa%2F0X0000000azM%2FICB9Y8.iCDJ3Em5TcTKxU4MPUCVnK0WLHY4JiRLVMFw&asPdf=false

iostm8s003k3.h.zip : https://st--c.eu10.content.force.com/sfc/dist/version/download/?oid=00Db0000000YtG6&ids=0680X000006HxWk&d=%2Fa%2F0X0000000azN%2Fvt5QhcFiElgmj7.wdnfVQ0UFIDMlnAeF_GRxFgsAL9c&asPdf=false

STM8S103F.h.zip : https://st--c.eu10.content.force.com/sfc/dist/version/download/?oid=00Db0000000YtG6&ids=0680X000006HxWf&d=%2Fa%2F0X0000000azO%2FnakUlj7U6AQZ7.AxwHhG5z78qAykYeHV3wYvhGPLVeI&asPdf=false
Posted on June 11, 2018 at 13:11

'

using with non IAR tools explicitly forbidden by the IAR license agreement.'

Then try some other header files that don't explicit forbid such repurposing.

Is IAR the only one who provides header files for those chips?