• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 773 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.

CC1200: 802.15.4g with FEC

SEHAK LEE
Prodigy 10 points
Part Number: CC1200


According to the Smartrf studio, SYNC1 was changed (0x90 -> 0x6F) by the Smartrf studio for FEC TX(using Symbol rate: 50kbps, 2-GFSK, IEEE 802.15.4g compliant, Dual sync word, ETSI Standard).

Even though SYNC1 changed on TX side, but I have to set SYNC1 0x90 on RX side for receiving CRC OK Packets.

Is it correct??

When I changed SYNC1 to 0x6f for receiving FEC Packets on RX side, appear RX FiFo Error.

  • 0
    TI__Mastermind 35070 points

    Hi,

    On RX side: sync3 and sync2 form the FEC syncword, while sync1 and sync0 form the non-FEC syncword. When RX receives the FEC syncword, it will begin FEC decoding for the rest of the packet. When RX receives the non-FEC syncword, it does not FEC decode the rest of the packet.

    On TX side: sync1 and sync0 form the syncword that will be transmitted. If you want to transmit FEC encoded packet, you need to make sure the transmitted syncword (0x6F4E) matches the RX FEC syncword (0x6F4E).

    So TX should have 0x6F for sync1, and RX should have 0x6F for sync3 and 0x90 for sync1.

    Regards,

    Toby