On Sat, Mar 29, 2014 at 4:34 PM, Ivan Kozic <[email protected]> wrote: > Hey getting closer :) There's still an issue with the LDO (I don't like this > debugfs issue) - check if you actually get sensor voltage first. If no, > there's still something funny going on with AXP, so triple-check the Fex > file for LDO init. Check with a multimeter whether you really get 2V8. > Ok, so the I2C stuff is located in the driver itself - just look at the > functions in the mt9d112 driver file (something like sensor_read and > sensor_write) - there you should see if the sensor address is correct. Also > bear in mind which I2C bus is used for sensor in the fex file for your > sensor - mine is twi0, but it can easily be that you've connected the sensor > to something else (on Olinuxino twi2 was also close to route for instance so > I made assembly options on my interface to either use TWI0 or TWI2, as I > didn't really know what is implemented in the kernel and what's not at the > time...). > If you're using level converters for I2C, check them as well, especially > OE's.
Are you planning on feeding this into the h.264 compression engine? That's where I got stuck with not enough compression being done - output stream is too many MB/s. > > > On Fri, Mar 28, 2014 at 11:47 PM, <[email protected]> wrote: >> >> пятница, 28 марта 2014 г., 11:41:49 UTC+2 пользователь Ivan Kozic написал: >> > Hi, >> > >> > You haven't given much info about this - take care with Cubieboard 1 & 2 >> > - as far as I can remember they don't have PIXCLK routed for CSI0 port, so >> > it's completely unusable. You should use CSI1. >> > >> > Regarding the seg fault - not sure how you connected the power supplies >> > to the sensor, but these regulator_enable are for AXP IC - if you connected >> > the sensor to the AXP, you need to use them I guess. I for instance have >> > just connected the sensor supply to fixed LDO's coming from either 3V3 or >> > 5V, which is always alive, so I don't really need them, but nevertheless >> > they aren't commented out in my driver (WiP, so still dirty) and they are >> > working, so maybe the culprit is something else. >> > >> > You didn't say which test application or given any snippets, but if it's >> > the one coming with the driver (app_test_ok or something similar), by >> > Rockie >> > Cheng (this name always amuses me :) ), then it's full of bugs and issues >> > and you should carefully go through every step and clean the crap code out >> > (a lot of it is crap). Better yet, write a much simpler V4L2 test app >> > yourself. >> > >> > Things that also pop is the old kernel (I'm using 3.4.75 and this is >> > already like couple of months old) and this Linaro rootfs (don't know about >> > this - is it fully supported on Cubies?). You should probably use newer >> > kernel just to be sure that something stupid is not breaking. >> > >> > Also take care with drivers - the one for OV5640 is very badly written >> > and full of bugs and I don't think that the supplied sensor settings are >> > usable for anyone (they are all like 3.75 and 7.5 fps, most of them just >> > wrong). Also sun4i_csi driver is bad (you can read some of the issues on >> > this thread, but there are other threads as well). So mostly for a >> > functional system all this needs to be cleaned and rewritten. >> > >> > On Thursday, March 27, 2014 11:54:08 PM UTC+1, [email protected] >> > wrote:Hello guys, >> > I want to get camera module mt9d112 working on cubieboard a10 over >> > CSI. I am using ubuntu linaro with kernel version 3.4.61. Test application >> > crashes with seg fault on (regulator_enable+0x4/0x1f8) from [<bf010138>] >> > (sensor_power+0x190/0x398 [mt9d112]). Could you please help me to figure >> > out >> > where the issue is? How can I debug kernel module? >> >> You are right for testing I using app_test_ok. This test application is >> full of mistakes but for now I did not even successfuly initialized camera >> module. >> I have connected VCC of camera module to CSI1_IO_2V8 pin on the board and >> other pins to the rest of CSI ports. The CSI1_IO_2V8 is actually LDO4 of >> AXP20 and I finally found in AllWinner documentation that string "axp_hdmi" >> should be used in script.fex instead of axp_p11 as described in tutorial. By >> the way the tutorial from cubieboard is full of such mistakes. So, when I >> change settings string to axp_hdmi I get new portion of errors: >> [ 383.721765] [CSI]Welcome to CSI driver >> [ 383.723657] [CSI]csi_init >> [ 383.934525] [CSI]registered sub device,input_num = 0 >> [ 383.939747] axp20_ldo4: Failed to create debugfs directory >> [ 384.003476] [CSI]V4L2 device registered as video1 >> [ 385.171443] incomplete xfer (0x20) >> [ 385.176430] [CSI_ERR][MT9D112]Error -70 on register write >> [ 385.181925] [CSI_ERR][MT9D112]sensor_read err at sensor_detect! >> [ 385.194199] [CSI_ERR][MT9D112]chip found is not an target chip. >> [ 385.199069] [CSI_ERR]sensor initial error when csi open! >> As I understand these error means that I2C communication is failed. The >> I2C address might by incorrect. But what is incomplete xfer (0x20) ? >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "linux-sunxi" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/linux-sunxi/ijitRnbl8c8/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> >> For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "linux-sunxi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- Jon Smirl [email protected] -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
