Hi,
Are those pins 7, 12, 35 able to be configured as GPIO and observe the signal after toggled by sysfs?
Hi,
Are those pins 7, 12, 35 able to be configured as GPIO and observe the signal after toggled by sysfs?
Hello,
Currently using the method provided by @jonathan
excel(generate dtsi) → .dtb → reflashing
Is in progress.
Are you saying that you want to restore the settings for the current audio codec and measure the signal of the corresponding pin On Devkit carrier board (b01)?
Thank you.
Hello,
For example
on devkit carrierboard + production module
Similar to the following image
Are you saying check if the value of /sys/class/gpio/ is toggled?

Thank you.
Yes, your tool is correct. We want to know if these pins can output correct signal/voltage when it is a gpio.
Hello,
In order to change the contents of the production module to sfio back to gpio, can I change the excel file to the initial value and compile again to update the dtb file?
Or, can I try flashing another production module (with dtb not updated for audio) and test it?
Can I use the jetson gpio python tool to check a signal with an oscilloscope?
GitHub - NVIDIA/jetson-gpio: A Python library that enables the use of Jetson's GPIOs
Thank you.
Hello,
Was there anything else in the attached dmesg?
Thank you.
Hi neuezeal,
What we want to know is the result from oscilloscope.
Hello,
Ok
Thank you.
Thanks for the result.
What is the pinmux setting when you toggle the gpio?
Do you use @jonathanh’s patched dtb or the original one from jetpack?
Hello,
after reflashing using quickstart guide.
Original one from jetpack.
Thank you.
Hi,
Please try these new patched dtb files.
nano-emmc.zip (88.7 KB)
and flash it with same command again.
$ sudo ./flash.sh -k RP1 jetson-nano-devkit-emmc mmcblk0p1
Hello,
Thank you for your effort.
Can you please explain how you modified it?
Thank you.
Hi,
The pin was not configured correctly as SFIO. It was still GPIO.
Thus, you can see we remove some gpio setting inside the latest patch.
Hello,
Because there could have been a mistake in the process of following the instructions or documentation
In order to organize, I ask you a few questions.
Can you correct anything wrong with reference to the following two articles?
Thank you.
Hello, @WayneWWW @jonathanh
I can check the sound by using the speaker-test command (a stereo beep is heard when an earphone is connected).
In this state, can you tell us what process to go through to make the sound come out from the application (eg YouTube, audio application)?
Thank you.
Hello!
You should open the “Sound” settings menu under the Ubuntu Desktop settings and select the “Analog” sound card. In the Sound settings menu you should see a “Test Speakers” button and you can then test the speakers again to confirm that the audio is being routed correctly to the codec. If that works, then youtube audio should be routed to the same sound card as well.
Regards,
Jon
Hello!
Yes “Test Sound” (I think that this has been changed to “Test Speakers” on more recent versions of Ubuntu). Click that and then you can test each speaker.
Jon