Other Parts Discussed in Thread: C2000WARE
Tool/software:
Hi champs,
I am asking this for our customer.
They used to use driverlib and bit-field codes on F28003x and are migrating onto F28P55x.
They are very troubled because we have changed not only the doc but also the software underlying codes for inclusive words and registers.
For driverlib, we have used driver_inclusive_terminology_mapping.h to solve this mapping issue between older driverlib and newer driverlib with inclusive words.
But for bit-field registers, do we have a similar one to solve this problem?
How does the user use their existing bit-field codes from F28003x onto F28P55x directly?
For example, in I2C,
I2CIER.AAS on F28003x becomes I2CIER.AAT.
I2CSTR.SDIR on F28003x becomes I2CSTR.TDIR
...
1. For coding, do we have a mapping file like driver_inclusive_terminology_mapping.h to solve this issue for bit-field codes?
2. For register mnemonics, can you show a mapping table in TRM (or at least migration guide) for all registers that have been changed because of inclusive words for the user to refer to because the user is familiar with old register names and needs to get familiar with new names. This is specifically helpful for the user to search by older mnemonics and then get to the new corresponding inclusive mnemonics.
OR do you have any suggestion to solve this?
