tinyCLUNX33
System on Module with CrosslinkU-NX
|
This app note covers various steps involved in customizing the tinyCLUNX platform to your application as well as FAQ's.
Going through each step is not mandatory but only informative, and reaching tinyVision.ai on the chat server or by email is more than welcome.
Parts of our codebase are provided by invitation only via a private Github repository. Please request access by sending email to sales.nosp@m.@tin.nosp@m.yvisi.nosp@m.on.a.nosp@m.i. We also provide support via Discord by setting up a private channel for Enginee-Engineer discussions.
Please provide Github and Discord ID's of staff who will be working on the firmware and RTL.
You will receive access to the following repos:
xyz
sensor. The answer is a most probable yes. If it has a MIPI interface that is capable of a maximum of 1.2Gbps and up to 4 lanee, the FPGA can interface with it. I2C and/or SPI interfaces can be supported, we provide the I2C sample.IMX219
or other sensors there as a baseline for your sensor in the tinyclunx33_zephyr_example
. It helps to have either a linux driver or the datasheets for reference.YUV422
, RAW10
etc.) as well as whether the MIPI clock is going to use a continuous clock or a discontinuous clock.Number of Rx lanes
, Rx Line rate
and D-PHY clock mode
. The deskew calibration detection is recommended to be turned on. The GUI will give you the Byte Clock Frequency
. Note this down, you will need it for the Byte2Pixel converter and PLL customization. Other settings can be modified ass needed but not necesary.Number of Rx lanes
, Byte Clock Frequency
. You should now select a suitable pixel clock frequency that exceeds the minimum required.Pixel clock
and Byte Clock
frequencies. Make sure the error in the byte clock is as low as possible, ideally zero. Turn on the fractional PLL if required.NOTE: The design must be timing clean!