Hi,
I have been Investigating an issue when using a product we have based on the AM335X processor. It appears there was a change put into the eMMC driver within u-boot as follows:
commit d2c05f50e12f87128597a28146de7092aaa847c3
Author: Faiz Abbas faiz_abbas@ti.com
Date: Fri Apr 5 14:18:46 2019 +0530
mmc: omap_hsmmc: Set 3.3V for IO voltage
Pbias voltage should match the IO voltage set for the SD card. With the
latest pbias change to 3.3V, update the capabilities and IO voltages
settings to 3.3V.
Signed-off-by: Faiz Abbas <faiz_abbas@ti.com>
The changes made to the voltage levels as part of this commit appear to cause an error when using the saveenv command in u-boot as follows:
saveenv
Saving Environment to MMC... mmc_init_stream: timedout waiting for cc!
omap_hsmmc_send_cmd : timeout: No status update
MMC init failed
Failed (1)
If this commit is reverted then the system appears to function correctly. On further inspection of the commit history there is reference to PBIAS documented in http://www.ti.com/lit/pdf/sprui30, however I cannot find any reference (besides a definition) to PBIAS in the am335x documentation at https://www.ti.com/lit/ug/spruh73q/spruh73q.pdf.. Has this issue been encountered before or is it expected that this commit will break the system in this way?
Many thanks in advance for your help.
Regards
Ben
