Achtung! Externe E-Mail: Klicken Sie erst dann auf Links und Anhänge, nachdem
Sie die Vertrauenswürdigkeit der Absenderadresse geprüft haben.
Hi Adam,
Thanks for the information and support.
Effectively, the emmc-driver is working without including any other device in
the vbus, and it prints the GPT partition as well.
I was missing to add the dma configuration in the io script of the mmc with:
Property.flags = Io.Hw_device_DF_dma_supported;
Additionally, I increased the bounce buffer data space from the ned script
example to 1MB as:
local bbds = ft:create(L4.Proto.Dataspace, 128 << 13, mem_flags, 21):m("rws")
Kind regards,
Alvaro
________________________________
Von: Adam Lackorzynski <[email protected]>
Gesendet: Sonntag, 5. Januar 2025 12:44:19
An: Alvaro Gallardo; [email protected]
Betreff: Re: emmc-driver imx8mp
________________________________
Achtung! Externe E-Mail: Klicken Sie erst dann auf Links und Anhaenge, nachdem
Sie die Vertrauenswuerdigkeit der Absenderadresse geprueft haben.
________________________________
Hi Alvaro,
Some things to check out:
- assuming u-boot initialized the emmc (you are using it in u-boot) all
the needed peripherals should be set up at this point
- the emmc-driver itself prints out partition infos, so if there is a
GPT partition on the emmc it should be displayed, i.e., then it is
working. This happens prior to VMs starting.
Adam
On Tue Dec 17, 2024 at 03:21:50 +0000, Alvaro Gallardo wrote:
> Dear L4Re experts,
>
>
> I hope you are doing well and enjoying this time of the year.
>
>
> I would like to ask for your help or insights on how to use the emmc-driver
> in an imx8mp based board.
>
>
> In this platform, the usdhc nodes are located out of the pci bus, and they
> require an i2c device to work, as well as gpio and clocks.
>
>
> I am able to start the emmc server, which identifies one usdhc device and
> starts the server loop. I pass a virtual bus to the emmc driver with all
> required devices, as they usually work in the Virtual Machine to access the
> mmc. The driver scans all of them, finding the usdhc node.
>
>
> But, everything stops when I create a client, either using a dynamic way
> with: create(0, "device=...","ds-max=5); or declaring the client in the
> argument as: "emmc-drv -v --client cl1 --device=... --ds-max=5". For the
> second way, it stops when the Virtual Machine starts to configure the related
> virtio device (I am using a virtio_net node).
>
>
>
> I will be grateful if you can give me some information about the issue or
> some of the following questions:
>
>
> 1. how should the node in the device tree of the Virtual Machine be
> configured to work with the emmc client?
>
>
> 2. is it possible that the board's specific hardware configuration
> required for the mmc is stopping the emmc client to work?
>
>
> 3. Is there any way to test the driver before linking it to a virtual
> machine? I found an example with the "virtio-block-chksum-sync" module, but I
> could not find this module.
>
>
> I attach the configuration files, the output text and the base device tree
> structure. Thank you in advance for your attention.
>
>
> Kind regards,
>
>
> Alvaro Gallardo
>
> _______________________________________________
> l4-hackers mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
_______________________________________________
l4-hackers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
