If it doesn't show the module name, please fill the module IP address and press OK. Whenever you boot the module or insert the pen drive or SD/MMC card, the cerdisp.exe tool will automatically run.Īfter a few seconds, the module will show up in the list of available devices. Copy the folders \AutoRun\ and \AutoCopy\ either.Installation Instructions (Automatic Start) Choose the Menu "File -> Connect".Īfter a few seconds, the Colibri/Apalis module will show up in the list of available devices. Copy CerHost.exe to any location on your PC, and execute it.Copy CerDisp.exe to any folder on the Colibri/Apalis.
Download the Remote Display V3 over Ethernet package. On WEC2013 remote display works over Ethernet only. The Remote Display Tool allows you to see the display content of the Toradex module. SDKĭownload and install the WEC2013 SDK from here. Note: WEC2013 is not available for the Colibri PXA Series, Colibri T20 (Nvidia Tegra 2), Apalis TK1(there is no Windows Embedded Compact Support).
Note: On WEC2013 application debugging is done only via an Ethernet connection. As the Community Edition is free in many cases, you can check the ( terms for details). Also, the Community Edition of Visual Studio 2015 will work too. Visual StudioĪpplication development for WEC2013 could be done with VS2012/2013/2015 and for this article, download and install Visual Studio 2015. If you require a 32-bit build of SFML you'll have to build it yourself.Install the following software on your development PC. So downloading the 64-bit libraries is the easiest solution if you're on a 64-bit Linux. Specific packages and/or use specific compiler options to do so. Compiling for 32-bit is possible, but you have to install On Linux, if you have a 64-bit OS then you have the 64-bit toolchain installed by default. GCC 7.3.0 MinGW (SEH) - 64-bit Download 16.5 MB GCC 5.1.0 TDM (SJLJ) - Code::Blocks - 32-bit Download 14.1 MB Here are links to the specific MinGW compiler versions used to build the provided packages: In case you are using Visual Studio 2015 or newer, you can go ahead and use the SFML version compiled for Visual C++ 15 (VS 2017), which is still compatible with newer versions of the toolchain. Unless you are using a newer version of Visual Studio, the compiler versions have to match 100%!
0 kommentar(er)
