I am using WDS to generate the SI4463 rev C configuration header. I am also using the corresponding patch file. Without CRC enabled communication works as expected however enabling CRC leads to CRC_ERROR on every packet. Specifically, PH_PEND CRC_ERROR_BIT is set high.
I have tried several projects including Empty framework and Bidirectional packet. If I leave "use predefined packet" to fully customizable or with no CRC it works. If I select "One Field payload with CRC" it no longer works and always results in CRC_ERROR. Same if I choose a custom packet and select "Transmit CRC at the end of this field", "Check CRC at the end of this field" and "Enable CRC over this field". "Reset CRC at the beginning of the packet" is set.
I have verified that the data in the FIFO is complete and intact. That is, once receiving CRC_ERROR, the packet is still good and shows no sign of why the CRC_ERROR was triggered.
Looking on the scope at the RX_DATA output, it does not seem like a CRC is being received as everything after my data bytes is just noise.
Is there a way to check why CRC is not working?
If you have Silabs dev boards, as first test, use the Custom packet TX and Custom packet RX sample applications without any change in the code. On the TX side configure "One Field payload with CRC". On the receive side configure "One field payload with no CRC" and with two bytes longer payload than on the TX side. This way you will see the CRC bytes on RX_DATA and in the RX FIFO. If this works, you can go on with "One Field payload with CRC" on the RX side.
Could you solve your CRC error issue?
Let me know if you need further help.
In order to get crc working I had to enable CRC on all fields and transmit crc on all fields but only check crc on last field. This is wasteful but at least works.
My packet has a 1 byte length and up to 63 byte variable data payload.
You have to calculate CRC for the same payload bytes on TX and RX side and transmit and check at the same position, usually at the end.
I can check your config GUI settings if you attach the xml file(s) saved from WDS with the floppy icon top right in the configurator window.
This issue seems to be the duplicate of https://www.silabs.com/community/wireless/proprietary/forum.topic.html/si4464_and_si4463compatibilityandcrcissues-skaq
Let's go on with this discussion there.