-
Notifications
You must be signed in to change notification settings - Fork 11
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
hi704 sensor #9
Comments
I have 2 boards:
I draw a pinout of HI704 connector from V720, it uses i2c1 from bk7252. Dump: https://gist.github.com/Apache02/089760cbc51f2c4add65b92265d07e27#file-hi704_i2c_dump_experiment-txt |
https://wiki.bekencorp.com/pages/viewpage.action?pageId=23692262 Maybe this can help you. Also, if you havent logs at uart2 - i2c2 is working... |
@Alvid81 thx for bekencorp/armino. Implementation of cameras looks useful.
I can't open https://wiki.bekencorp.com/pages/viewpage.action?pageId=23692262 . Chinese server blocks my ip and vpn's ip. |
Me too, maybe some tech issues. |
BK7256 looks seems to BK7252, but bk7252 is ARM and BK7256 is RISC-V.. although the principles are general to both. |
I'm sure that 2 of my cameras use uses sensor HYNIX hi704 (i've test 2 sensors on one camera - both works). Current source code don't have hi704 support. As I see the only thing required is i2c initialization. So i tried to monitor i2c pins connected to camera using https://github.com/jjsch-dev/pico_i2c_sniffer . I tried this couple times and result always the same:
https://gist.github.com/Apache02/089760cbc51f2c4add65b92265d07e27#file-hi704_i2c_dump-txt
i2c address multiplied by 2 in this log.
hi704 i2c address is 0x30
init_table: https://gist.github.com/Apache02/089760cbc51f2c4add65b92265d07e27#file-camera_intf-h
I tried to use it, but according to sniffer somthing broken with i2c1 driver.
The text was updated successfully, but these errors were encountered: