TDA4AEN-Q1: [TDA4] Does the MCU domain code have support Flash EEPROM Emulation

Hi Ashleigh:

       Does have like AutoSAR have define the FEE HAL layer to support flash manager driver on FreeRTOS?

Hi Ashleigh:

       I saw the MCUSW_J722S_11.00.00.05.zip provide on the website https://www.ti.com/tool/PROCESSOR-SDK-J722S?keyMatch=J722S%20mcal&tisearch=universal_search&cf-designResourceProvider=Texas%20Instruments. This is TI provide for the AutoSAR MCAL driver. There have find a fls driver under mcusw/mcal_drv/mcal/Fls. Does this Fls only support flash driver access interface process? I mean support access through the OSPI interface. But does have include upper layer flash manager as FEE to manager the flash accessing from TI?

Hi Sheng, 

Yes, the fls driver provides the low-level driver interface to access flash memory, typically over the OSPI interface. TI does not currently provide an AUTOSAR FEE layer in the J722S Software package. J722S MCU+ SDK: Flash

Best, 

Ashleigh

Hi Ashleigh:

        If TI doesn't have the FEE layer on the J722S, Do you have any suggestion about how can I have the Fee layer SW on another way? Or does have any opensource can use it?

Simon

Hi Ashleigh:

      One more question about the OSPI. I saw TI reference design can put the boot code images(tispl.bin, tiboo3.bin and MCU firmware) in OSPI flash. Can we also put the MCU data into OSPI flash? Can we put both boot code image/MCU image and MCU data in OSPI flash? What you think for this design? And that's why we need to FEE SW module. How can we doing that? Or How can I to store the MCU data in where?

Hi Sheng,

Let me do some research and I can get back to you on that.  

Best, 

Ashleigh 

Hi, Simon

As far as I know, we only provide "low-level driver" interface to access flash memory

Some literature for reference & implementation,

https://www.ti.com/lit/an/slaae58/slaae58.pdf?ts=1753083261728&ref_url=https%253A%252F%252Fwww.google.com%252F

https://www.ti.com/lit/an/slaaeb4/slaaeb4.pdf?ts=1753083658318&ref_url=https%253A%252F%252Fwww.google.com%252F

https://www.ti.com/lit/sd/slaaen3/slaaen3.pdf?ts=1753083659687&ref_url=https%253A%252F%252Fwww.google.com%252F

https://www.autosar.org/fileadmin/standards/R22-11/CP/AUTOSAR_SWS_FlashEEPROMEmulation.pdf

If you use FEE w/AUTOSAR, it should be belong part of component from "ECU (memory) abstraction layer" not MCAL, so I think SW 3rd party may to need implement it w/ EB Tresos

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/921481/tda4vm-mcal-fee-support?tisearch=e2e-sitesearch&keymatch=TDA4%252520FEE#

Many Thanks

Gibbs

Hi Gibbs Shih 

  >>If you use FEE w/AUTOSAR, it should be belong part of component from "ECU (memory) abstraction layer" not MCAL,

  >>so I think SW 3rd party may to need implement it w/ EB Tresos

     But other major MCU vendors, such as NXP and STMicroelectronics, provide a Flash EEPROM Emulation (FEE) module for FreeRTOS and AutoSAR environments, not  provided by SW 3rd party.

Based on our experience developing in-vehicle systems, a FEE solution is a critical requirement. To guarantee a 15-year product lifespan with frequent data logging to non-volatile memory, the wear-leveling provided by a FEE module is essential.

Q1) Given this requirement, does TI have a Plan to provide its own FEE solution for the TDA4xxx MCU series, particularly for non-AUTOSAR systems using FreeRTOS?

Q2) Are other customers also requesting a Flash EEPROM Emulation (FEE) solution to meet long-term product lifespans (e.g., 15 years) that involve frequent writes to non-volatile memory?

B.R.

SanHsin Kuo

CC: Lance Shen ,  Sheng-Shun Chang