-xXx-
Newbie
 Offline
Posts: 1
|
 |
« on: June 11, 2008, 06:26:46 AM » |
|
Has anyone managed to get the device drivers to work under windows Vista?
I get an error everytime.
|
|
|
|
|
Logged
|
|
|
|
cgp208
Jr. Member
Offline
Posts: 19
|
|
« Reply #1 on: June 12, 2008, 02:00:20 PM » |
|
I see you were able to update your firmware. Did you use Vista? Could you explain how you did this? I can't get Vista or XP to work on mine.
|
|
|
|
|
Logged
|
|
|
|
|
MMuecke
|
|
« Reply #2 on: June 12, 2008, 09:14:22 PM » |
|
It will work in 32 bit Vista or XP.
|
|
|
|
|
Logged
|
|
|
|
|
Grimmace
|
|
« Reply #3 on: June 18, 2008, 08:30:59 PM » |
|
I couldn't get it to work in XP SP3 to save me life at this point, and Vistax64 is out. However, I got Vistax86 to work with no problems. It recognized to device after the sequence and I manually pointed it to the d/l folder with the drivers and it installed no problems. Loaded the Hex file and hit new program. A few seconds later new firmware (1.03) installed and working great. I am still going to see why XP did not work for me though.
|
|
|
|
|
Logged
|
|
|
|
|
MMuecke
|
|
« Reply #4 on: June 19, 2008, 08:27:37 AM » |
|
Thanks for the bit of good news!
|
|
|
|
|
Logged
|
|
|
|
falcontx
Jr. Member
Offline
Posts: 21
|
|
« Reply #5 on: June 20, 2008, 11:12:44 PM » |
|
I couldn't get it to work in XP SP3 to save me life at this point, and Vistax64 is out. However, I got Vistax86 to work with no problems. It recognized to device after the sequence and I manually pointed it to the d/l folder with the drivers and it installed no problems. Loaded the Hex file and hit new program. A few seconds later new firmware (1.03) installed and working great. I am still going to see why XP did not work for me though.
It wouldn't work on my desktop computer (XP Pro SP2), either. The hardware would be detected, but the wizard continually told me that the drivers were not correct. I tried everything I could think of, but it wouldn't work. Finally, I decided to try my laptop (also XP Pro SP2), and it worked fine on there. As such, I don't think that the provided .INF file is appropriately coded for all variants of Windows. |
|
|
|
|
Logged
|
|
|
|
|
....mr anders(son)
|
|
« Reply #6 on: June 21, 2008, 05:45:31 AM » |
|
I couldn't get it to work in XP SP3 to save me life at this point, and Vistax64 is out. However, I got Vistax86 to work with no problems. It recognized to device after the sequence and I manually pointed it to the d/l folder with the drivers and it installed no problems. Loaded the Hex file and hit new program. A few seconds later new firmware (1.03) installed and working great. I am still going to see why XP did not work for me though.
Have you come up with something? |
|
|
|
|
Logged
|
|
|
|
|
Grimmace
|
|
« Reply #7 on: June 21, 2008, 09:45:36 AM » |
|
It may be the that cybus driver. I updated a different device that also used the cybus.dll and after that my XP SP3 finally let the Bootloader work properly.
|
|
|
|
|
Logged
|
|
|
|
|
....mr anders(son)
|
|
« Reply #8 on: June 23, 2008, 11:00:29 AM » |
|
 something must happend now please Mike I have a 100$ useless gadget for now 
|
|
|
|
|
Logged
|
|
|
|
|
MMuecke
|
|
« Reply #9 on: June 27, 2008, 01:09:27 PM » |
|
something must happend now please Mike I have a 100$ useless gadget for now This is a particularly difficult problem that is taking longer than usual to understand and fix since I can't seem to recreate the problem here in the lab. You are in no danger of losing your $100. I stand behind my products 100%. We will get to the bottom of this. Please see the relevant thread for updated info. OR just check for new posts. The updates will show up in the list. Although I understand your situation, please realize that sprinkling the same desperate messages all over the boards does not help matters in the least. The forum is here to provide support and give us a common place to work out any problems in the products and give feedback as to how to make the products better. It's an important part of the development process. I humbly ask that you try to be a constructive part of this process and remember that posting here is a privilege. |
|
|
|
|
Logged
|
|
|
|
|
Grimmace
|
|
« Reply #10 on: June 28, 2008, 08:23:07 PM » |
|
Hey Mike how this bit of information helps
On both my XP SP3 and Vistax86 I can get the system to see the Pro. I can get it to load the drivers. However, it always comes back with code 10, device not ready. I cannot update to 1.06 for the moment. I'll see what else I can find out.
|
|
|
|
|
Logged
|
|
|
|
madmole
Newbie
Offline
Posts: 1
|
|
« Reply #11 on: June 29, 2008, 07:32:11 AM » |
|
I am tring to update my firmware in vista.
I can load the drivers and it shows up working in device manager as Schmartz BOOTLOADER
When I run the updater utility and press find bootloader I get the following Unhandled exception:
The find Hex file stays disabled
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at CyUSB.CyHidConstruct..ctor(HIDP_REPORT_TYPE rType, HIDP_CAPS hidCaps, Byte* PreparsedDta)
at CyUSB.CyHidDevice.Open(Byte dev)
at CyUSB.USBDeviceList.InitList(Byte DeviceMask)
at CyUSB.USBDeviceList..ctor(Byte DeviceMask)
at PS3IR_Firmware_Updater.Form1.Button14_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
PS3IR_Firmware_Updater
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/Barbara%20Bercik/Desktop/ps3ir/Update%20tool/PS3IR_Firmware_Updater.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
CyUSB
Assembly Version: 2.2005.35.2
Win32 Version: 2.2005.35.2
CodeBase: file:///C:/Users/Barbara%20Bercik/Desktop/ps3ir/Update%20tool/CyUSB.DLL
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
|
|
|
|
|
Logged
|
|
|
|
|
MMuecke
|
|
« Reply #12 on: July 01, 2008, 11:07:04 AM » |
|
I am tring to update my firmware in vista.
I can load the drivers and it shows up working in device manager as Schmartz BOOTLOADER
When I run the updater utility and press find bootloader I get the following Unhandled exception:
The find Hex file stays disabled
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at CyUSB.CyHidConstruct..ctor(HIDP_REPORT_TYPE rType, HIDP_CAPS hidCaps, Byte* PreparsedDta)
at CyUSB.CyHidDevice.Open(Byte dev)
at CyUSB.USBDeviceList.InitList(Byte DeviceMask)
at CyUSB.USBDeviceList..ctor(Byte DeviceMask)
at PS3IR_Firmware_Updater.Form1.Button14_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
PS3IR_Firmware_Updater
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/Barbara%20Bercik/Desktop/ps3ir/Update%20tool/PS3IR_Firmware_Updater.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
CyUSB
Assembly Version: 2.2005.35.2
Win32 Version: 2.2005.35.2
CodeBase: file:///C:/Users/Barbara%20Bercik/Desktop/ps3ir/Update%20tool/CyUSB.DLL
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Do you have the latest Microsoft .NET installed? Unfortunately, the download app supplied by the chip vendor is based on .NET and adds these complications. I'm working on a version that just uses the USB HID device interface. This is a pretty big task as Microsoft doesn't make things easy. It SHOULD be a slam dunk, but... not! |
|
|
|
|
Logged
|
|
|
|
Miwa
Newbie
Offline
Posts: 3
|
|
« Reply #13 on: July 03, 2008, 11:22:16 AM » |
|
So folks with Vista x64 are hosed until we can find a 32bit OS install somewhere?
|
|
|
|
|
Logged
|
|
|
|
|
Grimmace
|
|
« Reply #14 on: July 03, 2008, 11:49:07 AM » |
|
Unless there is a Cybus driver for 64 bit I do not see how. Except for a laptop and old machine I put together I use Vistax64 and I'm sure you know about the stringent driver requirements. I did not think these older Cybus drivers would work, but tried. They are not approved, so that may be it. Anyone know if they have a 64 bit version out there?
|
|
|
|
|
Logged
|
|
|
|
|
MMuecke
|
|
« Reply #15 on: July 03, 2008, 12:20:13 PM » |
|
Unless there is a Cybus driver for 64 bit I do not see how. Except for a laptop and old machine I put together I use Vistax64 and I'm sure you know about the stringent driver requirements. I did not think these older Cybus drivers would work, but tried. They are not approved, so that may be it. Anyone know if they have a 64 bit version out there?
Actually, Cypress is pretty good about moving to supporting x64 after initially dragging their feet. So, it may actually exist. In any case, a fully HID compliant application should work in all cases since it uses the built-in Windows OS USB driver. That's why I'm experimenting with that direction. |
|
|
|
|
Logged
|
|
|
|
|
Grimmace
|
|
« Reply #16 on: July 03, 2008, 07:35:39 PM » |
|
Sounds great Mike. One more question. Is there a way to reset the Pro? If we could, that may get us out of the cannot upgrade area. I am not afraid to open it up and would give it a try. Is there a reset or clear that might help?
|
|
|
|
|
Logged
|
|
|
|
|
MMuecke
|
|
« Reply #17 on: July 11, 2008, 03:22:31 PM » |
|
When you plug it in, it does a reset automatically. But reset is not the problem. That would be nice.
I have received several of the original units that had this problem and flashed them with V1.6. I then used the firmware updater to load each of the other versions and finally loaded back V1.6 in the end. Each version was loaded and worked flawlessly. So I am absolutely certain it was a problem with the firmware version that was flashed in a few of the earlier units. The firmware update module is flashed in permanantly here in the lab along with the latest downloadable firmware image. Then, the region of memory holding the firmware update module is protected from being overwritten by a field update. That way, no matter what you do, it can't get bricked by damaging the firmware update portion. However... I must have sent out units with a flawed firmware update module to begin with so, it was possible to brick those units. Doh!
|
|
|
|
|
Logged
|
|
|
|
|
Grimmace
|
|
« Reply #18 on: July 11, 2008, 03:48:11 PM » |
|
It would make sense, mine was in one of the first batches. Can we mail them back to get fixed? Or, if we are adventurous, could we just get the new chip and mail back the old chip to save on mailing?
|
|
|
|
|
Logged
|
|
|
|
higuy
Jr. Member
Offline
Posts: 16
|
|
« Reply #19 on: July 11, 2008, 06:38:02 PM » |
|
When you plug it in, it does a reset automatically. But reset is not the problem. That would be nice.
I have received several of the original units that had this problem and flashed them with V1.6. I then used the firmware updater to load each of the other versions and finally loaded back V1.6 in the end. Each version was loaded and worked flawlessly. So I am absolutely certain it was a problem with the firmware version that was flashed in a few of the earlier units. The firmware update module is flashed in permanantly here in the lab along with the latest downloadable firmware image. Then, the region of memory holding the firmware update module is protected from being overwritten by a field update. That way, no matter what you do, it can't get bricked by damaging the firmware update portion. However... I must have sent out units with a flawed firmware update module to begin with so, it was possible to brick those units. Doh!
Mike, mine shipped with v1.2. It works fine, but I'm thinking of updating to v1.6 just to test to see that my PC will allow me to successfully use the firmware update function. You said you loaded the other versions in your test. Will I be able to flash back to v1.2 if need be? I know you said v1.6 works great even after sony's 2.41 update, but I have had no problems with v1.2 either. I would only be updating to ensure a successful process when an advanced firmware update is necessary. |
|
|
|
|
Logged
|
|
|
|
|
