CC1312R: Compliance Testing Setup

Which CCS version do you use? Do you use the CCS version that is listed in the release notes for the SDK you use? I had an issue when I tried to open syscfg in a project that was based on SDK 4.40 with CCS 10.3. I had to use CCS 10.2 to open the file. 

Hi,

I'm not sure what you mean. I don't use CCS at all. Not even installed on my PC. I use Sysconfig tool v1.9.0 to open sysconfig files, and IAR as the IDE.

Cheers,

Andy

Sorry, overlooked the information about IAR. Have you tried syscfg 1.8.x? I suspect that you basically see the same as I experienced just with a different toolchain. 

Hi,

No probs. I don't think it's anything to do with versions as it's always been this way for several years no matter what version of sysconfig or SDK I'm using. 

However, this subject is an aside from my main question about carrier signal configuration which is far more pressing as I'm testing next week.

Thanks,

Andy

I've edited the original post as I think my additional question about sysconfig made it unclear as to what my main question was. 

For reference the original question also asked why SYSCONFIG fails to open the example sysconfig files unless I add the follwing at the top of  the file:

* @cliArgs --board "/ti/boards/CC1312R1_LAUNCHXL" --product "simplelink_cc13x2_26x2_sdk@4.30.00.54"
* @versions {"data":"2021031521","timestamp":"2021031521","tool":"1.8.0+1863","templates":null}

Thanks,

Andy

Compliance testing can be done either with SmartRF Studio or writing code. We tend to use Studio for the Launchpads since then it's just to connect to USB and start the test. Some customers also use code but with one difference to what you have written above. 

Compliance testing typically requires a number of modes. Typically sending CW, sending a modulated signal, sending packets etc. With Studio it's relatively easy to tell the certification lab how to setup Studio for each mode. If you write code you typically don't want to provide the lab with a number of .hex files since it could be a bit complicated. Then you typically need a code where you can easily switch between the required modes with bussing a button (and ideally show which mode the DUT is in if the DUT has a way to display data). Step 1 - 4 looks correct and the way to do it but as covered above, check if you need an easy way to switch between modulated and unmodulated etc. 

I never really use IAR so I haven't the relevant version installed and I'm therefore not able to easily test and replicate the syscfg issue you are seeing. Let me know if syscfg 1.8.x makes a difference, if not I will see if I find someone with IAR installed that could do some testing for me. 

Hi,

Thanks for your help. I'll be in the test lab and programming if I need to, or, like you say, have code that switches between configurations if desired. This I have done several times before and so it's no issue. All I needed was confirmation of my approach to produce a carrier which you have given. Thanks.

I think the sysconfig issue is not very clear to you so I will briefly explain. It's nothing to do with IAR, CCS or any piece of software other than SYSCONFIG (TI System Configuration Tool) 

https://www.ti.com/tool/SYSCONFIG

Basically, if you use SYSCONFIG to open any of the *.syscfg files from the example folders in the SDK, for example,

C:\ti\simplelink_cc13x2_26x2_sdk_4_30_00_54\examples\rtos\CC1312R1_LAUNCHXL\drivers\rfCarrierWave\tirtos\rfCarrierWave.syscfg

it fails to open as it needs a part explicitly including in the comments section at the top. It's a small problem I can easily fix but slightly strange as it seems to need a timestamp including.

Many thanks,

Andy

Is it this error message you get if you are not including the header?

Hi,

Yes it is.

Andy

Hi,

I'm almost setup for compliance testing but have a question I can't quite get my head around:

1) If I want to transmit a packet of data representative of a packet from the Collector/Sensor Ti15.4 example for radio compliance testing, is it feasible to simply use the example like rfPacketTx or does the TI 15.4 stack change the RF output to the extent that I need to use the Ti15.4 stack for compliance testing?

2) I have a question about FEC. For EN 300 220-1 RX Sensitivity testing, the recommendation is that FEC is disabled if possible. My application uses the Collector/Sensor examples in 5kbps 868MHz LRM. I'm assuming it's not even an option to disable FEC as it's handled by the PHY. 

Would that be a correct assumption?

Thanks,

Andy

Correct, since this is part of the phy, see https://www.ti.com/lit/pdf/swra642 if you need more details.

For syscfg, I will ask the development team about it when they are back from vacation. 

Do I need to use the TI 15.4 stack when compliance testing or will a Tx Packet from rfPacketTx be representative if using the same PHY?

ah ha! I've just spotted the 'compliance testing' option in SYSCONFIG. Sounds perfect.

Yes, for the 15.4, use the compliance testing option.