Attached_mmio with platform_drv

Duss Pirmin pirmin.duss at gapfruit.com
Wed Sep 2 13:26:00 CEST 2020


Hello Stefan

On 01.09.20 13:46, Stefan Kalkowski wrote:
> The Attached_mmio abstraction from the `os/include/os/attached_mmio.h`
> header is no appropriated one for your use-case anymore. Instead you
> might use the Attached_dataspace abstraction to map the I/O memory
> into the address space, and put the resulting "local_addr" into the
> Mmio abstraction explicitly. That is the one you have used before for
> the register definitions and access.

Many thanks. With this I can initialize an Mmio structure that
represents the registers of the device.

But as soon I try to read from a register the driver terminates with the
following error:
Kernel: MMU-fault not handled ESR=0x92000210
Kernel: init -> i2c2_drv -> ep raised unhandled MMU fault ip=0x1009930
fault-addr=0x20008 type=unknown
Writing to a register never returns.

If I change the base address to 0x30B5000 (usdhc2) the read succeeds.

I had the same error before the update without using `platform_drv`,
which led me to think, that maybe the clocks for the subsystem aren't
initialized. But this is now done by `platform_drv`.

Best regards, Pirmin


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.genode.org/pipermail/users/attachments/20200902/b4937556/attachment.sig>


More information about the users mailing list