Step 2: Install Windows Components.

Now that the virtual appliance is running and configured, we can install the Windows components of Go!. The Go! virtual appliance provides a Windows share called "goembedded". The "goembedded" share contains the various Go! user components for Windows. Map the \\''ApplianceHostname''\goembedded share to a drive on your host computer. Note that you will have to check off "Connect using different credentials" when mapping this share, and then enter username "go", and the go password when prompted. If you can not map this share, then it is probably because ''ApplianceHostname'' is not resolving properly, so remember you can always us \\''IP Address''\goembedded (eg. \\\goembedded). To find the IP address of your appliance, just look at the title bar of your web browser when webmin is loaded.

After you have mapped the "goembedded" share, go to the Windows_Installs directory in Windows Explorer for the mapped drive.

Step 2a: Install Eclipse, QEMU, and Msys.

The IDE used by Go! is the popular Eclipse IDE with some additional plugins such as CDT, RSE, and others. QEMU is a generic and open source machine emulator and virtualizer. When used as a machine emulator, QEMU can run OSes and programs made for one machine (e.g. an ARM board) on a different machine (e.g. your own PC). By using dynamic translation, it achieves very good performance. Msys, a sub-project of MinGW provides unix commands for Windows. Msys is installed to provide a consistent command interface between embedded Linux targets, and the Windows host environment. With Msys one can open a DOS command shell and run unix commands like ls. Note that Windows 7 comes with the Windows Powershell which provides many unix commands like ls. In Windows 7 you may want to run the powershell instead of a DOS command prompt. Powershell is available as a free download for Windows XP as well, just Google it.

The install wizard for Eclipse, QEMU, and Msys, is distributed from The file will be called setupGo.x.y.z.exe, where x=major version, y=minor version, and z=build id. Download the most recent version and run the install. Note that the version number for this setup does not have to match the version number of the virtual machine.

Step 2b: Configure shared folders between development host and Go! virtual appliance.

When Eclipse starts, the user is asked for a directory on the host filesystem to act as the Eclipse workspace. When a project is opened in Eclipse it is placed in this directory. The virtual appliance needs access to the workspace directory in order to find the source code for a build, so the workspace directory is shared with the Go! virtual appliance using VMware's shared folders feature. To make this work, you must configure your installation with the path to your workspace directory. To configure shared folders, in VMware Player, open the shared folders menu item as below:


Next, select the workspace share in the shared folders selection screen, and press the "Properties" button:


Next, enter the path to your workspace directory into the shared folders properties screen, and press the "Ok" button on the shared folders properties screen, and "Ok" again on the shared folders screen. Note that if the last segment of the path to your Eclipse workspace folder is not workspace, then you must also change the share "Name" in the "Shared Folders Properties" screen. For instance, if your Eclipse workspace directory is called C:\Users\billy\MyWorkspace, then you must change the shared folders name to MyWorkspace instead of workspace. Also, do yourself a big favor, and don't use spaces in the last segment of your workspace folder directory name.


The workspace shared folder is mounted to /mnt/hgfs inside the virtual appliance. Thus, if you have a project named MyProject in your workspace directory, then the path to that project inside the virtual machine will be /mnt/hgfs/workspace/MyProject. When Eclipse builds inside the virtual machine, it will build from the path /mnt/hfgs/workspace/MyProject, and all compiler messages will contain this path. For example, if there was a C file called MyCFile.c in the workspace directory, and there was an error message during compilation, then the path output by gcc on the error messsage will be /mnt/hgfs/workspace/MyProject/MyCFile.c. In Eclipse, running in Windows, this path will not be recognized, so we would not be able to double click on the error to open MyCFile to the line with the error. To fix this we need to create the /mnt/hgfs path on the drive containing the workspace, and we can do that with an NTFS symbolic link. For example, if our Eclipse workspace path is C:\Users\chris\workspace, then we need to create an NTFS symbolic link from C:\mnt\hgfs to C:\Users\chris. This can be achieved by following the example in the screen shot below:


Of course, you can skip mklink if you just create the directory C:\mnt\hgfs\workspace, and use that directory as your Eclipse workspace. In reality, as time goes by, you will probably end up with multiple workspace directories, so the mklink technique is handy in that case. Finally, note that if you use different workspace folders for different projects in Eclipse, then everytime you change your Eclipse workspace folder, you must also change the Go! virtual appliance shared folder for workspace, and you must also create a new symbolic link so that the virtual machine path matches the host path.

When you are ready to continue, press the Next link below.

Next >>

Last edited Feb 23, 2010 at 5:19 AM by castone, version 2


No comments yet.