Hello,
I am experiencing an issue with the I2S interface on my nRF5340 DK while using the nRF5340 Audio Unicast Server application with the nRF Connect SDK v3.1.0.
I am trying to output audio via I2S to a MAX98357A amplifier, but I am encountering the following problems:
No Signal on P0.13 (I2S_SDOUT):
- The I2S pins are pre-configured in the overlay file (nrf5340dk_nrf5340_cpuapp.overlay), with P0.13 specifically assigned to the SDOUT, which is intended to carry the audio data output. When playing audio from a connected smartphone (via Bluetooth LE Audio), I measure the following voltages :
- P0.12 (I2S_MCK): 1.453 V (indicating Master Clock activity).
- P0.13 (I2S_SDOUT): 0 V.
The LED 2 (P0.30) lights up during audio playback, confirming that the application detects the stream, but no data appears on P0.13, where the audio should be output according to the I2S configuration.
IRQ 40 Conflict with CONFIG_I2S=y:
- When I add CONFIG_I2S=y to my configuration file, the build fails with the following error:
FAILED: zephyr/isr_tables.c zephyr/isr_tables_vt.ld zephyr/isr_tables_swi.ld ... gen_isr_tables.py: error: multiple registrations at table_index 40 for irq 40 (0x28) Existing handler 0x44f31, new handler 0x44f31 Has IRQ_CONNECT or IRQ_DIRECT_CONNECT accidentally been invoked on the same irq multiple times?
Commenting out the I2S configuration in the .overlay resolves the build error, but this also disables the I2S hardware configuration.
Could you please provide guidance?
Thank you for your support!
Best,
