Go Down

Topic: connect new raspberry HQ camera  (Read 1 time) previous topic - next topic

eljuligallego

hello,
I would like to know if anyone have tried to connect the new HQ camera and I it was successful.

I don't know about the I2C configuration since there is no complete datasheet, the only info I found is this where there is several functions modes:

https://github.com/konradwilk/linux/blob/clearlinux.4.14/drivers/media/i2c/crlmodule/crl_imx477_master_configuration.h.

Thanks!.




eljuligallego

#1
Jun 28, 2020, 11:54 pm Last Edit: Jun 29, 2020, 10:02 am by eljuligallego
Anyone?,the MKRvidor forum seems a little bit dead...

For now tried to configure the I2C with the next code taken from purisame and edited to send the IMX477 configuration but no clock is present from mipi interface after program the FPGA...

The I2C address should be "1A" from the schematics:

https://www.raspberrypi.org/documentation/hardware/camera/schematics/rpi_SCH_HQcamera_1p0.pdf

But in the raspberry if I connect the camera and enable the I2C bus 0 I have the address 64...(also tried this address but nothing)

and the I2C speed assume 400Khz...

I'm using the configuration for 656_512 mode after send the I2C commands in onetime_init_regset_master

See code attached:


purisame

If you have an oscilloscope you could check the mipi clock lane to see if it's active. If there's no clock ,the register sets are bad. Otherwise, the clock could be too fast for the FPGA (fmax ~ 600-700 MHz I think) and you can manually lower the speed by adjusting the register sets based on the datasheet.

eljuligallego

#3
Jul 09, 2020, 05:41 pm Last Edit: Jul 09, 2020, 05:42 pm by eljuligallego
I don't have an oscilloscope.. but got signal-tap:

https://photos.app.goo.gl/A58quv4cJyPM6QGu8

what do you think?. Still I'm not sure if my I2C setup is correct.


Limba

From that picture it seems device didn't respond for that address. NACK for address is that there isn't any device with that address in bus.

For rare chips like some oled displays drivers have weird thing that you can configure these to not send NACK/ACK (I think these had SPI/I2C functionality in same IP. so they use one pin for input and one for output. in I2C these have to be connected but in design was disconnected)

Go Up