Hi Jonas,
On 2/5/24 14:05, Jonas Karlman wrote:
Hi Quentin,
On 2024-02-05 10:47, Quentin Schulz wrote:
Hi Jonas,
On 2/4/24 21:53, Jonas Karlman wrote:
Testing has shown that writing to eMMC using a slower mode then HS200
typically generate an ERROR on first attempt on RK3588.
# Rescan
Hi Quentin,
On 2024-02-05 10:47, Quentin Schulz wrote:
> Hi Jonas,
>
> On 2/4/24 21:53, Jonas Karlman wrote:
>> Testing has shown that writing to eMMC using a slower mode then HS200
>> typically generate an ERROR on first attempt on RK3588.
>>
>># Rescan using MMC legacy mode
>>=> mmc
Hi Jonas,
On 2/4/24 21:53, Jonas Karlman wrote:
Testing has shown that writing to eMMC using a slower mode then HS200
typically generate an ERROR on first attempt on RK3588.
# Rescan using MMC legacy mode
=> mmc rescan 0
# Write a single block to sector 0x4000 fails with ERROR
=>
On Mon, Feb 5, 2024 at 4:53 AM Jonas Karlman wrote:
>
> Testing has shown that writing to eMMC using a slower mode then HS200
> typically generate an ERROR on first attempt on RK3588.
>
> # Rescan using MMC legacy mode
> => mmc rescan 0
>
> # Write a single block to sector 0x4000 fails with
On 2024/2/5 04:53, Jonas Karlman wrote:
Testing has shown that writing to eMMC using a slower mode then HS200
typically generate an ERROR on first attempt on RK3588.
# Rescan using MMC legacy mode
=> mmc rescan 0
# Write a single block to sector 0x4000 fails with ERROR
=> mmc
Testing has shown that writing to eMMC using a slower mode then HS200
typically generate an ERROR on first attempt on RK3588.
# Rescan using MMC legacy mode
=> mmc rescan 0
# Write a single block to sector 0x4000 fails with ERROR
=> mmc write 2000 4000 1
# Write a single block to
6 matches
Mail list logo
