• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 82 subscribers
  • Views 136 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.

BOOSTXL-POSMGR: BOOSTXL-POSMGR interface with F28379d Controller - Issue with 62-64 Bit biss slave

Divyesh Patel
Intellectual 815 points
Part Number: BOOSTXL-POSMGR

Tool/software:

Dear TI team,

I am currently working with the BOOSTXL-POSMGR driver interfaced with f28379d controller. The driver is being used for a BISS master/slave interface, and I have various biss slaves providing position data.

The driver performs well with BISS slave up to 61 bits. However, when I use BISS slave with 62,63 or 64 bit positions, the system enter the "ESTOP" state. Upon checking in the expressions window, the CRC and CRC raw data appear to be valid, but the position variable remains zero.

Below Snapshot is of BISS SLAVE :

Below Snapshot is of BISS MASTER BOOSTXL-POSMGR

Below Snapshot is of BISS SLAVE : Given Different Value

Below Snapshot is of BISS MASTER BOOSTXL-POSMGR

I would greatly appreciate any support or suggestions to resolve this issue.

thank you in advance!

Best Regards,

  • 0
    TI__Guru* 92140 points

    The PM_bissc_receivePosition() function returns a failure if the CRC calculated and the CRC received do not match. Since you have determined that the raw data is correct, there must be a limitation/bug/boundary in the CRC calculation routine when the number of bits reaches 61. The calculation source code is included in the library.  I suspect it may be in the bissc_getBits() routine since that routine is a bit tricky depending on the layout of the bits in the SPI FIFO.  I suggest starting there and checking that it extracts the correct bits for > 61.