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.
Part Number: TMS570LS1227
in current MCAL version 05.40.00 EA1, the Fls module was not developed according to AUTOSAR standard and Can not be able to interface and integrated with the FEE module provide by AUTOSAR BSW vendor. So in order to integration the AUTOSAR NVM stack we have to use the FEE module by TI MCAL. Some NVM feature like CRC, redundant block is not supported in TI FEE module.
If we use the FEE module which has full NVM feature supported provided by AUTOSAR BSE vendor we need to rewrite the Fls driver to be able to interact with FEE module. I think it is not realistic.
Do you have any updated MCAL which has implemented Fls as stand AUTOSAR module? Or is there are any workaround?
Could you tell us the requirement number from the AUTOSAR FEE specifications for the features that you intend to use.
Currently, we do not have an AUTOSAR compliant Fls module and there are no development plans for the same.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Akshay Manikantan:
It is about the dataset calculation, details can see below figure
I have checked in MCAL configureation, there was one configuration item related to this feature but the value is limit to 1...
In reply to user6116028:
I apologize for the delay.
The dataset configurations are a part of the NVM module. The workaround to implement this using FEE Driver is as follows:
1. Each block configured using EB tresos will be considered as a dataset block.
2. In the Fee_Cfg.c file (generated from EB tresos), we would need to manually change the value of "Number of datasets" for each block configuration.
3. Also ensure to configure the NVM_DATASET_SELECTION_BITS in the nvm module, accordingly as the number of datasets should not be more than 2 power NVM_DATASET_SELECTION_BITS.
For example, If we need to configure 4 datasets per block and need 13 such blocks, configure 4*13 = 52 blocks using the EB tresos. The dataset blocks for logical Block 1 would be blocks 1,2,3 and 4 (ensure these blocks have the same parameters). The value of "Number of datasets" in each block configuration in Fee_Cfg.c would be 4U. The NVM_DATASET_SELECTION_BITS value will be 2.
Thanks and Regards,
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.