Issue related to running unicast server application on custom board.

[embdev61]

Hi Nordic Team and Other,

We are evaluating an audio product using a NRF5340 Audio Dk (Custom Board) and using nrf5340 DK for flashing the custom board using the setup as mentioned below.

We are using v2.9.0 and referencing the unicast server application for testing purpose.

We are using following setup to program our custom board.

Currently, we are utilizing RTT for console messages instead of the serial port.

We are encountering issues and receiving error messages.

Please find attached the prj.conf file for the nRF audio application we are using.

2133.prj.conf

Could you kindly review the configuration and assist us in programming the custom board(this is based on the NRF5340 Audio DK)?

Thanks for your support.

[dejans]

Hi,

Your connections mostly follow programming board with custom connections guide. You could try to replace your connection to VDD (nRF) with one to VDD (nrf') as shown in the linked document. In addition, you can look at this discussion.

Best regards,
Dejan

[embdev61]

Hi Dejan,

Thank you for your response.

I changed the connection to VDD (nrf'), but I am still encountering the same error.

I also tried flashing a different sample application (the Eddystone application) and was able to flash it successfully, with the correct output appearing on the RTT terminal.

However, for the audio application, I am flashing both the Network MCU (ipc_radio) and the Application MCU (nrf5340_audio). Could there be a step that I am missing?

[dejans]

Hi,

Can you provide details on your building and flashing process?

Best regards,
Dejan

[embdev61]

Hi,

I'm working on building an application using the nrf5340_audio application. I am selecting nrf5340_audio_dk/nrf5340/cpuapp from the build configuration and modifying prj.conf to enable RTT log.

I am using Visual Studio Code as my IDE, building ipc_radio and nrf5340_audio, and then flashing ipc_radio first, followed by the nrf5340_audio application.

I have identified that the issue might be related to the INA230 peripheral, which is an I2C-related issue.

Guidance Needed:

1. Disabling INA230 Peripheral: How can I disable this peripheral from the build system?

2. Disabling DSP System: Additionally, can I disable the DSP system in the code to test just the Bluetooth functionality and diagnose what might be missing in our custom board?

We are facing this issue and need to determine the root cause.

[dejans]

Hi,

embdev61 said:

Disabling INA230 Peripheral: How can I disable this peripheral from the build system?

You can try to remove your device from i2c devicetree node and disable i2c in your board's devicetree overlay.

&i2c0 {
    status = "disabled";
};

embdev61 said:

Disabling DSP System: Additionally, can I disable the DSP system in the code to test just the Bluetooth functionality and diagnose what might be missing in our custom board?

Do you think of disabling anything specific?

Best regards,
Dejan