Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1683165 > unrolled thread
| Started by | Jagan Teki <jagannadh.teki@gmail.com> |
|---|---|
| First post | 2017-07-07 14:50 +0200 |
| Last post | 2017-07-07 16:30 +0200 |
| Articles | 4 — 3 participants |
Back to article view | Back to linux.kernel
coda 2040000.vpu: firmware request failed Jagan Teki <jagannadh.teki@gmail.com> - 2017-07-07 14:50 +0200
Re: coda 2040000.vpu: firmware request failed Fabio Estevam <festevam@gmail.com> - 2017-07-07 15:40 +0200
Re: coda 2040000.vpu: firmware request failed Philipp Zabel <p.zabel@pengutronix.de> - 2017-07-07 16:00 +0200
Re: coda 2040000.vpu: firmware request failed Jagan Teki <jagannadh.teki@gmail.com> - 2017-07-07 16:30 +0200
| From | Jagan Teki <jagannadh.teki@gmail.com> |
|---|---|
| Date | 2017-07-07 14:50 +0200 |
| Subject | coda 2040000.vpu: firmware request failed |
| Message-ID | <u0ARQ-44v-11@gated-at.bofh.it> |
Hi, I'm observing firmware request failure with i.MX6Q board, This is with latest linux-next (4.12) with firmware from, [1] and converted v4l-coda960-imx6q.bin using [2]. Log: ------ coda 2040000.vpu: Direct firmware load for vpu_fw_imx6q.bin failed with error -2 coda 2040000.vpu: Direct firmware load for vpu/vpu_fw_imx6q.bin failed with error -2 coda 2040000.vpu: Direct firmware load for v4l-coda960-imx6q.bin failed with error -2 coda 2040000.vpu: firmware request failed I've verified md4sum and VDDPU as well, hope these look OK. # md5sum /lib/firmware/v4l-coda960-imx6q.bin af4971a37c7a3a50c99f7dfd36104c63 /lib/firmware/v4l-coda960-imx6q.bin # dmesg | grep regu | grep -i vddpu [ 0.061552] vddpu: supplied by regulator-dummy Did I missed any, request for help? [1] http://www.freescale.com/lgfiles/NMG/MAD/YOCTO/firmware-imx-3.0.35-4.0.0.bin [2] http://lists.infradead.org/pipermail/linux-arm-kernel/2013-July/181101.html thanks! -- Jagan Teki Free Software Engineer | www.openedev.com U-Boot, Linux | Upstream Maintainer Hyderabad, India.
[toc] | [next] | [standalone]
| From | Fabio Estevam <festevam@gmail.com> |
|---|---|
| Date | 2017-07-07 15:40 +0200 |
| Message-ID | <u0BEe-4FV-23@gated-at.bofh.it> |
| In reply to | #1683165 |
Hi Jagan, On Fri, Jul 7, 2017 at 9:45 AM, Jagan Teki <jagannadh.teki@gmail.com> wrote: > Hi, > > I'm observing firmware request failure with i.MX6Q board, This is with > latest linux-next (4.12) with firmware from, [1] and converted > v4l-coda960-imx6q.bin using [2]. There is no need to do the conversion with current code.
[toc] | [prev] | [next] | [standalone]
| From | Philipp Zabel <p.zabel@pengutronix.de> |
|---|---|
| Date | 2017-07-07 16:00 +0200 |
| Message-ID | <u0BXA-4Oh-5@gated-at.bofh.it> |
| In reply to | #1683165 |
Hi Jagan,
On Fri, 2017-07-07 at 18:15 +0530, Jagan Teki wrote:
> Hi,
>
> I'm observing firmware request failure with i.MX6Q board, This is with
> latest linux-next (4.12) with firmware from, [1] and converted
> v4l-coda960-imx6q.bin using [2].
>
> Log:
> ------
> coda 2040000.vpu: Direct firmware load for vpu_fw_imx6q.bin failed with error -2
> coda 2040000.vpu: Direct firmware load for vpu/vpu_fw_imx6q.bin failed
> with error -2
> coda 2040000.vpu: Direct firmware load for v4l-coda960-imx6q.bin
> failed with error -2
The error code is -ENOENT, so the firmware binary is not found where the
firmware loader code is looking. That could be caused by the coda driver
being probed before the file system containing the firmware binary is
mounted. Have you tried compiling the coda driver as a module
(CONFIG_VIDEO_CODA=m)?
> coda 2040000.vpu: firmware request failed
>
> I've verified md4sum and VDDPU as well, hope these look OK.
>
> # md5sum /lib/firmware/v4l-coda960-imx6q.bin
> af4971a37c7a3a50c99f7dfd36104c63 /lib/firmware/v4l-coda960-imx6q.bin
> # dmesg | grep regu | grep -i vddpu
> [ 0.061552] vddpu: supplied by regulator-dummy
>
> Did I missed any, request for help?
>
> [1] http://www.freescale.com/lgfiles/NMG/MAD/YOCTO/firmware-imx-3.0.35-4.0.0.bin
> [2] http://lists.infradead.org/pipermail/linux-arm-kernel/2013-July/181101.html
>
> thanks!
Note that converting the NXP provided firmware is not necessary anymore
since commits a1a87fa3a0cf ("[media] coda: add support for native order
firmware files with Freescale header") and 2ac7f08e3075 ("[media] coda:
add support for firmware files named as distributed by NXP").
Also there are newer firmware binaries available, see
https://patchwork.linuxtv.org/patch/42332/
regards
Philipp
[toc] | [prev] | [next] | [standalone]
| From | Jagan Teki <jagannadh.teki@gmail.com> |
|---|---|
| Date | 2017-07-07 16:30 +0200 |
| Message-ID | <u0CqC-5eN-17@gated-at.bofh.it> |
| In reply to | #1683202 |
On Fri, Jul 7, 2017 at 7:09 PM, Philipp Zabel <p.zabel@pengutronix.de> wrote: > Hi Jagan, > > On Fri, 2017-07-07 at 18:15 +0530, Jagan Teki wrote: >> Hi, >> >> I'm observing firmware request failure with i.MX6Q board, This is with >> latest linux-next (4.12) with firmware from, [1] and converted >> v4l-coda960-imx6q.bin using [2]. >> >> Log: >> ------ >> coda 2040000.vpu: Direct firmware load for vpu_fw_imx6q.bin failed with error -2 >> coda 2040000.vpu: Direct firmware load for vpu/vpu_fw_imx6q.bin failed >> with error -2 >> coda 2040000.vpu: Direct firmware load for v4l-coda960-imx6q.bin >> failed with error -2 > > The error code is -ENOENT, so the firmware binary is not found where the > firmware loader code is looking. That could be caused by the coda driver > being probed before the file system containing the firmware binary is > mounted. Have you tried compiling the coda driver as a module > (CONFIG_VIDEO_CODA=m)? Yes, true unless it is module firmware files can't get by coda # modprobe -a coda [ 24.474662] coda 2040000.vpu: Firmware code revision: 36350 [ 24.480556] coda 2040000.vpu: Initialized CODA960. [ 24.485415] coda 2040000.vpu: Unsupported firmware version: 2.1.9 [ 24.493494] coda 2040000.vpu: codec registered as /dev/video[0-1] thanks! -- Jagan Teki Free Software Engineer | www.openedev.com U-Boot, Linux | Upstream Maintainer Hyderabad, India.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web