• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 32 subscribers
  • Views 997 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

AM263P4: Migration from AM2634-Q1 to AM263P4-Q1, Replacing QSPI with OSPI

AM263P4: Functional Safety Compliance Documentation for AM263P4-Q1

John Martin4
Prodigy 80 points

Part Number: AM263P4
Other Parts Discussed in Thread: AM2634-Q1

Can I ask whether the FUSA documentation for AM2634-Q1 carries across to AM263P4-Q1?

Is there any difference for the sensor and SIP variants? 

Can I ask where there is a good clarification on the meaning of the 'Sensor Variant' - I searched the datasheet and manuals and couldn't find any clear explanation, apologies if it's obvious.

  • 0
    TI__Mastermind 36803 points

    Hey John,

    1) AM263Px will undergo functional safety compliance testing and have dedicated documentation once available. Many of the IP may reuse the same FUSA details between the two devices, but there will be unique AM263Px documents.

    2) The SIP variant (ZCZ-F) includes embedded OSPI flash (no) external OSPI flash interface available.

    3) The term Sensor comes from the package designator (ZCZ-S). In this case the "Sensor" is the Resolver Subsystem and associated pin/signal requirements.

    Best Regards,

    Zackary Fleenor

  • 0 in reply to Fleenor
    Prodigy 80 points

    Hi Zackary,

    1a) The question will be whats the timeline, do you know when the targeted safety manual will be issued. This is vital for implementation on an OEM traction inverter application with SOP late 2025.

    1b) Are there AUTOSAR compliant traction applications already in development? Our AUTOSAR provided implies we are the only one, which seems very hard to believe - could you dm me on john.martin@empelsystems.com if this is sensitive (we have full NDA in place with TI).

    2) Understood, I thought this was the case,thanks.

    3) OK thanks. Found the ball gate array charts in the datasheet :)

  • 0 in reply to John Martin4
    TI__Guru*** 135355 points

    Hi John,

    John Martin4 said:

    1a) The question will be whats the timeline, do you know when the targeted safety manual will be issued. This is vital for implementation on an OEM traction inverter application with SOP late 2025.

    1b) Are there AUTOSAR compliant traction applications already in development? Our AUTOSAR provided implies we are the only one, which seems very hard to believe - could you dm me on john.martin@empelsystems.com if this is sensitive (we have full NDA in place with TI).

    I'll have to ask around to get some details on those topics - I'll let you know if the second topic is one that requires a private conversation. I'll send a friend request just in case to enable that if necessary.

    Best Regards,

    Ralph Jacobi

  • 0 in reply to John Martin4
    TI__Guru*** 135355 points

    Hi John,

    John Martin4 said:
    1a) The question will be whats the timeline, do you know when the targeted safety manual will be issued. This is vital for implementation on an OEM traction inverter application with SOP late 2025.

    You can use the AM263 document as a strong initial reference for AM263P, the only areas that it won't apply for would be changes in features covered by our Migration Guide: https://www.ti.com/lit/pdf/spradb3

    Expectation is that AM263P Safety Manual will be available in 3Q24.

    John Martin4 said:
    1b) Are there AUTOSAR compliant traction applications already in development? Our AUTOSAR provided implies we are the only one, which seems very hard to believe - could you dm me on john.martin@empelsystems.com if this is sensitive (we have full NDA in place with TI).

    No current development plans for AUTOSAR based traction inverter application but I have shared your feedback with our teams and gap we have in not providing this is understood.

    Best Regards,

    Ralph Jacobi