• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 101 subscribers
  • Views 594 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.

C6678 sRIO booting from C6455

kenshow
Genius 3725 points

Is it OK to use C6678 sRIO boot from C6455?

We are considering to use the sRIO from C6455 (master) to C6687 for boot.

sRIO on C6678 and C6455 are different revision of sRIO. Are there any problems in this case? 

  • 0
    TI__Mastermind 30825 points

    Yes, this is fine.  There is no concerns w/ the interoperability between the SRIO generations.

    Best Regards,

    Chad

  • 0 in reply to Chad Courtney
    Genius 3725 points

    Hi Chad,

     

     I would like to know more detail about your answer. What is the basis of your answer?

    It means only that the specification v2.1 is upper compatible with v1.2.

     

    Is it possible that the specification v1.2 of sRIO can access to the specification v2.1 device?

    Is there anything I should consider in designing with specification v2.1 (C667x) and v1.2 (C6455).

     

    Thank

  • 0 in reply to kenshow
    TI__Mastermind 30825 points

    SRIO v2.1 is backwards compatible to v1.2

    Following the Hardware Design Guidelines for each device will be necessary, and they will need to be set to the same Gbaud but they are designed to inter-operate seamlessly

    Best Regards,

    Chad

  • 0 in reply to Chad Courtney
    Genius 3725 points

    Hi Chad,

    >SRIO v2.1 is backwards compatible to v1.2

    C6678 booting is not the boot of a specification has been enhanced in V2.1, it’s used the standard  access of v1.2?

    So, in sRIO Booting of C6678, It is possible to drive from C6455, isn't' it?

    Best regards,

    Kenshow

  • 0 in reply to kenshow
    TI__Mastermind 30825 points

    Kenshow,

    To my understanding there is no SRIO Boot Spec.  It would be the devices boot spec over SRIO.  That is, that it's not part of the SRIO spec, but the boot spec of the device using SRIO.  The SerDes connection and communication would remain the same (i.e. they create their link just like normal when the RBL configures the SerDes.) 

    Then it's following the requirements of the booted device.  Please see the Bootloader for Keystone Architecture UG - SPRUGY5.

    Best Regards,

    Chad

  • 0 in reply to Chad Courtney
    Genius 3725 points

    Hi Chad,

     

     I would like to know about your suggestion in your previous message.

     You said “Following the Hardware Design Guidelines for each device will be necessary…”.

     

    Are “Design Guidelines”  Hardware Design Guide for KeyStone I Devices (SPRABI2B) and SerDes Implementation Guidelines for KeyStone Devices (SPRABC1)? However, I cannot get SPRABC1 from web site. How can I get SPRABC1?

    Or, are there any other useful guides?

     

    Thanks,

    Kenshow

  • 0 in reply to kenshow
    TI__Mastermind 30825 points

    There is no SPRABC1, there was going to be a separate SerDes Implementation Guideline at one point, but it was integrated into the Hardware Design Guidelines.

    Can you let me know where you found the reference to SPRABC1 so I can make sure it gets removed?  I thought we had removed all of those references but it appears not.

    All of the Design Guidelines are posted on there respective product pages.

    Best Regards,
    Cahd

  • 0 in reply to Chad Courtney
    Genius 3725 points

    SPRABC1 has been introduced in SPRABI2B, Hardware Design Guide for KeyStone Devices.

    Best Regards,
    Kenshow

  • 0 in reply to kenshow
    TI__Expert 6850 points

    We hope to have SPRABC1 posted to the product folders by mid to late next week.