How does one detect incoming data on Jetson Xavier MIPI port?

Currently we have a MAX96712 configured in 2x4 mode connected to a Jetson AGX Xavier Module.

With a scope we measured the MIPI clock and observed a 1 GHz clock (this matched our expected value) and also monitored DA0 MIPI Lane and observed data.

We are currently developing with: Linux4Tegra R32.2.3, JetPack 4.2.3

Now we are hoping to learn:

  1. Is their some method or utility to detect if the Xavier is receiving data on MIPI ports?

  2. Is their some method or utility to detect if the Xavier is receiving data on a particular MIPI port?
    -For example if we have several 1x4 MIPI Ports configured on the Xavier is their a command that can detect if a particular MIPI port is receiving data?

  1. Check the trace log.
    Jetson/l4t/Camera BringUp -

  2. Nope.

Hello ShaneCCC, Thank you for your response

We went to the Jetson/l4t/Camera BringUp - page and ran the following commands:

Boost clock for debug commands:
sudo su
echo 1 > /sys/kernel/debug/bpmp/debug/clk/vi/mrq_rate_locked
echo 1 > /sys/kernel/debug/bpmp/debug/clk/isp/mrq_rate_locked
echo 1 > /sys/kernel/debug/bpmp/debug/clk/nvcsi/mrq_rate_locked
cat /sys/kernel/debug/bpmp/debug/clk/vi/max_rate |tee /sys/kernel/debug/bpmp/debug/clk/vi/rate
cat /sys/kernel/debug/bpmp/debug/clk/isp/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/isp/rate
cat /sys/kernel/debug/bpmp/debug/clk/nvcsi/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/nvcsi/rate

Then we enabled more trace information with the commands:
echo 1 > /sys/kernel/debug/tracing/tracing_on
echo 30720 > /sys/kernel/debug/tracing/buffer_size_kb
echo 1 > /sys/kernel/debug/tracing/events/tegra_rtcpu/enable
echo 1 > /sys/kernel/debug/tracing/events/freertos/enable
echo 2 > /sys/kernel/debug/camrtc/log-level
echo 1 > /sys/kernel/debug/tracing/events/camera_common/enable
echo > /sys/kernel/debug/tracing/trace
cat /sys/kernel/debug/tracing/trace

Then we ran the command expecting that this command would generate the enabled trace information:
gst-launch-1.0 -q v4l2src device=/dev/gmsl/cam1 num-buffers=1 ! jpegenc ! filesink

We checked /var/log/messages before and after running the gst-launch-1.0 command, however we did not see trace information.

  1. Are we looking for the trace information in the correct place (/var/log/messages)?
  2. Are their any further steps necessary to enable/view the trace information?

Found it: cat /sys/kernel/debug/tracing/trace

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.