This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

F28M36P63C2: F28M36P63C2

Part Number: F28M36P63C2

Hello,

Can somebody tell me where I can find the information about the F28M36P63C2 controller cross section?

Cross section:  In radiation terms for proton and neutron interactions, this is a combination of sensitive area and probability of an interaction depositing the critical charge for a SEE (single event effect):

σ = number of errors / (particle fluence[n/cm²] x memory size [bits])    (cm²/bit)

Thank you in advance.

Thomas

  • Hi Thomas,

    Are you interesting neutron or proton effects?  Since this is a commercial product we have no heavy-ion or proton cross-sections.

    If you are interested in SEUs at flight altitudes or on the ground we have extensive modeling based on neutron and alpha characterization that can give an upper bound fail rate from SEU (SER) - this will not be a  cross-section but rather a failure rate in FIT (failure per billion hours). Our method was the basis and is compliant with the JEDEC JESD89A test standard.

    Hope this helps, Rob

  • Hi Rob,

    Thank you for your response.

    I am interested in both proton and neutron effect for the risk analysis in my product. Since you could not have this information I would be pleased to have the rate of SEU failure in FIT. If you can provide this info to me.

    Thank you again.

    Thomas
  • Hi Thomas,

    To support an upper-bound estimation I need the following:

    1.) min Vdd

    2.) max temp

    3.) max altitude

    4.) max latitude

    5.) max flight time at altitude

    Thanks, Rob

  • I only have these data for now,

    1) Min vdd=3.135V
    2) max temp=105°C (component, ambient=85°C)
    3) max altitude = 50000 fts during 10mins
    5) • 940 Flight Cycles per year,
    • 5 Flight hours per Flight Cycle,
    • Total annual utilization 4 700 FH,
    • Daily utilization (FH): 12,9 FH


    I hope it's enough for your estimation.

    Thanks.

    Thomas
  • Thomas,
    Please state all 3 voltages (VDDIO, VDD18 & VDD12). Refer to page 43 of SPRS825E.
  • Sure my bad,

    VDDIOmin=3,135V
    VDD12min=1.176V
    VDD18min=1.764V
  • Hi Thomas,

    A few clarifications.  I am assuming latitude of 45 N since this makes things a bit worse.

    Also, I notice you claim 5 minutes at a 50k...can you give me the flight profile.  What I am interested in is

    the altitude you spend the most time at - for many avionics it is usually the max altitude but you show flight time

    of 5 hrs but only 10 minutes at 50k - what is the max cruising altitude for the 5 hr flight. I do not need much detail

    preferably just one altitude, but since the SEU rate is such a strong function of altitude, even the 10 minutes 

    at 50k might wash out the other "cruising" altitude if it is significantly lower.

    This is probably overkill and it should be considered an upper bound.

    assumptions - min voltage, T=85, altitude = 50k ft, Lat = 45N, flight time 5 hours

    Since Flash and L1,L2, etc SRAM have ECC they both almost never fail < 0.4 FIT

    The SRAM w parity ~ 2625 FIT (of which 90-94% are a single bit and thus detectable)

    The random sequential logic ~ 5722 FIT (assuming 10% derating - based on data and literature)

    Assuming you did 1M flights of 5 hours each spending 100% of the flight time at 50kfeet,

    999,958 flights would have no events

    42 flights would have a single event of which about 30% would be detectable (so the system could restart)

    0 flights with more than a single upset.

    Please let me know if you have any questions.

    Rob

  • Hello Rob,

    Thank you for this precision at 50k of altitude.
    This is in fact the absolute maximum altitude but the cruising altitude is 15kfts.
    Can you tell me what is the rate of SEU at this altitude.

    Thank you in advance.

    Thomas
  • assumptions - min voltage, T=85, altitude = 50k ft, Lat = 45N, flight time 5 hours

    50,000ft, 5hrs, 45N latitude (I found one typo and redid the model with better info correction)

    Flash was < 0.4 and L1,L2, etc SRAM < 0.9 FIT (both have ECC)

    The SRAM w parity ~ 202 FIT (of which 90-94% are a single bit and thus detectable) <<<<note I miss typed this and the last re

    The random sequential logic ~ 5722 FIT (assuming 10% derating - based on data and literature)

    Assuming you did 1M flights of 5 hours each spending 100% of the flight time at 50kfeet,

    999,970 flights would have no events

    30 flights would have a single event of which about 30% would be detectable (so the system could restart)

    0 flights with more than a single upset.

    15,000ft, 5hrs, 45N latitude

    Flash was < 0.01 and L1,L2, etc SRAM < 0.03 FIT (both have ECC)

    The SRAM w parity ~ 6 FIT (of which 90-94% are a single bit and thus detectable) <<<<note I miss typed this and the last re

    The random sequential logic ~ 184 FIT (assuming 10% derating - based on data and literature)

    Assuming you did 1M flights of 5 hours each spending 100% of the flight time at 15kfeet,

    999,999 flights would have no events

    1 flights would have a single event of which about 30% would be detectable (so the system could restart)

    0 flights with more than a single upset.

    Note that both of these are upper-bounds based on 100% memory utilization and 100% sensitivity, assuming that

    an error in any bit any time will cause a system error. Also, since I do not have a component count for the sequential 

    logic, I used a rough approximation of 15% of the total number of memory bits.  Historically for processors with

    fairly large Flash and SRAM bands this is also an over-estimate. The only derating that I applied is on the sequential

    logic SEU since it is well documented (both with our own data and in extensive literature on the subject) that upsets

    in logic usually only get propagated < 10% on average, I used 10% derating on this.

    Hope this is clear and helps with your calculations.

    Rob