Hello,
I'm using peripheral_past sample on nrf5340 audio DK board, and select nrf5340dk_nrf5340_cpuapp_ns for Build Target.
I added the following config to enable RTT log in prj.conf, other than that I did not make any changes.
CONFIG_USE_SEGGER_RTT=y CONFIG_RTT_CONSOLE=y
I have used nRF Connect SDK 2.2.0 and 2.6.0, and the results are the same as follows:
SEGGER J-Link V7.94i - Real time terminal output
SEGGER J-Link (unknown) V1.0, SN=1050169355
Process: JLink.exe
*** Booting nRF Connect SDK v3.5.99-ncs1 ***
Starting Peripheral Periodic Advertising Synchronization Transfer (PAST) Demo
[00:00:00.425,201] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.425,231] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)
[00:00:00.425,262] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 54.58864 Build 1214809870
[00:00:00.426,879] <inf> bt_hci_core: Identity: DD:E1:04:06:A5:B7 (random)
[00:00:00.426,910] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x218f, manufacturer 0x0059
[00:00:00.426,940] <inf> bt_hci_core: LMP: version 5.4 (0x0d) subver 0x218f
Connection callbacks register...Success
Periodic Advertising callbacks register...Success.
Subscribing to periodic advertising sync transfers
PAST subscribe failed (err -134)
Is there anything else I need to modify to make it work properly?