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.

Read zero in RXbytes

Other Parts Discussed in Thread: CC1101

I have pair of TX/RX CC1101,

when i strobe the GDO0 to 0x06(RX side) and press the TX,

I can see data packet exactly the waveform of the TX one,

However, once i read the FIFORX, i get zero, does anyone can help, notice that only one of my RX fail, it works in TX ok .

    i = ccxxx0_Read(CCxxx0_RXBYTES);
            ccxxx0_ReadBurst(CCxxx0_RXFIFO, temp, i);   

i get i = 0;

pls help thanks

  • It's a bit unclear from the post;

    what are you seeing on the GDO0 of the receiver when you transmit the packet. Does the GDO line assert or does it stay low?

    On the transmitter side does the GDO0 (0x06) line assert and de-assert in correspondence with the transmission?

    Be sure that you have disabled CRC auto flush (PKTCTRL0) so that any packets with CRC fault do not get flushed.

  • Thx Martin again,

    I have a paire of TX(A) // RX(B)

    when A send to B,

    I get the same waveform of TXand RX (both assign as 0x06, and assert when get packet and dessert when the packet end,

    however, once i read the FIFO, i get zero byte received!

    And more STRANGE IS THAT , once i exchange the TX with RX, the B send to A, i get the correct result with the same code.

    PLs help for that, thanks

    Jeff

  • Hi,

    Have you tested if your devices can communicate with each other in SmartRF Studio?
    If you have SmartRF05EB, TrxEB or CC Debugger, see the SmartRF Studio help document (section "Transceiver packet handler") for signals needed for packet handling (packet TX/RX in SmartRF Studio).

    If you get that to work, then you could try to use your software on one device, and SmartRF Studio on the other, and that way try to find out what causes the problems you see.

    Br,
    TIABO

  • Hi Jeff

    If it works on one of the devices and not the other, it could be that one of the devices is damaged (e.g esd hit). If you follow TIABO's advice ant try to set up a link using SmartRF Studio. This will at least identify if the issue is related to the software or not.