User requirements for flash

Marco Moreno

Other Parts Discussed in Thread: TMS570LS10106

Hi,

I just wanted to clarify a couple of things from the safety manual regarding flash user requirements. From section 2.2.6.4 there are a couple of statements:

1. The flash memory information shall be protected by ECC during normal operation. The device shall be
configured properly to report the ECC fault and CPU address bus fault to system including the device
(i.e.Map them to ESM nERROR pin).

2. The flash shall be protected against illegal modification through configuring the sector protection
registers (BSE). The BSE shall also be protected against illegal modification by clearing PROTLIDIS
protection bit in bank protection register.

For 1, does this mean that simply jumping to an exception handler and restarting the system will not be sufficient? Are we to somehow remap the ECC error to the nERROR pin in hardware? If so, how do I accomplish this?

For 2, is this handled already by the FlashAPI?

Thanks,
Marco

over 13 years ago

0 A Arora over 13 years ago

TI__Mastermind 30845 points

Marco,

The document you seem to be referring to is quite old and has been comprehensively updated. I'd recommend the updated version:

http://www.ti.com/litv/pdf/spnu550

For 1, ECC errors are already mapped to ESM channels. The decision for the system integrator is whether a single bit correctable ECC error should trigger a nERROR pin event or not.

For 2, I don't believe so, but I will ask the FlashAPI expert.

Regards,

Abhishek

0 John Hall over 13 years ago

TI__Genius 9015 points

Hello Marco,

On item 2, as you did not specify which device you are using, this answer applies to F021 Flash API( Up to and including v1.51):

The API uses callback functions Fapi_setupEepromSectorEnable() and Fapi_setupBankSectorEnable() to allow the user to setup the FBSE however they want. Additionally, everywhere in the API that needs to set PROTL1DIS to allow writing to locked FMC registers, there is a corresponding clearing of this bit usually after the last write to registers requiring this unlock, but definitely before exiting the function.

0 Marco Moreno over 13 years ago in reply to John Hall

Intellectual 300 points

John,

We are using the TMS570 which I believe is the F035. Anything different there?

Thanks,

Marco

0 A Arora over 13 years ago in reply to Marco Moreno

TI__Mastermind 30845 points

Marco,

From the safety manual you referenced, I am guessing this is a TMS570LS20x/10x family device - which is part of our F035 family.

We also have TMS570s in F021 ( TMS570LS31x/21x family, TMS570LS12x/11x family, TMS570LS04/03x family).

Regards,

Abhishek

0 Marco Moreno over 13 years ago in reply to A Arora

Intellectual 300 points

OK, thanks for clarifying...

The exact part number is TMS570LS10106.

Marco

0 John Hall over 13 years ago in reply to Marco Moreno

TI__Genius 9015 points

Hello Marco,

The difference on the Platform F035 API is it uses only one callback function, Flash_Sector_Select_V().

0 Marco Moreno over 13 years ago in reply to John Hall

Intellectual 300 points

John,

So it looks like this callback function Flash_Sector_Select_V() has a default implementation. From the manual:

"The default function provided in the API library enables all sectors of all banks."

Does this mean that all sectors in all banks are enabled _all the time_ or only when the API is called to erase or program them? In other words, when not trying to erase or program, are the protection bits set to not prevent programming by default?

Thanks,

Marco

0 Marco Moreno over 13 years ago in reply to Marco Moreno

Intellectual 300 points

Sorry, bad wording...

Are the protection bits set by default to prevent erasing/programming when the API is not in use?

Thanks,

Marco

0 John Hall over 13 years ago in reply to Marco Moreno

TI__Genius 9015 points

Marco,

The FBSE is set to 0 on power on reset of the device. The API operations that use the callback function do not, when they are done, set the FBSE back to 0. You would need to do this yourself after calling an API function.

Arm-based microcontrollers

Arm-based microcontrollers forum

User requirements for flash