You didn’t name the input format. The “-O dtb” is an output format, the “ppsv2.dts” is input content, but lacks a way to see its format (the .dts might seem to specify that, but it is not set up to allow this). Try: dtc -I dts -O dtb -o ppsv2.dtbo ppsv2.dts
A question needs to be confirmed first: You’ve shown snippets of device tree code. Those snippets are set up in what looks like the C-compatible kernel code. If building kernel code, then the kernel first assembles fragments and removes the C-compatibility before it truly becomes device tree source. Are you using this on actual device tree source, or is this C-escaped kernel snippets? If this is actually source, then you could rename “ppsv2.dts” to “ppsv2.txt” and upload it to the thread, and someone else could then try to compile it into binary. If this is actually kernel escaped, then there is no need to upload since the procedure for kernel escaped requires the kernel to build this.
I just need to enable pps time synchronization by my GNNS modlue’s output pps pulse. And use Orin nx 16GB dev board, with Jetpack 5.1.5 installed. Do I need to recompile linux kernel?
So, I guess Does I need to put ppsv2.dts under special direcotry? Or, specialfy Include directory for this macro?
On other hand, If I know what exactrly gpio number on board PIN 31 is, I can skip to use TEGRA234_MAIN_GPIO macro. I have tried gpio454 which /sys/kernel/debug/gpio told me
But It don’t work(Added a FDT node in /boot/extlinux/extlinux.conf point to compiled dtbo),Orin nx can’t boot anymore, and I need to reburn jetpack with nvidia SDK.