• State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 21 subscribers
  • Views 2032 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

CAN RX FIFO on XE164

Alto Speckhardt

Hi,

I'm using CAN communication on an XE164 (MultiCAN). Currently, I'm trying to use an RX FIFO and not having much luck with it. The FIFO is set up using DAVE, but when I watch in the debugger I can see that only the first slave object (BOT) is ever filled. The pointer CUR is not advanced after reception, it remains set on the BOT object. The PNEXT of the BOT object does point to the next slave object, and all other BOT/TOP pointers appear to be correct.

Can anyone figure how this might happen?

Regards,
Alto Speckhardt

Parents
  • 0 in reply to Chris Wunderlich

    Hum... My experience is DAVE is not always right :(

    Well... ;-)

    I do see a problem that you (DAVE) is setting the RXEN bit in a slave object.

    Yes, you're absolutly right! When I began to manually (after the DAVE initialization) reset the RXEN bits in the slave objects the FIFO started to work as expected.

    Thank you very much indeed!

    Regards,
    Alto Speckhardt

Reply
  • 0 in reply to Chris Wunderlich

    Hum... My experience is DAVE is not always right :(

    Well... ;-)

    I do see a problem that you (DAVE) is setting the RXEN bit in a slave object.

    Yes, you're absolutly right! When I began to manually (after the DAVE initialization) reset the RXEN bits in the slave objects the FIFO started to work as expected.

    Thank you very much indeed!

    Regards,
    Alto Speckhardt

Children
No data