Using of FEE error correction

We forward your question to the FEE expert.

Regards,

Haixiao

Hi Frank,

Did you mean SECDED(single error correction double error detection) tests or FEE error recovery tests?

Regards,

Vishwanat Reddy.

Hi Vishwanat,

i meaned the use of FEE error recovery tests. I'm not sure what parameters to choose for
TI_Fee_ErrorRecovery(TI_Fee_ErrorCodeType ErrorCode, uint8 u8VirtualSector);

I'm assume that "ErrorCode" is the one found with TI_FeeErrorCode() but vs do i have to choose? Some errors are indepentend from virtuel sectors (e.g. Error_FeeUninit) and how to choose the vs in case of a vs-error (e.g. Error_TwoActiveVS).

Am I right that SECDED is handled by the FEE itself?

Regards,

Frank

Hi Frank,

Error code is returned by TI_Fee_ErrorCode API.

Error_NoFreeVS, Error_TwoCopyVS, and Error_TwoActiveVS:

With our modified design, Error_NoFreeVS, Error_TwoActiveVS, Error_TwoCopyVS error will not happen.

Error_SetupStateMachine:

This error happens when RWAIT/EWAIT are not configured correctly to match the frequency at which Flash API is operating.  This error is easily detectable since none of the tests would pass unless this error is resolved.

Error_NoActiveVS:

INIT will try to create Active VS. This error cannot be ignored because FEE will be in UNINIT state and hence upper layers will always see FEE in uninitialized state.

Error_CopyNOActiveVS :

This is not an error. In INIT, copy virtual sector is marked as Active.

Error_EraseVS:

This error can happen when FEE tries to erase a virtual sector and perform a blank check, after copying all the blocks. FEE tries to erase the VS again in the error recovery API. If it is not able to erase, then virtual sector is locked out permanently. No further jobs will be accepted

Regards,

Vishwanath Reddy.

Hi Vishwanath,

thanks for your explanation.

But i wonder how to resolve those errors and, expecially for TI_Fee_ErrorRecovery() which vs should be delivered to the function call?

Regards,

Frank

Hi Frank,

For "Error_EraseVS", we will provide a software variable to upper layer. This is not yet available in current software version.

Regards,

Vishwanath Reddy.

If my reply answers your question please click on the green button "Verify Answer"

Hi Vishwanath,

but what about the other errors (e.g. Error_TwoCopyVS and Error_TwoActiveVS)?

Regards,

Frank

Hi Frank,

As already mentioned, with our new design(already available in HALCoGen 03.06.00) , Error_TwoCopyVS and Error_TwoActiveVS do not occur.

Regards,

Vishwanath Reddy.

If my reply answers your question please click on the green button "Verify Answer"

Hi Vishwanath,
if i understand you correctly the only real errors which should be user-handled are Error_SetupStateMachine, Error_NoActiveVS and Error_EraseVS.
Please tell me how to handle them and which vs should be delivered to the TI_Fee_ErrorRecovery()-function.
Regards,
Frank

Hi Frank,

For Error_SetupStateMachine and Error_NoActiveVS, VS information is not required.

For Error_EraseVS, as I mentioned in my previous post, we can provide this information to upper layers via a global variable.

Regards,

Vishwanath Reddy.

If my reply answers your question please click on the green button "Verify Answer"