search

controlbox2 / siren-of-shame

Automatically exported from code.google.com/p/siren-of-shame
0 stars 0 forks source link

Firmware Upgrade Fails Through VMWare #11

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Run siren of shame firmware upgrade through VMWare

What is the expected output? What do you see instead?

2012-01-20 09:20:26,801 [4] ERROR SirenOfShame.SirenFirmwareUpgrade [(null)] - 
Error performing upgrade
System.Exception: Timeout waiting for device
   at TeensyHidBootloaderLib.TeensyDevice..ctor(Boolean waitForDeviceToAppear, Int32 blockSize, TimeSpan timeOut)
   at TeensyHidBootloaderLib.TeensyHidBootloaderProgrammer.Program(Stream hexFileStream, Boolean waitForDeviceToAppear, Boolean rebootAfterProgramming, TimeSpan timeOut, Action`1 progressFunc)
   at SirenOfShame.Lib.Device.SirenOfShameDevice.PerformFirmwareUpgrade(Stream hexFileStream, Action`1 progressFunc)
   at SirenOfShame.SirenFirmwareUpgrade.PerformUpgrade()
   at SirenOfShame.SirenFirmwareUpgrade.DoUpgradeThread()
2012-01-20 09:20:26,815 [1] INFO  SirenOfShame.Lib.ExceptionMessageBox [(null)] 
- OperatingSystem: Microsoft Windows NT 6.1.7601 Service Pack 1
2012-01-20 09:20:26,815 [1] INFO  SirenOfShame.Lib.ExceptionMessageBox [(null)] 
- DotNetVersion: 4.0.30319.239
2012-01-20 09:20:26,815 [1] INFO  SirenOfShame.Lib.ExceptionMessageBox [(null)] 
- SosVersion: 1.0.0.0
2012-01-20 09:20:26,815 [1] INFO  SirenOfShame.Lib.ExceptionMessageBox [(null)] 
- DeviceConnected: True
2012-01-20 09:20:26,815 [1] INFO  SirenOfShame.Lib.ExceptionMessageBox [(null)] 
- FirmwareVersion: 1
2012-01-20 09:20:26,815 [1] INFO  SirenOfShame.Lib.ExceptionMessageBox [(null)] 
- HardwareVersion: 1
2012-01-20 09:20:26,815 [1] INFO  SirenOfShame.Lib.ExceptionMessageBox [(null)] 
- HardwareType: Standard
2012-01-20 09:20:26,815 [1] INFO  SirenOfShame.Lib.ExceptionMessageBox [(null)] 
- ErrorDate: 20-01-2012 09:20:26
2012-01-20 09:20:26,815 [1] INFO  SirenOfShame.Lib.ExceptionMessageBox [(null)] 
- ErrorMessage: Timeout waiting for device
2012-01-20 09:20:26,815 [1] INFO  SirenOfShame.Lib.ExceptionMessageBox [(null)] 
- StackTrace: System.Exception: Timeout waiting for device
   at TeensyHidBootloaderLib.TeensyDevice..ctor(Boolean waitForDeviceToAppear, Int32 blockSize, TimeSpan timeOut)
   at TeensyHidBootloaderLib.TeensyHidBootloaderProgrammer.Program(Stream hexFileStream, Boolean waitForDeviceToAppear, Boolean rebootAfterProgramming, TimeSpan timeOut, Action`1 progressFunc)
   at SirenOfShame.Lib.Device.SirenOfShameDevice.PerformFirmwareUpgrade(Stream hexFileStream, Action`1 progressFunc)
   at SirenOfShame.SirenFirmwareUpgrade.PerformUpgrade()
   at SirenOfShame.SirenFirmwareUpgrade.DoUpgradeThread()

Please use labels and text to provide additional information.

Original issue reported on code.google.com by lpric...@gmail.com on 20 Jan 2012 at 10:10

GoogleCodeExporter commented 9 years ago 
My team is having the same issue.  The software seems to working and we are 
notified of when the build is running, working and breaking; however, the USB 
Siren will not fire.  Please advise if anyone has a resolution.

Original comment by mrh...@yahoo.com on 8 Feb 2012 at 9:38

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I have a brand new USB siren of shame 5/2012. In installed on a machine that 
happens to be running a vmware guest. I am using this from the host not from 
inside the vmware vm. It goes through the initialization process but is 
unrecognized by Windows 7. Then the s-o-s software does know how to upgrade the 
firmware but "show off" is never enabled. 

I then installed this on a machine without a VMWare VM on it and everything 
worked fine.

Original comment by j...@freemansoft.com on 24 May 2012 at 5:16

GoogleCodeExporter commented 9 years ago 
@Joe Sounds like you at least have a work-around, so unless I hear otherwise 
I'm going to continue to leave this ticket in the low priority bucket.

@mrhauk We resolved your issue via e-mail, correct?

Original comment by lpric...@gmail.com on 25 May 2012 at 4:02