Load Firmware By Driver

9 posts / 0 new
Last post
bugg_tb
Load Firmware By Driver

Okay this one may be a step too far but I'll give it a shot.

The camera I'm using is crap due to the fact that it would appear the driver wants to pump firmware too it when its loaded so it would seem.

So......

On my windows client, if I plug the camera in, it is detected in the Device Manager but seems to get its knickers in a twist and when I load up some video software it complains about a bunch of stuff and basically doesn't work.

I have another option, where I can load the firmware directly on the linux host and have it load up the firmware via a udev rule, which seems to work, as when I check it with some linux video software I get stuff on the scree, but when I load the firmware via the host, whilst VirtualHere sees the device(it even knows what its called now) when I use it Winblows 8.1 fails to "detect" it and nothing appears in the Device Manager,

Now I don't for a second think anyone else has used a QHY5, but has anyone had any similar experiences loading firmware to devices?

Thanks

Tom

bugg_tb
Okay part of the reason was

Okay part of the reason was lack of the expansion pack on Virtualbox it would appear as now it loads into the windows client regardless of whether the firmware was enabled or not (something to do with USB2.0 I believe), still can't get it to communicate though annoyingly.

bugg_tb
Also, most of the time when

Also, most of the time when it gets upset, the whole Virtual Hub vanishes and does a reset or something although nothing appears to be logged on the server side.

Michael
What is your server platform?

What is your server platform? Pi? Beagle? etc...

bugg_tb
Just a debian box at the

Just a debian box at the moment

Michael
Could you grep the syslog and

Could you grep the syslog and dmesg and see what is says about the usb "disconnect" or similar messages around the time the camera is dropped. And also if you could update to 1.8.6 of the server as there was a bug fixed with connection dropping ...

bugg_tb
I have the latest client so I

I have the latest client so I assume thats 1.8.6 there doesn't seem to be an easy way of telling.

Ah its in the log, yes I have 1.8.6

Here is the output:

Jul 27 08:52:06 craptop vhusbdw64: >>> Starting v1.8.6 (Built: Jul 26 2014, 13:20:10)<<<
Jul 27 08:52:06 craptop vhusbdw64: Using default configuration /root/config.ini
Jul 27 08:52:06 craptop vhusbdw64: Serial:
Jul 27 08:52:06 craptop vhusbdw64: Server licensed to= max_devices=unlimited
Jul 27 08:52:06 craptop vhusbdw64: Using small URB's
Jul 27 08:52:06 craptop vhusbdw64: TCPServer bound to port 7575
Jul 27 08:52:07 craptop vhusbdw64: Successfully advertised service 'VirtualHere USB Sharing' over dns-sd (Bonjour/avahi)
Jul 27 08:52:10 craptop kernel: [149413.472272] usb 8-1: reset high-speed USB device number 47 using ehci_hcd
Jul 27 08:53:13 craptop vhusbdw64: Connection 1 successfully removed
Jul 27 08:53:35 craptop kernel: [149499.280347] usb 8-1: reset high-speed USB device number 47 using ehci_hcd
Jul 27 08:55:09 craptop vhusbdw64: Connection 2 successfully removed
Jul 27 08:55:11 craptop kernel: [149594.688272] usb 8-1: reset high-speed USB device number 47 using ehci_hcd

Regards

Tom

Michael
OK thats not showing much

OK thats not showing much unfortunately, it looks like it may not be compatible. If i could try connecting with my client remotely from my office i could try to trace the problem. Let me know via mail@virtualhere.com if its possible...

bugg_tb
Aye figured as much, a shame

Aye figured as much, a shame but due to the silly camera and its firmware I reckon. I found on virtualbox that it didn't like being connected via the USB pass through until I enabled USB2.0 and the EHCI stuff then it started working fine, all be it the error message on that issue was different to this time. This time it seems fine until you use it then it bails so I guess it just doesn't like working over the network.

I'm waiting for a new router cause of a change of ISP's once I have it I'll send you some details and you can have a prod around. If that fails I'll have to find a new guide camera.

Cheers
Tom

Log in or register to post comments