Getting Started with the NI SoftMotion Development Module for LabVIEW

RELEASE AND UPGRADE NOTESLabVIEW Real-Time Module Version 2015This document provides system requirements, installation instructions, descriptions of new features, and information about upgrade and compatibility issues for the LabVIEW 2015 Real-Time Module.Refer to the Getting Started with the LabVIEW Real-Time Module manual for exercises you can complete to familiarize yourself with the Real-Time Module.TipRefer to the Real-Time Module Best Practices book in the LabVIEW Helpfor programming recommendations on designing, developing, and deploying applications with the LabVIEW Real-Time Module. Select Real-Time Module»Real-Time Module Best Practices on the Contents tab of the LabVIEW Help to display this book.ContentsSystem Requirements (2)Installing the LabVIEW 2015 Real-Time Module (2)Installing Japanese and Simplified Chinese Languages (3)Activating the Real-Time Module (3)Configuring Real-Time Targets (3)New Features (4)Shared Libraries on NI Linux Real-Time Targets (4)Getting Started with a Real-Time Application (4)NI Device Monitor Notification for RT Target Discovery (4)New Hardware Support (4)NI Linux Real-Time Kernel Updates (4)SELinux Support on NI Linux Real-Time Targets (5)Calibrating Touchscreen Monitors on the Embedded UI (5)Upgrade and Compatibility Issues (5)Known Issues with the Real-Time Module (5)Where to Go from Here (5)Related Documentation and Examples (5)NI Website (6)Worldwide Support and Services (6)™2||LabVIEW Real-Time Module Release and Upgrade Notes System RequirementsIn addition to the LabVIEW system requirements listed in the LabVIEW Readme , the LabVIEW 2015 Real-Time Module has the following requirements:•LabVIEW 2015 Full or Professional Development System (32-bit)•At least 200 MB of disk space in addition to the LabVIEW-recommended minimum •RT target hardware and driver software •One of the following operating systems for application development:–Windows 8 (32-bit)–Windows 8 (64-bit with 32-bit LabVIEW installed)–Windows 7 (32-bit)–Windows 7 (64-bit with 32-bit LabVIEW installed)–Windows Server 2003 R2 (32-bit)–Windows Server 2008 R2 (64-bit with 32-bit LabVIEW installed)–Windows Vista (32-bit)–Windows Vista (64-bit with 32-bit LabVIEW installed)–Windows XP Pro (Service Pack 3)Note You might need more memory than the LabVIEW-recommended minimum depending on the size of the application you design in LabVIEW on the host computer.Installing the LabVIEW 2015 Real-Time Module Complete the following steps to install LabVIEW and the Real-Time Module on a development computer:1.Log in to the development computer as an administrator or as a user with administrative privileges.2.Insert the LabVIEW 2015 Platform media.NoteTo request or download additional media, refer to the NI website. If youpurchased this product with an NI Software Suite or NI Product Bundle, use the installation media that shipped with your purchase to install this product.3.Follow the instructions on the screen to install software in the following order:a.LabVIEW b.Real-Time Module c.Device DriversNote Refer to your hardware-specific documentation for information aboutinstalling the appropriate device drivers.LabVIEW Real-Time Module Release and Upgrade Notes |© National Instruments |3The Real-Time Module installs the following real-time operating systems (RTOSes). Refer to the specific RT target hardware documentation for information about which RTOS your RT target uses.•NI Linux Real-Time •Phar Lap ETS •VxWorksInstalling Japanese and Simplified Chinese Languages After you install the Real-Time Module on your development computer, you can complete the following steps to install and use Japanese and Simplified Chinese languages on an RT target:e the LabVIEW Real-Time Software Wizard in NI Measurement & AutomationExplorer (NI MAX) to install the Language Support for Japanese or Language Support for Simplified Chinese software component on the RT target. Refer to the Measurement & Automation Explorer Help for information about the LabVIEW Real-Time Software Wizard.2.Open the System Settings tab and select Japanese or Simplified Chinese as the Locale .Note You cannot use Japanese or Simplified Chinese characters in directory names or filenames on the RT target.Activating the Real-Time ModuleThe Real-Time Module relies on licensing activation. When the evaluation period expires, you must activate a valid Real-Time Module license to continue using the Real-Time Module. You must create an User Profile to activate your software.You can use the NI License Manager, available by selecting Start»All Programs»National Instruments»NI License Manager , to activate NI products. (Windows 8)Click NI Launcher and select NI License Manager in the window that appears.Refer to the National Instruments License Manager Help , available by selecting Help»Contents in the NI License Manager, for information about activating NI products.Configuring Real-Time TargetsUse NI MAX to configure RT targets and to install software and drivers on targets. You can install NI MAX from the LabVIEW Platform media.•Networked RT Targets —Refer to the MAX Remote Systems Help book in theMeasurement & Automation Explorer Help , available by selecting Help»MAX Help from MAX, for information about configuring networked RT targets.•Desktop PC Targets —Refer to the Using Desktop PCs as RT Targets with theLabVIEW Real-Time Module document for information about configuring a desktop PC as a networked RT target. Open the labview\manuals directory and double-click RT_Using_PC_as_RT_Target.pdfto open the document.Note If you install NI Web-based Configuration & Monitoring on an RT target, Array you can use a web browser to perform common monitoring and configuration taskson the target. On the Contents tab in the LabVIEW Help, select Fundamentals»Working with Projects and Targets»How-To»Monitoring and Configuring aRemote Device from a Web Browser for information about NI Web-basedConfiguration & Monitoring.New FeaturesThe LabVIEW 2015 Real-Time Module includes the following new features. Refer to theLabVIEW Help, available by selecting Help»LabVIEW Help, for more information about thesefeatures.Shared Libraries on NI Linux Real-Time T argetsThe LabVIEW 2015 Real-Time Module includes support for creating shared libraries onNI Linux Real-Time targets. You can use shared libraries to share the functionality of your VIswith other developers.Getting Started with a Real-Time ApplicationThe LabVIEW 2015 Real-Time Module includes a tutorial that guides you through creating areal-time application. The tutorial demonstrates VIs that acquire and process data on the RTtarget and display that data on the host computer. Navigate to the Tutorial: Creating a Real-TimeApplication topic of the LabVIEW Help to view the tutorial.NI Device Monitor Notification for RT T arget Discovery The LabVIEW 2015 Real-Time Module includes support for simplified device discovery and configuration. When you connect an NI Linux Real-Time target to a host computer using an Ethernet over USB connection, the NI Device Monitor displays the RT target IP address and allows you to launch LabVIEW, NI MAX, and NI Web-based Configuration & Monitoring, as well as access Getting Started information available on /getting-started. New Hardware SupportThe LabVIEW 2015 Real-Time Module supports new RT targets, including the sbRIO-9607,sbRIO-9627, sbRIO-9637, and the NI3173 RT Industrial Controller.NI Linux Real-Time Kernel UpdatesThe LabVIEW 2015 Real-Time Module includes updates to the NI Linux Real-Time kernel.These updates include networking improvements, bug fixes, and security updates. NI alsoprovides new packages in the NI Linux Real-Time repository. These packages include GCC 4.8,MySQL, and PHP. (ARM-based targets) The LabVIEW 2015 Real-Time Module updates thekernel on NI Linux Real-Time targets from version 3.2 to version 3.14. (Intel x64-basedtargets) The LabVIEW 2015 Real-Time Module updates the kernel on NI Linux Real-Timetargets from version 3.10 to version 3.14.4||LabVIEW Real-Time Module Release and Upgrade NotesSELinux Support on NI Linux Real-Time T argetsThe LabVIEW 2015 Real-Time Module includes the SELinux security policy on NI Linux Real-Time targets. After configuring SELinux, you can control access between applications and resources and enforce a wide range of security goals, from sandboxing applications to restricting users to a limited set of resources. Visit /info and enter the Info Code RTSecurity to learn about security on real-time systems.Calibrating T ouchscreen Monitors on the Embedded UI The LabVIEW 2015 Real-Time Module includes the RT Calibrate Touchscreen VI on the RT Utilities palette. This VI opens an interactive wizard that allows end users to calibrate touch panel monitors on RT targets that support the embedded UI.Upgrade and Compatibility IssuesYou might encounter compatibility issues when upgrading to the LabVIEW 2015 Real-Time Module from the LabVIEW 2014 Real-Time Module. Refer to previous versions of the LabVIEW Real-Time Module Release and Upgrade Notes, available on /manuals, for changes in previous versions of the Real-Time Module.Known Issues with the Real-Time ModuleRefer to the NI website at /info and enter the Info Code LVRT2015KIL to access the known issues for the LabVIEW 2015 Real-Time Module.Where to Go from HereNI provides many resources to help you succeed with your NI products. Use the following resources as you start exploring LabVIEW and the Real-Time Module.Related Documentation and ExamplesUse the following resources to learn more about using LabVIEW and the Real-Time Module:•LabVIEW Help—Available by selecting Help»LabVIEW Help in LabVIEW. Browse the Real-Time Module book in the Contents tab for an overview of the Real-TimeModule.•Context Help Window—Available by selecting Help»Show Context Help. Context help provides brief descriptions of VIs, functions, and dialog boxes. Context help for most VIs and functions includes a link to the complete reference for a VI or function.•Hardware-Specific Documentation—Some RT targets provide printed documentation as well as content in the LabVIEW Help. Use the hardware documentation for information about using the RT target with LabVIEW and for information about hardwarespecifications.•Examples—Use the NI Example Finder, available by selecting Help»Find Examples from LabVIEW, to browse or search for RT example VIs. You also can access example VIs from the labview\examples\Real-Time Module directory.LabVIEW Real-Time Module Release and Upgrade Notes|© National Instruments|5NI WebsiteRefer to /info and enter the Info Code rttrn to access the product support page for the Real-Time Module.Worldwide Support and ServicesThe National Instruments website is your complete resource for technical support. At / support you have access to everything from troubleshooting and application development self-help resources to email and phone assistance from NI Application Engineers.Visit /services for NI Factory Installation Services, repairs, extended warranty, and other services.Visit /register to register your National Instruments product. Product registration facilitates technical support and ensures that you receive important information updates from NI. National Instruments corporate headquarters is located at 11500 North Mopac Expressway, Austin, Texas, 78759-3504. National Instruments also has offices located around the world. For telephone support in the United States, create your service request at /support or dial 1866ASK MYNI(2756964). For telephone support outside the United States, visit the Worldwide Offices section of /niglobal to access the branch office websites, which provide up-to-date contact information, support phone numbers, email addresses, and current events.Refer to the NI Trademarks and Logo Guidelines at /trademarks for more information on National Instruments trademarks. Other product and company names mentioned herein are trademarks or trade names of their respective companies. For patents covering National Instruments products/technology, refer to the appropriate location: Help»Patents in your software, the patents.txt file on your media, or the National Instruments Patents Notice at /patents. You can find information about end-user license agreements (EULAs) and third-party legal notices in the readme file for your NI product. Refer to the Export Compliance Information at /legal/export-compliance for the National Instruments global trade compliance policy and how to obtain relevant HTS codes, ECCNs, and other import/export data. NI MAKES NO EXPRESS OR IMPLIED WARRANTIES AS TO THE ACCURACY OF THE INFORMATION CONTAINED HEREIN AND SHALL NOT BE LIABLE FOR ANY ERRORS. U.S. Government Customers: The data contained in this manual was developed at private expense and is subject to the applicable limited rights and restricted data rights as set forth in FAR 52.227-14, DFAR 252.227-7014, and DFAR 252.227-7015.© 2000–2015 National Instruments. All rights reserved.371374M-01Jun15。

Micrium Tools Training: µC/Probe and SystemViewLabsMicrium’s µC/Probe and SEGGER’s SystemView can be invaluable for developers whose projects are based on the Micrium OS. The lab exercises described in this document will familiarize you with these two tools. The instructions for the lab assume that you have a Mighty Gecko Wireless Starter Kit (SLWSTK6000B), and that you’ve already insta lled µC/Probe and SystemView, as well as the Simplicity Studio IDE, on your PC. Download links for all of these tools are provided below.Download LinksSimplicity Studio: /products/development-tools/software/simplicity-studioThe Micrium OS example project prepared for these labs was developed using SimplicityStudio. You’ll need the IDE in ord er to build and run the project.µC/ProbeA visit to Micrium’s Web site to download µC/Probe is not necessary, since the tool was recently integrated into Simplicity Studio. However, you may need to use the IDE’s Package Manager to update your install and gain access to µC/Probe. Within the Package Manager, which you can find by clicking the button with the green, downward-facing arrow appearing near the upper-left corner of Simplicity Studio in the Launcher perspective, the link for installing µC/Probe is located on the Tools page, as indicated in the below screenshot. The Educational Edition of µC/Probe referenced by the link can be used without a license. If you’d like access to the full-featured Professional Edition of the tool, you can contact Micrium to get a one-year FAE license at no cost.SystemView: https:///downloads/free_tools/Setup_SystemView_V242.exe SystemView is a free tool from SEGGER. In order for the tool t o work properly, you’ll need the latest J-Link software, which is also available from SEGGER: https:///downloads/jlink/JLink_Windows_V614c.exe.Lab 1: Building and Running the Example ProjectIn this lab, you’ll build and run a Simplicity Studio example proj ect incorporating the Micrium OS. You’ll use this project in Lab 2 and Lab 3 to explore the features of µC/Probe and SystemView.Procedure:1.Your hardware platform for the labs is the Mighty Gecko Wireless Starter Kit. Youshould now connect one of your k it’s main boards (BRD4001A) to a radio board(BRD4161A). You should then establish a USB connection between your PC and thecombined boards. Your main board features a built-in J-Link debugger, and the USB connection will allow you to leverage this debugger within Simplicity Studio.2.If you’re not al ready running Simplicity Studio, you should start it now. You shouldmake sure that you’re in the Simplicity IDE perspective, which you can open by selecting Window>Perspective>Simplicity IDE.3.The example project for the labs is delivered in a zip file named Micrium-Tools-Lab.zip.You should now extract the contents of this zip file to a folder of your choice. To avoid any possible issues with long path names, it is recommended to keep the zip file contents relatively close to your root folder.4.You’ll now need to import the example project that was delivered in Micrium-Tools-Lab.zip. You should start the import process in Simplicity Studio by selecting File>Import…. On the dialog that subsequently appears, you should expand General and select Existing Projects into Workspace, as indicated in the below screenshot. You should then click the Next button.5.Within the second Import dialog, you should ensure that Select root directory is chosenand you should then click the corresponding Browse button. You must then navigate to the location of the project folder (named Tools-Lab-1) that was provided in Micrium-Tools-Lab.zip. Before clicking the Finish button, you should ensure that the Tools-Lab-1 is checked in the Projects field and that Copy projects into workspace is likewise checked, as indicated in the below screenshot.6.The example project should now appear in your Project Explorer, as indicated below.To clean any build artifacts that might exist for the project, you should right-click its name, Tools-Lab-1, and select Clean Project from the menu that appears. If the clean operation was successful, you should then attempt to build the project by again right-clicking the project name and this time selecting Build Project.7.The build operation for your project should have completed without any errors. (Thereshould have been one warning associated with deprecated interrupt code in the BSP.) In the case of a successful build, you should now attempt to download your project’s code to your board by right-clicking Tools-Lab-1in the Project Explorer and then selecting Debug As>1 Silicon Labs ARM Program.8.Simplicity Studio should automatically switch to the Debug perspective as a result ofyour actions in the previous step. Within this pers pective’s editor area, the tool should indicate that execution of your project is halted on the first line of the main() function. You should now start execution of the project’s code by clicking the Resume button shown below. LED0and LED1should then begin alternately blinking on yourboard.9.After confirming that your code is running and your LEDs are blinking, you can terminateyour debug session by right-clicking the Silicon Labs ARM MCU item that, as indicated inthe below screenshot, should appear in the Debug window. You should selectTerminate from the subsequent pop-up menu. Your LEDs should continue to blink afterthe debug session has ended, since your project’s code now resides in Flash memory.Lab 2: µC/ProbeIn this lab, you’ll use µC/Probe to visualize the internals of the project that you built in Lab 1. You’ll first monitor one of the project’s C variables, and you’ll then use µC/Probe’s kernel-awareness capabilities to view statistics output by the µC/OS 5 kernel on which the project is based.Procedure:1.You should now run µC/Probe. You can actually start the tool within Simplicity Studio byclicking the button shown in the below screenshot.2.µC/Probe makes it possible to view the values of an application’s variables as codeactually runs. In order to offer this capability, it needs information on the variables’ locations. It typically gets this information from an ELF file. When you built the Micrium OS example project following the procedure given in the previous section of this document, an ELF file, Tools-Lab-1.axf, should have been generated by Simplicity Studio and placed at the path listed below. In this path, <project_location> is the folder where your project resides. If you’re uncertain of this location, you should right-click the project’s name in Project Explorer and select Properties. If you then select Resource from the categories listed on the left side of the Properties dialog, you’ll be able to read your project folder from the Location field in the upper half of the dialog.<project_location>\GNU ARM v4.9.3 - Debug3.You can pass an ELF file to µC/Probe using the Symbol Browser located at the bottom ofthe tool’s main window. You should now click the Symbol Broswer’s ELF button, which is shown in the below screen shot. In the ensuing dialog, you should simply browse to the ELF file described above and then click the Open button.4.µC/Probe will be able to use your board’s built-in J-Link debugger to access variables inyour running example code. In order to establish J-Link as your preferred communication interface, you’ll need to select it in the Settings dialog. You should now open this dialog by clicking the Settings button shown below.5.As indicated in the below screenshot, the lower left corner of the Settings dialogcontains a list of Debug Interfaces containing just one item: J-Link. You should confirm that J-Link is selected, and you should then ensure that Don’t Change has been specified for the Interface Mode. Before clicking OK, you should choose Silicon Labs as the Manufacturer, and, using the provided table, select EFR32MG12PxxxF1024as your Device.6.µC/Probe provides a variety of graphical components that can be used for displaying thevalues of variables. You can access these components via the Toolbox located on the left side of the main program window. You should now instantiate a new component—a gauge—by first clicking Angular Gauges in the lower half of the Toolbox and thendragging and dropping the Semicircle 3gauge onto the data screen in the middle of µC/Probe’s program window. The data screen should then appear as shown in thebelow screenshot.7. A graphical component is not of much use until it has been associated with a variable, orsymbol. The Symbol Browser will be your means of associating a variable with your new gauge. If the Symbol Browser is not already displaying a list of C files corresponding to the code that you built in the first part of the lab, you can make such a list appear by expanding the entry for Tools-Lab-1.axf that appeared when you specified the path of this file in Step 2. Once the list is visible, you should expand the entry for the C file ex_main.c in order to make the variables contained in that file appear. You should then drag and drop the variable Ex_MainSpeed from the Symbol Browser to your gauge. As indicated below, the variable name will appear below thegauge to indicate that the two are associated.8.You should now click µC/Probe's Run button, which, as indicated below, is located in theupper left-hand corner of the tool's main program window. If you’re using the Educational Edition of the tool, you’ll be presented with a dialog indicating that you won’t have access to µC/Probe’s full set of features unless you upg rade to the Professional Edition. You can simply click this dialog’s Close button. You will then enter µC/Probe’s Run-Time mode. The dial on your gauge should begin moving from 0 to 100 and then back to 0. It should repeat this pattern indefinitely. Keep in mind that, with the Educational Edition, you will only be able to remain in Run-Time mode for one minute before a time-out occurs and another dialog prompting you to upgrade appears.9.µC/Probe can be used with nearly any embedded system—including those not based ona real-time kernel. However, the tool is especially helpful when paired with projectsthat incorporate Micrium’s embedded software modules, in part because of its kernel-awareness capabilities. These capabilities are implemented via a number of pre-populated data screens that show the values of different kernel variables. You should now stop µC/Probe (by clicking the Stop button located in the upper left-hand corner of the main program window) and add the kernel-awareness screens for µC/OS 5, the kernel featured in the example project, to your workspace. You can add the screens by first clicking Project1in µC/Probe's Workspace Explorer window and then clicking Screens>Micriµm OS Kernel (µC/OS-5), as indicated in the below screenshot. After making this change, you can again click Run to prompt µC/Probe to begin updating the new screens with kernel statistics.10. Within the main µC/OS 5 kernel-awareness screen, there are a number of subordinatescreens, including one for Task(s). As shown below, this screen displays the status of each task running in your project. You should now take a moment to look over the screen and familiarize yourself with the various tasks that the example incorporates.The percentage of CPU cycles consumed by the tasks is provided in the CPU Usage column, and you should note that, after the kernel’s Idle Task—which runs when no application tasks are ready—it is the Tick Task—the kernel task responsible for processing periodic tick interrupts—that consumes the most CPU cycles, with a usage of approximately 5.5%.11.After you’ve looked over Task(s), you should stop µC/Probe (via the Stop buttonmentioned in Step 9). You should then return to Simplicity Studio to make a simple change to the example project’s code. Within the IDE, you should open the file ex_main.c. You’ll be able to find this file by expanding the Micrium folder within the Project Explorer, and then similarly expanding Micrium_OS_V5.00 and examples. You should add the below two lines to ex_main.c, placing the new code at line 156, just below the variable declaration in the main() function. The result of your addition will be to change the frequency of tick interrupts received by the kernel, from 1 kHz to 100 Hz.OS_TASK_CFG Ex_MainCfgTick = {DEF_NULL, 256u, 4u, 100u};OS_ConfigureTickTask(&Ex_MainCfgTick);12.You should now build and run your modified project, following the same procedure thatyou used in Lab 1. Afterward, you should return to µC/Probe and again run your workspace. With tick interrupts now occurring at 1/10 of their original frequency, you should confirm that the overhead of the kernel’s Tick Task has experienced a similar decrease, meaning that the task’s CPU usage should be around 0.6%.Lab 3: SystemViewThis lab w ill walk you through the steps needed to use SEGGER’s SystemView with the example project featured in the previous two labs. With SystemView, you’ll be able to see the cont ext switches, interrupts, and kernel function calls that occur as the project runs.Procedure:1.Because the latest Micrium OS is a relatively new software module, it is not yetsupported by the version of SystemView available from the SEGGER Web site.Fortunately, though, it is fairly easy to update SystemView so that it will recognize applications based on MicriumOS. To make the update, you should now copy SYSVIEW_Micrium OS Kernel.txt, which was provided in Micrium-Tools-Lab.zip, and paste this file into the Description folder in the SystemView install path—Program Files (x86)\SEGGER\SystemView_V242.2.You should now run SystemView by clicking the tool’s entry in the Windows Start menu.3.When you run SystemView for the first time, you’ll be presented with the below dialog,asking whether you’d like to load a sample recording. You can simply click this dialog’s No button.4.In order to begin analyzing the behavior of your example project’s code, you’ll need torecord the code’s activity. To initiate recording, you should select Target>Start Recording within SystemView. You will then be presented with a Configuration dialog.Once you’ve verified that the contents of this dialog match the screenshot shown below, you should click the OK button to initiate recording.5.Shortly after you’ve started to record, you may be presented with the dia log shown inthe below screenshot. This dialog indicates that some of the data that would otherwise be displayed by SystemView was lost, because the buffer used to temporarily store that data on your target experienced overflows. You can simply click OK to close the dialog.For information on how to limit the potential for overflows, you can consult the last section in this document.6.Once you’ve gathered a few second’s worth of data, you should click the Stop Recordingbutton shown in the first of the two screenshots shown below. As the second screenshot indicates, the Timeline located near the center of the SystemView main program window should subsequently display all of the task and ISR activity that occurred during the period the recording was active. You now can begin investigating the execution of the example project’s code in detail.7.If you adjust the zoom on the timeline, you should be able to see, every 40 ms, thepattern of events depicted in the below screenshot. The example project incorporates three application tasks, in addition to a number of kernel, or system, tasks. One of the application’s tasks, labeled Post Task, peridocially performs a post operation on a semaphore, and that is what is shown in the screenshot. In the next couple of steps, you’ll adjust the period of the Post Task and then make an additional SystemViewrecording to confirm the results.8.The period of the Post Task is established by a variable in the same file that youmanipulated in Step 11 of the previous lab, ex_main.c. The variable is named Ex_MainDelayPostms and you have two different options for changing its value.One is to simply replace the variable’s initialization on line 371 of ex_main.c with thebelow code. You’l l then need to rebuild the example project and again download its code to your board. The second option involves µC/Probe. In addition to allowing you to read variables, µC/Probe offers a number of Writable Controls for changing variable values. You can drag and drop one of these controls—a Horizontal Slider, for example—into your workspace from Lab 2, and use the new control to adjust the value of ExMainDelayPostms.Ex_MainDelayPostms = 20;9.With the value of the variable adjusted, you should return to SystemView and make anew recording. Now the post operation described in Step 6 should be visible every 20 ms, as opposed to 40 ms. If time permits, you can make further adjustments to the code, changing, for example, the priority of the Post Task (established by the #define EX_MAIN_POST_TASK_PRIO), and you can use SystemView to observe the results of the changes.Limiting OverflowsThere are a few steps that you can take to limit overflows and maximize the amount of data recorded by SystemView. One of these is to increase the size of the buffer used to temporarily store SystemView data on your target before it is passed to the PC application. The buffer size is established by the #define SEGGER_SYSVIEW_RTT_BUFFER_SIZE in the file SEGGER_SYSVIEW_Conf.h. This file is contained in Micrium/Tools/SystemView/Config within the example project. The provided copy of SEGGER_SYSVIEW_Conf.h uses a buffer size of 4096, but you’re free to increase to any size that the hardware can accomodate.An additional measure, recommended by SEGGER for reducing the number of overflows, is to ensure that SystemView is the only tool using your J-Link. In other words, if you were previously running µC/Probe or the Simplicity Studio debugger while recording data, you should stop the other tools and try a new recording. With exclusive access to the J-Link, SystemView should have fewer impediments to capturing all of the example project’s events.。

Linux MDS Getting Started GuideFirst EditionFebruary 2007Table of Contents Introduction (1)Purpose of this Document (1)Navigating this Document (1)Manage Users (2)Adding Users (2)Administering and Configuring Users (2)Removing Users (3)Manage Email (4)Configuring Virtusertable entries (4)Configuring Catchalls (4)Configuring Aliases (5)Manage Subhosts (6)Adding a Subhost (6)Configuring a Subhost (7)Removing a Subhost (7)Use Vinstall and Vuninstall (8)IntroductionThe Linux Managed Dedicated Server (Linux MDS) offers the benefits of a managed hosting solution with the flexibility of a dedicated Red Hat Enterprise Linux (RHEL) server. The customized technology of Linux MDS provides a solution where the operating system and core services are managed for you. At the same time, you have full root access to your files and programs.Purpose of this DocumentThis document provides information for basic administration of your account. It provides important information about creating users, configuring email and subhosts (or virtual hosts), and server software management to help you begin using your account. This document describes server management from a shell command line and assumes you understand shell clients and command-line interaction with Linux (or other UNIX-like) servers. If you do not use shell command line or are not familiar with shell interaction, you can install and use the CPX: Control Panel Web interface. For more information about CPX: Control Panel, see customer documentation for the CPX: Control Panel, which includes a guide to getting started with that Web interface. Your account includes several v-commands. These commands, created specifically for your product, enable server administration. Some examples discussed in this document include vadduser, vrmuser, and vaddhost.Navigating this DocumentThis document describes how to add, remove, or configure server users, email addresses, aliases, virtual user table (virtusertable) entries, catchalls, and subhosted Web site configurations. In addition, this document describes how to use custom installation scripts (vinstall and vuninstall) which enable you to install and/or remove programs, packages, and features. Refer to the following sections for instructions:•“Manage Users” on page 2.•“Manage Email” on page 4.•“Manage Subhosts” on page 6.•“Use Vinstall and Vuninstall” on page 8.Manage UsersAs part of the automatic maintenance provided with your account, your server contains several necessary root and application users by default, such as root, ftp, pop, and the administrative user (created when you ordered the server). You can create additional users and offer them services, such as FTP, email, and shell access. This section describes adding, managing, and removing users.Note: When adding, configuring, or removing users, you must be the root user. You can become the root user by typing su- at the command line and supplying the root user password.Adding UsersTo add a server user, follow these steps from the command line:1.Type vadduser and press Enter.2.Further instructions and information for vadduser will display during this step and throughout the vadduserprocess. Press Enter to continue after reviewing the information.3.Type the username for the user you wish to create and press Enter. Usernames consist of alphanumericcharacters up to sixteen (16) characters. The first character cannot be a number.Note: The operating system supports multi-byte characters in usernames, but will not support the following multi-byte characters because they are reserved for system use: @, $, #, / or \. (To learn more about using multi-byte characters in usernames, refer to the following Web site: /c/charset.html.)4.Type the user’s password and press Enter. Use a password that will not easily be guessed. A combination ofuppercase and lowercase letters, numbers, and symbols is an example of a more secure password. If aparticularly insecure password is entered, the system will prompt you to enter a more secure password. You will need to type the same password twice for confirmation.5.Type the user’s full name and press Enter. This information displays when you use system tools such asvlist (used to list all server users).6.Type the user’s home directory path and press Enter. The vadduser command simplifies this step andprovides a recommended Linux MDS path for you. You can press Enter without typing a path to select this default.7.Select the services to offer the user. This is a toggle-style prompt, with the FTP and email services enabled forthe user by default. Available services include ftp, mail, and shell. Type the service name at the prompt and press Enter to toggle the service on or off. Press Enter when done.Caution:Shell access enables control over many aspects of the server. Shell access should only be offered to trusted users. With shell access users can potentially change files or settings affecting your entire server. Use care when offering the shell service to users.8.Type the user’s allotted file system (or filesystem) quota in megabytes (MB). The quota must be a wholenumber. Enter 0 to give the user an unlimited quota (up to the free space available for your plan). Press Enter to complete the addition of the user.Administering and Configuring UsersTo list all existing server users, type vlist at the command prompt.To change the full name, services offered, or quota for a user, follow these steps from the command line:1.Type vedituser and press Enter2.Type the name of the user in question and press Enter.3.Select the services to offer the user. This prompt is a toggle-style prompt, with the FTP and email servicesenabled for the user by default. Available services include ftp, mail, and shell. Type the service name at the prompt and press Enter to toggle the service on or off. Press Enter when done.4.Type the user’s allotted filesystem quota in megabytes (MB). The quota must be a whole number. Enter 0 togive the user an unlimited quota (up to the free space available for your plan). Press Enter to complete the addition of the user.To change a server user’s password, follow these steps from the command line:1.Type passwd name, where name is the username of the user in question. Press Enter.2.Type the new password and press Enter. Type the new password again for confirmation and press Enter. Ifthe two passwords do not match, you will be prompted to type them again.Note: Use a password that will not easily be guessed. A combination of uppercase and lowercase letters, numbers, and symbols is an example of a more secure password. If a particularly insecure password is entered, the system will prompt you to enter a more secure password.Removing UsersTo remove a server user, follow these steps from the command line:1.Type vrmuser and press Enter.2.Type the username of the user to remove. If the user does not exist, the system will indicate the user does notexist in the password database and exit the removal process.3.The system will display the password entry for the user to be removed and ask you to confirm the removal ofthe user. Type yes if the information is correct or no to exit the process. Press Enter.Caution:Use extreme caution when removing the home directory of users (step 4). You will not be warned if Webcontent or other important information is stored in the user’s home directory. Removing a user’s homedirectory will immediately delete all contents of that directory.4.The system will display the user’s home directory and ask if you wish to remove it. Type yes and press Enterto remove the directory and complete the removal of the user, or type no and press Enter to remove the user, but keep the user’s home directory and its contents.Note: If you remove a user, but not the files or home directory they own, the files or directories of the removed user will be owned by a system-generated four digit ID (for example: 1007).Manage EmailAll user email boxes reside in the /var/mail directory. The system automatically creates email boxes for server users. If no other email routing settings (such as aliases or virtusertable entries) are configured, the username is the default valid email for all domains that resolve to the server. For example, if and resolve to the server, for the user bob, both *************** and *************** would deliver email to the/var/mail/bob email box. The system checks for matches in email routing and addresses in the following order and delivers to the first match it finds:•virtusertable entries•aliases•usersThis section describes virtusertable entries, catchall, and alias configurations.Note: To edit the virtusertable entries and aliases files, you must be the root user. You can become the root user by typing su - at the command line and supplying the root user password.Configuring Virtusertable entriesVirtual user table (virtusertable) entries route the full email address (both sides of the @) to a local user, alias, or remote email address, but cannot map to files or programs. Only aliases can route email to a file or program. A virtusertable entry consists of the virtusertable entry and its destination, or mapping. For example, a virtusertable entry for *************** could be mapped to the user bob with the following virtusertable entry: ******************Virtusertable entries enable you to create email addresses without the need to create a corresponding user. For example, a virtusertable entry for *************** could be mapped to ******************** with the following virtusertable entry:******************@In this example, would indicate a remote domain which does not resolve to your account. Specify virtusertable entries in the /etc/mail/virtusertable file, with one virtusertable entry per line. The virtusertable.sample file provided with each server contains example virtual user tables. You can change virtusertable entry settings by editing the virtusertable file and then executing a hash command:makemap hash /etc/mail/virtusertable < /etc/mail/virtusertableThe hash command rebuilds the virtusertable.db file which includes the new virtusertable entries. Configuring CatchallsCaution:Catchall virtusertable entries should be used sparingly. Spammers often send many emails to every conceivable address for a domain, often numbering in the thousands. A catchall virtusertable entry wouldcause the system to receive all of these emails and map them to the recipient.A special virtusertable entry called a catchall maps all email not otherwise configured with a virtusertable entry for a given domain to a single recipient. For example, the following catchall virtusertable entry would map all email not configured with another virtusertable entry for the domain to the joe user:@ joeIf no virtusertable entry exists for an email address, and a catchall virtusertable entry is configured for the domain, the system would route all email sent to that address to the catchall virtusertable entry.Configuring AliasesEmail aliases forward email to a user, another alias, email address, list of addresses, file, or program. Aliases enable you to create email addresses without the need to create a corresponding user. For example, the following alias would forward email sent to ******************** to the stan user:webmaster:stanAliases also enable you to send email to a list or to a program. For example, the following alias would forward email sent to ********************* to the bob, joe, and stan users:sales:bob,joe,stanFor long email lists, place the emails in a file, one address per line, and use the include option. For example, the following alias would forward email sent to ********************* to all addresses in the /lists/promotion file:promotion: :include:/lists/promotionSpecify aliases in the /etc/aliases file, with one alias per line. You configure the aliases by editing the aliases file according to your needs. After making changes to the file, execute the newaliases command from the command line to load the new aliases into the system. Changes to aliases will not be used by your account until you execute newaliases.Note: The system only considers the first portion of the email address (before @) for aliases. To map an entire email address to a certain recipient, use a virtusertable entry.Manage SubhostsYour account enables you to configure multiple Web sites and domains in addition to the main domain of the server. The main domain or site for the server is called the hostname. Place the Web content for this site in the/www/htdocs directory.You may have configured a custom hostname during the order process. To aid with configuring and testing your server, all Linux MDS servers receive a temporary domain name, or temp domain, which resolves to your account. This domain can be used if the custom hostname is inaccessible or does not yet resolve to your server.Other domains or sites hosted by your server are called subhosts. This section explains adding, removing, and configuring subhosts.Note: To execute the vaddhost command or edit the httpd.conf file, you must be the root user. You can become the root user by typing su - at the command line and supplying the root user password.Adding a SubhostSubhosts are configured with the Apache VirtualHost directive. The Apache Web server looks for VirtualHost entries in the /www/conf/httpd.conf file. The vaddhost v-command assists in the creation of the subhost configuration VirtualHost tags in your Apache configuration file.Subhost configuration includes many variables. While separated here into three sections, the entire process includes all three and you must complete all of them to entirely configure the subhost.To begin the subhost configuration and specify the domain and administrator, follow these steps from the command line:1.Type vaddhost and press Enter. Instructions and information for vaddhost will display during this step andthroughout the vaddhost process.2.Type the domain for the subhost (, for example), any secondary domains (,, etc), and any other domains used for this subhost, pressing Enter after each. The firstdomain entered will be the main domain for the subhost. Additional variations will be aliases that point to the main domain. Press Enter without any text after providing all variations to move to the next step.Note: The hostname or subhost usually consists of the top-level domain () instead of a canonical name such as . Canonical names are usually added as secondary domains or aliases.3.The system displays the list of domains and variations for verification. Type y and press Enter to continue ortype n and press Enter to input the domains again.4.Type the username of the user who will administer the subhost and press Enter. (Press Enter without any textto display a list of existing users.) This user should be the owner of the site files and folders; otherwise the Web server will not be able to load the site.5.Verify the information and type y and press Enter to continue or type n and press Enter to input the usernameagain.To continue the configuration and specify SSL, administrative email, and document root (Web directory) settings, follow these steps from the command line:1.To enable SSL for the subhost type y and press Enter or type n and press Enter to not enable SSL for thesubhost.2.Verify the information and type y and press Enter to continue or type n and press Enter to input the SSLinformation again.3.Type the email address of the subhost administrator and press Enter.4.Verify the information and type y and press Enter to continue or type n and press Enter to input the addressagain.5.Type the path for the subhost Web directory, or document root, on the server. The vaddhost commandsimplifies this step and provides a recommended path for you. You can press Enter without typing a path to select this default, which will create a subhosted directory in the home directory of the user specified in step 4.6.Verify the information and type y and press Enter to continue or type n and press Enter to input the pathagain.To continue the configuration and specify log and cgi-bin settings, follow these steps from the command line:1.Select an option for the subhost transfer log and press Enter.2.Verify the information and type y and press Enter to continue or type n and press Enter to choose the transferlog configuration again.3.Select an option for the subhost error log and press Enter.4.Verify the information and type y and press Enter to continue or type n and press Enter to choose the errorlog configuration again.5.Select an option for the subhost cgi-bin and press Enter. This will enable the subhost to execute scripts andprograms.6.Verify the information and type y and press Enter to continue or type n and press Enter to choose the cgi-binconfiguration again.7.The system will display the VirtualHost entry to be added to the httpd.conf file for confirmation. Type yand press Enter to add the entry to the httpd.conf file, or type n and press Enter to abort the vaddhost process.8.If you typed y to accept the entry, type y and press Enter to restart the Web server and complete the subhostaddition.Note: Press ctrl+c to exit the vaddhost process at any time. This immediately cancels vaddhost and any subhost configuration entered during the vaddhost process is lost.Configuring a SubhostYou may configure a subhost further by editing the VirtualHost entries for the subhost in the/www/conf/httpd.conf file. Execute the restart_apache command from the command line after editing the file to restart the Web server and make the changes effective.Removing a SubhostThe /www/conf/httpd.conf file contains the configuration for subhosts. To remove the subhost configuration from the Web server, follow these steps:1.Edit the httpd.conf file and remove the VirtualHost entries for the subhost in question.2.After modifying the httpd.conf file, execute the restart_apache command from the command line torestart the Web server.3.Remove any unneeded files or directories for the subhost from the server.Note: See “Removing Users” on page 3 for further information about subhost files and directories assigned to a user and considerations when removing that user.Use Vinstall and VuninstallYour server contains another feature unique to Linux MDS which makes configuration of your server easier. The vinstall v-command enables the installation and configuration of programs to your server. Programs available for installation through vinstall have been configured specifically for the Linux MDS system and enable you to utilize a variety of programs without complicated manual configuration.The vuninstall utility removes files and configurations created by the vinstall utility. This section describes using vinstall and vuninstall to list available programs, find information about them, install, and/or remove programs.You can execute the vinstall utility using interactive commands, or supply the needed information as command-line options to avoid the interactive vinstall prompts. Refer to Table 1 for a list of the possible vinstall actions you can execute and the interactive and non-interactive commands for each. Substitute vuninstall for vinstall when removing programs.Note: Certain programs may prompt for further information as part of their own installation process, even when using the non-interactive vinstall commands.Table 1: vinstall command optionsActions Interactive Command Non-interactive CommandEnter interactive mode vinstall n/aList available programs ? vinstall –lFind additional information about aprogram n/aprogramEnter install mode install n/aInstall a program programvinstall program(while in install mode)Exit interactive mode quit n/aNote: Press ctrl+c at any time to exit the interactive or non-interactive vinstall process. Use this option with caution as it immediately cancels vinstall and may leave installations and programs incomplete and non-functional.。

Getting Started with Osmo Newton Updated 10.05.2019 Version 2.9.1What’s Included? (if you have a Creative Set)● 1 x Osmo Creative Board● 6 x Yoobi Erasable Markers●1 x Blue Fuzzy PouchOsmo Creative Board Quantity: 1Yoobi Erasable Markers Quantity: 6Blue Fuzzy Pouch Quantity: 1Menu NavigationTap (or your avatar, if you’re already logged in) in the upper right corner of the home screen to view the myOsmo account screen. See this g uide to myOsmo accounts and profiles for more information.●Bounce○Tap B ounce t o bounce on into Newton! There are 61 levels of Bounce.●Roll○Tap R oll (once unlocked with Creative Board) and enjoy any one of 18 slightly more difficult rocking and rolling levels!Game ManualObject of the GameUse your creative noggin and inventive objects like a hand-drawn basket, Grandma’s glasses, Dad’s keys, or anything around you to guide falling on-screen balls into targeted zones. Osmo Newton is very much y our game. Grab any object near you to help you hit targets for points and to reach more levels.Achievements include:●Winner: Complete 3 levels.●Two-Pointer: Hit 2 targets at the same time.●Achiever: Complete 9 levels.●Hat Trick: Hit 3 targets at the same time.●Grand Slam: Hit 4 targets at the same time.●Overpopulated: Keep 100 balls on screen at the same time.●Completionist: Complete all levels.●Efficient: Complete 5 levels without losing any balls off screen.●Fission: Break 100 balls inside walls.BounceUse the objects in front of your iPad to bounce theballs toward the balloon targets. Hit each targetfour times to make it charge, then move on to amore challenging round.RollIn the Roll level, balls roll along lines, so the playermust draw paths rather than bounce the balls totheir targets.Tips and Tricks●Balloon targets require 4 hits from balls of the same color to explode. All balloonsneed to be exploded to finish a level.●Fans need balls of the same color passing through them to power up. All fans in alevel must be spinning fast enough to complete the level (they shoot out sparkswhen they're fast enough).●Balls bounce off grey walls.●Color changers do just that: they change balls from one color to another. This canbe useful when you need to change purple balls to green so they can hit a green balloon, for example.●Some levels utilize "No Draw" zones (represented by a white bubble) that don'tallow for lines to exist. Players have to redirect the ball away from or throughthese zones using other means.●Rolling levels were designed to take advantage of physics that is different fromBounce, so certain puzzles are best completed by making ramps or loops.●More complex levels might require you to think about several different elementsat once, especially some of the later Roll levels. Look for ways to mix and matchthe different gameplay elements to complete each round.○For example: You may need to use a "teleporter" to get balls of one color into a different part of the level so that they can more easily go into a "colorchanger".●Speed boost arrows are normally placed as a hint towards the direction you mightwant the balls to go to easily complete the puzzle.●Only certain colors can "complete" that color's targets (like the balloons or fans),however, "grey" targets can be satisfied by balls of any color.Best practices for effective Osmo detection1.If you are using a Creative Board, place it flat against the Osmo Base so that theOsmo logo is closest to the screen. If you are not using a Creative Board, wesuggest securing your paper beneath the Osmo base so it doesn’t move whileyou’re playing.2.Keep the reflector placed squarely in the center so the camera can see the playspace.3.Play Newton in a well lit room.4.Make sure you are using a device that is compatible with Osmo. Please check t hislist of Osmo-compatible devices.5.If you experience any issues despite this setup, please reach out to********************for assistance.Other QuestionsWhat do I do if I lose a piece from my Creative Set?Please reach out to us at s*******************.How can I best clean the Creative Board?Blue fuzzy pouch included in the Creative Set works well (you can lightly dampen it with water). For a more thorough cleaning, you can use products such as Mr. Clean Magic Eraser or Windex.Here are some other options:1. Vinegar and water solution2. Peroxide3. 99% or 90% Isopropyl alcohol4. Hand sanitizer。