This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi Team,
My customer find a conflict of the register offset description between the TRM and the CCS Memory browser view:
spruii0d_TMS320F2838x Real-Time Microcontrollers With Connectivity Manager TRM (Rev. D) shows that the address of McanRegs_MCAN_RXESC is 0x0005_C6BC:
(P5096 & P5110)
But in CCS Memory browser view, it is 0x0005_C6A8:
It lead operation failed to change the value of McanRegs_MCAN_RXESC by using driverlib.
--
Thanks & Regards,
Yale Li
Yale,
I will take this up with the Driverlib team. Please give me a few days to resolve this.
Yale,
I am awaiting a response from the C2000ware team and following up with them. Thank you for your patience.
Yale,
The register offset description in the TRM is accurate, and the driverlib function is based on the same offset as well. It has been validated that using the driverlib function can be accurately used to set the data field sizes, which can be verified by looking at the Message RAM in the Memory Browser itself.
The bug here is that the offset has been incorrectly stored in the CCS Register View XML, which will be fixed. Just to reiterate, the functionality is intact, just that it is not being correctly shown in CCS.
Thanks.
Correction: This has already been fixed in the latest version of CCS (12.2.0)