Activity
From 05/05/2026 to 06/03/2026
06/03/2026
- NZ 08:03 PM Software Development: RE: Camera driver development
- Let me know if adding the pixel readout info to your XML made a difference.
Thanks,
Noah - NO 05:04 PM Software Development: RE: Camera driver development
- The other side is a long-wave infrared camera with a 16-bit parallel output. I have this setup working on an iMX.8MP SOM, so I know exactly what registers need to be written.
- NZ 04:39 PM Software Development: RE: Camera driver development
- Hi Nathan,
I saw you are using a tc358746 bridge IC. What is on the other side of it?
There is existing support for lt6911gxc and lt7911uxc bridge ICs, but they are for HDMI or DP to MIPI so I'm not sure if that is helpful.
Than... - NZ 02:32 PM Software Development: RE: Camera driver development
- Hi Nathan,
When I did this I used tag r1.0_00095.0 for "Qualcomm_Linux.SPF.1.0|AP|Standard|OEM|NM_QIMPSDK", repo url https://qpm-git.qualcomm.com/home2/git/qualcomm/qualcomm-linux-spf-1-0_ap_standard_oem_nm-qimpsdk.git. It contains r1...
06/02/2026
- NO 11:25 PM Software Development: RE: Camera driver development
- Here's where I've gotten to. The sensor is probed successfully but there are a bunch of other errors that don't mean anything to me.
- NO 10:17 PM Software Development: RE: Camera driver development
- After rolling @chicdk@ and @chicdk-kt@ back to @r1.0_00092.0@, I am able to successfully probe my sensor. Onward!
- NO 05:10 PM Software Development: RE: Camera driver development
- Nathan Olson wrote in message#7341:
> My current theory is that there is a problem with using the prebuilt camx and building chicdk from source (version mismatch?). I'm currently attempting to build camx from source as well but no luc... - NO 04:35 PM Software Development: RE: Camera driver development
- Noah Zins wrote in message#7338:
> Did you see any different behavior with the power fields reinstated?
I'm making some progress, but still not seeing an attempt to probe my sensor. I am seeing attempts to probe imx577, imx415, and... - NO 04:12 PM Software Development: RE: Camera driver development
- Hi Noah, I'm trying to match the version you used for your camx modifications, but I can't find @r1.0_00095.0@. Any clues? (and where does @r1.0_00376@ fit in?)
- NZ 03:48 PM Software Development: RE: Camera driver development
- Hi Nathan,
Did you see any different behavior with the power fields reinstated?
I noticed your sensor XML has no pixel/resolution information which I would think is necessary.
Thanks,
Noah - NZ 03:55 PM Software Development: RE: Streaming from 5 cameras simultaneously
- It should be possible with the hardware, but currently our BSP uses Qualcomm Linux 1.5 that does not support it. Upgrading to version 1.8 is supposed to be the fix, but I noticed the release notes stated issues with multicamera streaming...
05/29/2026
- What is the status of streaming from 5 cameras simultaneously? Is this possible with software mods, or are there hardware limitations that prevent this?
05/27/2026
- NO 08:50 PM Software Development: RE: Camera driver development
- I removed the power-related fields because my camera is powered by an always-on supply, and I was trying to simplify things as much as possible. I'll try adding that stuff back, in particular @power-domains@ seems like it might be import...
- NZ 08:43 PM Software Development: RE: Camera driver development
- Hi Nathan,
I too have noticed the probing of sensors 0-12, I have not looked into it but we see this same behavior. I expect your sensor to be 0.
If your sensor XML has the correct I2C address, I2C speed, sensor ID, and sensor ID r... - NO 01:06 AM Software Development: RE: Camera driver development
- Thanks, Noah.
I'm trying to bring up a new sensor, and no luck so far. To simplify things, I've removed all camera modules except mine, and removed all multicamera configs except mine, which has a single camera at cameraId 0, slot 0, ...
05/22/2026
- NZ 03:30 PM Software Development: RE: Camera driver development
- Hi Nathan,
It is posted here: https://support.criticallink.com/redmine/projects/mitysom_qc6490/wiki/Camera_Config
Please don't hesitate to reach out if you have further questions!
Thanks,
Noah
05/20/2026
- NZ 09:15 PM Software Development: RE: Camera driver development
- Hi Nathan,
We used the r1.0_00095.0 release of Qualcomm_Linux.SPF.1.0|AP|Standard|OEM|NM_QIMPSDK for our firmware development. It contains the r1.0_00376 release of QCM6490.LE.1.0 where the meta-qcom-extras layer resides. These versio...
05/18/2026
- WE 12:21 PM PCB Development: RE: USB3 Data Port with External PD Control
- Good morning David, I hope you had a good weekend!
I'm not super familiar with the kernel framework but I would think that it would get both the "role" the processor needs to be (either host or device) as well as the "orientation" of ...
05/15/2026
- DC 09:28 PM PCB Development: RE: USB3 Data Port with External PD Control
- Hello William,
Thanks for your response!
Unfortunately we're locked into having the MUX/PD on the baseboard, so we can't continue down the easy path.
But I've checked and confirmed that the PD controller we are using exposes ... - WE 07:45 PM PCB Development: RE: USB3 Data Port with External PD Control
- Hello David,
After thinking about this, here are my thoughts.
The MitySOM-QC natively supports USB 3.0 signal MUXing as well as USB PD. The simplest path, if you're not committed to the external PD/MUX, is to let the SOM handle bo... - Do you have any resources to help with camera driver development? I've found Qualcomm's "Linux Build Guide", "Linux Camera Guide", and "Linux Camera Guide - Addendum". I'm now working on building the camera and sensor files from source.
...
05/14/2026
- GG 08:53 PM Software Development: RE: UART bringup
- Hi Nathan,
I am able to reproduce and it seems the issue is not with uart14, but rather with trying to instantiate more than 4 UARTs.
I have not yet found anything in Qualcomm's docs that explains such a limitation.
I will re... - GG 03:13 AM Software Development: RE: UART bringup
- Hi Nathan,
Nothing immediately stands out as to why you're having this issue (I have a project where I have success using this QUP for spi14 without issue).
I will try and reproduce your issue on my end and get back to you.
T...
05/13/2026
- Hey Team,
I'm working on porting a hardware design for a custom carrier board to leverage the MitySOM platform. This carrier board owns the USB3 port's CC lines for PD negotiation and cable orientation detection. We don't need Displa...
05/08/2026
- I've got a device tree building for my carrier board, and a custom QUP configuration working! However, only 4 out of 5 of my UARTs are working. uart14 returns an error when it is probed. Here's the relevant output from dmesg:
05/05/2026
- NO 06:58 PM Software Development: RE: Processor rebooting
- Thanks Greg. I'll leave USB1 enabled for now as I work on bringing up other peripherals. I'd love to eventually figure out how to disable it, especially if that can result in any power savings.
- GG 06:34 PM Software Development: RE: Processor rebooting
- Hi Nathan,
Thank you for all the information. We have worked with another design that also did not connect the SS lines for this USB and they have not had to make the same changes in the DTS (e.g. having usb_1_qmpphy enabled is not a...