TMS570LC4357: Read/write to emulated EEPROM vs rest of flash

Hello Tobias,

Bootloader is to update the application. It needs to erase the sectors of flash and write the new application to the flash. The F021 flash APIs are required.

Our bootloader examples don't read/write data to FEE. Yes, you need to add code for FEE operations. Please refer to the FEE example under HALCOGen Help.

Thanks for the quick response!

We will develop all code by ourselves (we will not use F021 API and not Halcogen).

So, I would like to know if we develop a bootloader with our own functions for read/write to flash, could we re-use those low level functions for also read/write to the area used for emulated EEPROM? Or is writing to the EEPROM area totaly different in terms of implementation?

BR
/Tobias

Hello,

The F021 flash APIs are highly recommended for flash operation: Initialization, erase, program, etc. If you have to optimize the flash erase/program functions for your application, please keep using flash API for flash initialization and bank selection.

The EEPROM is data flash which is similar to program flash, you can use the same functions to erase/program it. If you use it as EEPROM, as I said TI HALCoGen generates a FEE driver. 

Hi,

I understand your recommendation, but my understanding is that F021 flash APIs and Halcogen are not any qualified tools?

Br
/Tobias

Hello Tobias,

HALCoGen and other SafeTI software (like F021 flash API library) development process are certified as suitable for development of ISO 26262 and IEC 61508 compliant software components.

The HALCoGen Compliance Support Package (CSP) was developed to provide the necessary documentation, reports and unit test capability to assist customers using HALCoGen generated software to comply with functional safety standards such as IEC 61508 and ISO 26262.

Hello,

That was new information to me - interesting.

How does that help us within aerospace industri (DO178-C)?
Have you had any customer within same industri using this CSP?

BR
/Tobias