Hi All, Please let me know if the below steps work for configuring Audio interface, I2C
a) Also just wanted to know from where can we get “config-by-function.py”
b) Can we do the same through Jetson IO tool method, be updating the Device tree firmware and rebooting the system.
Thanks. I have moved to “Automonous Machines” Section…
1 Like
Hi nagesh_accord,
Are you using the devkit or custom board for AGX Xavier?
What’s your Jetpack version in use?
Jetson-IO should only work for the devkit board.
We are using both devkit and custom boards both in our team. As a beginner I would be working on devkit initially and later on will be working on the customized board.
Just wanted to know the method which works for what.
Thanks for confirming that Jetson-IO method works only for devkit board
.
Jetpack version is - [JetPack 5.0.1 Developer Preview]
I have some more questions:
- How do find out which device tree source or include file ( .dts or dtsi) files we should modify and rebuild the kernel image and flash the customized image n the custom board.
- Also I read there is one more method to configure the IO pins through the PINMUX spreadsheet updated method, which will generate a new configuration file, which has to be flashed on the Jetson device.
Configuring the Jetson Expansion Headers — Jetson Linux<br/>Developer Guide 34.1 documentation changes
Just want to know we can use this PINMUX spreadsheet method for custom board configuration updates? or should we manually modify the device tree source files?
I would suggest updating to the latest JP5.1.2(R35.4.1) for the devkit.
You could simply use SDKM to flash the board.
Everything is starting from the board config (which you use in flash command), it would include all necessary dtb and config files.
Yes, please just refer to the following instruction for the usage of pinmux spreadsheet.
Jetson Module Adaptation and Bring-Up: Jetson AGX Xavier Series — Pinmux Changes
Yes, you have to use pinmux spreadsheet to configure the pinmux according to your board design. The default configuration in that excel is used for the devkit.
1 Like
Thanks for the response.
One more query I have:
After generating the .cfg file from the .dtsi files( which are generated from the PINMUX spreadsheet), using the python tool ( as per the read me file in the path: Linux_for_Tegra/kernel/pinmux/t19x/ ), where the steps to be followed for copying the generated .cfg file to corresponding directories and rebuilding the customized kernel image.
You just need to replace the cfg file in use for your board with the generated .cfg and use flash command to apply it. Pinmux will be configured during early boot.
No need to generate or re-build the kernel image.
1 Like
Thanks for the response.
This flashing of the CFG file suits only for evaluation board but for our customized carrier board, we need to rebuild the entire image and flash the final image.
Any idea what is the exact path and cfg file name that we need to replace?
No, you don’t need to rebuild the entire image for your custom board.
Please share the flash log and also the board config used for flash.
Did not get it.
We want the cfg name before running the flash command.
Flash log will be obtained after running flash command. But we need the cfg file name and it’s path before running the flash command for the cfg file alone.
From the flash log, you would know which pinmux cfg is used in your case so that please share the full flash log.
It says galen. Cfg when I opened the readme.txt file and observed that, They are archiving the output inside this galen. Cfg file as shown below:
python pinmux-dts2cfg.py
–pinmux
addr_info.txt gpio_addr_info.txt por_val.txt
tegra19x-p2888_galen_devkit-pinmux.dtsi
tegra19x-p2888_galen_devkit-gpio-default.dtsi
1.0
> galen.cfg
I was able to generate the .cfg file.
After that please point me to the steps to be followed for flashing only the CFG file to the board but not the entire image?
There is no support to flash this cfg only. Must flash the whole board.
You mean we have to rebuild the entire kernel once again with the.cfg, dtb files to generate the image file once again
And later flash it
But in the above posts from kelvin in the same thread, they told no need to rebuild the entire image for custom board…
Not clear enough
Kernel has nothing to do with the cfg file.
For example, you can change the cfg content 1000 times but your kernel shall be still the same.
That is the point Kevin is talking about… Please be aware that previous comment is talking about "kernel image’.
No need to generate or re-build the kernel image.
I feel the point here is your definition of “image” is not same as what we are telling here.
Thanks, I understand.
It would be better, if I get clear steps link of flashing for my jetson AGX Xavier Industrial board.
https://docs.nvidia.com/jetson/archives/r35.4.1/DeveloperGuide/text/IN/QuickStart.html
Then you could start from the quick start guide first.
1 Like
Thanks for the link. I have gone through some steps before, this link looks very elaborate.
Note: I am working on a cutomised carrier board where CFG file is generated from the device tree files generated from the PIN MUX sheet.
Also some things like HDMI port enabling from Display port and one of PCIe lanes enabling we have done by manually editing the existing .DTSI files( as were not able to that using PIN MUX spreadsheet method for our customied carrier board ).
It would be more helpful to pinpoint the section which speaks about flashing after pinmux Cfg file is generated by python script and also some DTSI files are edited seperately. Want to proceed from here to rebuild/flash etc to the target board.
What to be done next. Thanks
It looks like you didn’t get some points. Kevin already replied your questions but you didn’t get it.
After you built out one cfg file, you should replace the original one that got flashed to your board.
Is this part where you didn’t understand?
Sorry, If i am confusing. As I am a newbie to this Nvia Jetson build and configuration process stuff.
How to replace the CFG file generated from python script with the original CFG files. This part I have studied.
As I have edited some other DTSI files manually apart from this CFG file generation from PIX MUX spreadsheet method.
My question is, can we flash both DTB, CFG files together on to the board using Flash command.