CTEInfo receive with antenna switch

RE: CTEInfo receive with antenna switch

loquat — Mon, 10 Mar 2025 23:12:23 GMT

OK.Thanks.

RE: CTEInfo receive with antenna switch

Simonr — Fri, 07 Mar 2025 07:56:57 GMT

I don't think there is much to do with this interval I'm afraid. The PHYEND_EVENT is sent as soon as the last bit is sent/received on air while the EVENTS_END is triggered when a packet is sent/received.

Best regards,

Simon

RE: CTEInfo receive with antenna switch

loquat — Thu, 06 Mar 2025 00:22:10 GMT

Thanks for the answer.

The test code uses the Timeslot API and there is no base sample.

I created the diagram.

The interval between ND_EVENT and PHYEND_EVENT is about 12us.

RE: CTEInfo receive with antenna switch

Simonr — Wed, 26 Feb 2025 14:42:06 GMT

Sorry about the late reply, but I've been tasked with taking over this case. Let me take a step back here before we move on. First off, what sample project have you used as the starting point here? The connectionless sample or peripheral + central samples? Is the image you uploaded of the no-CTEInfo diagram something you made yourself or have you found it in documentation somewhere?

Since the CTEInfo is appended at the end of advertising packets (after the CRC), since the advertisement has told the application that there is CTEInfo appended, it might be that the guard/ref period is alreadty scheduled no matter what the CTEInfo is, and that's why you see these pulses. I will need to confirm with the devs whether or not this is the case though. How long is the delay between END_EVENT and PHYEND_EVENT exactly?

Best regards,

Simon

RE: CTEInfo receive with antenna switch

loquat — Fri, 21 Feb 2025 06:22:08 GMT

Thanks.

>isn't unnecessary

The advertising does not include a CTE, so there is no need to switch antennas.

Below are the AoA related configuration parameters.
(Sorry, my environment is optimized for NCS2.9 and can no longer run on NCS2.2.)

	RADIO_DEV->DFEMODE = (RADIO_DFEMODE_DFEOPMODE_AoA << RADIO_DFEMODE_DFEOPMODE_Pos);

	const nrf_radio_cteinline_conf_t cteconf = {
		.enable				= true,
		.info_in_s1			= false,
		.err_handling		= true,
		.time_range			= NRF_RADIO_CTEINLINE_TIME_RANGE_20,
		.rx1us				= NRF_RADIO_CTEINLINE_RX_MODE_2US,
		.rx2us				= NRF_RADIO_CTEINLINE_RX_MODE_4US,
		.s0_pattern			=  0b0000'0111,
		.s0_mask			=  0b0000'1111,
	};
	nrf_radio_cteinline_configure(RADIO_DEV, &cteconf);

	const nrf_radio_dfectrl_conf_t dfeconf = {
		.dfe_len			= 20, /* 受信時はINLINE=disable時のみ有効 */
		.extension			= NRF_RADIO_DFECTRL_EXTENSION_CRC,
		.switch_spacing		= NRF_RADIO_DFECTRL_SWITCH_SPACING_2US,
		.spacing_ref		= NRF_RADIO_DFECTRL_SAMPLE_SPACING_1US,
		.sample_type		= NRF_RADIO_DFECTRL_SAMPLE_TYPE_IQ,
		.sample_spacing		= NRF_RADIO_DFECTRL_SAMPLE_SPACING_2US,
		.repeat_pattern		= 0,
		.gain_steps			= 0,
		.switch_offset		= 0,
		.sample_offset		= 0,
	};
	nrf_radio_dfectrl_configure(RADIO_DEV, &dfeconf);

	nrf_radio_dfe_buffer_set(RADIO_DEV, m_iq_sample, sizeof(m_iq_sample));

RE: CTEInfo receive with antenna switch

Priyanka — Tue, 11 Feb 2025 13:49:47 GMT

[quote user="loquat"]'reference period' and 'sample period' will be output, but this is unnecessary processing.[/quote]

If you are referring to this "part of the protocol" then it definitely isn't unnecessary - it's important in order to find the bias etc.

[quote user="loquat"]Additionally there is an unnecessary delay between END_EVENT and PHYEND_EVENT.[/quote]

If you are seeing delays etc. that is interesting, but you will have to give us more details than that. You should measure this with a logic analyzer or PPK and give us what values for sample slot etc. you are using, or if you're simply using the default values. And whether you are using zephyr controller, and what ncs version. And you should definitely try this with NCS 2.2, as that is the only version we've tested and know that we have a QDID. Most likely you would just need to look at the WP.

-Priyanka

RE: CTEInfo receive with antenna switch

Priyanka — Tue, 11 Feb 2025 08:19:38 GMT

Hi,

Apologies for the delay. I am checking this internally with experts and will get back to you.

-Priyanka

RE: CTEInfo receive with antenna switch

loquat — Tue, 21 Jan 2025 15:39:41 GMT

The timing is output to GPIO using PPI.
END_EVENT -> PPI -> GPIO0
PHYEND_EVENT ->PPI -> GPIO1
etc.

About CTEInfo
The sender uses Timeslot API to add CTEInfo to the ExtendedHeader of the ADV_EXT_IND packet, and also sets it to send CTE after CRC.
The receiver uses Timeslot API to receive in inlineAoA mode.

RE: CTEInfo receive with antenna switch

Priyanka — Tue, 21 Jan 2025 11:12:40 GMT

Could you tell me whether you made this block/timing diagram yourself?

Could you tell me what you mean by "receiving no CTE info"?

Regards,

Priyanka

RE: CTEInfo receive with antenna switch

loquat — Fri, 10 Jan 2025 01:33:46 GMT

Thanks.

I changed the settings a little.

PSEL.DFEGPIO[0]=28
PSEL.DFEGPIO[1]=29
PSEL.DFEGPIO[2]=30
PSEL.DFEGPIO[3]=31

SWITCHPATTERN=0x00 (Scan and Payload)
SWITCHPATTERN=0x01 (reference period)
SWITCHPATTERN=0x02 (1st sample period)
SWITCHPATTERN=0x04 (2nd sample period)
SWITCHPATTERN=0x08 (3rd sample period)

GPIO.DIRSET=0xF0000000
GPIO.OUT=0x00000000

result is follow,

On recv no-CTEInfo (INLINE AoA mode)
'reference period' and 'sample period' will be output, but this is unnecessary processing.
Additionally there is an unnecessary delay between END_EVENT and PHYEND_EVENT.

Is this behavior as expected?

RE: CTEInfo receive with antenna switch

Priyanka — Thu, 09 Jan 2025 08:23:45 GMT

Hi,

It looks fine, because as you mentioned,

[quote user=""]If Advertising with CTEInfo is received, the antenna switch will work as expected.[/quote]

This is correct.

[quote user=""]If Advertising without CTEInfo is received, PORT28/29 will change immediately after receiving the Advertising. (It outputs a pulse)[/quote]

The pulse that you see initially might be the radio getting ready for the CTE reception, but since the CTEInfo is not received, the antenna switching is not performed.

[quote user=""](There will be no change if no Advertising is received at all)[/quote]

That also looks fine.

Regards,

Priyanka