I don't want to run U-boot and kernel from eMMC. Just want to access raw eMMC and perform some read/write cycle tests. Can we access the eMMC by writing the application layer?
Thanks,
I don't want to run U-boot and kernel from eMMC. Just want to access raw eMMC and perform some read/write cycle tests. Can we access the eMMC by writing the application layer?
Thanks,
Yes, if you load your filesystem as a ramdisk and then use that, you can run performance tests on the eMMC. The kernel is already running in memory. The exact details on this will depend on things such as what SoC you are using.
eMMC software drivers are typically fairly complex, supporting multiple commands. So any tests will require a fairly large amount of software to be written (or borrowed) to get even basic read/write functionality.
uboot's emmc "core" driver is around 2.5k lines of code for example: https://github.com/ARM-software/u-boot/blob/master/drivers/mmc/mmc.c
and that's not including the device specific parts.
That's not taking into consideration that fact that booting from eMMC works differently. Or that eMMC could be running in different modes during different stages of operation. E.g. HS400 once full OS is running, but legacy mode in the bootloader.
So sure... it's certainly possible. But why? What's the end game?