RFBee firmware updating

[Icing]

Hi Team,

Thank you so much for the updating.

reading the fifo when GDO0 goes high results in a half frame packet, waiting a microsecond in receiveData for the fifo to stabilize solves that issue.
Packets are then coming in stable, however it is a bit of a kludge as we don’t want to waste time

A more stable solution is to change IOCFG0D (GDO0 output pin configuration)
its currently set to:
7 (0x07) Asserts when a packet has been received with CRC OK. De-asserts when the first byte is read from the RX FIFO.

However when CRC is OK the packet is not yet fully passed to the FIFO.
Changing this to:
1 (0x01) Associated to the RX FIFO: Asserts when RX FIFO is filled at or above the RX FIFO threshold or the end of packet is
reached. De-asserts when the RX FIFO is empty.

Hans, you are right, CRC OK does not mean packet is fly passed to the FIFO, which causes the problem we met. The setting of GO0 to 0x01 can solve this problem.
However, I still found several problems:

1. When in ATCF1~3, RFBee doesn’t work well, as the receiver can receive only one byte what ever the transmitter sends.

2. In ATCF0(default configuration), the RFBee will receive some nonsense bytes when keep it silent there. I think it is the interruption of the RF signal around it. And when we set GDO0 with 0x01, which also means it has no CRC, the interruptive RF data may be received by the RFBee.

How about your testing result?

Regards,

-Icing