In order to use spi.use '' to flash board

Hello, I want to use SPI now, but I found out that I need to modify the DTB file to remove some GPIOs and then reflash the board.
Like this said: Jetson Nano SPI Bus Not Working - #10 by KevinFFF
Can I use to only flash the DTB file? (Because I don’t want to rebuild the Python environment on the board). Is a command like this correct: sudo ./ -r -k DTB jetson-nano-emmc mmcblk0p1?

If this is possible, is this command correct? How do I know my board model: “jetson-nano-emmc” and “mmcblk0p1”?

Also, my board is a Jetson Nano B01 L4T: 32.7.4 Jetpack: 4.6.4.

Hi lululu991129,

We would suggest you flash the whole board since dtb may be loaded from /boot/dtb/ instead of DTB partition.

Are you using Jetson Nano with eMMC or SD module?

OK, thank you for your reply.
My board have 16G emmc and SD card.
When I used the “lsblk”, shows as follow:
Does the "dmasg | -i kernel " show that did dtb load from /boot/dtb/?

When I use the" sudo ./ -r jetson-nano-emmc mmcblk0p1 ?"
it has something wrong.

Please tell me what’s wrong.

It seems not the expected result to me for the devkit.

There’s only eMMC module or SD module for Jetson Nano.
If you have both, then you might use eMMC module on custom carrier board.

The log showed the source of your device tree.

Do you modify
Please use the following command instead to flash your board.

$ sudo ./ jetson-nano-emmc mmcblk0p1

Which dtb file I should modify It means?

I did not modify the

@KevinFFF Thank you for your help.
My spi test success after I change dtb and rebuild kernel and flash the board.
But the result is different with yours, using the command “sudo cat /sys/kernel/debug/tegra_pinctrl_reg | grep -i spi”.
As follows showed, I would like to know if this has any impact.

Please check you log with “copying dtbfile”, you would know it is tegra210-p3448-0000-p3449-0000-b00.dtb

It seems the pinmux for SPI2 is not correct in your case for SPI usage.
If you just need the SPI1 work, then you can ignore this.
If you want to use SPI2, please check the pinmux configuration.