Hashimoto Kenichi

I don't use Tinker OS. git://git.yoctoproject.org/meta-rockchip https://source.denx.de/u-boot/u-boot.git v2022.01

1. what are the results of: devnum and devtype is not set. Because I use distro_bootcmd. 2. where was the uboot flashed onto? eMMC 3. is there any other storage (such as sd card/ usb flash storage ... etc) attached to tinker board 2s? SD card is removed.

CMD_SEND:1 ARG 0x00000000 MMC_RSP_R3,4 0xffffffff The above is clearly an outlier and we are trying to find the cause.

1. are you using tinker os? No. I am using Yocto (kirkstone) with patches. u-boot version is 2022.01. 2. what's the error you encountered? The second "mmc dev 0" execution results in an error. Writing to eMMC, such as saveenv, succeeds, but distro_bootcmd executes "mmc dev 0", so it fails there.

=> mmc dev 0 CMD_SEND:0 ARG 0x00000000 MMC_RSP_NONE CMD_SEND:8 ARG 0x000000aa RET -110 CMD_SEND:55 ARG 0x00000000 RET -110 CMD_SEND:0 ARG 0x00000000 MMC_RSP_NONE CMD_SEND:8 ARG 0x000000aa RET -110 CMD_SEND:55 ARG 0x00000000 RET -110 CMD_SEND:0 ARG 0x00000000 MMC_RSP_NONE CMD_SEND:1 ARG 0x00000000 MMC_RSP_R3,4 0xffffffff CMD_SEND:2 ARG 0x00000000 RET -110 CMD_SEND:2 ARG 0x00000000 RET -110 CMD_SEND:2 ARG 0x00000000 RET -110 CMD_SEND:2 ARG 0x00000000 RET -110 CMD_SEND:2 ARG 0x00000000 RET -110 Enable CONFIG_MMC_TRACE

Even if You don't write mmc dev 0 was not working.

The following settings were made to save the u-boot env to eMMC. U-Boot 2022.01 CONFIG_ENV_IS_IN_MMC=y CONFIG_SYS_MMC_ENV_DEV=0 CONFIG_SYS_MMC_ENV_PART=0 The write operation succeeds once, but then the eMMC stops responding. Writing by ums is also successful, so writing itself seems to be OK, but there seems to be a problem in the subsequent operation. What are the problems with writing to eMMC?