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.

Packet DMA Does Not Update RX PS Region Location Bit Usage Note

Other Parts Discussed in Thread: 66AK2H06

hi,

It is mentioned in the ERRATA sheet of TMS320C6670 that Packet DMA Does Not Update RX PS Region Location Bit Usage Note.This means that the software cannot use this bit to determine if any PS information present is located in the RX packet descriptor or at the beginning of the data buffer.

But i can see that in the FFTC example project (pdk_C6670_1_0_0_18\pdk_C6670_1_0_0_18\packages\ti\drv\fftc), test project is writing PS information at the start of the data buffer and updating this information in the descriptor (that PS information is present at start of data buffer ). This test project is running succesfully. This test project results is contradicting with BUG "Packet DMA Does Not Update RX PS Region Location Bit Usage Note".

Is this BUG specfic to any scenerio or is it generic? Please provide insight on this BUG.

regards

Virendra

  • Hi Virendra,

    Thanks for your post.

    Yes, it is a generic bug which is not specific to any scenario but this issue affects only host type packets . Actually, the packet DMA module would fail to update the PS region location bit (bit 22 of packet descriptor word) to 1 when it tries to write an Rx. host-mode packet to memory which is located in the start of the data buffer instead of the descriptor. So, you could use monolithic packets instead of host type packets to overcome this issue as a tentative workaround.

    You could also try other workaround which is to place the PS info. in the descriptor instead of the data buffer so that the PS location bit is always 0 and the issue is not applicable to this case.

    Also, you could think of the software which can be designed to keep track of the PS info. location so it does not have to rely on the bit in the RX packet descriptor and the software can always use the same PS location setting which would eliminate to find out the location from the Rx. descriptor.

    Alternatively, the software could place some form of identifier in any of the user-defined tag fields in the TX descriptor and configure the Packet DMA to pass that information through to the RX descriptor. You could try these workarounds which would suit you probably.

    I believe, the above issue affects only silicon revisions 1.0, 1.1 and it is fixed in PG2.0. Please check 66AK2H06/12/14 silicon errata (sprz402b.pdf) doc and see "KeyStoneII.BTS_errata_usagenote.13"

    http://www.ti.com/lit/er/sprz402b/sprz402b.pdf

    Thanks & regards,

    Sivaraj K

    -------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question.

    -------------------------------------------------------------------------------------------------------