Jump to content

Orange PI RK3399 HDMI IN


nano

Recommended Posts

Hi, 

 

Thank you very much for all the work. I recently purchased 4GB RAM version of Orange PI RK3399. Was able to install armbian WIP version:

4.4.180-rk3399

 

I'm trying to capture video via HDMI IN port using gstreamer but I see the following error messages in kernel log, 

 

Spoiler

Jun 12 03:19:37 localhost kernel: [    3.956986] tc358749xbg 1-000f: probing...
Jun 12 03:19:37 localhost kernel: [    3.957006] tc358749xbg 1-000f: GPIO lookup for consumer int
Jun 12 03:19:37 localhost kernel: [    3.957016] tc358749xbg 1-000f: using device tree for GPIO lookup
Jun 12 03:19:37 localhost kernel: [    3.957101] tc358749xbg 1-000f: GPIO lookup for consumer power
Jun 12 03:19:37 localhost kernel: [    3.957111] tc358749xbg 1-000f: using device tree for GPIO lookup
Jun 12 03:19:37 localhost kernel: [    3.957174] tc358749xbg 1-000f: GPIO lookup for consumer power18
Jun 12 03:19:37 localhost kernel: [    3.957184] tc358749xbg 1-000f: using device tree for GPIO lookup
Jun 12 03:19:37 localhost kernel: [    3.957245] tc358749xbg 1-000f: GPIO lookup for consumer power33
Jun 12 03:19:37 localhost kernel: [    3.957255] tc358749xbg 1-000f: using device tree for GPIO lookup
Jun 12 03:19:37 localhost kernel: [    3.957316] tc358749xbg 1-000f: GPIO lookup for consumer csi-ctl
Jun 12 03:19:37 localhost kernel: [    3.957326] tc358749xbg 1-000f: using device tree for GPIO lookup
Jun 12 03:19:37 localhost kernel: [    3.957387] tc358749xbg 1-000f: GPIO lookup for consumer reset
Jun 12 03:19:37 localhost kernel: [    3.957397] tc358749xbg 1-000f: using device tree for GPIO lookup
Jun 12 03:19:37 localhost kernel: [    3.957458] tc358749xbg 1-000f: GPIO lookup for consumer stanby
Jun 12 03:19:37 localhost kernel: [    3.957468] tc358749xbg 1-000f: using device tree for GPIO lookup
Jun 12 03:19:37 localhost kernel: [    3.957556] tc358749xbg 1-000f: probing successful
Jun 12 03:19:37 localhost kernel: [    4.228517] tc358749xbg.pltfrm_camera_module_get_data(331) ERR: cannot not get camera-module-facing property of node camera-module
Jun 12 03:19:37 localhost kernel: [    4.228543] tc358749xbg.pltfrm_camera_module_get_data WARN: could not get default pinstate
Jun 12 03:19:37 localhost kernel: [    4.228555] tc358749xbg.pltfrm_camera_module_get_data WARN: could not get sleep pinstate
Jun 12 03:19:37 localhost kernel: [    4.228693] tc358749xbg.pltfrm_camera_module_get_data(537) ERR: could not get module rockchip,camera-module-name and rockchip,camera-module-len-name from dts!
Jun 12 03:19:37 localhost kernel: [    4.228709] tc358749xbg.pltfrm_camera_module_get_data(548) ERR: could not get module rockchip,camera-module-orientation from dts!
Jun 12 03:19:37 localhost kernel: [    4.228725] tc358749xbg.pltfrm_camera_module_get_data(559) ERR: could not get module rockchip,camera-module-flip from dts!
Jun 12 03:19:37 localhost kernel: [    4.228739] tc358749xbg.pltfrm_camera_module_get_data(570) ERR: could not get module rockchip,camera-module-mirror from dts!
Jun 12 03:19:37 localhost kernel: [    4.228755] tc358749xbg.pltfrm_camera_module_get_data(581) ERR: could not get module rockchip,camera-module-flash-support from dts!
Jun 12 03:19:37 localhost kernel: [    4.228797] tc358749xbg.tc_camera_module_attach(243) ERR: enter
Jun 12 03:19:37 localhost kernel: [    4.264297] tc358749xbg.tc_camera_module_write_config(182) ERR: no active sensor configuration
Jun 12 03:19:37 localhost kernel: [    4.264311] tc358749xbg.tc_camera_module_write_config(233) ERR: failed with error -14
Jun 12 03:19:37 localhost kernel: [    4.268634] tc358749xbg.tc358749xbg_check_camera_id(737) ERR: read pid return 0x4701
Jun 12 03:19:37 localhost kernel: [    4.268728] cif_isp10_pltfrm_get_img_src_device: tc358749xbg attach to cif isp10 img_src_array[0]
Jun 12 03:19:37 localhost kernel: [    4.268765] tc358749xbg.tc_camera_module_set_active_config(107) ERR: activating config '1920x1080_60fps'
Jun 12 03:19:37 localhost kernel: [    4.268781] tc358749xbg.tc_camera_module_s_frame_interval(420) ERR: custom.s_vts isn't support!
Jun 12 03:19:37 localhost kernel: [    4.268794] tc358749xbg.tc_camera_module_s_frame_interval(443) ERR: failed with error -14
Jun 12 03:19:37 localhost kernel: [    4.268836] tc358749xbg.tc_camera_module_s_frame_interval(420) ERR: custom.s_vts isn't support!
Jun 12 03:19:37 localhost kernel: [    4.268847] tc358749xbg.tc_camera_module_s_frame_interval(443) ERR: failed with error -14
Jun 12 03:19:37 localhost kernel: [    5.955174] dhd_dbg_detach_pkt_monitor, 2204
Jun 12 03:19:37 localhost kernel: [    7.475778] tc358749xbg.tc_camera_module_s_frame_interval(420) ERR: custom.s_vts isn't support!
Jun 12 03:19:37 localhost kernel: [    7.475788] tc358749xbg.tc_camera_module_s_frame_interval(443) ERR: failed with error -14
Jun 12 03:19:37 localhost kernel: [    7.511494] tc358749xbg.tc_camera_module_s_frame_interval(420) ERR: custom.s_vts isn't support!
Jun 12 03:19:37 localhost kernel: [    7.511505] tc358749xbg.tc_camera_module_s_frame_interval(443) ERR: failed with error -14

 

I also see lot of  irq mismatch errors in kernel log, 

 

Spoiler

[51474.621268] genirq: Flags mismatch irq 36. 00000080 (serial) vs. 00004000 (debug)
[51474.621470] genirq: Flags mismatch irq 36. 00000080 (serial) vs. 00004000 (debug)
[51474.632722] genirq: Flags mismatch irq 36. 00000080 (serial) vs. 00004000 (debug)
[51484.636572] genirq: Flags mismatch irq 36. 00000080 (serial) vs. 00004000 (debug)
[51484.636815] genirq: Flags mismatch irq 36. 00000080 (serial) vs. 00004000 (debug)
[51489.870555] genirq: Flags mismatch irq 36. 00000080 (serial) vs. 00004000 (debug)
[51489.870742] genirq: Flags mismatch irq 36. 00000080 (serial) vs. 00004000 (debug)
[51489.878549] genirq: Flags mismatch irq 36. 00000080 (serial) vs. 00004000 (debug)
[51499.880993] genirq: Flags mismatch irq 36. 00000080 (serial) vs. 00004000 (debug)

 

I tried with installing full firmware and rebooting, still have same errors. Any suggestions are greatly appreciated or if you can guide me to the correct kernel and driver source files to rebuild, I'm happy to compile and test. 

 

Thank you! 

Link to comment
Share on other sites

Feel free to give the dev branch a shot and see if that solves your problems. RK3399 SoC is WIP anyways, so no official support. Either go to https://www.armbian.com/orange-pi-rk3399/ and scroll to the very bottom or grab the build script here https://github.com/armbian/build and build your own image including the latest changes.

 

Btw. RK3399 forums are here: https://forum.armbian.com/forum/33-rockchip-3399/

Link to comment
Share on other sites

Thank you guys, if Armbian doesn't manage HDMI input, don't think dev branch will work either.

 

I'm going to build from xunlong's orangepi rk3399 repo in github. Fingers crossed.

Link to comment
Share on other sites

ffmpeg with hw encoding 1080p/60 (some stutter) working on stock debian image

 

 

don't have my board at the moment. process was:

 

1) get orange pi linux sdk and debian image

2) pull armbian latest

3) diff debian config, cherry pick HDMI, audo, encoders

4) diff kernel, cherry pick hdmi, audio, encoders

5) compile and flash

 

 

if you don't want to tinker and 1080p30 is sufficient @ H.264: https://www.inforcecomputing.com/products/application-ready-platforms/qualcomm-snapdragon-600-inforce-6420t is $99 and you get helpful support

Link to comment
Share on other sites

On 11/19/2019 at 4:54 PM, gounthar said:

You make it sound as if it was easy. ;)

It looks really difficult to me, but that's super cool to know that it worked for you.

Thanks for the link.

everything's easy.. AFTER you've done it :P

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines