Issue related to running unicast server application on custom board.

RE: Issue related to running unicast server application on custom board.

dejans — Mon, 03 Feb 2025 16:51:13 GMT

Hi,

[quote user="embdev61"]Thank you so much for your support! My RTT logs has improved significantly, so we can close this ticket. I'll open a new one for any other issues.[/quote]

Thank you for the update. I am glad to hear that it worked for you.

Best regards,
Dejan

RE: Issue related to running unicast server application on custom board.

embdev61 — Sun, 02 Feb 2025 16:22:21 GMT

Thank you so much for your support! My RTT logs has improved significantly, so we can close this ticket. I'll open a new one for any other issues.

RE: Issue related to running unicast server application on custom board.

dejans — Wed, 29 Jan 2025 14:38:38 GMT

Hi,

Which logging mode do you use? You could try to increase RTT buffer size or set CONFIG_LOG_MODE_IMMEDIATE=y.

Best regards,
Dejan

RE: Issue related to running unicast server application on custom board.

embdev61 — Tue, 28 Jan 2025 14:25:05 GMT

Hi,

Thanks for the support.

We determined that our custom board lacks support for the TI INA230 and voltage divider components, so I will proceed with application development without them. Regarding RTT logging, I'm encountering an issue where the log intermittently stops. I've attached the 2133.prj.conf file for your review. Please advise on any necessary configuration changes to ensure continuous logging

# Enable RTT backend for logging

CONFIG_LOG_BACKEND_RTT=y

CONFIG_LOG_BUFFER_SIZE=4096

# Use buffer index 0 for RTT logging

CONFIG_LOG_BACKEND_RTT_BUFFER=0

RE: Issue related to running unicast server application on custom board.

dejans — Mon, 27 Jan 2025 16:38:23 GMT

Hi,

[quote user="embdev61"]

Could you please refer us to the document and section where the ADC details are mentioned for getting the board version?

board_id: board_id {

compatible = "voltage-divider";

io-channels = <&adc 0>;

output-ohms = <20000>;

full-ohms = <47000>;

power-gpios = <&gpio0 24 GPIO_ACTIVE_HIGH>;

};

[/quote]

Mentioned configuration can be found in nrf5340_audio_dk_nrf5340_cpuapp_common.dtsi file. The details can be found in the overview of the battery voltage measurement sample by pressing on "Explain this code" above the configuration.

For details about ti,ina230, you can refer to ti,ina230 Zephyr dts bindings.

Best regards,
Dejan

RE: Issue related to running unicast server application on custom board.

embdev61 — Sat, 25 Jan 2025 16:55:42 GMT

Hi,

Could you please refer us to the document and section where the ADC details are mentioned for getting the board version?

board_id: board_id {

compatible = "voltage-divider";

io-channels = <&adc 0>;

output-ohms = <20000>;

full-ohms = <47000>;

power-gpios = <&gpio0 24 GPIO_ACTIVE_HIGH>;

};

In our case, we are getting an ADC value of 656, which is way beyond the tolerance value. It seems we have an incorrect ADC configuration.

Also, please let us know the section where we can find details on the following configuration:

arduino_i2c: &i2c1 {

compatible = "nordic,nrf-twim";

status = "okay";

pinctrl-0 = <&i2c1_default>;

pinctrl-1 = <&i2c1_sleep>;

pinctrl-names = "default", "sleep";

vbat_sensor: ina231@44 {

compatible = "ti,ina230";

reg = <0x44>;

adc-mode = "Bus and shunt voltage continuous";

vbus-conversion-time-us = <4156>;

vshunt-conversion-time-us = <4156>;

avg-count = <1024>;

current-lsb-microamps = <1>;

rshunt-micro-ohms = <510000>;

};

vdd1_codec_sensor: ina231@45 {

compatible = "ti,ina230";

reg = <0x45>;

adc-mode = "Bus and shunt voltage continuous";

vbus-conversion-time-us = <4156>;

vshunt-conversion-time-us = <4156>;

avg-count = <1024>;

current-lsb-microamps = <1>;

rshunt-micro-ohms = <2200000>;

};

vdd2_codec_sensor: ina231@41 {

compatible = "ti,ina230";

reg = <0x41>;

adc-mode = "Bus and shunt voltage continuous";

vbus-conversion-time-us = <4156>;

vshunt-conversion-time-us = <4156>;

avg-count = <1024>;

current-lsb-microamps = <1>;

rshunt-micro-ohms = <2200000>;

};

vdd2_nrf_sensor: ina231@40 {

compatible = "ti,ina230";

reg = <0x40>;

adc-mode = "Bus and shunt voltage continuous";

vbus-conversion-time-us = <4156>;

vshunt-conversion-time-us = <4156>;

avg-count = <1024>;

current-lsb-microamps = <1>;

rshunt-micro-ohms = <1000000>;

};

RE: Issue related to running unicast server application on custom board.

embdev61 — Sat, 25 Jan 2025 14:16:10 GMT

Despite disabling the I2C interface in the nrf5340dk_nrf5340_cpuapp.overlay, I'm still encountering errors related to the INA230/INA231 peripherals and ADC readings. Additionally, the RTT log output stalls after a few prints.

My setup includes:

Custom Board: NRF5340-CLAA with CS47L63-CWZR DSP
Flashing Method: nRF5340 DK via P20 Debug Output Connector
Flashed Images: ipc_radio and nrf5340_audio
Board Target: nrf5340_audio_dk/nrf5340/cpuapp
IDE: Visual Studio Code with default settings

Issues Faced:

Persistent Peripheral Errors:
- INA230/INA231 errors despite disabling I2C in the overlay.
- ADC read register errors impacting board version detection.
RTT Logging Limitations:
- RTT logs halt after a few outputs, hindering debugging efforts.

Request:

Guidance on properly adding custom board support, including necessary configurations to eliminate unwanted peripheral initialization.
Assistance in resolving RTT logging issues, ensuring continuous and reliable log output for debugging.

Your expertise in this area would be immensely valuable in helping us overcome these challenges promptly.

Thank you for your support.

RE: Issue related to running unicast server application on custom board.

dejans — Fri, 24 Jan 2025 15:08:24 GMT

Hi,

[quote user="embdev61"]Disabling INA230 Peripheral: How can I disable this peripheral from the build system?[/quote]

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

&i2c0 {
    status = "disabled";
};

[quote user="embdev61"]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?[/quote]

Do you think of disabling anything specific?

Best regards,
Dejan

RE: Issue related to running unicast server application on custom board.

embdev61 — Thu, 23 Jan 2025 17:31:35 GMT

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:

Disabling INA230 Peripheral: How can I disable this peripheral from the build system?
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.

RE: Issue related to running unicast server application on custom board.

dejans — Wed, 22 Jan 2025 17:06:13 GMT

Hi,

Can you provide details on your building and flashing process?

Best regards,
Dejan

RE: Issue related to running unicast server application on custom board.

embdev61 — Tue, 21 Jan 2025 16:59:57 GMT

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?

RE: Issue related to running unicast server application on custom board.

dejans — Mon, 20 Jan 2025 14:10:54 GMT

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