Channel sounding issues

[Patrick49]

Hello, 

I'm having some issues with the channel sounding on the nRF54L15.
I'm using two nRF54L15-dk and two custom bords with the nRF54L15.I'm using SDK v3.0.2 for my software and work on Windows 11.

The first one, is that I'm getting some broken ifft values equal to 0, sometimes, as shown below. This issue is happening both with the dk and my custom boards.

Since the ifft should be the best measuring method, it's problematic to have some null values.

The second one is with a custom board. When I run my program for about 30-35 minutes, a warning about ranging data overwritten shows up. Therefore, it doesn't stock new values after 4096 values ? and we need to reboot if several errors appear to resume normally the measurements. 

This warning doesn't show up with the dk when I run the same code and for a longer period of time as well. 

My code can be found in the archive in the attached documents.

CS_code.zip

Thanks and best regards,

Patrick 

[Simonr]

Hi

So it's only on the custom boards you're having issues now, correct? What are you using as the VCOM interface between the nRF54L15 and the computer in this case to get logging on the computer? Is it the DK or another interface? Since this worked on an older device I assume it's not HW related, I'm just trying to understand the differences between the custom and DK setups better.

Best regards,

Simon

[Patrick49]

Hello Simon, 

Yes, that's right, it's only happening with my custom boards.
I'm using a FTDI TTL to USB cable with only Rx and Tx for the UART signals, on my custom board side. 
The only major difference is that I don't use the external LFXO on my custom board but I don't see why this channel sounding sample wouldn't work on the newer sample compared to the older one. 

Ok I've just tried with SDK 3.1.0 and 3.1.1, some other samples like the LBS, or the UART peripheral but none are working properly on my custom board. It doesn't detect my device on the nRF Connect application nor print any log in the console. I guess I've found a new issue then. Do I need to open a new ticket to solve this problem ?

Best regards,

Patrick

[Simonr]

Hi Patrick

It would be smoothest if you open a new ticket describing it in detail. That way we can keep a good overview of what's going on. If you'd prefer I can take that case as well, or we can let the assignment process do its magic.

It's much easier to keep an overview of tickets in DevZone if we keep each ticket to one subject. Thank you for your thorough testing here though. I'm sure we will figure out what the issue is.

Best regards,

Simon

[Patrick49]

Hi Simon, 

Alright, I've created the ticket. Hopefully I can solve that issue so we can continue our channel sounding testing. 

Thanks and best regards,

Patrick