basler camera with 4k resolution on IMX8MP EVK android

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

basler camera with 4k resolution on IMX8MP EVK android

1,186 Views
darsh_dev
Contributor V

Hi,

I am able to get basler camera daA3840 on IMX8MP EVK with Android. Android bsp package have .drv for basler camera for 1080P resolution only. daA3840 also have support for 4K resolution which is working in Linux BSP but not on android as .drv, xml and json is not available in android BSP for 4k resolution of basler camera.

Could you please help us from where we can .drv (similar to vendor/nxp/fsl-proprietary/isp/lib64/DAA3840_30MC_1080P.drv) of basler camera for 4K resolution? I tried using .drv from linux BSP but that is not working.

Thanks in advance.

0 Kudos
3 Replies

1,177 Views
Bio_TICFSL
NXP TechSupport
NXP TechSupport

Hello darshak,

The MX8MP has a resolution of 1080p max. you can not seen the resolution mora than that.

 

Regards

0 Kudos

1,155 Views
darsh_dev
Contributor V

Hi,

According to "i.MX 8M Plus Applications Processor Reference Manual, Rev. 1, 06/2021", "Section 13.1.2 Display Interface", out of three LCDIF controllers one drives HDMI Tx and it supports up to 4kp30. In same section, it is mentioned that "The chip supports a HDMI 2.0a Tx interface (controller and PHY). It supports a maximum resolution upto 4Kp30"

Also, as per section 13.1.5 Image Signal Processor (ISP) "Table 13-1 Supported Resolution and Formats - 1 ISP", 4k resolution is supported.

As per section 13.1.6 Dewrap Engine, Dewrap supports one camera up to 4K at 30 fps.

In fact, basler camera with 4k resolution is working with Linux BSP. If you check  https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/isp-imx-4.2.2.13.0.bin, in that .drv for basler camera with 4k resolution is there. Which is working with Linux BSP but not android. When I use same .drv with Andorid, I see below trace where isp_media_server gets crashed.

 

"

01-01 00:00:36.284 519 519 F DEBUG : backtrace:
01-01 00:00:36.284 519 519 F DEBUG : #00 pc 0000000000092c94 /vendor/lib64/libcam_device.so (camdev::SensorOps::queryCaps(HalHolder*, vvcam_mode_info_array*, unsigned int*, unsigned int*)+136) (BuildId: 735e68062dd7e0643e2b1bbfc041037c95f7667c)
01-01 00:00:36.284 519 519 F DEBUG : #01 pc 00000000000a5648 /vendor/lib64/libcam_device.so (camdev::CitfSensor::queryCaps(Json::Value&, Json::Value&)+68) (BuildId: 735e68062dd7e0643e2b1bbfc041037c95f7667c)
01-01 00:00:36.284 519 519 F DEBUG : #02 pc 00000000000a5450 /vendor/lib64/libcam_device.so (camdev::CitfSensor::process(int, Json::Value&, Json::Value&)+60) (BuildId: 735e68062dd7e0643e2b1bbfc041037c95f7667c)
01-01 00:00:36.284 519 519 F DEBUG : #03 pc 000000000005947c /vendor/lib64/libmedia_server.so (MediaPipeline::jsonRequest(int, int, Json::Value&, Json::Value&)+452) (BuildId: 266f7d5d6e98bae63fdbea513dfbad0beb2c2f69)
01-01 00:00:36.284 519 519 F DEBUG : #04 pc 0000000000059884 /vendor/lib64/libmedia_server.so (MediaPipeline::handleEvent(EventData&)+896) (BuildId: 266f7d5d6e98bae63fdbea513dfbad0beb2c2f69)
01-01 00:00:36.284 519 519 F DEBUG : #05 pc 0000000000010920 /vendor/bin/isp_media_server (EventSource::notifyAll(EventData&)+88) (BuildId: abb861f2c819933aa16aea557b155fb88ccd693a)
01-01 00:00:36.284 519 519 F DEBUG : #06 pc 000000000000effc /vendor/bin/isp_media_server (V4l2Event::eventLoop()+1828) (BuildId: abb861f2c819933aa16aea557b155fb88ccd693a)
01-01 00:00:36.285 519 519 F DEBUG : #07 pc 00000000000103fc /vendor/bin/isp_media_server (void* std::__ndk1::__thread_proxy<std::__ndk1::tuple<std::__ndk1::unique_ptr<std::__ndk1::__thread_struct, std::__ndk1::default_delete<std::__ndk1::__thread_struct> >, V4l2Event::V4l2Event()::$_5> >(void*)+44) (BuildId: abb861f2c819933aa16aea557b155fb88ccd693a)
01-01 00:00:36.285 519 519 F DEBUG : #08 pc 00000000000b0c08 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+64) (BuildId: 2338ca8a340db969666f0073f3371d96)
01-01 00:00:36.285 519 519 F DEBUG : #09 pc 00000000000505d0 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 2338ca8a340db969666f0073f3371d96)

"

0 Kudos

1,143 Views
Bio_TICFSL
NXP TechSupport
NXP TechSupport

Yes, it is working but videos encode or decode it won't work at 4k, and the lcd neither.

 

0 Kudos