• State Verified Answer
  • Replies 7 replies
  • Subscribers 66 subscribers
  • Views 360 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 327849
Options

About the sample source of unicast_audio_client, unicast_audio_server

Junichi

The sample source of unicast_audio_client and unicast_audio_server can be built with VScod or command line, but an error occurs when writing.

The error is as follows.

-- west flash: using runner nrfjprog
-- runners.nrfjprog: Flashing file: c:\unicast_audio_client\build\zephyr\merged_domains.hex
-- runners.nrfjprog: c:\unicast_audio_client\build\zephyr\merged_domains.hex targets both nRF53 coprocessors; splitting it into: c:\unicast_audio_client\build\zephyr\GENERATED_CP_NETWORK_merged_domains.hex and c:\unicast_audio_client\build\zephyr\GENERATED_CP_APPLICATION_merged_domains.hex
[error] [ Client] - Encountered error -2: Command enable_coprocessor executed for 15 milliseconds with result -2
Failed to enable coprocessor with unknown error.
[error] [ Worker] - Cannot call read_access_port_register when connect_to_emu_without_snr or connect_to_emu_with_snr has not been called.
ERROR: Requested operation is currently unavailable.
ERROR: Check logs for more details.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
FATAL ERROR: command exited with status 66: nrfjprog --program 'c:\unicast_audio_client\build\zephyr\GENERATED_CP_NETWORK_merged_domains.hex' --sectorerase --verify -f NRF53 --coprocessor CP_NETWORK --snr 821007475

What could be the cause?

Parents
  • 0

    Hi!

    What version of the nRF5340-DK do you have?

    What version of nrfjprog are you using?

    Try doing:

    nrfjprog --recover --coprocessor CP_NETWORK
    nrfjprog --recover

    And then flash again.

  • 0 in reply to Sigurd

    The nRF5340 DK uses PCA10095 2.0.2.
    The ncs uses 2.5.0.
    I built and flashed (debug) using VSCODE.

    I solved the problem of not being able to write by myself.

    However, when I debug, both unicast_audio_server and unicast_audio_client have functions that return error codes.

    The functions in main.c are different, but when I dig into the function causing the error, both sample sources return -5 in bt_hci_cmd_send_sync.

    I found a similar post on Devzone, and added
    CONFIG_BT_CTLR_TX_PWR_DYNAMIC_CONTROL=y
    CONFIG_BT_HCI_VS_EXT=y
    to prj.conf, but the situation remains the same.

    I currently have two nRF5340 Audio DK boards.
    I have created a Gateway and Hedset using a script from the nRF5340 Audio source. (CIS mode)

    Assuming that unicast_audio_client is written to the nRF5340 DK and is working properly, will the nRF5340 Audio DA (Gateway) and nRF5340 DK (Client) be connected via Bluetooth?

Reply
  • 0 in reply to Sigurd

    The nRF5340 DK uses PCA10095 2.0.2.
    The ncs uses 2.5.0.
    I built and flashed (debug) using VSCODE.

    I solved the problem of not being able to write by myself.

    However, when I debug, both unicast_audio_server and unicast_audio_client have functions that return error codes.

    The functions in main.c are different, but when I dig into the function causing the error, both sample sources return -5 in bt_hci_cmd_send_sync.

    I found a similar post on Devzone, and added
    CONFIG_BT_CTLR_TX_PWR_DYNAMIC_CONTROL=y
    CONFIG_BT_HCI_VS_EXT=y
    to prj.conf, but the situation remains the same.

    I currently have two nRF5340 Audio DK boards.
    I have created a Gateway and Hedset using a script from the nRF5340 Audio source. (CIS mode)

    Assuming that unicast_audio_client is written to the nRF5340 DK and is working properly, will the nRF5340 Audio DA (Gateway) and nRF5340 DK (Client) be connected via Bluetooth?

Children
Related