[support]

Hi,

OK, regarding the registry traces, Windows keeps the track of all devices that it recognizes, including the WinCDEmu drives. Same would happen if you plug in USB stick. We could add some special cleanup mechanism to remove them, but why? Windows is designed that way and it does not really cause any trouble to users.

With cmd output, it happens because the WinCDEmu executable is a ‘GUI Mode’ executable and cmd.exe does not wait for it to terminate. You can work around it by creating a .bat file with the following contents:

%~dp0\PortableWinCDEmu %*

Then just run the .bat file instead of the .exe file and cmd will handle it correctly.

/CreateISO is just a convenient shortcut for running mkisofs.exe; if you want to use it from command-line, you can just download it here and you don’t need any extra tools for that.

We don’t need to compile the project in every language, but we need to customize the translation system to allow embedding the .lng files into the portable executable. Currently we don’t have the resources to do that, so we are waiting for someone from the community to contribute a pull request.

[support]

Hi,

Thanks a lot for the log. Looks like we have nailed it now: http://sysprogs.com/files/WinCDEmu/WinCDEmu-4.1.exe

Let us know if this resolves the problem.

[support]

Strange. Could you please share the log file from the new DLL? Is should help us locate the problem.

[support]

Hi,

We have found a bug in the code responsible for reading language files, but we have fixed it in the 4.1 build. Just to do a clean check, could you try to restore the langfiles, install 4.1 and replace the x64\WinCDEmuContextMenu.dll with this DLL, i.e.:

1. Rename the old WinCDEmuContextMenu.dll to WinCDEmuContextMenu.old
2. Copy the new DLL into the x64 folder
3. Restart (or kill all instances of explorer.exe via task manager and re-run it)
4. Delete the WinCDEmuContextMenu.old to ensure that it’s not loaded into Explorer
5. Check whether the bug still happens and see if the log file contains anything different.

Does the bug still happen (langfiles needs to be in place)?

 

[support]

Hi,

Looks like the problem might be caused by the translation engine. Can you try temporarily deleting the c:\Program Files (x86)\WinCDEmu\langfiles folder and restarting? Does this solve the problem?

[support]

Hi,

Thanks, this is strange. Please try uninstalling 4.1 and installing this build. It should create a log file and show what is going on.

[support]

Hi,

Have you tried uninstalling WinCDEmu 4.0, restarting and installing WinCDEmu 4.1? Perhaps the old plugin was still loaded.

If this does not help, could you try running the instrumented build here and sending us the %LOCALAPPDATA%\WinCDEmuLog.txt file? It should explain what causes the crash.

[support]

Hi,

You can get the Angstrom toolchain from here. Once you install it, VisualGDB will show it in the list. We hide it by default because Angstrom is far less stable than Debian and we do not recommend new customers to use it. Let us know if you encounter problems with the cross-compilation. In the meanwhile, we will check it on our side and make a separate tutorial.

[support]

Hi,

Sorry again for the confusion. The Angstrom Linux used to be the primary distro for Beaglebone and our Beaglebone Qt tutorials explain how to get it to work. We also provide a toolchain for that, but we do not recommend using Angstrom for new projects, as it is being replaced by Debian.

If you are not required to use the Angstrom image, we would recommend using the newest Debian image from http://beagleboard.org/latest-images.

It looks like the Qt package in the Beaglebone-debian distro is broken, so you would need to cross-compile it. We currently have a detailed tutorial on cross-compiling Qt 5 for Raspberry Pi and cross-compiling it for Beaglebone should be very simlar. We will re-check the exact steps with the latest image and publish an updated tutorial within the next few days.

 

[support]

Hi,

If you are using conditional directives in your Android.mk, VisualGDB won’t detect them automatically.

The easiest way to handle this would be to specify those directories manually on the IntelliSense Settings page of VisualGDB Project Properties.

[support]

Hi,

Sorry for the confusion. We do have separate tutorials for Angstrom-based and Debian-based images for Beaglebone. Please let us know which one you are using so that we could point you to the correct one.

It could have also happened that the Beaglebone image you are using contains a breaking change that prevents VisualGDB from doing the automatic setup. If you could point us to the image and let us know the problem you are experiencing, we will gladly update the tutorial and release a hotfix.

[support]

Hi,

Deleting the registry key would also break some context menus like “Create ISO from folder”.

It looks like we have found and fixed the problem. Could you try this build: http://sysprogs.com/files/WinCDEmu/WinCDEmu-4.1.exe?

[support]

Hi,

Good to know it works now. If you encounter this problem again, please attach a screenshot of the error showing the exact command you are using and SmarTTY output. This should help understand what could be causing it.

[support]

Hi,

Yes, please try experimenting with the flash size, speed and mode. Unfortunately there is not much documentation available from Espressif, so it’s hard to say which exact settings will work with your board.

Was the board working before with VisualGDB? Does it work with the bootloader now? Some users reported that that some of the boards come with very low-quality SPI FLASH that dies after less than 10 rewrite cycles.

[support]

Hi,

Does the correct firmware start now if you manually restart the board? I.e. does the program happen during debugging only or does the programming fail?

[Author]

Posts