tinyCLUNX33
System on Module with CrosslinkU-NX
Loading...
Searching...
No Matches
Frequently Asked Questions

This app note covers various high level FAQ's about the capabilities of the platform as well as typical applications etc.

You may contact us via the chat server or by email is more than welcome.

High Level FAQ's

How to control the I2C for my sensor: Here are a couple of ways to do this:

  1. Once the driver is properly written, the enumeration process will expose the exposure, gain etc. to the host UVC stack. UVC control changes now flow through to the I2C automagically.
  2. Many of your sensor controls may not map directly to what UVC offers. In such a case, you can write your own protocol over a serial port. To do this: a. Use the exported Zephyr shell over the USB link and write your own commands there so that the application can talk to the Zephyr shell over a serial port. b. Export a dedicated serial port over the USB link and host your commands/applications over this link.

What sensors can you support?

We can support any sensor (cameras, thermal, vibration, IMU, audio etc.) that has the following interfaces:

  • 1/2/4 lane MIPI sensors with up to 1.2Gbps MIPI data rate
  • LVDS, SPI, DVP sensor interfaces. IO pads on the FPGA are limited to 1.8V and an external translator is required to support 3.3V IO.
  • We bring out 1 bank of IO on the Compute module and 2 banks of IO on the Connectivity module.
    • Each bank must have the same voltage IO.
    • If you use MIPI, that bank voltage shall be set to 1.2V.
  • A maximum of 27 pins on the Compute and 37 pins on the Connectivity module can be used to interface to the sensor, excluding the I2C.

Unsupported sensor interfaces

  • We use a soft MIPI which is limited to 1.2Gbps per link. Any data stream that requires a higher data rate than this cannot be supported. Suggest using a 4 Lane setup in this case.
  • MIPI C-PHY: We do not support the new MIPI CPHY standard since the FPGA IO cells do not have this capability.

What is the maximum frame rate you can support?

The data path does not use the RISCV processor. As a result, there is no overhead for an increased frame rate. We have measured test patterns at well over 1.5kHz for smaller sizes. The bridge can sustain a data rate of 3.4Gbps for a single stream. The frame rate is not a consideration.