fec_nic_drv runtime error in Genode 22.11

Pontus Åström ponast at gmail.com
Tue Dec 20 20:29:28 CET 2022


I upgraded genode-imx and genode to version 22.11 for my IMX project.
As per the drivers.config example in
genode-imx/recipes/raw/drivers_nic-imx8q_evk/drivers.config I added a
new ROM service for the nic_drv.dtb as follows:
<service name="ROM" label="nic_drv.dtb"><parent
label="fec_nic_drv-imx8q_evk.dtb"/>

My fec_nic config now looks like as follows:
<start name="eth0_drv" caps="130" priority="0">
    <binary name="fec_nic_drv" />
    <resource name="RAM" quantum="20M"/>
    <resource name="CPU" quantum="30"/>
    <config verbose="yes" mode="uplink_client"/> }
    <route>
        <service name="CPU"><parent/></service>
        <service name="LOG"><parent/></service>
        <service name="PD"><parent/></service>
        <service name="RM"><parent/></service>
        <service name="ROM" label="nic_drv.dtb">
            <parent label="fec_nic_drv-imx8q_evk.dtb"/>
        </service>
        <service name="ROM"><parent/></service>
        <service name="Uplink">  <child name="net0_router"/></service>
        <service name="Timer">   <child name="timer_drv"/></service>
        <service name="Platform"><child name="platform_drv"/></service>
    </route>
</start>

Now everything compiles successfully but I get a runtime setup error
where the driver complains about an unavailable IO resource:

[init -> eth0_drv] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[init -> eth0_drv] clocksource: dde_counter: mask: 0xffffffffffffff
max_cycles: 0x1d854df40, max_idle_ns: 3526361616960 ns
[init -> eth0_drv] sched_clock: 64 bits at 1000kHz, resolution 1000ns,
wraps every 2199023255500ns
[init -> eth0_drv] clocksource: jiffies: mask: 0xffffffff max_cycles:
0xffffffff, max_idle_ns: 7645041785100000 ns
[init -> eth0_drv] clocksource: Switched to clocksource dde_counter
[init -> eth0_drv] mdio_bus: Fixed MDIO Bus: probed
[init -> eth0_drv] Error: memory-mapped I/O resource 0x30be0000
(size=0x10000) unavailable

What might be the cause of this error?

Best regards,
Pontus



More information about the users mailing list