Playing with with the Infiray Tiny1-C core. Anyone else have experience?

[globoy]

I got a Tiny1-C core from Infiray (256x192 pixels, 25 FPS, SPI or parallel DVP interface) and made a break-out board to use it with the SPI interface (like the Pure Thermal breakout for Lepton).  I also get a little documentation and the STM32 demo software from Infiray and was able to get a simple demo up and running on my own dev board.  It's easy enough to figure out basic operation from their code and the documentation.  However the advanced features are not so well documented and not demonstrated in the code.  Things like calibration and dealing with the radiometric data.  In addition it appears some functionality is in a library for which they don't provide source for in the demo package.  Unfortunately for me the library is for a STM chip and I'm using an ESP32.

I am curious if anyone else has used this core - or one in its family - and has experience with the more advanced features.  It seems like a pretty nice little device judging from my initial images (using default settings).  Infiray seems like they want to be helpful but I suspect they're mostly used to dealing with domestic customers.

My goal is to see if I can extend my tCam stuff to work with this core.

[DaneLaw]

Interesting.. looking forward to seeing what your find going down this rabbit hole.
what cost did you have to shill up for one of these Tiny1-C based in the US?.
If I recall most of their Android units, are being handled like a basic UVC/webcam camera, so any basic third-party webcam UVC-android app..like fx USB UVC camera, or USB dual camera will give you the basic black cold/white hot thermal image in 26hz.. so all these basic features like motion detection = recording..IP camera feed etc.. is straightforward.

[globoy]

I bought it from Infiray.  With shipping and wire transfer fees I think I paid about $300USD.  I am interested to see if this can be used in a product so I signed agreements with them, etc.

@DaneLaw ~ yeah, I know that most modules are used in devices that appear USB UVC class cameras.  I'm interested in interfacing at a lower level to leverage work I've already done with my other devices whose primary goal is to make radiometric data available to people (as opposed to presenting as a traditional thermal imaging camera, of which there are plenty).  I think you are right though, there will be a bit of a rabbit hole with this sensor...  Lots of details to fathom.  I'm actually looking at Flir's documentation with respect now, LOL.

[globoy]

I signed a sales contract, not an NDA.  It covered the usual payment stuff.  It also prohibits me from violating the Export Administration Rules (prohibiting selling products to the usual list of countries or "Foreign Sanctions Evaders List") - or - military/police (which worries me as how can one prevent that?).  However I would want to check with Infiray before sharing any of the documentation they sent me as the contract mentions not sharing information that could be "reasonably classified as confidential" without permission.  It doesn't seem like anything they sent me is confidential (not marked as such) but I hope you can understand that I am careful.  I don't want to anger them.

That being said, the documentation I got was essentially the same that has already been shared elsewhere in this forum - just with the google Chinese-English translation done to some of it (lol, but not all!).  Which is also why I'm interested in talking to anyone else who has low level experience with these modules.  Lots of important stuff is undocumented.  For example power-on reset sequencing.  I have a hardware reset manager on my board which should follow the one timing diagram I got but I still have issues reliably getting an initial stream after power-on.  Do I need to do wait some time for their embedded controller to boot?  Do I need to do some init and then wait?  Not clear.

Also, as an aside for DaneLaw:  The dev kit has a Realtek camera controller chip designed to interface with DVP compatible camera modules and turn them into a USB UVC device.  There's an I2C flash eeprom on-board which I assume contains the specific CCI initialization for the camera.  However this board didn't work for me (installed Windows app, driver and connected to the USB UVC class device but no bueno).  I was afraid I'd damaged the module before even using it.  It was only when I hooked it up to my dev board and wrote some code that I got it working.

[memet arif karakaşoğlu]

Hi.   Where can I find the stm32 code?