Yes, for example I did:
=> mmc read 0x00000000 512 1
MMC read: dev # 0, block # 1298, count 1 ... CMD_SEND:16
ARG 0x00000200
MMC_RSP_R1,5,6,7 0x00000900
CMD_SEND:17
ARG 0x00000512
MMC_RSP_R1,5,6,7 0x00000900
1 blocks read: OK
Then I tried to write into it like this:
=> mmc write 0x00000000 512 1
MMC write: dev # 0, block # 1298, count 1 ... CMD_SEND:16
ARG 0x00000200
MMC_RSP_R1,5,6,7 0x00000900
CMD_SEND:24
ARG 0x00000512
MMC_RSP_R1,5,6,7 0x00000900
CMD_SEND:13
ARG 0x00010000
sdhci_send_command: MMC: 0 busy timeout increasing to: 200 ms.
MMC_RSP_R1,5,6,7 0x00000900
CURR STATE:4
1 blocks written: OK
What do you think?
I'm reading JEDEC Specification Version 5.0 document maybe it could bring
some insight on what is happening. The driver is supposed to match with any
eMMC but still.
On Tue, Feb 27, 2018 at 7:24 PM, Yang, Wenyou <wenyou.y...@microchip.com>
wrote:
>
> On 2018/2/28 0:55, Mariano Coromac wrote:
>
>> Hmmm, by sequential number do you mean the Specification Version? This
>> one is correct.
>> Here's my eMMC info.
>> => mmc info
>> Device: sdio-host@a0000000
>> Manufacturer ID: eb
>> OEM: 10d
>> Name: eMMC
>> Tran Speed: 52000000
>> Rd Block Len: 512
>> MMC version 5.0
>> High Capacity: Yes
>> Capacity: 3.6 GiB
>> Bus Width: 4-bit
>> Erase Group Size: 512 KiB
>> HC WP Group Size: 8 MiB
>> User Capacity: 3.6 GiB
>> Boot Capacity: 2 MiB ENH
>> RPMB Capacity: 512 KiB ENH
>>
> This is right, did you try the command,
> => mmc read addr blk# cnt
> does it work?
>
> Best Regards,
> Wenyou Yang
>
--
Mariano Coromac <https://gps.gt/>
I&D of Electronics Engineer
mcoro...@stsa.info
+502 41544712
www.gps.gt <http://facebook.com/startracksa>
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
