• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 101 subscribers
  • Views 360 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

SK-AM64B: AM64B , OTP keywriter on SK-AM64B?

Rio Chan
Genius 14160 points
Part Number: SK-AM64B
Other Parts Discussed in Thread: TMDS64EVM

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1198808/faq-how-to-run-otp-keywriter-on-sk-am64b

By reading the above E2E.

Some questions:

          Q1.

           The above is for SDK8.5, How do we deal with SDK9.2?

           We need to manually patch those files?

           Q2.

           How about the SDK8.6?

BR Rio

  • 0
    TI__Genius 14160 points

    The outside customer patched file shall be merged into our SDK.

    Otherwise, more customers who does not know the IO-expender issue will come to all of us.

    plz consider to merge it.

  • 0 in reply to Rio Chan
    TI__Guru* 82045 points

    In general our recommendation is that for customers trying HS-SE flow , use the bigger EVM. As SK is not supported well with MCU+ SDK. 

    https://www.ti.com/tool/SK-AM64B (this is listed in the beginning bullet)

    The SK-AM64B is best suited for:

    • Linux code development
    • 2-port Gigabit Ethernet with TSN support
    • USB 3.0 + wireless connectivity (both hotspot and endpoint)
    • Industrial communication Controller support

    See the TMDS64EVM for:

    • Linux and MCU+ SDK code development
    • 3-port Gigabit Ethernet with TSN support
    • PCIe support
    • Industrial communication Device & Controller support
    • HSE (high speed extension) connector for advanced HW development.

    However yes overall I agree in long term it would be good to decouple this OTP writer dependency from MCU+ SDK , for Linux users and provide some more native testing.

    No timelines as of now. 

    Regards

    Mukul 

  • 0 in reply to Mukul Bhatnagar
    TI__Guru 51271 points

    Adding to Mukul,

    The lack of support for SK-AM64B has been because of no MR till now. I will create now after discussion with the team and let them take the best course of action.

    For now, the customer will have to follow the thread you mentioned and port it to any SDK version the customer is using.

  • 0 in reply to Prashant Shivhare
    TI__Genius 14160 points

    Hi Prashant:

    -->The lack of support for SK-AM64B has been because of no MR till now. 

    Sorry, I dont get this 100% clear.

    May you explain more precisely?

    BR Rio

  • +1 in reply to Rio Chan
    TI__Guru* 82045 points

    MR = Marketing Requirement. 

    There was no marketing requirement to support VPP programming on SK-AM64B. The OTP writer and HS evaluation is done using MCU+ SDK which is supported on the other EVM. 

    We have created a requirement for software development team to consider adding support for SK-AM64B VPP/OTP writer evaluation by default, which requires supporting the GPIO through IO expander. This way the FAQ that was done by another customer to show how one can do this on their own does not to be replicated every new SDK release etc. 

    For now the customer can leverage that FAQ to see if they can try this or buy the other EVM to evaluate. Long term we will request SW development to add something in SDK 10.1 for supporting this more natively on SK-AM64B 

  • 0 in reply to Mukul Bhatnagar
    TI__Genius 14160 points

    Thanks, Mukul.

    When will we have the 10.1?

  • 0 in reply to Rio Chan
    TI__Guru 51271 points
    Rio Chan said:
    When will we have the 10.1?

    The scheduled release is the mid of December.

    Regards,

    Prashant