Orin Nano I2S audio output Jetpack 6.2

I’m not successful in getting the Orin Nano Dev kit to output I2S audio to a simple external MAX98357 DAC. I’ve successfully tested the MAX98357 with a Raspberry Pi but only get noise or clicks from the Orin.

Jetpack 6.2 fixes the problems I had with running:

sudo /opt/nvidia/jetson-io/jetson-io.py

So I’m able to select compatible hardware “Adafruit UDA1334A” and confirm that the GPIO pins are configured for I2S:

40pin header:
(12) i2s2_sclk → BCLK
(35) i2s2_fs → LRCLK
(40) i2s2_dout → DOUT

The DAC is connected to GND and 5V.

My APE settings are:

amixer -c APE cget name=“I2S2 BCLK Ratio”
: values=64

amixer -c APE cget name=“I2S2 Client Bit Format”
: values=16

amixer -c APE cget name=“I2S2 Client Channels”
: values=2

amixer -c APE cget name=“I2S2 FSYNC Width”
: values=32

amixer -c APE cget name=“I2S2 Loopback”
: values=off

amixer -c APE cget name=“I2S2 Mux”
: values=1 (ADMAIF1)

amixer -c APE cget name=“I2S2 Playback Audio Bit Format”
: values=1 (16)

amixer -c APE cget name=“I2S2 Playback Audio Channels”
: values=2

amixer -c APE cget name=“I2S2 Playback FIFO Threshold”
: values=3

amixer -c APE cget name=“I2S2 Playback Mono To Stereo”
: values=0

amixer -c APE cget name=“I2S2 Playback Stereo To Mono”
: values=0

amixer -c APE cget name=“I2S2 Sample Rate”
: values=48000

amixer -c APE cget name=“I2S2 codec frame mode”
: values=1 (i2s)

amixer -c APE cget name=“I2S2 codec master mode”
: values=0 (None)

But when testing all I get is an initial click:

speaker-test -D hw:APE,0 -r 48000 -c 2 -F S16_LE -t sine -f 1000

According to the documentation APE,0 (card 1, device 0) should map to ADMAIF1.

I confirmed that the overlay is selected in the boot loader (abbreviated from /boot/extlinux/extlinux.conf):

DEFAULT JetsonIO

LABEL JetsonIO
MENU LABEL Custom Header Config:
LINUX /boot/Image
FDT /boot/dtb/kernel_tegra234-p3768-0000+p3767-0005-nv-super.dtb
INITRD /boot/initrd
APPEND ${cbootargs} root=PARTUUID=734aafce-28e8-46a9-b048-eeaab46bba46 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 nospectre_bhb video=efifb:off console=tty0 nv-auto-config
OVERLAYS /boot/tegra234-p3767-0000+p3509-a02-audio-adafruit-uda1334a.dtbo

It’s worth noting that if I open the “Settings” and go to “Sound” the speakers output a constant hiss until I close the window.

But any other aplay or speaker-test to the APE,0 device outputs only a short click in the beginning.

Here the relevant logs:
settings.txt (307.2 KB)
kernel.log (77.7 KB)
dt.log (312.9 KB)

When not playing any sound the regmap looks like this:

sudo cat /sys/kernel/debug/regmap/2901100.i2s/registers
00: 00000000
04: XXXXXXXX
08: 00000000
0c: XXXXXXXX
10: XXXXXXXX
14: 00000003
18: 00000000
1c: 00000000
20: 03113300
24: 00000100
28: 00000000
2c: 00000000
30: 00000000
34: XXXXXXXX
38: 00000000
3c: 00000000
40: 00000000
44: XXXXXXXX
48: 00000000
4c: XXXXXXXX
50: XXXXXXXX
54: 00000003
58: 00000000
5c: 00000000
60: 00113300
64: 00000100
68: 00000000
6c: 00000000
70: 00000000
74: XXXXXXXX
78: 00000000
7c: 00000000
80: 00000001
84: 00000000
88: 00000001
8c: XXXXXXXX
90: XXXXXXXX
94: 00000000
98: 00000000
9c: 00000000
a0: 20000403
a4: 000003ff
a8: 00000000
ac: 00000000
b0: 00000001

When running “speaker-test -D plughw:1,0 -c2 -r48000 -F S16_LE -t sine -f 440” it looks like this:

sudo cat /sys/kernel/debug/regmap/2901100.i2s/registers
00: 00000001
04: 00000000
08: 00000000
0c: 00000001
10: 0000000c
14: 00000003
18: 00000000
1c: 00000000
20: 03113300
24: 00000100
28: 00000000
2c: 00000000
30: 00000000
34: 00000020
38: 00000000
3c: 00000000
40: 00000000
44: 00000000
48: 00000000
4c: 00000002
50: 00000000
54: 00000003
58: 00000000
5c: 00000000
60: 00113300
64: 00000100
68: 00000000
6c: 00000000
70: 00000000
74: 00000000
78: 00000000
7c: 00000000
80: 00000001
84: 00000000
88: 00000001
8c: 00001102
90: 00000c00
94: 00000000
98: 00000000
9c: 00000000
a0: 20000403
a4: 000003ff
a8: 00000000
ac: 00000000
b0: 00000001

Never mind. I switch to a different Orin Nano and everything is working as expected. When I have time I’ll re-flash the problem Orin and see if it’s a software issue.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.