I flashed the board with flash.sh (./flash.sh jetson-nano-emmc mmcblk0p1) and then I edited the dts file tegra210-p3448-0002-p3449-0000-b00.dts to set sdhci@700b0400 status as “okay” and also I added nvidia,vmmc-always-on.
Also, I activated the pins GPIO07 and GPIO09 but still not working.
If you are new to such kernel and dts work, then you should share below information
The full dmesg
The full dts. Convert the dtb back to dts and share it here.
Your board schematic.
Setting sdhci@700b0400 to enabled is just turning on the controller, it does not have other parameters to match your board. For example, the cd-gpios, and the power supply. If you don’t change them, then they are just same as our default setting. Which may not match your board at all.
R37 is not placed (internal pull-up expected). R36 protects the SOM in case GPIO07 is configured as output for other purposes and the card is inserted, shouldn’t disturb card detect functionality with a strong internal pull-up.
I followed the steps and flashed the board again. I set the initial configurations (language, user, password,…) but then the board is not working. It’s connected to a monitor and when it’s booting three errors appear, ‘Failed to start Load Kernel Modules’, ‘Failed to start nvpmodel service’, and ‘Failed to start Configure USB flashing port for device mode…’
I am not sure why you asked the same question again. The answer is already provided in the previous comment.
The purpose of pinmux is just change the functions of some pins. That is, we do have some pins that can be either gpio or SFIO. If such pin setting is already GPIO as you need, then you don’t need to modify it from pinmux spreadsheet again.