If you have no datasheet for the sensor, then you're going to be a bit stuck.
I assume you've already contacted Melexis via the "Request datasheet for MLX75027" link at the bottom of https://www.melexis.com/en/product/MLX7 ... -3D-camera
A websearch has turned up https://www1.futureelectronics.com/doc/ ... 200-TR.pdf.
All the MIPI CSI2 and I2C electrical level stuff is standard. CSI2 is going to deliver 12 bit/pixel data, and using 4 data lanes by default.
Section 6 is dealing with what your driver needs to configure via I2C. If you believe the first bit, then just sending "0x10 0x00 0x00" and "0x10 0x01 0x01" should be enough to get it streaming, however that doesn't define any of the image parameters - it'll all be just off the default values.
If you took the imx290 sensor driver from the kernel and removed all cci_*write calls, adding justrecompile the kernel, and then use "dtoverlay=imx290,4lane,media-controller=0" in /boot/firmware/config.txt, then in theory the driver should load and be configured for 4 lane 12bpp operation. "v4l2-ctl --stream-mmap=3 --stream-count=1000 --stream-to=raw.bin" will capture the incoming data to raw.bin. You may want to select the option to unpack the data into the least significant 12bits of 16bit words, using "v4l2-ctl -v pixelformat=RG12".
I don't know what the situation is with this project, but $3000 can be expended very quickly in your time, particularly if you need to design the support hardware for the raw sensor.
I also note that Mouser say "NRND: Not recommended for new designs." against this part. Talking to Melexis would therefore seem an essential step before investing significant amounts of time or money into that sensor.
The web search also turned up this app note - https://media.melexis.com/-/media/files ... elexis.pdf
I assume you've already contacted Melexis via the "Request datasheet for MLX75027" link at the bottom of https://www.melexis.com/en/product/MLX7 ... -3D-camera
A websearch has turned up https://www1.futureelectronics.com/doc/ ... 200-TR.pdf.
All the MIPI CSI2 and I2C electrical level stuff is standard. CSI2 is going to deliver 12 bit/pixel data, and using 4 data lanes by default.
Section 6 is dealing with what your driver needs to configure via I2C. If you believe the first bit, then just sending "0x10 0x00 0x00" and "0x10 0x01 0x01" should be enough to get it streaming, however that doesn't define any of the image parameters - it'll all be just off the default values.
If you took the imx290 sensor driver from the kernel and removed all cci_*write calls, adding just
Code:
cci_write(imx290->regmap, CCI_REG8(0x1000), 0x00, &ret);usleep_range(12000, 15000);cci_write(imx290->regmap, CCI_REG8(0x1001), 0x01, &ret);I don't know what the situation is with this project, but $3000 can be expended very quickly in your time, particularly if you need to design the support hardware for the raw sensor.
I also note that Mouser say "NRND: Not recommended for new designs." against this part. Talking to Melexis would therefore seem an essential step before investing significant amounts of time or money into that sensor.
The web search also turned up this app note - https://media.melexis.com/-/media/files ... elexis.pdf
Statistics: Posted by 6by9 — Mon Feb 26, 2024 3:12 pm