-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
imx585 datasheet or description #5
Comments
Hi @phodina. Thank for your help! |
@deecct If you need the application notes and software reference manual, I am happy to share privately. |
I have the full imx585 datasheet if you would like it. Why sony tries to keep this stuff top secret is beyond me. |
Hello! Currently I am working on a project based on Novatek and IMX678. I have a datasheet from Sony, but it does not contain register addressing and contains a link to external application notes. Therefore, I am unable to adapt the IMX678 sensor to Novatek SDK based on Linux. I was able to find a mention of the sensor I was interested in only in this thread. Could you please share the mentioned information about IMX678 (IMX585) in a private message? Perhaps there are also examples of driver implementations for this type of sensor? If suddenly you have similar information on IMX471 and IMX363, then this is absolutely magic! These two types of sensors are next in line for driver development for this evaluation board. If the other authors of the thread can also help, I would be very grateful! |
Hello! Can you share privately to me please? |
Vadim -- the datasheet I have is mostly about the hardware. It describes how to write to chip registers, there is only a reference to an excel file (IMX585_Standard_Register_Setting) that probably gives better description of where they are and what they do. I dont have the spreadsheet, likely essential for writing a driver. I dont know how exactly to get private contact with you you can text me at 561-762-3314 (USA). |
@KharlamovVadim. I don't have full register map for imx678, but I have found purposes and values of several most important registers related with operation modes of this sensor. I can share it with you. The implementation of driver is similar to another sony's sensors if you use it as v4l2 subdevice. P.S. I found an example of implementation here in github with "imx678" keyword. Maybe this imx678.c will help you. |
Thank you very much for your response! |
Thank you very much for your response! Yes, I use v4l2, all drivers are designed approximately the same, but the difference is in working with various Sony sensors, including in the register map. Could you please share the information you mentioned to my email [email protected]? |
Hello, I have a Raspberry Pi 4 and I will buy an IMX586 sensor. Can I use my Raspberry Pi 4 to power the IMX586 sensor? |
@phodina @notiska @robertimorrison Hello guys. I'm trying to create something similar but with another image sensor, IMX387. Do you guys have the real "full" datasheet and reference designs for that? I'm very glad if you could give me them in private. My use case is for FPGA on SLVS-EC. The ultimate purpose is actually for academics. I have searched everywhere and even made a personal inquiry to Sony Semi. and FRAMOS (we know it's Sony's official distributor), but the result is zero. |
Sam – I nearly as I can tell there are three levels of sony documentation for their image sensors:
1. The marketing wank that is widely available and says nothing particularly useful;
2. Datasheets that do provide pinouts, voltages and communication timings for almost-purely-hardware connections. These are available but slightly difficult to find;
3. A super-secret excel spreadsheet that sets out the sensor registers and their expected values for the sony sensor line. The spreadsheet is referenced in the hardware data sheet in (2) above, but I’ve never seen it and don’t know anyone who has a copy. (Will?)
Why sony regards the register spreadsheet as top secret-ultra-eyes-only for a product they presumably want to sell more of is beyond me. Its all very Japanese and very strange. Sony is not going to talk to you unless you are plausibly handing an order for 5-10k pieces and I wouldn’t even bother with Framos who are probably even less responsive than sony.
The sony sensor hardware is great; their business practices, not so much.
R. Morrison
From: sam ***@***.***>
Sent: Tuesday, January 14, 2025 7:58 AM
To: will127534/StarlightEye ***@***.***>
Cc: robertimorrison ***@***.***>; Mention ***@***.***>
Subject: Re: [will127534/StarlightEye] imx585 datasheet or description (Issue #5)
@phodina <https://github.com/phodina> @notiska <https://github.com/notiska> @robertimorrison <https://github.com/robertimorrison> Hello guys. I'm trying to create something similar but with another image sensor, IMX387. Do you guys have the real "full" datasheet and reference designs for that? I'm very glad if you could give me them in private. My use case is for FPGA on SLVS-EC. The ultimate purpose is actually for academics.
I have searched everywhere and even made a personal inquiry to Sony Semi. and FRAMOS (we know it's Sony's official distributor), but the result is zero.
—
Reply to this email directly, view it on GitHub <#5 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKAG7ACGSHRIG7HFRO45B32KUXZDAVCNFSM6AAAAABMZWZYQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJQGMZDSMZTGM> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/ABKAG7HJMYSUOAOK3NXOYTL2KUXZDA5CNFSM6AAAAABMZWZYQGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTU2MVE7K.gif> Message ID: ***@***.*** ***@***.***> >
|
Hello! You made great work and it helps a lot for creating driver for image sensor.
I try to connect imx678 sensor to rockchip rv1126. I am starting to work on linux kernel driver for this images sensor. The imx678 sensor is very similar to imx585, at least the have identical resolution and both based on startvis2. Could you privately share the datasheet for imx585? Or may be sections that related with registers, functional and operation descriptions?
The text was updated successfully, but these errors were encountered: