Combined WiFi and BLE Radio testing for nRF7002DK

[uh-ashishlele]

Hello,

We are in certification stages for our custom product based on the nRF7002DK. Our application requires BLE and WiFi to be operational simultaneously. Consequently, the certification process also requires capability to test both WiFi and BLE radio simultaneously.

We have been referring to the existing separate nordic samples for BLE and WiFi radio tests but unable to find a sample/ guide which can make both work as part of the same application.

Is there any way to achieve this where the radio tests can be performed simultaneously for WiFi and BLE through a common build?

Thanks,

Ashish 

[uh-ashishlele]

Hello Håkon,

In continuation to the certification tests that we need to support, the next test has the following high-level requirements:

1. DUT connects to a WiFi network
2. Test equipment/ WiFi sniffer will scan for the WiFi advertised by the DUT and connect to it
3. Configuration will be performed on the DUT related to IPV4/IPV6 interfaces i.e., different combinations of IPV4 and IPV6 enabling/ disabling

Is there a sample to support tests as per the above requirement? This is the test specification for your reference RFC 4213:2005, 2460:1998, 8200:2017

[Håkon Alseth]

uh-ashishlele said:

• DUT connects to a WiFi network
• Test equipment/ WiFi sniffer will scan for the WiFi advertised by the DUT and connect to it

Please see this section of the previously linked application note:

https://docs.nordicsemi.com/bundle/nan_046/page/APP/nan_046/wifi_shell_sample.html

 

uh-ashishlele said:

Configuration will be performed on the DUT related to IPV4/IPV6 interfaces i.e., different combinations of IPV4 and IPV6 enabling/ disabling

Did you read my former comment on this matter?

Håkon Alseth said:

Unfortunately, there is no direct command in the network shell to take down ipv4/ipv6, but you can add or remove IP addresses, for instance:

net ipv4 del index ip

ie.

net ipv4 del 1 192.168.1.x

 

Where '1' is the index, and 'xx.yy.zz.xx' is the IP assigned. You will then need to add it manually again:

net ipv4 add 1 ip mask

 

Similar with ipv6.

I am not sure why you are referring to these RFCs:

uh-ashishlele said:

This is the test specification for your reference RFC 4213:2005, 2460:1998, 8200:2017

These RFCs are for describing IPv6 implementation in general.

What specifically are you testing? Is this a specific test case with teleregulatory requirements, and if yes; can you please share the test case?

 

Kind regards,

Håkon

[uh-ashishlele]

Hello Håkon,

We need to fulfil the below clauses from Essential Requirements No.TEC24492408 from TEC, India

Please let me know if this information is sufficient.

Regards,

Ashish

[Håkon Alseth]

Hi,

 

Can you please share the .pdf for the specific document?

uh-ashishlele said:

TEC24492408

I have tried for the last half hour, but I am unable to load the website.

 

Kind regards,

Håkon

[uh-ashishlele]

I have this version (attached) . The clause numbers seem to differ but you can check by the parameter name/ standard name in column 2 and 3 respectively

Thanks,

Ashish.

TEC24492408_IoT.pdf

[Håkon Alseth]

Hi,

 

Thank you for sharing the document.

These two columns specify parameters that are linked with the variant (ie. if LoRA, BLE, Wifi, fiber, etc) - so there seems to be a prerequisite that the device supports IPv4 and IPv6, which the network stack within zephyr does.

 

Interface 26 explains what is an added requirement for Wi-Fi and what specification is linked to that specific test-case(s). If you have a 3rd party module, they are usually ETSI/FCC precertified.

 

Kind regards,

Håkon

[uh-ashishlele]

Hello Håkon,

We have received a more detailed list from the lab regarding the RFC clauses for testing. The clauses are as below:

RFC-791 clause-3.1

https://datatracker.ietf.org/doc/html/rfc791#section-3.1 

RFC 4213 Clause 2.1

https://datatracker.ietf.org/doc/html/rfc4213#section-2.1 

 RFC 2460/8200 Clause 3,4.1,4.4,4.5 & Annex to ER P7.1 to 7.8 & P7.11 -to P7.12

https://datatracker.ietf.org/doc/html/rfc2460#section-3

https://datatracker.ietf.org/doc/html/rfc2460#section-4.1

https://datatracker.ietf.org/doc/html/rfc2460#section-4.4

https://datatracker.ietf.org/doc/html/rfc2460#section-4.5

7.1 to 7.8, 7.11 and 7.12 https://datatracker.ietf.org/doc/html/rfc2460#section-3

Would you able to guide on the best approach to support these tests? The DUT is a nRF7002DK based custom device and the lab normally uses an Alfa AWUS036ACH Wi-Fi adapter for monitoring

Thank you,

Ashish Lele.

[Håkon Alseth]

Hi,

 

Please share the specific test cases in either ETSI/FCC for those specific tests. As previously mentioned; quoting/linking a whole RFC does not make sense in regulatory compliance testing.

You are basically stating that you require IPv4/IPv6 protocol support, which I have mentioned that the SDK supplies you with.

  

For instance, for ETSI you want to look at these compliance testing documents:

https://docs.nordicsemi.com/bundle/nan_046/page/APP/nan_046/regulatory_test_cases.html

uh-ashishlele said:

Would you able to guide on the best approach to support these tests? The DUT is a nRF7002DK based custom device and the lab normally uses an Alfa AWUS036ACH Wi-Fi adapter for monitoring

Run any sample that has Wi-Fi station capabilities, as mentioned in the nAN-046, with a tester (access point):

https://docs.nordicsemi.com/bundle/nan_046/page/APP/nan_046/wifi_sta_sample.html

 

uh-ashishlele said:

the lab normally uses an Alfa AWUS036ACH Wi-Fi adapter for monitoring

This is not a Wi-Fi 6 capable adapter.

 

What is your end-goal here? Everything you have shared of documents, like this:

uh-ashishlele said:

TEC24492408_IoT.pdf

states that you want to do RF PHY related tests, ie. either FCC (for US) or ETSI (Europe), but you keep linking protocol implementations, which can indicate that you want to do Wi-Fi Alliance listing:

https://docs.nordicsemi.com/bundle/nwp_045/page/WP/nwp_045/intro.html 

 

Do you need regulatory compliance testing (FCC/ETSI) or do you want to list your end product (Wi-Fi Alliance)?

 

Kind regards,

Håkon

[uh-ashishlele]

Hi,

I attached links for specific clauses rather than the entire RFC which need to be fulfilled to achieve compliance. The objective is to achieve compliance for the following:

1. Primarily - Fulfilment of TEC requirements.
2. The TEC requirements are clauses in the previously attached file TEC24492408_IoT.pdf
3. The clauses from the above mentioned document, in turn, resolve to the RFC Clauses which I have highlighted in my previous message.

Summarizing, the DUT needs to support the following to pass compliance:

1. Dual IP parameters
2. IPV4 parameters
3. IPV6 Dual stack parameters
4. IPV6 parameters

I want to understand whether a single sample application can be used to support the above tests. Please let me know if the details/ summary is still insufficient.

Note: I could not find any reference of ETSI/FCC test cases in any of the requirements that I'm working with.

[Håkon Alseth]

Hi,

 

Please read carefully what I stated in my former responses, and be sure to read both nAN46 and nWP-045 chapter-to-chapter. The answer to your questions are in those documents.

 

uh-ashishlele said:

Note: I could not find any reference of ETSI/FCC test cases in any of the requirements that I'm working with.

It is clearly stated in my former link what test-cases are for each band:

Håkon Alseth said:

For instance, for ETSI you want to look at these compliance testing documents:

https://docs.nordicsemi.com/bundle/nan_046/page/APP/nan_046/regulatory_test_cases.html

 

You need to contact a certified test house to help you with this.

 

Kind regards,

Håkon