MT4017 PIXER LED aka 0c45:6242 problem and fix

56 views
Skip to first unread message

Kir Kolyshkin

unread,
Nov 23, 2008, 7:23:28 PM11/23/08
to micr...@googlegroups.com
Hi,

First of all thank you all for your work on microdia!

Executive summary: repeating microdia_6242_start_stream() twice made my
webcam working. How do I debug it to fix it in a more proper manner?

Gory details follow.

I am a semi-happy owner of Media-Tech MT4017 a.k.a. PIXER LED webcam [1].

This is how I see it in lsusb output:
Bus 004 Device 005: ID 0c45:6242 Microdia

Apparently this is SN9C201 bridge + MI1310 image sensor, as described in [2].

I am using driver from the latest git (top commit is 8eaf625). What I
see with test mplayer command is green screen with some minor
light-green flickering and errors from mplayer (let me know if you need more info, logs etc.).

I found this [3] thread which describes a problem very similar to mine,
and decided to try implementing the similar workaround.

This is what I did (the patch is also attached):

@@ -1044,6 +1044,8 @@ int dev_microdia_start_stream(struct usb_microdia *dev)
*/
int microdia_6242_start_stream(struct usb_microdia *dev)
{
+ int xxx;
+ for (xxx = 0; xxx < 2; xxx++) {
int i = -1;
__u8 buf[48];

@@ -1472,6 +1474,7 @@ int microdia_6242_start_stream(struct usb_microdia *dev)
buf[0] = 0x03;
usb_microdia_control_write(dev, 0x1061, buf, 1);

+ }
return 0;
}


Apparently that worked -- I am now seeing something with mplayer (way
too dark but visible).

Could anybody suggest me how to debug the init sequence to fix in in a
less hackish way?

[1] http://www.media-tech.eu/page.php?do=details&lang=uk&pid=1283&kid=15
[2] http://groups.google.com/group/microdia/web/0c45-6242
[3] http://www.mail-archive.com/micr...@googlegroups.com/msg00001.html

fix-6242-init.patch

GWater

unread,
Nov 24, 2008, 3:43:58 AM11/24/08
to micr...@googlegroups.com
Hopefully you won't have to fix this at all.

Please check if the error still shows up in the development branch:
$ git checkout --track -b development origin/development

GWater


Kir Kolyshkin schrieb:

> --~--~---------~--~----~------------~-------~--~----~
> Lets make microdia webcams plug'n play, (currently plug'n pray)
> To post to this group, send email to micr...@googlegroups.com
> Visit us online https://groups.google.com/group/microdia
> -~----------~----~----~----~------~----~------~--~---
>
>

signature.asc

k001

unread,
Nov 25, 2008, 8:43:21 PM11/25/08
to microdia
Right, development branch works fine for me, thanks!

Except for one thing -- loaded microdia module breaks suspend-to-ram :
(
Do you want me to provide some kind of debug info?
> > [1]http://www.media-tech.eu/page.php?do=details〈=uk&pid=1283&kid=15
>  signature.asc
> < 1KViewDownload

GWater

unread,
Nov 26, 2008, 3:23:51 AM11/26/08
to micr...@googlegroups.com
If you use pm-tools for suspend2ram please read their README. You can
automatically unload microdia before suspension and rreload after it.

GWater


k001 schrieb:

signature.asc

Knysliux001

unread,
Dec 13, 2008, 9:32:20 AM12/13/08
to microdia
Hello,

I have 0C45:6242 and I was really happy when test drivers worked about
2 months ago on Ubuntu 8.04. But 8.10 uses 2.6.27-9-generic kernel and
all I can get now is totally black or random color static screen and
led indicating activity.
Some logs may be valuable for developers.


When connected it's all OK (dmesg output)
[ 5502.392043] usb 1-3: new high speed USB device using ehci_hcd and
address 20
[ 5502.563142] usb 1-3: configuration #1 chosen from 1 choice
[ 5502.563762] microdia: Microdia USB 2.0 Webcam - 0C45:6242 plugged-
in.
[ 5502.563773] microdia: Detected SN9C20X Bridge
[ 5502.603165] microdia: Detected MT9M111 Sensor
[ 5502.644897] microdia: Microdia USB 2.0 Webcam is now controlling
video device /dev/video0

However when trying open the device logs are flooded with messages:
[ 5614.729992] microdia: Iso frame 0 of USB has error -18
[ 5614.730008] microdia: Iso frame 1 of USB has error -18
[ 5614.730011] microdia: Iso frame 2 of USB has error -18
[ 5614.730014] microdia: Iso frame 3 of USB has error -18
[ 5614.730017] microdia: Iso frame 4 of USB has error -18
[ 5614.730020] microdia: Iso frame 5 of USB has error -18
[ 5614.730023] microdia: Iso frame 6 of USB has error -18
[ 5614.730026] microdia: Iso frame 7 of USB has error -18
[ 5614.730029] microdia: Iso frame 8 of USB has error -18
[ 5614.730032] microdia: Iso frame 9 of USB has error -18
[ 5614.730042] microdia: Iso frame 0 of USB has error -18
[ 5614.730045] microdia: Iso frame 1 of USB has error -18
[ 5614.730048] microdia: Iso frame 2 of USB has error -18
[ 5614.730051] microdia: Iso frame 3 of USB has error -18
[ 5614.730054] microdia: Iso frame 4 of USB has error -18
[ 5614.730057] microdia: Iso frame 5 of USB has error -18
[ 5614.730060] microdia: Iso frame 6 of USB has error -18
[ 5614.730063] microdia: Iso frame 7 of USB has error -18
[ 5614.730066] microdia: Iso frame 8 of USB has error -18
[ 5614.730068] microdia: Iso frame 9 of USB has error -18
[ 5614.730722] microdia: Iso frame 0 of USB has error -18
[ 5614.730726] microdia: Iso frame 1 of USB has error -18
[ 5614.730729] microdia: Iso frame 2 of USB has error -18
[ 5616.064053] usb 1-5: reset high speed USB device using ehci_hcd and
address 19
and further with
[ 5616.316070] usb 1-5: reset high speed USB device using ehci_hcd and
address 19

webcam complains:


grabber config:
size 320x240 [none]
input (null), norm (null), jpeg quality 75
rotate=0, top=0, left=0, bottom=240, right=320
libv4lconvert: Error decompressing JPEG: unknown huffman code:
0000ffd9
libv4lconvert: Error decompressing JPEG: fill_nbits error: need 1 more
bits
libv4lconvert: Error decompressing JPEG: fill_nbits error: need 2 more
bits
libv4lconvert: Error decompressing JPEG: fill_nbits error: need 3 more
bits
libv4lconvert: Error decompressing JPEG: fill_nbits error: need 6 more
bits
libv4lconvert: Error decompressing JPEG: unknown huffman code:
0000ffd9
libv4lconvert: Error decompressing JPEG: fill_nbits error: need 2 more
bits

Hope this helps :)
>  signature.asc
> < 1KŽiūrėtiAtsisiųsti
Reply all
Reply to author
Forward
0 new messages