Hi There,
I am a little confused about the FlexCAN ECC fault-injection RTD driver sequence in particular:
1) Can you give me some examples ? I don't find anything in S32 studio nor in RTD examples nor in NXP community...
2) Anywhere another question is related to Reference manual rev8 page 2976
a) the initialization of all flexcan memory address range and register (red-1) is done by FlexCAN_ip_Init() or must be done by user ?... I don't find any initialization in RTD and (red-2) I don't understand it, this bit should be set or reset, and what is the meaning of the statement?
3) is it necessary to call FlexCAN_Init() before fault injection process ?. It seems it is not necessary (and this would be a good thing for my software structure)
4) I suppose that a correct sequence starts with :
FlexCAN_Ip_SetMemErrorDetection(INST_FLEXCAN_0,true);
FlexCAN_Ip_SetMemErrorDetectionInt(INST_FLEXCAN_0, FLEXCAN_ALL_ECC_ERROR, true);
FlexCAN_Ip_SetMemErrorInjection();
... ??...
Can you give me some help ?
Best Regards
Fabio
Thank you @PetrS for the answer,
1)regarded point 2) of previous post, I checked too that FlexCAN_ClearRAM, called by FlexCAN_Init() clears a fewer part of the ram indicated in table "FlexCAN Error injection Map" par 73.1.2. p 2975 of RM rev8.
What does it mean that this, do I have to initialize all uninitialized register manually by myself for fault injection?
2) In the project, I previous configured ECC error detection and correction for safety punctual faults management, by calling FlexCAN_Ip_SetMemErrorDetection(..,true) function and and configuring ECC in Normal Mode. But again, I checked that:
So also in runtime detection/correction mechanism, memory(CAN_BASE_ADDR related) from 0x80-0xAD and 0xC20-0x31FF must be initializated.
But FlexCAN_Init() initialize a few part of it.
So does aspect me that runtime Safety Mechanism does not function properly (also without latent faults mechanism (falultInj) developed)?
3) Maybe there are other RTD functions that initializes missing ones ?
Best Regards
Fabio
Hi @PetrS
I tried to initialize memory as you suggested in previous post:
You said:
"yes, seems RTD is not fully correct with respect of ECC usage. This is disabled by default, i think, so does not bring any issue.
So before you want to enable ECC you need to manually initialize RAM from offsets 0x80-0xAD and 0xC20-0x31FF (or just parts does not covered by FlexCAN_ClearRAM).:
I have a lot of problems to initialize it outside RTD, because, first you must enter in Freeze mode (and not sure if it is necessary to reset MCR[MDIS] or other stuff ), then clear CAN memory and finally (I think, disable freeze mode (and, maybe disable can....and probabilly some other stuff...)).
But happens to me that sometimes MCU fails to enter in freeze mode and I don't know why .... and other unpredictable behaviours.
Anyway in RM rev8 is reported as Follow (see point 3.):
So ALL flexcan memory is to be initialized only at step 3, after steps 1 and 2 !
FlexCAN_Init() follows exactly these steps and calls correctly FlexCAN_ClearRAM() function. The problem (or bug?) is that function doesen't initialize all 0x80-0xAD and 0xC20-0x31FF (related to CAN_0) memory........... as requested by R. manual.
this is a big problem because:
1) Fault Injection is not possible
2) also ECC runtime management, enabled by FlexCAN_Ip_SetMemErrorDetection() could have some problems, because ECC parity bit are not cleared at init.
So manual says that clear ram need to be performed at a specific initialization step (step 3), but RTD does't clear all memory. (ECC and Fault Inj are required by ASILD)
What is the solution ?
Best regards,
