Here is dmseg | grep spi, Pinmux and tegra234-p3737-0000-a04.dtsi
I’m not sure why I can’t find the clock. I would appreciate it if you could give me a solution.
Thanks.
Hi cndqhrwogus,
Are you using the devkit or custom board for AGX Orin?
What’s your Jetpack version in use?
What did you modify in device tree?
It seems there’s no clocks and clock-names in your spi@3210000 node.
yes i use custom board and, i use on Jetpack 5.1.2. version
clock and clock-name have different dtsi. Here is dtsi.
Do you have the different design of the clock source for SPI on your custom carrier board?
It seems there are more error message in your log.
Please share the full dmesg for further check.
No, The custom carrier board has the same clock design.
dmesg.txt (65.0 KB)
It seems the latest log is different from the one from your original post.
In your original post, there’s the error message as following:
OF: /spi@3210000: could not get #gpio-cells for /aconnect@2a41000/ahub/ports/port@27
Do you have the devkit to get the same result?
I can’t reproduce the similar “can not get clock” issue on my local AGX Orin devkit.
The above result seems to be caused by not adding &tegra_main_gpio.
I can see the current SPI clock, data, etc. being communicated.
However, The initial value of the chip select pin is set low, it occur a communication error.
Is there a way to change the initial value of the chip select pin to high?
It could be configured through pinmux spreadsheet for initial state.
Please refer to Changing the Pinmux for details.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.