The issue is that the name appear when the peripheral is in 1M PHY but he don't apprear when the device is in Coded PHY, do you know why ?
I use NCS 2.0.0 and to scan i use a central with shell commands.
The issue is that the name appear when the peripheral is in 1M PHY but he don't apprear when the device is in Coded PHY, do you know why ?
I use NCS 2.0.0 and to scan i use a central with shell commands.
I use a central with shell bluetooth command with NCS 2.0 and tere is UART communication to see the board in serial port.
I use putty to sens command like to scan and to connect with my peripheral.
My board is a custom board with uart communication, but this is not the issue here, the issue isn't hardware i think.
I use NCS 2.0 in VS Code and not NFR5, i can't use this simple scanner exemple. But i really think the probleme came from the peripheral and not central because the difference orcured in 1m and not in coded, the central take the information of the name exactely the same way that it does in 1m or in coded.
For the nRF Connect SDK we already have central/peripheral sample projects that showcase how to use the Coded PHY. Please check out the Heart Rate Monitor with Coded PHY central and peripheral to make sure advertising and scanning is set up correctly for using Coded PHY.
If you think the issue is with the peripheral, you could also do a sniffer trace to see what is happening on-air and make sure. A sniffer trace can be gotten by using either a dedicated BLE sniffer (like the Ellisys sniffers), or if you have a spare nRF52 DK or Dongle, you can use the nRF Sniffer and Wireshark to sniff the connection and pairing method.
Best regards,
Simon