Jump to content

Recommended Posts

Posted

I tried FW Update.  It updates the new firmware, then I still cannot upload/dowload settings.  Is there a manual reboot on the device itself??

At least if I can do that I can still continue to vape.  As of now it still is stuck on "upload settings"

Posted

There are 2 reboot commands in escribe tools menu, but on the mod you will need to disconnect the battery.  You may need to do the update on a different machine, there is a thread on Mac support that has more detail on the USB implementations of various virtual host set ups for Windows that is worth reviewing.

Posted

Does it just intermittently pause and fail with EEPROM Programming Failed, or something more consistent?
If these VMs just have a tendency to pause, I wonder if we just need to increase the timeout time.

Posted

I am using VMWare Fusion on my Mac, running Windows 7.  I double checked the USB was being recognized on the Mac and on the VMWare.  SO the DNA200 is being recognized.  It consistently says "EEPROM programming failed" when I try to upload settings to the device via Escribe.  Now my DNA200 is stuck and only displays "Upload Settings".  I cannot fire device. Any way to fix this or just use a PC based computer to fix issue?  Or is my DNA200, that is stuck on "Upload Settings", requires maintenance.   I did click "hard reboot" on Escribe, but if the device is not being recognized, I doubt that command went through.  Please advise and thank you for your time.

Posted

We bought a Mac Mini yesterday to test on.

In my testing with VirtualBox...
If the firmware update has a problem, the DNA goes into its bootloader/recovery mode. You need to add the bootloader device (it just shows as a serial number) in USB Devices. Once you do that, if you reconnect it, it does detect. (It seems that the effects of VirtualBox settings changes are only seen after a reconnect.) After that I had no problems doing firmware updates on Mac OS.

In my testing with Parallels...
Parallels was about the same, except it seemed to have trouble detecting when I disconnected the device. The Windows XP image I was using still thought it was connected. Also, it was very slow to detect the connection.

So the real problem with both of these is they don't automatically hand over the DNA 200 to the virtualized OS. If you make sure both the normal device and its recovery mode get handed over, though, it works okay.

On both I *did* find that USB is slower under virtualization. I raised the timeouts from 750 milliseconds to 2 seconds in my test version, which made for less spurious errors.

Posted

Thanks James (odd as I am James).  I added the serial number recovery device as a USB device, but I may not have restarted the host OS.  I am thinking with your longer timeout may make the issue moot (hopefully).  I have tested VirtualBox and VMware and I think all methods function about the same with the lag.

Posted

I was making changes last night with the current version of EScribe and Virtualbox.  I did notice an improvement... I only received one EEPROM error.  Far fewer than in the past!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...