Hello everyone,
I am currently working on upgrading a custom carrier board from Jetson Linux R35.4.1 (L4T 35.4.1 / Ubuntu 20.04) to the new Jetson Linux R36.4.4 (L4T 36.4.4 / Ubuntu 22.04).
Our board is a custom design, not a devkit, and it has significant modifications to the kernel and pin configurations (pinmux) to support our specific hardware.
I have already done a comparison (diff) between our modified R35.4.1 BSP and the stock jetson_linux_r35.4.1_aarch64.tbz2 release. From this, I have a clear list of the changes we made (e.g., custom device tree settings, pinmux files, and kernel patches).
My problem is that when I examine the new R36.4.4 BSP (Jetson_Linux_R36.4.4_aarch64.tbz2), the file paths, directory structures, and even the filenames for these configurations (especially for pinmux and device tree) are completely different. The old R35.x configuration methods and file locations don’t seem to apply anymore.
I am looking for guidance on the correct methodology to port our custom R35.x configurations to the new R36.x structure.
-
How do we migrate our custom pinmux settings to the new R36.x format?
-
What is the new process for applying custom device tree (DTS) patches?
-
Are there any official migration guides, porting documents, or community tutorials that specifically address this R35.x to R36.x BSP migration for custom boards?
Any advice or pointers to relevant documentation would be greatly appreciated.
Thank you.