Firmware File for RPI-CAM-MINISAS

[rudolf_streif]

I am trying to get the RPI-CAM-MINISAS board to work. The ap1302 driver asks for the firmware file ap1302_ar0144_single_fw.bin.

This page https://docs.nxp.com/bundle/RM00293/page/topics/ar0144.html states

A firmware named ap1302_ar0144_single_fw.bin is needed. Put it under the /lib/firmware folder.

However, there is no mention from where to get the file.

I tried to find it in this OnSemi Github repo: https://github.com/ONSemiconductor/ap1302_binaries/tree/main

There is no file with this exact file name in that repo. The closest I could find is: https://github.com/ONSemiconductor/ap1302_binaries/blob/main/NXP_i.MX93/ap1302_60fps_ar0144_27M_2Lan...

However, this firmware file does not work. The driver seems to load the file but then dmesg shows:

[ 11.201244] ap1302 1-003c: __ap1302_read: register 0x0000 read failed: -6

[rudolf_streif]

Thank you, @Zhiming_Liu, for confirming the firmware file.

I am using the RPI-CAM-MINISAS adapter together with the AP1302/AR0144 module. The FPC cable is attached correctly as the LEDs on the adapter and the red LED on the camera module are lit.

Now, I am not using the imx93 evk but the imx8mp evk. I found somewhere that this combination is not officially supported by NXP. I did create the device tree for the I2C to work. However, it could be that the 24 MHz clock is not working correctly. As I understand it, the camera module runs on an internal clock for the I2C communication and then switches to the external clock after the firmware is downloaded.

Maybe you have some more insight.

[Zhiming_Liu]

Hi @rudolf_streif 

Based on the log you provided earlier, there appears to be an issue with the I2C communication.  Had the firmware already been loaded before this log? If not, i think you need to check the GPIO status for the AP1302 reset and enable pins (R82 → RST, TP1 → enable).

Best Regards,
Zhiming

[Zhiming_Liu]

Hi @rudolf_streif 

Can you share the BSP verison you are using?

Best Regards,
Zhiming

[rudolf_streif]

It's a custom Yocto Project build with these NXP layers:

meta-freescale = "master:4cc4bc05063f7f4c105587332493742379d11ad7"
meta-freescale-3rdparty = "master:29c36ae80ba5762091f48d6d15b637455cc15758"
meta-freescale-distro = "master:70b7591ecaa99cb6366f93ee05df7c38d94d724b"

It's essentially YP Whinlatter/Wrynose.

I thought the firmware would be part of firmware-imx (the version is 8.28), but it is not.

[Zhiming_Liu]

Hi,

This link is correct firmware link, i did test on L6.18.2 and it worked.

root@imx93evk:~# dmesg | grep ap1302
[    0.350765] /soc@0/bus@42000000/i2c@42530000/ap1302_mipi@3c: Fixed dependency cycle(s) with /soc@0/bus@42800000/csi@4ae00000
[    0.391204] /soc@0/bus@42800000/csi@4ae00000: Fixed dependency cycle(s) with /soc@0/bus@42000000/i2c@42530000/ap1302_mipi@3c
[    0.486760] /soc@0/bus@42000000/i2c@42530000/ap1302_mipi@3c: Fixed dependency cycle(s) with /soc@0/bus@42800000/csi@4ae00000
[    0.518939] /soc@0/bus@42000000/i2c@42530000/ap1302_mipi@3c: Fixed dependency cycle(s) with /soc@0/bus@42800000/csi@4ae00000
[    0.560106] /soc@0/bus@42800000/csi@4ae00000: Fixed dependency cycle(s) with /soc@0/bus@42000000/i2c@42530000/ap1302_mipi@3c
[    0.572201] /soc@0/bus@42000000/i2c@42530000/ap1302_mipi@3c: Fixed dependency cycle(s) with /soc@0/bus@42800000/csi@4ae00000
[    0.591913] /soc@0/bus@42800000/csi@4ae00000: Fixed dependency cycle(s) with /soc@0/bus@42000000/i2c@42530000/ap1302_mipi@3c
[    2.783982] /soc@0/bus@42800000/csi@4ae00000: Fixed dependency cycle(s) with /soc@0/bus@42000000/i2c@42530000/ap1302_mipi@3c
[    2.795274] /soc@0/bus@42000000/i2c@42530000/ap1302_mipi@3c: Fixed dependency cycle(s) with /soc@0/bus@42800000/csi@4ae00000
[    9.648423] ap1302 2-003c: AP1302 revision 0.2.6 detected

Please check your hardware connection.

Best Regards,
Zhiming