CC2340R5: Proprietary rf RX - using 2 sync words simultaniously

Hi Hristo,

Here is the documentation you are referring to: https://dev.ti.com/tirex/explore/content/simplelink_lowpower_f3_sdk_9_14_02_16/docs/rcl/html/generic_rx_handler.html 

If you are using rfEchoRx then the CMD_GENERIC_RX is already supported and you do not need to switch PHYs.  Can you please provide a code snippet of the changes you've made as well as describe what packet contents you are transmitting on the TX side?

Regards,
Ryan

Hi Ryan,
I can't provide a snippet right now, but you can count that my code for Rx is very similar to the rfEchoRx example with exception that I setup syncWordB and then enable it before submitting my command. I have also tried swapping syncWordA for syncWordB and then I receive packets with the second sync word that I want to setup, but not what was originally syncWordA.
One notable change is that I start listening only after I first transmit a packet and I listen just for less than 10ms.
From these experiments I'm left with the impression that there should be a limitation on receiving packets with 2 different sync words simultaneously.

I've been informed that only the PHYs listed under Proprietary RF in SysConfig supports two sync words. Please try using the 1 Mbps PHY.

Regards,
Ryan

Oh, this seems to be a problem - because of pending certification, switching the phy doesn't seem an option for us.

If I reconfigure with your suggestion, it seems that the RCL_Cmd struct is renamed to NESB. I suppose this means that the radio will be now geared to talk Nordic's Enhanced ShockBurst or it's just an artifact of sysConfig?

Do you have a comprehensive documentation for proprietary RF where I can see the pro's and con's of the different PHYs? (e.g. BLE phy vs NESB phy and parts which are not supported in them(2 sync words for example)

Also from what I can see the main change of this config is seen in the LRF_commonRegConfig array. The PBE, MCE and RFE binaries are still kept the same and so on. Do you also have any documentation on this regs config array as well? Would it be possible to keep the BLE phy and do a minimal reconfiguration so that 2 sync words are supported?

And a final oftopic question:
I have also seen that after recent updates of the SDK LRF_commonRegConfig, now has a field for txPowerLimitTable which is set to NULL. Do you have a documentation/examples for that as well? Having a guaranteed limit of the Tx power may help us with certification topics in the future.