[Buildroot] Firmware auto-loading does not work

Guillaume GARDET - Oliséo guillaume.gardet at oliseo.fr
Fri Feb 3 09:51:56 UTC 2017


Hi,

I found the problem thanks to mdev log:
     mdev[716]: 00:04:57.841774 ACTION:add SUBSYSTEM:firmware DEVNAME:(null) DEVPATH:/devices/platform/musb-omap2430/musb-hdrc.0/usb2/2-1/2-1:1.0/firmware/2-1:1.0 FW:rt2870.bin
     mdev[716]: rule matched, line -1
     mdev[716]: can't change directory to '/sys/devices/platform/musb-omap2430/musb-hdrc.0/usb2/2-1/2-1:1.0/firmware/2-1:1.0': No such file or directory
     mdev[717]: 00:05:57.982454 ACTION:remove SUBSYSTEM:firmware DEVNAME:(null) DEVPATH:/devices/platform/musb-omap2430/musb-hdrc.0/usb2/2-1/2-1:1.0/firmware/2-1:1.0 FW:rt2870.bin
     mdev[717]: 00:05:57.982545 exiting

The thing is that the PATH is not good :
* requested : /sys/devices/platform/musb-omap2430/musb-hdrc.0/usb2/2-1/2-1:1.0/firmware/2-1:1.0
* real: /sys/devices/platform/musb-omap2430.0/musb-hdrc.0/usb2/2-1/2-1:1.0/firmware/2-1:1.0

The only difference is the ".0" missing after musb-omap2430. Any idea why there is this difference?


Guillaume




Le 30/01/2017 à 16:27, Peter Korsgaard a écrit :
>>>>>> "Guillaume" == Guillaume GARDET <- Oliséo <guillaume.gardet at oliseo.fr>> writes:
> Hi,
>
>   >> Can you confirm that it works if you enable that option.
>   >>
>
>   > I get back the hardware for testing and it still does not work, even if I enable CONFIG_FEATURE_MDEV_LOAD_FIRMWARE=y :
>   >     phy0 -> rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'.
>   > and after 60 seconds, I get:
>   >     phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware.
>   >     phy0 -> rt2x00lib_request_firmware: Error - Error is '-2'.
>
>   > Whereas the firmware file is in /lib/firmware/
>
>   > Any idea what could be wrong?
>
> Not really. Please double check that you enabled
> CONFIG_FEATURE_MDEV_LOAD_FIRMWARE in busybox. To debug further, I
> suggest you stick some fprintf statements (E.G. to your serial port /
> console) in mdev.c to see if it gets called and what is going on.
>



More information about the buildroot mailing list