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.

TSB12LV01B+TSB81BA3E Issues

Other Parts Discussed in Thread: TSB12LV01B, TSB81BA3E

Hi Team,

The customer is using TSB81BA3E,TSB12LV01B and FPGA with the hardware structure of AS5643 protocol for their design. 

They  found it cannot send the data without cycle start packet, so they have several issues as follows:

Q1: How to send asynchronous streams packets when TSB12LV01B neither transmiting cycle start packet nor receiving cycle start packet?

Q2:  Is there any mistake to achieve the AS5643 protocol by using TSB81BA3E and TSB12LV01B? Do you have any recommend advices for achieving  the AS5643 protocol?

Q3: Can you send me the full data sheet of TSB12LV01B ? E-mail: mickey-zhang@ti.com

Thanks,

Best Regards,

  • The TSB12LV01 conforms to IEEE1394-1995, which says:

    6.3.1.2 Sending an asynchronous packet

    […] After the packet is sent, the link layer will usually expect an acknowledge to be returned. […] If the acknowledge is not valid, or if it is not received within a time-out period, the link layer considers the acknowledge missing. The link layer does not expect an acknowledge if the packet was a broadcast packet.

    If the TSB12LV01 does not realize that the asynchronous stream packet is an isochronous packet, it will treat it like an asynchronous packet, and without a broadcast destination ID, it will report a missing ACK (if it sends the packet at all).

    As for receiving, IEEE1394-2008 says:

    6.2.4.3 Loose vs. strict isochronous packet reception

    Although this standard previously prohibited the reception of an isochronous stream packet outside of the isochronous period (strict isochronous), a significant number of contemporary serial bus link designs relax this requirement and permit the reception of an isochronous stream packet at any time (loose isochronous).

    The strict isochronous requirement is removed; link designs compliant with this standard shall be capable of receiving stream packets (primary packets identified by tcode A16) without regard to whether or not the packet falls within or without the isochronous period.


    Asynchronous stream packets are not related with AS5643; the problem is that the link layer controller must be new enough support them. (I don't know if the GP2Lynx or one of the ceLynx devices would support them.)