STMA_ATCT_Ops_Training_Course_book4_ch2_Eurocat-TWR_SSN

Teaching Design for Computer Organization and Embedded Systems (Hamacher) 6th Edition Course OverviewThis course ms to provide students with a comprehensive understanding of computer organization and embedded systems. It covers various topics such as architecture, assembly language programming, digital logic, memory systems, I/O systems, and embedded system design.Learning OutcomesBy the end of this course, students should be able to:•Understand the basic principles of computer organization, including digital logic circuits, computer architecture, andmemory systems.•Write assembly language programs for various architectures, such as x86 and ARM.•Understand the basic principles of embedded systems, including the design and implementation of microcontrollers.•Identify common I/O devices and their interfaces, and design I/O systems to interface with them.Teaching Methods1.Lectures: The course will be delivered through traditionallectures that cover the theoretical concepts, followed by examples and demonstrations.b Exercises: The lab exercises are designed to reinforcethe theoretical concepts taught in the lectures. They involveprogramming assignments and hardware experiments that will helpstudents develop a hands-on understanding of the concepts.3.Project Work: Students will work on a project that involvesdesigning and implementing an embedded system. The project workwill be carried out in groups, and will help students apply their understanding of the theory to real-world problems.AssessmentThe assessment for this course will be based on the following components:1.Quizzes (15%): There will be regular quizzes to assessstudents’ understanding of the material covered in the lectures.b Exercises (25%): Students’ performance in the labexercises will be assessed based on the quality of their code, the accuracy of their results, and their ability to troubleshootproblems.3.Project Work (30%): Students’ performance on the projectwork will be assessed based on the quality of their design, thecompleteness of their implementation, and their ability to present their work effectively.4.Final Exam (30%): The final exam will assess students’overall understanding of the course material.Recommended Textbooks1.Hamacher, V., Vranesic, Z. G., & Zaky, S. A. (2011).Computer organization and embedded systems (6th ed.). McGraw-Hill Education.2.Yaghmour, K., Masters, J., Ben-Yossef, G., & Gerum, P. R.(2013). Embedded Android: Porting, extending, and customizing.。

TI Bluetooth Stack for WL18xx - Getting Started GuideTI Bluetooth Stack - Demo GuideContentsIntroductionOverviewBluetopiaBluetopia Platform ManagerRequirementsHardwareSoftwareGetting StartedStep 1. Installing Bluetopia Platform ManagerStep 2. SD card creationBuild and export the Bluetopia PMStep 3. Sample ApplicationsGstreamer PluginVNET PluginVoice Over BLE Python ScriptBluetooth Hardware configuration scriptStep 4. Installing updated Firmware Service Pack (Init-scripts)Step 5. Terminal ConnectionStep 6. Running a Sample ApplicationBluetopia PM SamplesIntroductionThe following guide explains how to get started with TI Bluetooth Protocol Stack on a host device running Linux. It provides a basic description of the package, and walks through the download and installation procedures. Finally, it shows how to run a sample application. For users who wish to modify any sample applications or the build environment, please visit the TI Bluetooth Stack - BluetopiaPM Build Process page for further information. This does not have to be done to run the out of box AM335x Wilink8 Demo applications as the BluetopiaPM installation comes with pre-built binaries for Wilink8.OverviewBluetopiaBluetopia is a low-level Bluetooth Protocol Stack. Bluetopia is designed to be small in code space and RAM so that it can be ran on small embedded platforms where memory is limited. The Bluetopia stack is limited in that only one application has access to the Bluetooth Controller at a time. This can make development difficult and complicated if multiple profiles are using the Bluetooth Controller concurrently.Bluetopia Platform ManagerBluetopia Platform Manager (Bluetopia PM) is a service that allows multiple applications to access the Bluetooth link concurrently. This allows developers to create multiple independent applications that each use the Bluetooth link. Take for example a Head Set running Linux that uses the Hands-Free Profile and also supports A2DP Sink audio playback. Using Bluetopia a development team would have to write one application that handles both Hands-Free Events and A2DP Events. With Bluetopia PM the team could write two independent applications: one to handle Hands-Free Events and one to handle A2DP Events.Bluetopia PM also provides features that simplify the management of device connections:1. It stores pairing and link key information for each device connection in persistent memory2. It automatically caches discovered device information such as the device name and class of the device3. It automatically caches remote device service discovery information for quick access to a device's services without having to retrieve them again from the remote deviceA convenient API is provided to access cached device information.TI Bluetooth Stack (based on Bluetopia) is provided with the WL18xx and CC256x devices. It is composed of Bluetooth protocol stack, Bluetooth profiles stack and Platform Manager. RequirementsHardware1x AM335x Evaluation Module (/tool/tmdxevm3358) or AM437x Evaluation Module (/tool/tmdsevm437x)For Wilink8: WL1837 (/tool/wl1837modcom8i?keyMatch=wilink%208&tisearch=Search-EN-Everything) or WL1835 (/tool/wl1835modcom8 b?keyMatch=wl1835&tisearch=Search-EN)For CC256x: CC2564MODNEM (/tool/cc2564modnem) or CC2564MODNEM (/product/cc2564moda/description) or CC2564C QFN (http:// /tool/cc256xcqfn-em)1x RS-232 console wire to access CLI interface on the platform from PCBluetooth remote devices (such as a phone or another EVM) that should support the above profiles, preferably with the opposite role for some cases, for demonstration purposesNote: When using a CC256x controller you need to perform the following Hardware Modifications in order to make it compatible to the Sitara platforms.CC256X Configuration (/index.php/SDMMC_Adapter_Configuration#CC256X_Configuration)Note: Hardware requirements may depend on the application, specific demos will have detailed hardware configurations.AM335x Linux SDK (/tool/PROCESSOR-SDK-AM335X) or image for flashing onto an SD cardWilink 8 Bluetooth Add-On (/tool/TI-BT-4-2-STACK-LINUX-ADDON)TI EVM (AM335x, AM437x, AM57x) Bluetooth setup script can be downloaded from the following <zip file>PC Terminal software (e.g. Putty or TeraTerm).Most recently updated BTS script from WL18xx-BT-SP (/tool/WL18xx-BT-SP) (see note below).Note: Download the latest WL18xx Bluetooth Firmware Script (BTS script) from: WL18xx-BT-SP (/tool/WL18xx-BT-SP). Read the license agreement and follow the installation instructions in the previous link. The script will be automatically be downloaded to the WL18xx device whenever the stack power up the device.Note: When using a CC256x controller you will need to copy the init scripts. Follow the instructions in CC256x Initscripts (/index.php/TI_Bluetooth_St ack_for_WL18xx_-_Build_Process#CC256x_Init-scripts)TI Bluetooth Stack (based on Bluetopia) is provided with the WL18xx or CC256x devices. It is composed of Bluetooth protocol stack, Bluetooth profiles stack and Platform Manager. The Bluetooth Add-On Packages and can be re-built and used with any Linux and WL18xx or CC256x platform but for convenience for those using an AM335x standard SDK the following pre-built packages are available for download. The stack is not part of platform SDK but is available as an add-on which can be downloaded from the Software Requirements (http://proc /index.php/TI_Bluetooth_Stack_for_WL18xx_-_Getting_Started_Guide#Software) section.The package is downloaded as tarball and should be extracted (in a Linux machine).$ AM335xBluetopiaLinuxProduction-4.2.1.0.1.0-linux-installer.tar.gzThe tarball includes 2 Linux installers: for 32b and 64b release. Please use the right one according to your working station type and execute it (the following demonstrates the 64b case): $ chmod +x ./AM335xBluetopiaLinuxProduction-4.2.1.0.1.0-linux-x64-installer.run$ ./AM335xBluetopiaLinuxProduction-4.2.1.0.1.0-linux-x64-installer.runWhen the installer completes, the installation directory should include Bluetopia Platform Manager (BluetopiaPM) Binaries, Sources and Documentation.Binaries - includes pre-compiled sample applications, BluetopiaPM server daemon and BluetopiaPM Client libraries.Sources - platform specific files (to enable recompiling for different platforms) and sample applications code.Documentation - License docs, users guides and API specifications.The installation directory can be updated during the installer execution. The default is~/AM335xBluetopiaLinuxProduction-4.2.1.0.1.0/For more details on the distribution content, please refer to the Bluetopia Platform Manager Architecture section.Once the SDK is installed and compiled and the Bluetooth Add-on is installed, the SD card needs to be created. This can be achieved by using a script to create the SD card (http://proces /index.php/Processor_SDK_Linux_create_SD_card_script).Once the SD card is ready, You will need to build the Add-on and copy the files to your SD-card. Source code for each sample can be found in the [install-dir]/BluetopiaPM/sample directory. To modify and re-build the samples follow the instructions in Build the Bluetopia PM (/index.php/TI_Bluetooth_Stack_for_WL18xx_-_Build_P rocess)Note: If using the WL183x there are pre-built applications that are ready to run out of the box.Adding the Bluetopia files to the SD card requires copying over 4 main components: the Sample Applications, Gstreamer Plugin, VNET Plugin, and Init-scripts. Follow the instructions below in order to install the Bluetopia Stack into the imaged SD card.SoftwareGetting StartedStep 1. Installing Bluetopia Platform ManagerStep 2. SD card creationBuild and export the Bluetopia PMCopy the BluetopiaPM server (SS1BTPM) and the provided Sample applications that were builtsudo mkdir [target-root]/home/root/BluetopiaPMsudo cp -rf <INSTALLATION_DIR>/BluetopiaPM/bin [target-root]/home/root/BluetopiaPM/BluetopiaPM include a GStreamer Plugin that should be copied to the target rootfs, The GStreamer is being used in AUD Demo applicationsudo cp <INSTALLATION_DIR>/BluetopiaPM/lib/libgstss1bluetooth.so [target-root]/usr/lib/gstreamer-1.0/Note: For 4.2 releases please see the release notes as this feature not included in the release. If needed, you can obtain the plugin from the 4.0 release available from the 4.0Download Page (/tool/TI-BT-STACK-LINUX-ADDON)BluetopiaPM include a VNET Plugin that should be copied to the target rootfs, The VNET is being used in PAN Demo applicationsudo mkdir -p [target-root]/home/root/BluetopiaPM/Bluetopia/VNET/driversudo cp -rf <INSTALLATION_DIR>/BluetopiaPM/Bluetopia/VNET/driver/VNETInst [target-root]/home/root/BluetopiaPM/Bluetopia/VNET/driver/ sudo cp -rf <INSTALLATION_DIR>/BluetopiaPM/Bluetopia/VNET/*.ko [target-root]/home/root/BluetopiaPM/Bluetopia/VNET/The VoLE Demo application utilizes a python script in order to decode, format and analyze the audio data.sudo cp <INSTALLATION_DIR>/BluetopiaPM/sample/LinuxVoLE/audio_frame_linux.py [target-root]/home/root/BluetopiaPM/binThe bt-en.sh script, downloaded from the Software Requirements (/index.php/TI_Bluetooth_Stack_for_WL18xx_-_Getting_Started_Guide#Software%7C) section which creates a custom configuration file based on the board you're using.Note: If using a Beaglebone see the page on patching the device tree (/index.php/WL18xx_Platform_Integration_Guide#Appendix_A:_Device_Tree_fi le_-_patching_and_updating) and skip the bt-en.sh setup script steps below.First unzip the file Downloaded file and then copy it to the target platform:sudo cp Downloads/bt-en.sh [target-root]/home/root/BluetopiaPM/Navigate to the correct directory on the target platform:cd /home/root/BluetopiaPM/Update the scripts permissions:chmod +x bt-en.shThen run the script:./bt-en.shWhen using a custom platform, you'll need to create a similar script with your platform specific settings. As an example, you'll have to update the following variables:tty andgpioNote, this includes the:echo gpiostatement at the start of the scriptEx:1. Create a new script file:Step 3. Sample ApplicationsGstreamer PluginVNET PluginVoice Over BLE Python ScriptBluetooth Hardware configuration scriptvi bt-en.sh2. Copy the following into the empty file:echo 16 > /sys/class/gpio/export echo out > /sys/class/gpio/gpio16/directionecho 1 > /sys/class/gpio/gpio16/value echo "Done enabling BT"gpio="nshutdown_gpio=16" tty="tty=/dev/ttyS3" flow="flow_cntrl=1"baud_rate="baud_rate=3000000" mkdir /home/root/tibtecho $gpio > /home/root/tibt/config echo $tty >> /home/root/tibt/config echo $flow >> /home/root/tibt/config echo $baud_rate >> /home/root/tibt/config3. Update the gpio and tty variables to match your platform, in this example we're using GPIO 16 and tty S3.4. Update the scripts permissions:chmod +x bt-en.sh5. Run the script:./bt-en.shBefore the stack can be used make sure to have an updated Bluetooth Script (BTS) on your target platform. The latest BTS file and installation instructions can be found in WL18xx-BT-SP (/tool/WL18xx-BT-SP) and can be copied directly to the SD card's firmware directory as shown below:sudo cp -rf TIInit_X.Y.Z.bts [target-root]/lib/firmware/In order to add support for AVPR , BLE or BR/EDR for the CC256x devices the CC256x Service Pack User's Guide (/index.php/CC256x_Service_Pack_Us er%27s_Guide) should be followed.Once the code is copied. Plug in the RS-232 0 port to a pc via NULL modem and then look at the Device manager for Communications Port (COM x) under Ports (COM & LPT). Attach a terminal program like PuTTY to the serial port (COM x) for the board, x means which COM is open for Communications Port in Device Manager. The serial parameter to use is 115200Baud rate. Once connected, Turn on the device Power button and you should see the am335x getting initialized on the terminal.Arago Project am335x-evm /dev/ttyS0 Arago 2015.05 am335x-evm /dev/ttyS0 am335x-evm login:When the initialization is over, type root in order to use the file system.Note: The serial port may differ for different platforms. E.g. AM437x will be /dev/ttyS1am335x-evm login: root root@am335x-evm:~#Now that you have installed Platform Manager to your host platform and copied relevant binaries (for this example at least SS1BTPM and LinuxSPPM should be copied) and init-scripts to your target, let's demonstrate running a Platform Manager application. The following should be done on the target (using USB or Ethernet connection):# cd /home/root/BluetopiaPM/bin # ./SS1BTPM & # ./LinuxSPPMYou should now see LinuxSPPM's menu displayed in the terminal. Now let's try to initialize the Bluetopia PM Server in LinuxSPPM and turn on the Bluetooth Controller.SPPM>Initialize 1SPPM>SetDevicePower 1If all went well you should see a "Device Powered On" message in the terminal. Congratulations, you have just run your first Platform Manager application! For more detailed information on using the LinuxSPPM Demo and for other Demo Guides, refer to Bluetopia Platform Manager Demo Guide. Next we'll go over the basics of Bluetopia Platform Manager's sample applications,Step 4. Installing updated Firmware Service Pack (Init-scripts)Step 5. Terminal ConnectionStep 6. Running a Sample ApplicationSamples are provided with the Bluetopia Platform Manager distribution to demonstrate how to use the Bluetopia PM modules. Each sample provides a command-line interface which can be used to send commands to the PM Server. The sample application commands encapsulate Bluetopia API commands and demonstrate how to use common API functions. The samples also display events and event data when an event is received from the PM Server.The samples are provided to help the end user get started with application development in PM. The samples are not ready-to-use production applications, as an application like this depends on the project-specific requirements. However, the samples can be used as a starting point for application development. We'll now go over re-building a sample which will help with getting started with application development in PM.For more information on how to use a specific sample, also referred to as a demo, refer to the Bluetopia Platform Manager Demo Guide.{{1. switchcategory:MultiCore=For technical support onMultiCore devices, pleasepost your questions in theC6000 MultiCore ForumFor questions related tothe BIOS MultiCore SDK(MCSDK), please use theBIOS ForumPlease post only comments related to the article TI Bluetooth Stack for WL18xx - Getting Started Guide here.Keystone=For technicalsupport onMultiCore devices,please post yourquestions in theC6000 MultiCoreForumFor questionsrelated to theBIOS MultiCoreSDK (MCSDK),please use theBIOS ForumPlease post onlycomments related to thearticle TI Bluetooth Stackfor WL18xx - GettingStarted Guide here.C2000=Fortechnicalsupport onthe C2000pleasepost yourquestionson TheC2000Forum.Pleasepost onlycommentsabout thearticle TIBluetoothStack forWL18xx -GettingStartedGuidehere.DaVinci=Fortechnicalsupport onDaVincopleasepost yourquestions onThe DaVinciForum. Pleasepost onlycommentsabout thearticle TIBluetoothStack forWL18xx -GettingStarted Guidehere.MSP430=Fortechnicalsupport onMSP430please postyourquestions onThe MSP430Forum.Please postonlycommentsabout thearticle TIBluetoothStack forWL18xx -GettingStartedGuide here.OMAP35x=Fortechnicalsupport onOMAP pleasepost yourquestions onThe OMAPForum. Pleasepost onlycommentsabout thearticle TIBluetoothStack forWL18xx -GettingStarted Guidehere.OMAPL1=Fortechnicalsupport onOMAP pleasepost yourquestions onThe OMAPForum.Please postonlycommentsabout thearticle TIBluetoothStack forWL18xx -GettingStartedGuide here.MAVRK=Fortechnicalsupport onMAVRKplease postyourquestionson TheMAVRKToolboxForum.Please postonlycommentsabout thearticle TIBluetoothStack forWL18xx -GettingStartedGuide here.For technical suplease post youquestions atPlease post oncomments abouarticle TI BluetStack for WL1Getting StarteGuide here.}}LinksAmplifiers & LinearAudioBroadband RF/IF & Digital Radio Clocks & TimersData Converters DLP & MEMSHigh-ReliabilityInterfaceLogicPower ManagementProcessorsARM ProcessorsDigital Signal Processors (DSP)Microcontrollers (MCU)OMAP Applications ProcessorsSwitches & MultiplexersTemperature Sensors & Control ICsWireless ConnectivityRetrieved from "https:///index.php?title=TI_Bluetooth_Stack_for_WL18xx_-_Getting_Started_Guide&oldid=226535"This page was last edited on 9 April 2017, at 19:41.Content is available under Creative Commons Attribution-ShareAlike unless otherwise noted.Bluetopia PM Samples。

TI mmWave Training mmWave DemoContents•Overview•Requirements•Software setup–Pre-requisites–Downloading the Lab Project–Building the project•Hardware setup–Preparing the EVM–Connecting the EVM•Running the Demo2Lab Overview•Configurable visualization tool forprocessed radar data•The following plots are available:−Scatter Plot−Range Profile−Noise Profile−Range Azimuth Heat Map−Range Doppler Heat Map−Statistics31. Requirements•Software–Pre-requisites•Latest TI mmWave SDK and all related dependencies installed as mentioned in the mmWave SDK release notes.–Google Chrome with TI Cloud Agent Extension•For running the mmWave Demo Visualizer•Download from TI Cloud Agent or install when accessing the demo–mmWave SDK Demo•Download from TI Resource Explorer–UniFlash•For flashing firmware images onto•Download from /tool/uniflash–XDS110 Drivers•For EVM XDS device support•Included with CCS Installation, or standalone through TI XDS Emulation Software •Hardware–xWR14xx EVM–Micro USB cable (included in the EVM package)–5V/2.5A Power Supply•Purchase from Digikey4Steps1.Pre-requisites2.DownloadDemoproject3.Build Demoproject4.Preparingthe EVM5.Running theDemo51. Pre-requisites1. Install Pre-requisites 2 3 4 5•It is assumed that you have the latest TI mmWaveSDK and all the related tools installed as mentionedin the mmWave SDK release notes.–The mmWave SDK release notes include the linksfor downloading the required versions of the abovetools.–Helpful Tips•Please make sure that any existing PERL installationsare removed from the PC before installing the versionof PERL listed in the SDK release notes•After you’ve downloaded and saved CRC.pm, locatethe saved file and remove the .txt extension if it isthere. Please ensure that the file has a .pm extensionand not a .txt extension at the end•XDC tools are provided as a zip file which needs tobe extracted in the TI install directory (typically C:\ti)–Note: For this video, we used mmWave SDK 1.0.0.5and the snapshot shown here corresponds tommWave SDK 1.0.0.5•If you have already installed the mmWave SDK andall the required tools, you can move on to the nextstep i.e. downloading the lab on to your machine.6Steps1.Pre-requisites2.DownloadDemoproject3.Build Demoproject4.Preparingthe EVM5.Running theDemo7•The mmWave projects areavailable under mmWave Trainingin CCS Resource Explorer.•To download the mmWave demo,start CCS v7.1 (or later) and selectView►Resource Explorer toopen the Resource Explorer.•In the Resource Explorer Window,select Software►mmWaveTraining►Demos.8•Select the mmWave SDK demo in the left view.•The right view shows the contents of the Lab which contains the CCS Project and the PC GUI.•Click on the Download and Install button in the top right corner as shown.•Select the Make Available Offline option from the drop down to start downloading the Lab.9Click here to download the project on to your PC•The project will be downloaded in C:\ti\mmwave_training•Select the CCS Project file in the left view •Click on the Import to IDE button which should be visible in the right side view after a successful download.•This copies the project in the user’s workspace and imports it into the CCS project explorer.–It is important to note that the copycreated in the workspace is the one that gets imported in CCS. The original project downloaded in mmwave_training is not touched.10Click here to import the project2. Download - continued•After successfully completing the Import to IDE operation, the project should be visible in CCS Project Explorer as shown here.•At this point, we have successfullydownloaded the mmWave demo and imported it in CCS.•We are ready to move on to the next step i.e. Building the project.1112Download Demo project3 4 5Steps1.Pre-requisites2.DownloadDemoproject3.Build Demoproject4.Preparingthe EVM5.Running theDemo123. Build the Lab•With the mmw project selected in Project Explorer, open the Project menu and select Rebuild Project .–Selecting Rebuild instead of Build ensures that the project is always re-compiled. This is especially important in case the previous build failed with errors.•On successful completion of the build, youshould see the output in CCS console as shown here and the following two files should be produced in the project debug directory–xwr14xx_mmw_mss.xer4f –xwr14xx_mmw_mss.bin•If the build fails with errors, please ensure that all the pre-requisites are installed as mentioned in the mmWave SDK release notes.131 23Build Demo project4 5Steps1.Pre-requisites2.DownloadDemoproject3.Build Demoproject4.Preparingthe EVM5.Running theDemo14• There are two ways to execute the compiled code on the EVM: –Deployment mode: Flashing the binary (.bin image) on to the EVM serial flash •In this mode, the EVM boots autonomously from flash and starts running the bin image.–Debug mode: Downloading and running the executable (.xer4f image) from CCS.•You will need to flash a small CCS debug firmware on the EVM (one time) to allowconnecting with CCS. This debug firmware image is provided with the mmWave SDK.–As a recap, the build process in Step 3 produces both the .bin and .xer4f images. •This presentation explains the second method i.e. Debug mode (CCS).–To prepare the EVM for debug mode, we start with flashing the CCS debug firmware image.–Please note that the same flashing process can be used to flash the Lab binary to run it in deployment mode.15•Power on the EVM using a 5V/2.5A power supply.•Connect the EVM to your PC and check the COM ports in Windows Device Manager•The EVM exports two virtual COM ports as shown below:–XDS110 Class Application/User UART (COM UART ):•Used for passing configuration data and firmware to the EVM–XDS110 Class Auxiliary Data Port (COM AUX )•Used to send processed radar data output•Note the COM UART and COM AUX port numbers, as they will be used later for flashing and running the Lab.16COM UART : COM38 COM AUX : COM39•The actual port numbers on your machine may be different1.Put the EVM in flashing mode by connectingjumpers on SOP0 and SOP2 as shown in theimage.2.Open the UniFlash tool3.In the New Configuration section, locateand select the appropriate device (xWR14xx)4.Click Start to proceed175.In the Program tab, browse and locate the Radar SS and MSS images shown below:6.In the Settings & Utilities tab, fill the COM Port text box with the Application/User UART COM port number (COM UART ) noted earlier1.7.Return to the Program tab, power cycle the device and click on Load Images8.When the flash procedure completes, UniFlash’s console should indicate: [SUCCESS] Program Load completed successfully9.Power off the board and remove the jumper from only header SOP2 (this puts the board back in functional mode)18ImageLocationMeta Image 1/RadarSSC:\ti\mmwave_sdk_<ver>\firmware\radarss\xwr12xx_xwr14xx_radarss.bin Meta Image 2/MSSC:\ti\mmwave_sdk_<ver>\packages\ti\utils\ccsdebug\xwr14xx_ccsdebug_mss.binLeave this empty Leave this emptySteps1.Pre-requisites2.DownloadLab project3.Build Labproject4.Preparingthe EVM5.Running theDemo195.1 Connecting EVM to CCS•It is assumed that you were able to download and build the Lab in CCS (completed steps 1, 2 and 3)•To connect the Radar EVM to CCS, we need to create a target configuration–Go to File ► New ► New Target Configuration File–Name the target configuration accordingly and check the “Use shared location” checkbox. Press Finish–In the configuration editor window:•Select “Texas Instruments XDS110 USB Debug Probe” for Connection•Select IWR1443 or AWR1443 in the Board or Device list•Press the Save button to save the target configuration.•You can press the Test Connection button to check the connection with the board.201 2 3 45. Running theDemo5.1 Connecting - continued•Go to View ► Target Configurations to open the target configuration window.•You should see your target configuration under User Defined configurations.•Right click on the target configuration and select Launch Select Configuration .•This will launch the target configuration in the debug window.•Select the Texas Instruments XDS110 USB Debug probe and press the Connect Target button211 2 3 4 5. Running the Demo Click here to Connect to the target CPU•With the target connected, click on theLoad button in the toolbar.•In the Load Program dialog, press theBrowse Project button .Load Program•Select the lab executable (.xer4f) asshown and press OK.•Press OK again in the Load Programdialog.22•With the executable loaded, press theRun/Resume button•The program should start executing andRun Programgenerate console output as shown.•If everything goes fine, you should seethe “CLI is operational” message whichindicates that the program is ready andwaiting for the sensor configuration.23ing Google Chrome, navigate to the following URL:https:///mmWaveDemoVisualizer–Alternatively, go to https:///gallery and search for “mmWave Demo Visualizer”2.If prompted, follow the on-screen instructions for installing TI Cloud Agent3.Once the demo is loaded, go to Options → Serial Port4.In the serial port window, enter the appropriate port in each of the drop down menus basedon your port numbers from Step 2245.Click on Configure and the demo will automatically connect to the EVM–Not connected: Connected:–If the connection fails, try clicking on the connection icon in the bottom left corner6.Select the appropriate mmWave device from the Platform dropdown menue the available options to create the desired configuration–Additional details about the configuration parameters can be found in the mmWave Demo Visualizer User Guide8.When ready to send the configuration, click on Send Config To mmWaveDevice9.Click on the Plots tab to view the plots that were selected to be shown10.Move a highly reflective object in front of the EVM and see how the demoresponds2526Learn more about TI mmWave Sensors•Learn more about xWR1x devices, please visit the product pages–IWR1443: /product/IWR1443–IWR1642: /product/IWR1642–AWR1443: /product/AWR1443–AWR1642: /product/AWR1642•Get started evaluating the platform with xWR1x EVMs, purchase EVM at –IWR1443 EVM: /tool/IWR1443BOOST–IWR1642 EVM: /tool/IWR1642BOOST–AWR1443 EVM: /tool/AWR1443BOOST–AWR1642 EVM: /tool/AWR1642BOOST•Download mmWave SDK @ /tool/MMWAVE-SDK•Ask question on TI’s E2E forum mmWave Sensors forum @https:///support/sensor/mmwave_sensors/2728。

2018年8月DocID029937 Rev 1 [English Rev 2]1/22AN4943应用笔记在STM32L496xx/L4A6xx/L4Rxxx/L4Sxxx 微控制器上使用Chorm-ART Accelerator ™来刷新LCD-TFT 显示器前言本应用笔记旨在说明如何使用STM32L496xx/L4A6xx/L4Rxxx/L4Sxxx 微控制器上的Chrom-ART Accelerator™，通过FSMC 接口刷新LCD-TFT 显示屏。

STM32L496xx/L4A6xx/L4Rxxx/L4Sxxx 微控制器实现Chrom-Art Accelerator™ （DMA2D ），即专用于图像处理的专用DMA 。

它可以执行下列操作：•用特定颜色填充目标图像的一部分或全部•通过像素格式转换将源图像的一部分或全部复制到目标图像的一部分或全部中•将像素格式不同的两个源图像部分和/或全部混合，再将结果复制到颜色格式不同的部分或整个目标图像中。

在STM32L496xx/L4A6xx/L4Rxxx/L4Sxxx 微控制器上，使用灵活的静态存储控制器（FSMC ）通过并行接口访问LCD-TFT 显示屏。

本应用笔记说明了以下内容：•如何通过FSMC 接口连接LCD-TFT 显示屏•如何为LCD-TFT 显示屏刷新配置DMA2D•如何使用DMA2D 字节重新排序功能直接驱动Intel 8080显示器。

要充分利用本应用笔记，用户应熟悉STM32 Chrom-ART Accelerator™（DMA2D ），如STM32L4x6基于Arm ®的高级32位MCU 参考手册（RM0351）和STM32L4Rxxx/L4Sxxx 基于Arm ®的高级32位MCU 参考手册（RM0432）中所述内容（可从意法半导体的网站 获取）。

表1. 适用产品类型产品线和部件号微控制器STM32L496AE 、STM32L496AG 、STM32L496QE 、STM32L496QG 、STM32L496RE 、STM32L496RG 、STM32L496VE 、STM32L496VG 、STM32L496ZE 、STM32L496ZGSTM32L4A6AG 、STM32L4A6QG 、STM32L4A6RG 、STM32L4A6VG 、STM32L4A6ZGSTM32L4R5/S5产品线，STM32L4R7/S7产品线，STM32L4R9/S9产品线目录AN4943目录1参考文档 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Chrom-ART Accelerator™（DMA2D）应用用例概述 . . . . . . . . . . . . . . . 63通过FSMC访问LCD-TFT显示屏 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73.1硬件接口描述 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73.2显示指令集（DCS）软件界面 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.3通过STM32L496xx/L4A6xx/L4Rxxx/L4Sxxx微控制器控制D/CX信号 . . . . . 94STM32CubeL4中的Chrom-ART Accelerator™（DMA2D）配置 . . . . . . 114.1LCD部分刷新 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115新的DMA2D功能可支持Intel 8080显示器 . . . . . . . . . . . . . . . . . . . . . . . . . 135.1Intel 8080接口颜色编码 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135.2DMA2D重新排序功能 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165.2.1红蓝交换 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165.2.2字节交换 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165.3DMA2D重新排序用例示例 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175.3.116位FSMC数据总线接口上的24bpp/18bpp . . . . . . . . . . . . . . . . . . . . . . 175.3.28位FSMC数据总线接口上的24bpp/18bpp . . . . . . . . . . . . . . . . . . . . . . . 185.3.3通过8位FSMC数据总线接口的16bpp . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 6结论 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 7版本历史 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212/22DocID029937 Rev 1 [English Rev 2]AN4943表格索引表格索引表1.适用产品. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1表2.FSMC 信号. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7表3.LCD-TFT 信号. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7表4.最小可使用FSMC地址位取决于图像大小（16位RGB565访问） . . . . . . . . . . . . . . . . . . . . 10表5.交换操作. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16表6.文档版本历史 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21表7.中文文档版本历史. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21DocID029937 Rev 1 [English Rev 2]3/22图片目录AN4943图片目录图1.显示应用典型用例. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6图2.显示总线接口规范. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8图3.用于LCD-TFT显示屏访问的存储器映射 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9图4.通过FSMC接口自动控制LCD-TFT显示屏数据/指令 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10图5.16位接口上的24bpp颜色编码. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14图6.8位接口上的16bpp颜色编码. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15图7.8位接口上的24bpp颜色编码. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15图8.支持16位接口上24bpp的DMA2D操作. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17图9.支持8位接口上24bpp的DMA2D操作. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18图10.支持8位接口上16bpp的DMA2D操作. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 4/22DocID029937 Rev 1 [English Rev 2]AN4943参考文档1 参考文档以下文档可从获得。

mmdetection float16训练MMDetection 是基于深度学习的目标检测框架，它为研究人员和开发人员提供了训练和测试各种目标检测模型的工具。

而float16 是一种低精度浮点数表示形式，它可以在加速硬件上进行快速计算，同时降低内存消耗。

本文将逐步介绍如何使用MMDetection 进行float16 训练。

首先，我们需要安装和配置MMDetection。

在安装MMDetection 之前，我们需要确保系统上已经安装了Python 3.6+、PyTorch 1.3+和CUDA 10.0+。

然后，我们可以使用以下命令克隆MMDetection 的代码仓库：git clone接下来，我们需要安装MMDetection 所需的依赖库。

进入MMDetection 的根目录并执行以下命令：cd mmdetectionpip install -r requirements/build.txtpip install -v -e .完成安装后，我们可以执行以下命令来验证MMDetection 是否正确安装：python tools/train.pyconfigs/faster_rcnn/faster_rcnn_r50_fpn_1x_coco.py如果没有出现错误信息，则说明MMDetection 已经正确安装。

接下来，我们需要修改配置文件以进行float16 训练。

配置文件通常位于`configs/` 目录下，例如`configs/faster_rcnn/faster_rcnn_r50_fpn_1x_coco.py`。

我们可以使用文本编辑器打开该文件，找到以下代码行：# FP16 training config parameterfp16 = dict(enabled=False, loss_scale=None)将`enabled` 的值修改为`True`，即`enabled=True`。

这将启用float16 训练。

a7680c指令流程下载温馨提示:该文档是我店铺精心编制而成，希望大家下载以后，能够帮助大家解决实际的问题。

文档下载后可定制随意修改，请根据实际需要进行相应的调整和使用，谢谢!并且，本店铺为大家提供各种各样类型的实用资料，如教育随笔、日记赏析、句子摘抄、古诗大全、经典美文、话题作文、工作总结、词语解析、文案摘录、其他资料等等，如想了解不同资料格式和写法，敬请关注!Download tips: This document is carefully compiled by theeditor. I hope that after you download them,they can help yousolve practical problems. The document can be customized andmodified after downloading,please adjust and use it according toactual needs, thank you!In addition, our shop provides you with various types ofpractical materials,such as educational essays, diaryappreciation,sentence excerpts,ancient poems,classic articles,topic composition,work summary,word parsing,copy excerpts,other materials and so on,want to know different data formats andwriting methods,please pay attention!1. 准备工作确保你已经熟悉了 A7680C 芯片的相关规格和手册。

© 2017 NXP B.V.SCM-i.MX 6 Series Yocto Linux User'sGuide1. IntroductionThe NXP SCM Linux BSP (Board Support Package) leverages the existing i.MX 6 Linux BSP release L4.1.15-2.0.0. The i.MX Linux BSP is a collection of binary files, source code, and support files that can be used to create a U-Boot bootloader, a Linux kernel image, and a root file system. The Yocto Project is the framework of choice to build the images described in this document, although other methods can be also used.The purpose of this document is to explain how to build an image and install the Linux BSP using the Yocto Project build environment on the SCM-i.MX 6Dual/Quad Quick Start (QWKS) board and the SCM-i.MX 6SoloX Evaluation Board (EVB). This release supports these SCM-i.MX 6 Series boards:• Quick Start Board for SCM-i.MX 6Dual/6Quad (QWKS-SCMIMX6DQ)• Evaluation Board for SCM-i.MX 6SoloX (EVB-SCMIMX6SX)NXP Semiconductors Document Number: SCMIMX6LRNUGUser's GuideRev. L4.1.15-2.0.0-ga , 04/2017Contents1. Introduction........................................................................ 1 1.1. Supporting documents ............................................ 22. Enabling Linux OS for SCM-i.MX 6Dual/6Quad/SoloX .. 2 2.1. Host setup ............................................................... 2 2.2. Host packages ......................................................... 23.Building Linux OS for SCM i.MX platforms .................... 3 3.1. Setting up the Repo utility ...................................... 3 3.2. Installing Yocto Project layers ................................ 3 3.3. Building the Yocto image ....................................... 4 3.4. Choosing a graphical back end ............................... 4 4. Deploying the image .......................................................... 5 4.1. Flashing the SD card image .................................... 5 4.2. MFGTool (Manufacturing Tool) ............................ 6 5. Specifying displays ............................................................ 6 6. Reset and boot switch configuration .................................. 7 6.1. Boot switch settings for QWKS SCM-i.MX 6D/Q . 7 6.2. Boot switch settings for EVB SCM-i.MX 6SoloX . 8 7. SCM uboot and kernel repos .............................................. 8 8. References.......................................................................... 8 9.Revision history (9)Enabling Linux OS for SCM-i.MX 6Dual/6Quad/SoloX1.1. Supporting documentsThese documents provide additional information and can be found at the NXP webpage (L4.1.15-2.0.0_LINUX_DOCS):•i.MX Linux® Release Notes—Provides the release information.•i.MX Linux® User's Guide—Contains the information on installing the U-Boot and Linux OS and using the i.MX-specific features.•i.MX Yocto Project User's Guide—Contains the instructions for setting up and building the Linux OS in the Yocto Project.•i.MX Linux®Reference Manual—Contains the information about the Linux drivers for i.MX.•i.MX BSP Porting Guide—Contains the instructions to port the BSP to a new board.These quick start guides contain basic information about the board and its setup:•QWKS board for SCM-i.MX 6D/Q Quick Start Guide•Evaluation board for SCM-i.MX 6SoloX Quick Start Guide2. Enabling Linux OS for SCM-i.MX 6Dual/6Quad/SoloXThis section describes how to obtain the SCM-related build environment for Yocto. This assumes that you are familiar with the standard i.MX Yocto Linux OS BSP environment and build process. If you are not familiar with this process, see the NXP Yocto Project User’s Guide (available at L4.1.15-2.0.0_LINUX_DOCS).2.1. Host setupTo get the Yocto Project expected behavior on a Linux OS host machine, install the packages and utilities described below. The hard disk space required on the host machine is an important consideration. For example, when building on a machine running Ubuntu, the minimum hard disk space required is about 50 GB for the X11 backend. It is recommended that at least 120 GB is provided, which is enough to compile any backend.The minimum recommended Ubuntu version is 14.04, but the builds for dizzy work on 12.04 (or later). Earlier versions may cause the Yocto Project build setup to fail, because it requires python versions only available on Ubuntu 12.04 (or later). See the Yocto Project reference manual for more information.2.2. Host packagesThe Yocto Project build requires that the packages documented under the Yocto Project are installed for the build. Visit the Yocto Project Quick Start at /docs/current/yocto-project-qs/yocto-project-qs.html and check for the packages that must be installed on your build machine.The essential Yocto Project host packages are:$ sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib build-essential chrpath socat libsdl1.2-devThe i.MX layers’ host packages for the Ubuntu 12.04 (or 14.04) host setup are:$ sudo apt-get install libsdl1.2-dev xterm sed cvs subversion coreutils texi2html docbook-utils python-pysqlite2 help2man make gcc g++ desktop-file-utils libgl1-mesa-dev libglu1-mesa-dev mercurial autoconf automake groff curl lzop asciidocThe i.MX layers’ host packages for the Ubuntu 12.04 host setup are:$ sudo apt-get install uboot-mkimageThe i.MX layers’ host packages for the Ubuntu 14.04 host s etup are:$ sudo apt-get install u-boot-toolsThe configuration tool uses the default version of grep that is on your build machine. If there is a different version of grep in your path, it may cause the builds to fail. One workaround is to rename the special versi on to something not containing “grep”.3. Building Linux OS for SCM i.MX platforms3.1. Setting up the Repo utilityRepo is a tool built on top of GIT, which makes it easier to manage projects that contain multiple repositories that do not have to be on the same server. Repo complements the layered nature of the Yocto Project very well, making it easier for customers to add their own layers to the BSP.To install the Repo utility, perform these steps:1.Create a bin folder in the home directory.$ mkdir ~/bin (this step may not be needed if the bin folder already exists)$ curl /git-repo-downloads/repo > ~/bin/repo$ chmod a+x ~/bin/repo2.Add this line to the .bashrc file to ensure that the ~/bin folder is in your PATH variable:$ export PATH=~/bin:$PATH3.2. Installing Yocto Project layersAll the SCM-related changes are collected in the new meta-nxp-imx-scm layer, which is obtained through the Repo sync pointing to the corresponding scm-imx branch.Make sure that GIT is set up properly with these commands:$ git config --global "Your Name"$ git config --global user.email "Your Email"$ git config --listThe NXP Yocto Project BSP Release directory contains the sources directory, which contains the recipes used to build, one (or more) build directories, and a set of scripts used to set up the environment. The recipes used to build the project come from both the community and NXP. The Yocto Project layers are downloaded to the sources directory. This sets up the recipes that are used to build the project. The following code snippets show how to set up the SCM L4.1.15-2.0.0_ga Yocto environment for the SCM-i.MX 6 QWKS board and the evaluation board. In this example, a directory called fsl-arm-yocto-bsp is created for the project. Any name can be used instead of this.Building Linux OS for SCM i.MX platforms3.2.1. SCM-i.MX 6D/Q quick start board$ mkdir fsl-arm-yocto-bsp$ cd fsl-arm-yocto-bsp$ repo init -u git:///imx/fsl-arm-yocto-bsp.git -b imx-4.1-krogoth -m scm-imx-4.1.15-2.0.0.xml$ repo sync3.2.2. SCM-i.MX 6SoloX evaluation board$ mkdir my-evb_6sxscm-yocto-bsp$ cd my-evb_6sxscm-yocto-bsp$ repo init -u git:///imx/fsl-arm-yocto-bsp.git -b imx-4.1-krogoth -m scm-imx-4.1.15-2.0.0.xml$ repo sync3.3. Building the Yocto imageNote that the quick start board for SCM-i.MX 6D/Q and the evaluation board for SCM-i.MX 6SoloX are commercially available with a 1 GB LPDDR2 PoP memory configuration.This release supports the imx6dqscm-1gb-qwks, imx6dqscm-1gb-qwks-rev3, and imx6sxscm-1gb-evb. Set the machine configuration in MACHINE= in the following section.3.3.1. Choosing a machineChoose the machine configuration that matches your reference board.•imx6dqscm-1gb-qwks (QWKS board for SCM-i.MX 6DQ with 1 GB LPDDR2 PoP)•imx6dqscm-1gb-qwks-rev3 (QWKS board Rev C for SCM-i.MX 6DQ with 1GB LPDDR2 PoP) •imx6sxscm-1gb-evb (EVB for SCM-i.MX 6SX with 1 GB LPDDR2 PoP)3.4. Choosing a graphical back endBefore the setup, choose a graphical back end. The default is X11.Choose one of these graphical back ends:•X11•Wayland: using the Weston compositor•XWayland•FrameBufferSpecify the machine configuration for each graphical back end.The following are examples of building the Yocto image for each back end using the QWKS board for SCM-i.MX 6D/Q and the evaluation board for SCM-i.MX 6SoloX. Do not forget to replace the machine configuration with what matches your reference board.3.4.1. X11 image on QWKS board Rev C for SCM-i.MX 6D/Q$ DISTRO=fsl-imx-x11 imx6dqscm-1gb-qwks-rev3 source fsl-setup-release.sh -b build-x11$ bitbake fsl-image-gui3.4.2. FrameBuffer image on evaluation board for SCM-i.MX 6SX$ DISTRO=fsl-imx-fb MACHINE=imx6sxscm-1gb-evb source fsl-setup-release.sh –b build-fb-evb_6sxscm$ bitbake fsl-image-qt53.4.3. XWayland image on QWKS board for SCM-i.MX 6D/Q$ DISTRO=fsl-imx-xwayland MACHINE=imx6dqscm-1gb-qwks source fsl-setup-release.sh –b build-xwayland$ bitbake fsl-image-gui3.4.4. Wayland image on QWKS board for SCM-i.MX 6D/Q$ DISTRO=fsl-imx-wayland MACHINE=imx6dqscm-1gb-qwks source fsl-setup-release.sh -b build-wayland$ bitbake fsl-image-qt5The fsl-setup-release script installs the meta-fsl-bsp-release layer and configures theDISTRO_FEATURES required to choose the graphical back end. The –b parameter specifies the build directory target. In this build directory, the conf directory that contains the local.conf file is created from the setup where the MACHINE and DISTRO_FEATURES are set. The meta-fslbsp-release layer is added into the bblayer.conf file in the conf directory under the build directory specified by the –e parameter.4. Deploying the imageAfter the build is complete, the created image resides in the <build directory>/tmp/deploy/images directory. The image is (for the most part) specific to the machine set in the environment setup. Each image build creates the U-Boot, kernel, and image type based on the IMAGE_FSTYPES defined in the machine configuration file. Most machine configurations provide the SD card image (.sdcard), ext4, and tar.bz2. The ext4 is the root file system only. The .sdcard image contains the U-Boot, kernel, and rootfs, completely set up for use on an SD card.4.1. Flashing the SD card imageThe SD card image provides the full system to boot with the U-Boot and kernel. To flash the SD card image, run this command:$ sudo dd if=<image name>.sdcard of=/dev/sd<partition> bs=1M && syncFor more information about flashing, see “P reparing an SD/MMC Card to Boot” in the i.MX Linux User's Guide (document IMXLUG).Specifying displays4.2. MFGTool (Manufacturing Tool)MFGTool is one of the ways to place the image on a device. To download the manufacturing tool for the SCM-i.MX 6D/Q and for details on how to use it, download the SCM-i.MX 6 Manufacturing Toolkit for Linux 4.1.15-2.0.0 under the "Downloads" tab from /qwks-scm-imx6dq. Similarly, download the manufacturing tool for the SCM-i.MX 6SoloX evaluation board under the "Downloads" tab from /evb-scm-imx6sx.5. Specifying displaysSpecify the display information on the Linux OS boot command line. It is not dependent on the source of the Linux OS image. If nothing is specified for the display, the settings in the device tree are used. Find the specific parameters in the i.MX 6 Release Notes L4.1.15-2.0.0 (available at L4.1.15-2.0.0_LINUX_DOCS). The examples are shown in the following subsections. Interrupt the auto-boot and enter the following commands.5.1.1. Display options for QWKS board for SCM-i.MX 6D/QHDMI displayU-Boot > setenv mmcargs 'setenv bootargs console=${console},${baudrate} ${smp}root=${mmcroot} video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24'U-Boot > run bootcmd5.1.2. Display options for EVB for SCM-i.MX 6SXNote that the SCM-i.MX 6SX EVB supports HDMI with a HDMI accessory card (MCIMXHDMICARD) that plugs into the LCD connector on the EVB.Accessory boards:•The LVDS connector pairs with the NXP MCIMX-LVDS1 LCD display board.•The LCD expansion connector (parallel, 24-bit) pairs with the NXP MCIMXHDMICARD adapter board.LVDS displayU-Boot > setenv mmcargs 'setenv bootargs console=${console},${baudrate} ${smp}root=${mmcroot} ${dmfc} video=mxcfb0:dev=ldb,1024x768M@60,if=RGB666 ldb=sep0'U-Boot > run bootcmdHDMI display (dual display for the HDMI as primary and the LVDS as secondary)U-Boot > setenv mmcargs 'setenv bootargs console=${console},${baudrate} ${smp}root=${mmcroot} video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24video=mxcfb1:dev=ldb,LDBXGA,if=RGB666'U-Boot > run bootcmdLCD displayu-boot > setenv mmcargs 'setenv bootargs ${bootargs}root=${mmcroot} rootwait rw video=mxcfb0:dev=lcd,if=RGB565'u-boot> run bootcmd6. Reset and boot switch configuration6.1. Boot switch settings for QWKS SCM-i.MX 6D/QThere are two push-button switches on the QWKS-SCMIMX6DQ board. SW1 (SW3 for QWKS board Rev B) is the system reset that resets the PMIC. SW2 is the i.MX 6Dual/6Quad on/off button that is needed for Android.There are three boot options. The board can boot either from the internal SPI-NOR flash inside the SCM-i.MX6Dual/6Quad or from either of the two SD card slots. The following table shows the switch settings for the boot options.Table 1.Boot configuration switch settingsBoot from top SD slot (SD3)Boot from bottom SD slot (SD2)Boot from internal SPI NORDefault1.References6.2. Boot switch settings for EVB SCM-i.MX 6SoloXThis table shows the jumper configuration to boot the evaluation board from the SD card slot SD3.7. SCM uboot and kernel repositoriesThe kernel and uboot patches for both SCM-i.MX 6 QWKS board and evaluation board are integrated in specific git repositories. Below are the git repos for SCM-i.MX 6 uboot and kernel:uBoot repo: /git/cgit.cgi/imx/uboot-imx.gitSCM Branch: scm-imx_v2016.03_4.1.15_2.0.0_gakernel repo: /git/cgit.cgi/imx/linux-imx.gitSCM branch: scm-imx_4.1.15_2.0.0_ga8. References1.For details about setting up the Host and Yocto Project, see the NXP Yocto Project User’s Guide(document IMXLXYOCTOUG).2.For information about downloading images using U-Boot, see “Downloading images usingU-Boot” in the i.MX Linux User's Guide (document IMXLUG).3.For information about setting up the SD/MMC card, see “P reparing an SD/MMC card to boot” inthe i.MX Linux User's Guide (document IMXLUG).9. Revision historyDocument Number: SCMIMX6LRNUGRev. L4.1.15-2.0.0-ga04/2017How to Reach Us: Home Page: Web Support: /supportInformation in this document is provided solely to enable system and softwareimplementers to use NXP products. There are no express or implied copyright licenses granted hereunder to design or fabricate any integrated circuits based on the information in this document. NXP reserves the right to make changes without further notice to any products herein.NXP makes no warranty, representation, or guarantee regarding the suitability of its products for any particular purpose, nor does NXP assume any liability arising out of the application or use of any product or circuit, and specifically disclaims any and all liability, including without limitation consequentia l or incidental damages. “Typical”parameters that may be provided in NXP data sheets and/or specifications can and do vary in different applications, and actual performance may vary over time. All operating parameters, including “typicals,” must be valida ted for each customer application by customer’s technical experts. NXP does not convey any license under its patent rights nor the rights of others. NXP sells products pursuant to standard terms and conditions of sale, which can be found at the following address: /SalesTermsandConditions .NXP, the NXP logo, NXP SECURE CONNECTIONS FOR A SMARTER WORLD, Freescale, and the Freescale logo are trademarks of NXP B.V. All other product or service names are the property of their respective owners.ARM, the ARM Powered logo, and Cortex are registered trademarks of ARM Limited (or its subsidiaries) in the EU and/or elsewhere. All rights reserved. © 2017 NXP B.V.。

ioLogik4000SeriesModular remote I/OFeatures and Benefits•I/O expansion without a backplane•Active communication with MX-AOPC UA Server•Supports SNMP v1/v2c•Easy configuration with Modular ioAdmin utility•Friendly configuration via web browser•Simplifies I/O management with MXIO library for Windows or LinuxCertificationsIntroductionThe ioLogik4000Series is suitable for remote monitoring and alarm systems,such as those used for water treatment systems,water supply systems,wastewater treatment systems,and power monitoring systems.These kinds of applications need more I/O points and a variety of I/O types,including temperature sensors,gas detectors,and water quality detectors,all of which can benefit from the versatile mixture of I/O features supported by the ioLogik4000Series.Slice Form Factor and Flexible I/O VarietyThe unique modular construction of the ioLogik4000Series allows for mixing and matching of modules to achieve the best combination of I/O modules to meet the needs of a wide range of remote automation applications.An industrial modular housing enables I/O modules to be added to the base unit without a backplane.The ioLogik4000Series is perfect for space-limited applications,and high-density I/O points are provided for greater flexibility and expandability.Modules can connect to virtually any type of sensor,including but not limited to those for temperature, pressure,flow,voltage,current,and contact closure.Easy MaintenanceThe ioLogik4000Series comes with removable spring-type terminal blocks(RTBs)that allow you to conserve field wiring for future use.SpecificationsInput/Output InterfaceButtons Reset buttonControl LogicLanguage ioLogik E4200:Click&Go,NA-4010/4020/4021:NoneEthernet Interface10/100BaseT(X)Ports(RJ45connector)NA-4010:1ioLogik E4200:2,2MAC addressesEthernet Software FeaturesConfiguration Options NA-4010/ioLogik E4200:Web Console(HTTP)NA-4010/4020/4021:Windows Utility(ioAdmin)ioLogik E4200:Windows Utility(Modular-ioAdmin)Industrial Protocols NA-4010:Modbus TCP Server(Slave),MXIO LibraryNA-4020/4021:MXIO LibraryioLogik E4200:Modbus TCP Server(Slave),Moxa AOPC(Active Tag),MXIO Library,SNMPv1/v2c,SNMPv1TrapManagement NA-4010/ioLogik E4200:DHCP Client,HTTP,IPv4,TCP/IP,UDPNA-4010/4020/4021:ioAdminioLogik E4200:Modular-ioAdminSerial InterfaceConnector NA-4021:DB9femaleNA-4020:Terminal blockData Bits7,8No.of Ports1Parity None,Even,OddSerial Standards NA-4021:RS-232NA-4020:RS-485Stop Bits1,2Baudrate NA-4020/4021:1200,2400,4800,9600,19200,38400,57600,115200bpsSerial Software FeaturesIndustrial Protocols NA-4020/4021:Modbus RTU/ASCII SlaveSerial SignalsRS-232NA-4021:TxD,RxD,GNDRS-485-2w NA-4020:Data+,Data-,GNDDIP Switch ConfigurationSerial Interface Fixed baudrateModbus TCPMax.No.of Client Connections8Mode Client(Master)Power ParametersNo.of Power Inputs1System Power ParametersPower Connector Spring-type Euroblock terminalNo.of Power Inputs1Input Voltage11to28.8VDCPower Consumption NA-4010:60mA@24VDCNA-4020/4021:70mA@24VDCioLogik E4200:175mA@24VDCField Power ParametersPower Connector Spring-type Euroblock terminalNo.of Power Inputs1Input Voltage11to28.8VDCCurrent in Field Power Contact10A(max.)Physical CharacteristicsHousing PlasticDimensions45x99x70mm(1.77x3.90x2.76in)Weight NA-4010/4020/4021:150g(0.33lb)ioLogik E4200:180g(0.396lb)Installation DIN-rail mountingEnvironmental LimitsOperating Temperature-10to60°C(14to140°F)Storage Temperature(package included)-40to85°C(-40to185°F)Ambient Relative Humidity5to95%(non-condensing)Altitude2000m1Standards and CertificationsEMC EN61000-6-2/-6-4EMI CISPR22,FCC Part15B Class AEMS IEC61000-4-2ESD:Contact:4kV;Air:8kVIEC61000-4-3RS:80MHz to1GHz:10V/mIEC61000-4-4EFT:Power:2kV;Signal:1kVIEC61000-4-5Surge:Power:2kV;Signal:1kVIEC61000-4-6CS:10VIEC61000-4-8PFMFSafety UL508Shock IEC60068-2-27Vibration IEC60068-2-6DeclarationGreen Product RoHS,CRoHS,WEEEMTBFTime NA-4010:4,739,300hrsNA-4020:4,721,640hrsNA-4021:4,695,360hrsioLogik E4200:357,000hrsStandards Telcordia SR332WarrantyWarranty Period2yearsDetails See /warranty1.Please contact Moxa if you require products guaranteed to function properly at higher altitudes.Package ContentsDevice1x ioLogik4000Series remote I/OInstallation Kit1x terminal block,8-pin,3.81mmDocumentation1x quick installation guide(ioLogik E4200)1x warranty cardNote This product requires additional modules(sold separately)to function.DimensionsI/O Network Adapter I/O ModuleOrdering InformationModel Name Control Logic Ethernet Interface Serial Interface No.of Support I/O Modules ioLogik E4200Click&Go2x RJ45–16NA-4010–1x RJ45–32NA-4020––RS-48532NA-4021––RS-23232 Accessories(sold separately)I/O ModulesM-1450For the ioLogik4000Series,4DIs,110VACM-1451For the ioLogik4000Series,4DIs,220VACM-1600For the ioLogik4000Series,16DIs,24VDC,sink typeM-1601For the ioLogik4000Series,16DIs,24VDC,source typeM-1800For the ioLogik4000Series,8DIs,24VDC,sink typeM-1801For the ioLogik4000Series,8DIs,24VDC,source typeM-2450For the ioLogik4000Series,4relays,24VDC/230VAC,2AM-2600For the ioLogik4000Series,16DOs,24VDC,0.5A,sink typeM-2601For the ioLogik4000Series,16DOs,24VDC,0.5A,source typeM-2800For the ioLogik4000Series,8DOs,24VDC,0.5A,sink typeM-2801For the ioLogik4000Series,8DOs,24VDC,0.5A,source typeM-3802For the ioLogik4000Series,8AIs,4to20mA,12bitsM-3810For the ioLogik4000Series,8AIs,0to10V,12bitsM-4402For the ioLogik4000Series,4AOs,4to20mA,12bitsM-4410For the ioLogik4000Series,4AOs,0to10V,12bitsM-6200For the ioLogik4000Series,2AIs,RTD:PT100,JPT100M-6201For the ioLogik4000Series,2AIs,TCPower ModulesM-7001For the ioLogik4000Series,system power moduleM-7002For the ioLogik4000Series,field power moduleM-7804For the ioLogik4000Series,potential distributor module,0VDC8channelM-7805For the ioLogik4000Series,potential distributor module,24VDC,8channelSoftwareMX-AOPC UA Server OPC UA Server software for converting fieldbus to the OPC UA standard©Moxa Inc.All rights reserved.Updated Dec09,2020.This document and any portion thereof may not be reproduced or used in any manner whatsoever without the express written permission of Moxa Inc.Product specifications subject to change without notice.Visit our website for the most up-to-date product information.。

Patch NotesPolycom ® DMA™ 7000 System© 2015 Polycom, Inc. All rights reserved. POLYCOM®, the Polycom logo, and the names and marks associated with Po lycom’s products are trademarks and/or service marks of Polycom, Inc. and are registered and/or common law marks in the United States and various other countries. All other trademarks are property of their respective owners. 1Release label:6.3.0_P1 Built on version:Polycom DMA 7000 System v6.3.0 Released file(s):upgrade file for 6.1.x, 6.2.0, 6.2.1, and 6.3.0Purpose The primary focus of this patch is to resolve minor issues with WebRTC. Patch 1 for DMA 6.3.0 (i.e. 6.3.0_P1_Build_198923) contains code changes to address the following issues:❑DMA-14736 RealConnect conference not working properly if DMA template is configured with cascade for size. ❑DMA-14764 DMA Conference Templates could not be loaded when try to schedule pooled conference from XMA. ❑ DMA-14798 Random generated RealConnect chair codes may result in conference creation failure.❑ DMA-14825 DMA Supercluster/UnauthorizedPrefix: SIP Call with unauthorized prefix fail to establish when backup DMA forwards the call to the active DMA.❑DMA-14898 WebRTC/RPWS Intermittent IVR display – interrupts meeting. ❑DMA-14911 Max limit on WebRTC clients needs to 5. ❑DMA-14926 DMA SIP Peer – DNS resolution of Destination Network field on RE-INVITE (Outbound Calling). ❑DMA-14948 API –display-name property value changes after promotion. ❑DMA-14956 DMA doesn’t pass the participant name in the participant notification for Web RTC participant. ❑DMA-14971 Improper CANCEL handling with Weighted SIP Peers. ❑ DMA-15010 Collabutron redirect response code should be be 302 (temporary) instead of 301 (permanent).Prerequisites/Configuration Considerations∙ Systems may have Polycom DMA 7000 v6.1.x, v6.2.0, v6.2.1, or v6.3.0 installed∙ When upgrading from DMA 6.1.x, 6.2.0, 6.2.1, 6.3.0 to 6.3.0.1, the system will not preserve the call history information. To keep this data, backup the databases, upgrade the DMAs, and then restore the databases.© 2015 Polycom, Inc. All rights reserved. POLYCOM®, the Polycom l ogo, and the names and marks associated with Polycom’s products are trademarks and/or service marks of Polycom, Inc. and are registered and/or common law marks in the United States and various other countries. All other trademarks are property of their respective owners.2 NOTE : Upgrades from DMA 6.2.2.x to 6.3.0.1 are not supported5.0.x5.1.x→ → 5.2.x Yes DMA-upgrade_5.2.2.6-bld9r144761.bin 5.2.x6.0.x→ → 6.1.x n/a rppufconv.bin (Pre 6.1.0 to 6.1.3.1) 6.1.3_P1_Build_185272-rppufconv.bin 6.1.x6.2.0.x6.2.1.x → → → 6.3.0.1 Yes full.bin (Upgrade to 6.3.0.1) 6.3.0_P1_Build_198923-full.bin 6.3.0 → 6.3.0.1 No full.bin (Upgrade to 6.3.0.1)6.3.0_P1_Build_198923-full.bin6.2.2X 6.3.0.1 Not supported 6.2.2.x X 6.3.0.1 Not supportedInstallation Notes1. Download the upgrade file for dma_6.3.0.12. Login to DMA and navigate to Maintenance > Software Upgrade3. Select “Upload and Upgrade ” and choose the upgrade file4. DMA processes and applies patch。

1CURRENT VERSION:IAR 4.11A/WIN,FET 5.12/WIN1.1KNOWN LIMITATIONSRelease NotesSLAA304I–June 2006–Revised June 2008Literature #slac050s.zip Executable file name FET_R512.exe HIL.dll version 1.2.4.0MSP430.dll version2.3.4.2JTAG2Attach to running targetDescription The "Attach to running target"feature is not working 100%reliably,especially for Spy-Bi-Wire capable devices.WorkaroundNoneEEM7Advanced Trigger of type Register does not work properly for MSP430X architectureDescriptionThe configuration of an Advanced Trigger of type Register [e.g.,to observe the Stack Pointer (SP)register value]does not show the expected behavior in the case when a device with the MSP430X architecture (e.g.,MSP430FG461x,MSP430F241x,and MSP430F261x)is the target of a debug session.WorkaroundNoneSLAA304I–June 2006–Revised June 2008IAR Embedded Workbench KickStart 1Submit Documentation Feedback2PRIOR VERSION:IAR 4.010E/WIN,FET 5.11/WIN2.1KNOWN LIMITATIONSPRIOR VERSION:IAR 4.010E/WIN,FET 5.11/WIN Literature #slac050r.zip Executable file name FET_R511.exe HIL.dll version 1.2.2.0MSP430.dll version2.3.3.0JTAG2Attach to running targetDescription The "Attach to running target"feature is not working 100%reliably,especially for Spy-Bi-Wire capable devices.WorkaroundNoneEEM7Advanced Trigger of type Register does not work properly for MSP430X architectureDescriptionThe configuration of an Advanced Trigger of type Register [e.g.,to observe the Stack Pointer (SP)register value]does not show the expected behavior in the case when a device with the MSP430X architecture (e.g.,MSP430FG461x,MSP430F241x,and MSP430F261x)is the target of a debug session.WorkaroundNoneCSPY1Integer values of C-type 'long'(32bit)are displayed incorrectly in Watch window for MSP430X architectureDescriptionThis affects 32-bit values that are held in two CPU registers;e.g.,a value of 0x00123456is stored in R14and R15.The lower word of the 32-bit value is stored as R14=0x3456,and the higher word is stored as R15=0x0012.The C-Spy Watch window shows a value of 0x12003456.This is a problem with the Watch window only–the program code produces the correct results.It is recommended not to change the dedicated 32-bit value via the Watch window,as this can cause unpredictable behavior.This limitation is only valid when a device with the MSP430X architecture is the target of a debug session.WorkaroundNoneIAR Embedded Workbench KickStart2SLAA304I–June 2006–Revised June 2008Submit Documentation Feedback3PRIOR VERSION:IAR 4.09A/WIN,FET 5.10/WIN3.1KNOWN LIMITATIONS PRIOR VERSION:IAR 4.09A/WIN,FET 5.10/WINLiterature #slac050q.zip Executable file name FET_R510.exe HIL.dll version 1.2.2.0MSP430.dll version2.3.1.0JTAG2Attach to running targetDescription The "Attach to running target"feature is not working 100%reliably,especially for Spy-Bi-Wire capable devices.WorkaroundNoneEEM7Advanced Trigger of type Register does not work properly for MSP430X architectureDescriptionThe configuration of an Advanced Trigger of type Register [e.g.,to observe the Stack Pointer (SP)register value]does not show the expected behavior in the case where a device with the MSP430X architecture (e.g.,MSP430FG461x,MSP430F241x,and MSP430F261x)is the target of a debug session.WorkaroundNoneIDE1Key bindings are deletedDescriptionIf this version of the IAR Embedded Workbench (4.09A/WIN)is installed in the same subdirectory where a previous version (e.g.,3.42A/WIN)is already installed,all key bindings [e.g.,debug hotkeys F5(Go),F10(Step Over),F11(Step Into)]are deleted in both versions.WorkaroundSelect in main menu Tools ->Options...->Key Bindings and push the 'Reset All'button in each IAR installation.CSPY1Integer values of C-type 'long'(32bit)are displayed incorrectly in Watch window for MSP430X architectureDescriptionThis affects 32-bit values that are held in two CPU registers;e.g.,a value of 0x00123456is stored in R14and R15.The lower word of the 32-bit value is stored as R14=0x3456,and the higher word is stored as R15=0x0012.The C-Spy Watch window shows a value of 0x12003456.This is a problem with the Watch window only–the program code produces the correct results.It is recommended not to change the dedicated 32-bit value via the Watch window,as this can cause unpredictable behavior.This limitation is only valid in the case where a device with the MSP430X architecture is the target of a debug session.WorkaroundNoneDEVICE3MSP430F2616and MSP430F2617devices are not correctly recognized by debuggerDescriptionWhen starting a debug session the Emulator shows a warning that "Chosen derivative (MSP430F2616)and actual hardware (MSP430F2619)do not match."for a project configured for MSP430F2616and "Chosen derivative (MSP430F2617)and actual hardware (MSP430F2618)do not match."for a project configured for MSP430F2617.WorkaroundMessage can be ignored.Click 'Yes'to continue download and start debug session.SLAA304I–June 2006–Revised June 2008IAR Embedded Workbench KickStart3Submit Documentation Feedback4PRIOR VERSION:IAR 3.42A/WIN,FET 4.63/WIN4.1KNOWN LIMITATIONSPRIOR VERSION:IAR 3.42A/WIN,FET 4.63/WIN Literature #slac050p.zip Executable file name FET_R463.exe HIL.dll version 1.2.2.0MSP430.dll version2.1.10.1JTAG2Attach to running targetDescription The "Attach to running target"feature is not working 100%reliably,especially for Spy-Bi-Wire capable devices.WorkaroundNoneEEM6Emulator Clock Control is not active by defaultDescription The "Emulator ->Clock Control"feature is not enabled by default when the C-Spy debugger starts.WorkaroundOpen "Emulator ->Clock Control"dialog box and close it again by clicking on the OK button.Emulation clock control is now activated.IAR Embedded Workbench KickStart4SLAA304I–June 2006–Revised June 2008Submit Documentation Feedback5PRIOR VERSION:IAR 3.42A/WIN,FET 4.62/WIN5.1KNOWN LIMITATIONS PRIOR VERSION:IAR 3.42A/WIN,FET 4.62/WINLiterature #slac050o.zip Executable file name FET_R462.exe HIL.dll version 1.2.2.0MSP430.dll version2.1.10.0DEVICE2Support for MSP430F11x1A device derivatives Revision JDescriptionSilicon revision J of MSP430F11x1A devices is not recognized correctly by the Emulator driver.It is not possible to download and debug program code on this dedicated silicon revision.WorkaroundNoneJTAG2Attach to running targetDescription The "Attach to running target"feature is not working 100%reliably,especially for Spy-Bi-Wire capable devices.WorkaroundNoneSLAA304I–June 2006–Revised June 2008IAR Embedded Workbench KickStart 5Submit Documentation Feedback6PRIOR VERSION:IAR 3.42A/WIN,FET 4.61/WIN6.1KNOWN LIMITATIONSPRIOR VERSION:IAR 3.42A/WIN,FET 4.61/WIN Literature #slac050n.zip Executable file name FET_R461.exe HIL.dll version 1.2.2.0MSP430.dll version2.1.9.0HEADERFILES1Definitions in generic header files msp430.h and io430.hDescription•Both files do not include any definitions for MSP430F161x devices.•Both files contain wrong definitions for FE,FG,and FW devices (exclusive MSP430FG461x devices).•The file msp430.h includes io430x22x2.h instead of msp430x22x2.h for MSP430F22x2devices.WorkaroundUse device-specific header files rather than the generic header files or edit generic header files accordingly.CONFIGFILES1RAM size definition in lnk430f223x.xcl linker command filesDescriptionA value of 0x02FF is specified for RAM segments (DATA16_I,DATA16_N,DATA16_N,CSTACK,HEAP),which corresponds to a RAM size of 256bytes.Actually,MSP430F223x devices have 512bytes of RAM,which results in a value of 0x03FF.WorkaroundEdit linker command files accordingly.CONFIGFILES2RAM size definition in lnk430f23x0.xcl linker command filesDescription•RAM segments definition in lnk430f2330.xcl should be 0x05FF instead of 0x02FF.•RAM segments definition in lnk430f2350.xcl should be 0x09FF instead of 0x03FF.WorkaroundEdit linker command files accordingly.JTAG1JTAG security fuse blowing for MSP430F23x0devicesDescription It is not possible to burn the JTAG security fuse of MSP430F23x0devices.WorkaroundNoneJTAG2Attach to running targetDescription The "Attach to running target"feature is not working 100%reliably,especially for Spy-Bi-Wire capable devices.WorkaroundNoneIAR Embedded Workbench KickStart6SLAA304I–June 2006–Revised June 2008Submit Documentation Feedback7PRIOR VERSION:IAR 3.42A/WIN,FET 4.60/WIN7.1KNOWN LIMITATIONS PRIOR VERSION:IAR 3.42A/WIN,FET 4.60/WINLiterature #slac050m.zip Executable file name FET_R460.exe HIL.dll version 1.2.2.0MSP430.dll version2.1.8.1DEVICE1Support for MSP430F22x2device derivativesDescriptionMSP430F22x2devices are recognized by the Emulator driver as the corresponding MSP430F22x4derivative.This results in an Emulator warning that the "Chosen derivative (MSP430F22x2)and actual hardware (MSP430F22x4)do not match".WorkaroundThe Emulator warning can be ignored.MSP430F22x2and MSP430F22x4derivatives are identical in terms of memory configuration.No issue is caused by ignoring the Emulator warning.SLAA304I–June 2006–Revised June 2008IAR Embedded Workbench KickStart 7Submit Documentation Feedback8PRIOR VERSION:IAR 3.41G/WIN,FET 4.53/WIN8.1KNOWN LIMITATIONSPRIOR VERSION:IAR 3.41G/WIN,FET 4.53/WIN Literature #slac050l.zip Executable file name FET_R453.exe HIL.dll version 1.2.2.0MSP430.dll version2.1.8.0EEM5Enhanced Emulation Module Advanced TriggerDescription Changing the Action in the Advanced Trigger dialog sometimes has no effect,especially with triggers of type Register.WorkaroundDisable/enable the according trigger by unchecking/checking the checkbox in the global Breakpoints window.IAR Embedded Workbench KickStart8SLAA304I–June 2006–Revised June 2008Submit Documentation Feedback9PRIOR VERSION:IAR 3.41A/WIN,FET 4.52/WIN9.1KNOWN LIMITATIONS PRIOR VERSION:IAR 3.41A/WIN,FET 4.52/WINLiterature #slac050k.zip Executable file name FET_R452.exe HIL.dll version 1.2.1.0MSP430.dll version2.1.7.0EEM1Enhanced Emulation Module Breakpoint CombinerDescription It is not possible to combine an Advanced Trigger of type Register with any other configured trigger.WorkaroundNoneEEM2Enhanced Emulation Module Sequencer ControlDescription Opening the Sequencer Control window prevents further debugging.The workbench hangs up.WorkaroundNoneSLAA304I–June 2006–Revised June 2008IAR Embedded Workbench KickStart 9Submit Documentation Feedback10PRIOR VERSION:IAR 3.40B/WIN,FET 4.51/WIN10.1KNOWN LIMITATIONS PRIOR VERSION:IAR 3.40B/WIN,FET 4.51/WIN Literature #slac050j.zip Executable file name FET_R451.exe HIL.dll version 1.2.1.0MSP430.dll version2.1.6.0EEM1Enhanced Emulation Module Breakpoint CombinerDescription It is not possible to combine an Advanced Trigger of type Register with any other configured trigger.WorkaroundNoneEEM2Enhanced Emulation Module Sequencer ControlDescription Opening the Sequencer Control window prevents further debugging.The workbench hangs up.WorkaroundNoneEEM3Enhanced Emulation Module Clock ControlDescription Any changes made in the Clock Control window have no effect and are discarded after clicking the "OK"button.WorkaroundNone EEM4BreakpointsDescription Advanced Triggers of type Register where the specified register is any other CPU register than the SP (Stack Pointer)have no effect.WorkaroundNoneFLASH1Debugger Flash ProgrammingDescription It is not possible to link any code/data into Information Memory segments B,C,and D of MSP430F2xx devices without erasing DCO calibration data in segment A.WorkaroundNoneIAR Embedded Workbench KickStart10SLAA304I–June 2006–Revised June 2008Submit Documentation Feedback11VERSION MATRIX:KNOWN LIMITATIONS VERSION MATRIX:KNOWN LIMITATIONSLiterature #H E A D E R F I L E S 1C O N F I G F I L E S 1C O N F I G F I L E S 2J T A G 1J T A G 2D E V I C E 1D E V I C E 2D E V I C E 3E E M 1E E M 2E E M 3E E M 4E E M 5E E M 6E E M 7F L A S H 1I D E 1C S P Y 1 slac050s.zip üüslac050r.zip üüüslac050q.zip üüüüüslac050p.zip üüüslac050o.zip üüüüslac050n.zip üüüüüüüslac050m.zip üüüüslac050l.zip üüüslac050k.zip üüüüslac050j.zipüüüüüüüSLAA304I–June 2006–Revised June 2008IAR Embedded Workbench KickStart11Submit Documentation FeedbackIMPORTANT NOTICETexas Instruments Incorporated and its subsidiaries(TI)reserve the right to make corrections,modifications,enhancements,improvements, and other changes to its products and services at any time and to discontinue any product or service without notice.Customers should obtain the latest relevant information before placing orders and should verify that such information is current and complete.All products are sold subject to TI’s terms and conditions of sale supplied at the time of order acknowledgment.TI warrants performance of its hardware products to the specifications applicable at the time of sale in accordance with TI’s standard warranty.Testing and other quality control techniques are used to the extent TI deems necessary to support this warranty.Except where mandated by government requirements,testing of all parameters of each product is not necessarily performed.TI assumes no liability for applications assistance or customer product design.Customers are responsible for their products and applications using TI components.To minimize the risks associated with customer products and applications,customers should provide adequate design and operating safeguards.TI does not warrant or represent that any license,either express or implied,is granted under any TI patent right,copyright,mask work right, or other TI intellectual property right relating to any combination,machine,or process in which TI products or services are rmation published by TI regarding third-party products or services does not constitute a license from TI to use such products or services or a warranty or endorsement e of such information may require a license from a third party under the patents or other intellectual property of the third party,or a license from TI under the patents or other intellectual property of TI.Reproduction of TI information in TI data books or data sheets is permissible only if reproduction is without alteration and is accompanied by all associated warranties,conditions,limitations,and notices.Reproduction of this information with alteration is an unfair and deceptive business practice.TI is not responsible or liable for such altered rmation of third parties may be subject to additional restrictions.Resale of TI products or services with statements different from or beyond the parameters stated by TI for that product or service voids all express and any implied warranties for the associated TI product or service and is an unfair and deceptive business practice.TI is not responsible or liable for any such statements.TI products are not authorized for use in safety-critical applications(such as life support)where a failure of the TI product would reasonably be expected to cause severe personal injury or death,unless officers of the parties have executed an agreement specifically governing such use.Buyers represent that they have all necessary expertise in the safety and regulatory ramifications of their applications,and acknowledge and agree that they are solely responsible for all legal,regulatory and safety-related requirements concerning their products and any use of TI products in such safety-critical applications,notwithstanding any applications-related information or support that may be provided by TI.Further,Buyers must fully indemnify TI and its representatives against any damages arising out of the use of TI products in such safety-critical applications.TI products are neither designed nor intended for use in military/aerospace applications or environments unless the TI products are specifically designated by TI as military-grade or"enhanced plastic."Only products designated by TI as military-grade meet military specifications.Buyers acknowledge and agree that any such use of TI products which TI has not designated as military-grade is solely at the Buyer's risk,and that they are solely responsible for compliance with all legal and regulatory requirements in connection with such use. TI products are neither designed nor intended for use in automotive applications or environments unless the specific TI products are designated by TI as compliant with ISO/TS16949requirements.Buyers acknowledge and agree that,if they use any non-designated products in automotive applications,TI will not be responsible for any failure to meet such requirements.Following are URLs where you can obtain information on other Texas Instruments products and application solutions:Products ApplicationsAmplifiers AudioData Converters AutomotiveDSP BroadbandClocks and Timers Digital ControlInterface MedicalLogic MilitaryPower Mgmt Optical NetworkingMicrocontrollers SecurityRFID TelephonyRF/IF and ZigBee®Solutions Video&ImagingWirelessMailing Address:Texas Instruments,Post Office Box655303,Dallas,Texas75265Copyright©2008,Texas Instruments Incorporated。

1 IntroductionThe MPC56xx 32-bit microcontroller family built on Power Architecture ® technology provides a mechanism by which the e200 core implements interrupts and exceptions. Thisapplication note describes a method for decoding the length of VLE instructions, one which is used to correctly increment the returning address of the exception.2 OverviewIn this application note, core exceptions are split into two types:•Exceptions for which the address located in the SRR0 is increased automatically.•Exceptions for which the address located in the SRR0has to be increased manually based on the length of the instruction that caused the exception.This information is located in the IVORx interrupt chapter in the related e200 Core Reference Manual .Table 1 highlights IVORx exceptions that require manual incrementing of the return address in the SRR0 register for thee200z7 core. For further information, refer to the "DebugApplication NoteRev. 1, 3/2013VLE 16-bit and 32-bit Instruction Length Decode Algorithmby:Pavel Bohacik© 2013 Freescale Semiconductor, Inc.Contents1Introduction................................................................12Overview....................................................................13Machine check interrupt (IVOR1exception) example...................................................24Book E or VLE instruction decoding (25)Decoding 16-bit or 32-bit VLEinstructions................................................................35.1Decoding the condition in C...........................45.2Decoding the condition inassembly.........................................................56Conclusion.. (57)References (5)Machine check interrupt (IVOR1 exception) exampleInterrupt—Register Settings" table in the Interrupts and Exceptions chapter of document number e200z760RM, e200z760n3 Power Architecture Core Reference Manual.3Machine check interrupt (IVOR1 exception) exampleWhen an IVOR1 exception occurs (due to memory protection, for example), the e200 core sets Machine Check Save/Restore Register 0 (MCSRR0) to the address of the instruction that was executed or about to be executed when the machine check condition occurred. If a recoverable machine check exception occurred, you should update MCSSR0 appropriately in the IVOR1 handler epilog based on all recommendations mentioned in AN2865, Qorivva Simple Cookbook available at .Freescale e200 cores allow you to use both variable length encoding (VLE) 16-bit and 32-bit instructions and Book E 32-bit instructions. (Book E is not supported by the e200z0 core, however.) When a machine check interrupt occurs, MCSRR0 contains the address of the instruction that was executed when the machine check occurred. To avoid a recurrence of the machine check interrupt, you should properly increment the instruction address in MCSSR0. The increment of the instruction address depends on the type of instruction interrupted by the machine check interrupt. An increment of 4 bytes is required for Book E instructions and VLE 32-bit instructions; an increment of 2 bytes is required for VLE 16-bit instructions.4Book E or VLE instruction decodingMore powerful types of e200 cores, like the e200z7, allow a mixed execution of VLE and Book E instructions. For this reason, Book E instruction detection is required when a machine check interrupt occurs.There are several ways to determine whether a Book E or a VLE instruction was used.1.Check Instruction Register Status Bit 8 in the Control State Register (CTL[IRSTAT8]) to determine the Power ISA VLE status for the Instruction Register (IR). This is a debug register, so it is not accessible by the main core. See e200z760RM, e200z760n3 Power Architecture Core Reference Manual for further details.2.Check the Power ISA VLE bit in the Memory Management Unit's MMU Assist Register 2 to determine the type of page. Your IVORx epilog should read all valid MMU table entries (MAS1[VALID]) and compare whether the returning address located in Machine Status Save/Restore Register 0 (SRR0) fits one of MMU entries.e a global variable. To simplify the procedure with the MMU, which may be undesired because it takes a significant amount of time, you can use a global array that lists memory ranges of VLE or Book E pages and is filled during the definition of MMU entries. Your IVORx epilog then reads SRR0 and determines whether a VLE or Book E instruction was executed based on global array values.5Decoding 16-bit or 32-bit VLE instructionsWhen a VLE instruction has been successfully decoded, the interrupt handler epilog should detect whether a 16-bit or 32-bit VLE instruction has been interrupted. Depending on the type of e200 core, different 32-bit instructions are available. See VLEPEM, Variable-Length Encoding (VLE) Programming Environments Manual , for the "VLE Instruction Set Sorted by Opcode" table, which contains both 32-bit and 16-bit instructions. After detailed investigation, the difference in opcodebetween all types of 16-bit and 32-bit VLE instructions is easily visible. Table 2, which lists a range of 16-bit and 32-bit VLE instructions, is based on the table from VLEPEM.Opcode size is determined by the first 4 bits (instruction bus[0:3]). 16-bit operations use encoding 0b0xx0 and 0b1xxx, with the exception of 0b1111, which are reserved operations (32-bit). 32-bit operations use 0b0xx1. As highlighted in thefollowing table, 32-bit instructions contain values 1, 3, 5, and 7 in the most significant byte position of this opcode. 16-bit VLE instruction contains values 0, 2, 4, 6, 8, 9, 0xA, 0xB, 0xC, 0xD, and 0xE in the most significant byte position of this opcode.Decoding 16-bit or 32-bit VLE instructions5.1Decoding the condition in Cif(VLE_INSTRUCTION){if((instruction & 0x9000) == 0x1000) {// first 4 bits have a value of 1,3,5,7return address +=4; //instruction was 32-bit } else {// first 4 bits have a value of 0,2,4,6,8,9,A,B,C,D,E (and F, but F is reserved) return address +=2; //instruction was 16-bit }}5.2Decoding the condition in assemblymfspr r5,570 # MCSRR0 -> r5se_lhz r4,0(r5) # determine opcode @ MCSRR0 e_andi. r3,r4,0x9000e_cmpli 0x0,r3,0x1000 # check bit 31,28 onlye_bne __machine_check_adjust_for_16bit_opcode se_addi r5,2 # 0xx1 => 32 bit __machine_check_adjust_for_16bit_opcode:se_addi r5,2 # all others just 16 bit long mtspr 570,r5 # save adjusted return address6ConclusionThis application note describes how to correctly increment the returning address for IVORx exceptions, which do notautomatically increase it. Incrementing the returning address is required only for instructions that would cause this exception continuously, causing software to get stuck. You should always correctly handle the root cause of the IVORx exception before incrementing the returning address.7ReferencesHow to Reach Us:Home Page:Web Support:/supportUSA/Europe or Locations Not Listed:Freescale SemiconductorTechnical Information Center, EL5162100 East Elliot Road Tempe, Arizona 85284+1-800-521-6274 or +/supportEurope, Middle East, and Africa:Freescale Halbleiter Deutschland GmbH Technical Information Center Schatzbogen 781829 Muenchen, Germany +44 1296 380 456 (English)+46 8 52200080 (English)+49 89 92103 559 (German)+33 1 69 35 48 48 (French)/supportJapan:Freescale Semiconductor Japan Ltd.Headquarters ARCO Tower 15F1-8-1, Shimo-Meguro, Meguro-ku,Tokyo 153-0064Japan0120 191014 or +81 3 5437 9125***************************Asia/Pacific:Freescale Semiconductor China Ltd.Exchange Building 23F No. 118 Jianguo Road Chaoyang District Beijing 100022China+86 10 5879 8000**************************Document Number: AN4648Rev. 1, 3/2013Information in this document is provided solely to enable system and softwareimplementers to use Freescale Semiconductors products. There are no express or implied copyright licenses granted hereunder to design or fabricate any integrated circuits or integrated circuits based on the information in this document.Freescale Semiconductor reserves the right to make changes without further notice to any products herein. Freescale Semiconductor makes no warranty, representation, orguarantee regarding the suitability of its products for any particular purpose, nor does Freescale Semiconductor assume any liability arising out of the application or use of any product or circuit, and specifically disclaims any liability, including without limitation consequential or incidental damages. "Typical" parameters that may be provided in Freescale Semiconductor data sheets and/or specifications can and do vary in different applications and actual performance may vary over time. All operating parameters,including "Typicals", must be validated for each customer application by customer's technical experts. Freescale Semiconductor does not convey any license under its patent rights nor the rights of others. Freescale Semiconductor products are not designed,intended, or authorized for use as components in systems intended for surgical implant into the body, or other applications intended to support or sustain life, or for any other application in which failure of the Freescale Semiconductor product could create a situation where personal injury or death may occur. Should Buyer purchase or useFreescale Semiconductor products for any such unintended or unauthorized application,Buyer shall indemnify Freescale Semiconductor and its officers, employees, subsidiaries,affiliates, and distributors harmless against all claims, costs, damages, and expenses, and reasonable attorney fees arising out of, directly or indirectly, any claim of personal injury or death associated with such unintended or unauthorized use, even if such claims alleges that Freescale Semiconductor was negligent regarding the design or manufacture of the part.RoHS-compliant and/or Pb-free versions of Freescale products have the functionality and electrical characteristics as their non-RoHS-complaint and/or non-Pb-free counterparts.For further information, see or contact your Freescale sales representative.For information on Freescale's Environmental Products program, go to /epp.Freescale™ and the Freescale logo are trademarks of Freescale Semiconductor, Inc.All other product or service names are the property of their respective owners.© 2013 Freescale Semiconductor, Inc.。

ISO certified in Akashi Works.ROBOT DIVISIONTokyo Head Office/Robot Division1-14-5, Kaigan, Minato-ku, Tokyo 105-8315, Japan Phone: +81-3-3435-2501 Fax: +81-3-3437-9880Akashi Works/Robot Division1-1, Kawasaki-cho, Akashi, Hyogo 673-8666, Japan Phone: +81-78-921-2946 Fax: +81-78-923-6548Global NetworkKawasaki Robotics (USA), Inc.28140 Lakeview Drive, Wixom, MI 48393, U.S.A.Phone: +1-248-446-4100 Fax: +1-248-446-4200Kawasaki Robotics (UK) Ltd.Unit 4 Easter Court, Europa Boulevard, Westbrook Warrington Cheshire, WA5 7ZB, United KingdomPhone: +44-1925-71-3000 Fax: +44-1925-71-3001Kawasaki Robotics GmbH29 Sperberweg, 41468 Neuss, Germany Phone: +49-2131-34260 Fax: +49-2131-3426-22Kawasaki Robotics Korea, Ltd.43, Namdong-daero 215beon-gil, Namdong-gu, Incheon, 21633, KoreaPhone: +82-32-821-6941 Fax: +82-32-821-6947Kawasaki Robotics (Tianjin) Co., Ltd.1·2/F, Building 6, No.19 Xinhuan Road, TEDA, China Phone: +86-22-5983-1888 Fax: +86-22-5983-1889Kawasaki Motors Enterprise (Thailand) Co., Ltd.(Rayong Robot Center)119/10 Moo 4 T.Pluak Daeng, A.Pluak Daeng, Rayong 21140 ThailandPhone: +66-38-955-040-58 Fax: +66-38-955-145https:///] Materials and specifications are subject to change without notice.R seriesK seriesRA seriesM seriesCP seriesduAroB seriesY seriesK-ROSET solves your problems and supports all the phases from startup to commercial production.K-ROSET makes installation efficient and shortens the startup time.Need to pre-check for robot interference with peripheral equipment. Need to know in advance if the robot can reach the workpiece. Need to confirm in advance the robot cycle time. Need to prepare an operation manual for the system. Need to minimize the downtime of the production line. Need to monitor the real robot posture and signal conditions.Planning/designing timeInstallation/startup timeD r a s t i c r e d u c t i o n o f o ver a l l c o s t s !AfterinstallationLayout planning Teaching/programming Simulation Manual creationModi cations of theprogram Monitoring of the realrobot operationVisualization of theproduction lineMonitoring of the realrobot operation Fine adjustments of theprogramPaintingHandling (duAro)Simulation of vision systemsThe vision filed of the camera used in a vision systemcan be monitored by using the virtual camera ofArc weldingOperation of multiple robotsK-ROSET can simultaneously simulate the operationsSpot weldingHandlingPicking and placePalletizingAdditions of robot(s) and workpiece(s) and layout modifications can easily be made through dialog-style operations.Movements of the robot and peripheralequipment and the conditions of interferingProcessing movements can easily be made Programs created by K-ROSET can beuploaded to the real robot, or saved on。

B-1Cisco ONS 15454 Reference Manual, R5.078-16296-01A P P E N D I XBAdministrative and Service StatesThis appendix describes administrative and service states for Cisco ONS 15454 cards, ports, and cross-connects. For circuit state information, see Chapter 10, “Circuits and Tunnels.” SoftwareRelease 5.0 states are based on the generic state model defined in Telcordia GR-1093-CORE, Issue 2 and ITU-T X.731.0.1Service StatesService states include a Primary State (PST), a Primary State Qualifier (PSTQ), and one or moreSecondary States (SST). Table 0-1 lists the service state PSTs and PSTQs supported by the ONS 15454.T able 0-1ONS 15454 Service State Primary States and Primary State QualifiersPrimary State, Primary State Qualifier DefinitionIS-NR (In-Service and Normal) The entity is fully operational and will perform as provisioned.OOS-AU (Out-of-Service and Autonomous) The entity is not operational because of an autonomous event.OOS-AUMA(Out-of-Service and Autonomous Management) The entity is not operational because of an autonomous event and has also been manually removed from service.OOS-MA(Out-of-Service and Management) The entity has been manually removed from service.Appendix B Administrative and Service States Administrative StatesTable0-2 defines the SSTs supported by the ONS 15454.T able0-2ONS 15454 Secondary StatesSecondary State DefinitionAINS(Automatic In-Service) The entity is delayed before transitioning to the IS-NRservice state. The transition to IS-NR depends on correction of conditions, or on asoak timer. Alarm reporting is suppressed, but traffic is carried. Raised faultconditions, whether or not their alarms are reported, can be retrieved on the CTCConditions tab or by using the TL1 RTRV-COND command.DSBLD(Disabled) The entity was manually removed from service and does not provide itsprovisioned functions. All services are disrupted; the entity is unable to carrytraffic.LPBK(Loopback) The entity is in loopback mode.MEA(Mismatched Equipment) An improper card is installed. For example, an installedcard is not compatible with the card preprovisioning or the slot. This SST appliesonly to cards.MT(Maintenance) The entity has been manually removed from service for amaintenance activity but still performs its provisioned functions. Alarm reportingis suppressed, but traffic is carried. Raised fault conditions, whether or not theiralarms are reported, can be retrieved on the CTC Conditions tab or by using theTL1 RTRV-COND command.OOG(Out of Group) The virtual concatenation (VCAT) member cross-connect is notused to carry VCAT group traffic. This state is used to put a member circuit out ofthe group and to stop sending traffic. OOS-MA,OOG only applies to thecross-connects on an end node where VCAT resides. The cross-connects onintermediate nodes are in the OOS-MA,MT service state.SWDL(Software Download) The card is involved in a software and database download.This SST applies only to cards.UAS(Unassigned) The card is not provisioned in the database. This SST applies only tocards.UEQ(Unequipped) The card is not physically present (that is, an empty slot). This SSTapplies only to cards.0.2Administrative StatesAdministrative states are used to manage service states. Administrative states consist of a PST and anSST. Table0-3 lists the administrative states supported by the ONS 15454. See Table0-2 for SSTdefinitions.Note A change in the administrative state of an entity does not change the service state of supporting or supported entities.Cisco ONS 15454 Reference Manual, R5.078-16296-01Cisco ONS 15454 Reference Manual, R5.078-16296-01Appendix B Administrative and Service StatesService State Transitions0.3Service State TransitionsThis section describes the transition from one service state to the next for cards, ports, and cross-connects. A service state transition is based on the action performed on the entity.0.3.1Card Service State TransitionsTable 0-4 lists card service state transitions.T able 0-3ONS 15454 Administrative StatesAdministrative State (PST,SST)Definition IS Puts the entity in-service.IS,AINS Puts the entity in automatic in-service.OOS,DSBLD Removes the entity from service and disables it.OOS,MT Removes the entity from service for maintenance.OOS,OOG(VCAT circuits only.) Removes a VCAT member cross-connect from service and from the group of members.T able 0-4ONS 15454 Card Service State T ransitionsCurrent Service State Action Next Service StateIS-NRChange the administrative state to OOS,MT.OOS-MA,MT Delete the card.OOS-AUMA,UAS Pull the card.OOS-AU,UEQ Reset the card.OOS-AU,SWDL OOS-AU,AINS and MEA Pull the card.OOS-AU,AINS & UEQ Delete the card.OOS-AUMA,UAS if the card is validOOS-AUMA,MEA & UAS if the card is invalidOOS-AU,AINS & SWDL Restart completed.IS-NRPull the card.OOS-AU,AINS & UEQ OOS-AU,AINS & UEQInsert a valid card.OOS-AU,AINS & SWDL Insert an invalid card.OOS-AU,AINS & MEA Delete the card.OOS-AUMA,UAS & UEQCisco ONS 15454 Reference Manual, R5.078-16296-01Appendix B Administrative and Service StatesService State TransitionsOOS-AU,MEAPull the card.OOS-AU,UEQDelete the card.OOS-AUMA,UAS if the card is validOOS-AUMA,MEA & UAS if the card is invalidChange the administrative state to OOS,MT.OOS-AUMA,MT & UEQ OOS-AU,SWDL Restart completed.IS-NR Pull the card.OOS-AU,UEQ OOS-AU,UEQInsert a valid card.OOS-AU,SWDL Insert an invalid card.OOS-AU,MEADelete the card.OOS-AUMA,UAS & UEQChange the administrative state to OOS,MT.OOS-AUMA,MT & UEQ OOS-AUMA,MEA & MTChange the administrative state to IS.OOS-AU,MEA Pull the card.OOS-AUMA,MT & UEQ Delete the card.OOS-AUMA,UAS if the card is validOOS-AUMA,MEA & UAS if the card is invalidOOS-AUMA,MEA & UAS Pull the card.OOS-AUMA,UAS & UEQ Provision the card.OOS-AU,MEA OOS-AUMA,MT & SWDL Restart completed.OOS-MA,MTPull the card.OOS-AUMA,MT & UEQOOS-AUMA,MT & UEQChange the administrative state to IS.OOS-AU,UEQ Insert a valid card.OOS-AUMA,MT & SWDL Insert an invalid card.OOS-AUMA,MEA & MT Delete the card.OOS-AUMA,UAS & UEQ OOS-AUMA,UAS Pull the card.OOS-AUMA,UAS & UEQ Provision an invalid card.OOS-AU,MEA Provision a valid card.OOS-AU,SWDL OOS-AUMA,UAS & UEQ Insert a valid card.OOS-AU,SWDLInsert an invalid card.OOS-AUMA,MEA & UAS Preprovision a card.OOS-AU,AINS & UEQT able 0-4ONS 15454 Card Service State T ransitions (continued)Current Service State Action Next Service StateCisco ONS 15454 Reference Manual, R5.078-16296-01Appendix B Administrative and Service StatesService State Transitions0.3.2Port and Cross-Connect Service State TransitionsTable 0-5 lists the port and cross-connect service state transitions. Port states do not impactcross-connect states with one exception. A cross-connect in the OOS-AU,AINS service state cannot transition autonomously into the IS-NR service state until the parent port is IS-NR.The following ports do not support all of the service states listed in Table 0-5:•E-Series Ethernet ports do not support service states; these ports are either enabled or disabled. •FC_MR-4 ports support the IS-NR; OOS-MA,DSBLD; and OOS-MA,MT service states; they do not support the OOS-AU,AINS service state.OOS-MA,MTChange the administrative state to IS.IS-NR Delete the card.OOS-AUMA,UAS Pull the card.OOS-AUMA,MT & UEQ Reset the card.OOS-AUMA,MT & SWDLT able 0-4ONS 15454 Card Service State T ransitions (continued)Current Service State Action Next Service StateT able 0-5ONS 15454 Port and Cross-Connect Service State T ransitionsCurrent Service State ActionNext Service State IS-NRPut the port or cross-connect in the OOS,MT administrative state.OOS-MA,MTPut the port or cross-connect in the OOS,DSBLD administrative state.OOS-MA,DSBLDOOS-MA,DSBLD & OOG for a VCAT cross-connect Put the port or cross-connect in the IS,AINS administrative state.OOS-AU,AINS 1Put the VCAT cross-connect in the OOS,OOG administrative state.OOS-MA,MT & OOGOOS-AU,AINSPut the port or cross-connect in the IS administrative state.IS-NR Put the port or cross-connect in the OOS,MT administrative state.OOS-MA,MTPut the port or cross-connect in the OOS,DSBLD.OOS-MA,DSBLDOOS-MA,DSBLD & OOG for a VCAT cross-connect Put the VCAT cross-connect in the OOS,OOG administrative state.OOS-MA,MT and OOGCisco ONS 15454 Reference Manual, R5.078-16296-01Appendix B Administrative and Service StatesService State TransitionsOOS-MA,DSBLDPut the port or cross-connect in the IS administrative state.IS-NRPut the port or cross-connect in the IS,AINS administrative state.OOS-AU,AINS Put the port or cross-connect in the OOS,MT.OOS-MA,MT Put the VCAT cross-connect in the OOS,OOG administrative state.OOS-MA,MT & OOGOOS-MA,LPBK & MTRelease the loopback.NoteWhile inOOS-MA,LPBK & MT, both CTC and TL1 allow a cross-connect to be deleted, which also removes the loopback. This applies only to the cross-connect, not the ports.OOS-MA,MTOOS-MA,MTPut the port or cross-connect in the IS administrative state.IS-NRPut the port or cross-connect in the IS,AINS administrative state.OOS-AU,AINS Put the port or cross-connect in the OOS,DSBLD.OOS-MA,DSBLDOOS-MA,DSBLD & OOG for a VCAT cross-connect Put the port or cross-connect in loopback.OOS-MA,LPBK & MT Put the VCAT cross-connect in the OOS,OOG administrative state.OOS-MA,MT & OOG1.For a VCAT member, an IS-NR to OOS-AU,AINS transition will not occur with a Loss of Multiframe (LOM) or SequenceMismatch (SQM) condition on the member.T able 0-5ONS 15454 Port and Cross-Connect Service State T ransitions (continued)Current Service State ActionNext Service State。

UM0427用户手册32位基于ARM微控制器STM32F101xx与STM32F103xx固件函数库介绍本手册介绍了32位基于ARM微控制器STM32F101xx与STM32F103xx的固件函数库。

该函数库是一个固件函数包，它由程序、数据结构和宏组成，包括了微控制器所有外设的性能特征。

该函数库还包括每一个外设的驱动描述和应用实例。

通过使用本固件函数库，无需深入掌握细节，用户也可以轻松应用每一个外设。

因此，使用本固态函数库可以大大减少用户的程序编写时间，进而降低开发成本。

每个外设驱动都由一组函数组成，这组函数覆盖了该外设所有功能。

每个器件的开发都由一个通用API(application programming interface应用编程界面)驱动，API对该驱动程序的结构，函数和参数名称都进行了标准化。

所有的驱动源代码都符合“Strict ANSI-C”标准（项目于范例文件符合扩充ANSI-C标准）。

我们已经把驱动源代码文档化，他们同时兼容MISRA-C2004标准（根据需要，我们可以提供兼容矩阵）。

由于整个固态函数库按照“Strict ANSI-C”标准编写，它不受不同开发环境的影响。

仅对话启动文件取决于开发环境。

该固态函数库通过校验所有库函数的输入值来实现实时错误检测。

该动态校验提高了软件的鲁棒性。

实时检测适合于用户应用程序的开发和调试。

但这会增加了成本，可以在最终应用程序代码中移去，以优化代码大小和执行速度。

想要了解更多细节，请参阅Section2.5。

因为该固件库是通用的，并且包括了所有外设的功能，所以应用程序代码的大小和执行速度可能不是最优的。

对大多数应用程序来说，用户可以直接使用之，对于那些在代码大小和执行速度方面有严格要求的应用程序，该固件库驱动程序可以作为如何设置外设的一份参考资料，根据实际需求对其进行调整。

此份固件库用户手册的整体架构如下：⏹定义，文档约定和固态函数库规则。

⏹固态函数库概述（包的内容，库的架构），安装指南，库使用实例。

AllFusion® Model ManagerRelease Summaryr7This documentation and related computer software program (hereinafter referred to as the “Documentation”) is for the end user’s informational purposes only and is subject to change or withdrawal by Computer Associates International, Inc. (“CA”) at any time.This documentation may not be copied, transferred, reproduced, disclosed or duplicated, in whole or in part, without the prior written consent of CA. This documentation is proprietary information of CA and protected by the copyright laws of the United States and international treaties.Notwithstanding the foregoing, licensed users may print a reasonable number of copies of this documentation for their own internal use, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the confidentiality provisions of the license for the software are permitted to have access to such copies.This right to print copies is limited to the period during which the license for the product remains in full force and effect. Should the license terminate for any reason, it shall be the user’s responsibility to return to CA the reproduced copies or to certify to CA that same have been destroyed.To the extent permitted by applicable law, CA provides this documentation “as is” without warranty of any kind, including without limitation, any implied warranties of merchantability, fitness for a particular purpose or noninfringement. In no event will CA be liable to the end user or any third party for any loss or damage, direct or indirect, from the use of this documentation, including without limitation, lost profits, business interruption, goodwill, or lost data, even if CA is expressly advised of such loss or damage.The use of any product referenced in this documentation and this documentation is governed by the end user’s applicable license agreement.The manufacturer of this documentation is Computer Associates International, Inc.Provided with “Restricted Rights” as set forth in 48 C.F.R. Section 12.212, 48 C.F.R. Sections 52.227-19(c)(1) and (2) or DFARS Section 252.227-7013(c)(1)(ii) or applicable successor provisions.Copyright © 2006 CA. All rights reserved.All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.ContentsChapter 1: Changes to Existing FeaturesDatabase and Model Conversion Management..................................................1-1 Services Menu Replaces ModelMart Menu......................................................1-2 Change Management Functionality Changed....................................................1-2 Review Changes uses the Complete Compare Functionality......................................1-2 Refresh uses the Complete Compare Functionality...............................................1-2 Version Manager uses the Complete Compare Functionality......................................1-3 Renamed Subject Areas to Submodels..........................................................1-3 Complete Compare Functionality Replaces the (ModelMart) Merge Manager.......................1-3 Version Dependency Removed.................................................................1-4 ModelMart Synchronizer Removed.............................................................1-4 Change in Database Support Policy.............................................................1-4 Additional Database Version Support.......................................................1-4 Databases No Longer Supported...........................................................1-4 Dropped Support for Database Versions....................................................1-41 Changes to Existing FeaturesThis chapter documents changes made to existing features and includes a list offeatures removed from the product for r7. A number of changes have been madeto the user interface to improve functionality and consistency. The changes areoutlined as follows:Database and Model Conversion ManagementServices menu replaces the ModelMart menuChange Management Functionality ChangedReview Changes uses the Complete Compare functionalityRefresh uses the Complete Compare functionalityVersion Manager uses the Complete Compare functionalityRenamed Subject Areas to SubmodelsComplete Compare functionality replaces the (ModelMart) Merge ManagerVersion Dependency RemovedModelMart Synchronizer RemovedChange in Database Support PolicyDatabase and Model Conversion ManagementIf you previously worked with AllFusion Model Manager (ModelMart), probablythe most important task is preserving the database structure and the contents ofyour ModelMart 4.1.4 database. AllFusion MM r7 includes a built-in conversionutility that the administrator uses to perform the conversion. The conversionutility does all the work of transforming the old into the new database and itconverts the AllFusion ERwin DM and AllFusion Process Modeler models to thenewest version as well. More information about using the conversion utility isincluded in the AllFusion Model Manager r7 Administrator Guide.Services Menu Replaces ModelMart MenuServices Menu Replaces ModelMart MenuThe client-server functionality available in the AllFusion Modeling Suite nowuses the broader term "Services." Features that formerly appeared under the"ModelMart'" menu item now appear under a "Services" menu.Change Management Functionality ChangedThe addition of the Action Log feature, and implementation of CompleteCompare have replaced the Change Control Manager user interface forAllFusion ERwin DM clients.Note: The Change Control Manager is still available for AllFusion ProcessModeler clients.If you make changes to a model checked out of AllFusion MM, and then try tosave the model to the mart, you are reminded to first use the Action Log toreview your changes. If no changes conflict with the version in the mart, yourmodel is saved. In earlier versions you were prompted to review changes usingthe Change Control Manager.If conflicts between your local model and the one in the mart are detected duringthe save process, the Complete Compare - Difference Reconciliation dialog isdisplayed to help you resolve the differences before committing the changes tothe mart.Review Changes uses the Complete Compare Functionality When you choose the Review Changes from the Services menu and changes aredetected, the Right Model Pane of Complete Compare is displayed. In earlierversions you were prompted to review changes using the Change ControlManager.Refresh uses the Complete Compare FunctionalityWhen you choose Refresh from the Services menu and changes are detected, theComplete Compare interface is used to display and reconcile the changes. Inearlier versions you were prompted to review changes using the Change ControlManager.Version Manager uses the Complete Compare FunctionalityVersion Manager uses the Complete Compare Functionality When you choose Diff to compare two model versions in the AllFusion VersionManager, the Right Model Pane of the Complete Compare interface is used todisplay and reconcile the differences. In earlier versions you were prompted toreview changes using the Change Control Manager.Renamed Subject Areas to SubmodelsAllFusion MM is now using the term Submodel instead of the ERwin termSubject Area. The corresponding item on the Services menu has been changed,and the dialog has been renamed to highlight the distinction between subjectareas and submodels. This is meant to highlight the distinction that opening aSubmodel from the AllFusion MM Open dialog just gives you access to thatsubmodel, and restricts access to other subject areas of that model in the ERwinediting session. There is no real inherent difference between subject areas andsubmodels, so whether you used the ERwin dialog to edit subject areas, or theAllFusion MM dialog on the Services menu to edit Stored Displays, the results ofeach do show up in the other.As we move into future releases, we expect submodels to become betterdifferentiated from Subject Areas by having more capabilities that are unique tothem.Complete Compare Functionality Replaces the (ModelMart) Merge ManagerIn previous versions, the Merge Manager presented a series of dialogs that letyou merge the current model with another model from the mart, or with a localmodel. New functionality in the Complete Compare wizard expands on thisfunctionality. The Complete Compare Wizard does the following:Load models from a variety of sources.Merge into an empty model.Merge into an existing model and use the Save As feature to create a newmodel.Lets you skip pages of the wizard, for instance, if you want to set up filters,you can.Lets you compare any combination of logical/physical, logical-only, andphysical-only models.Version Dependency RemovedVersion Dependency RemovedIn earlier releases of the AllFusion Modeling Suite, the release version ofAllFusion ERwin Data Modeler and AllFusion Model Manager had to beidentical. With r7, this dependency has been removed. Although we recommendthat you install the latest service pack for all products, the requirement of havingall products installed to the same service pack level no longer exists.ModelMart Synchronizer RemovedThe ModelMart Synchronizer feature has been removed from AllFusion MM.Previously it synchronized AllFusion ERwin DM and AllFusion PM modelswhile these models were stored in AllFusion MM. There is no longer adependency on AllFusion Model Manager in order to accomplishsynchronization. Synchronization is now done within AllFusion ERwin DM andAllFusion PM. For more information, see the AllFusion ERwin DM ReleaseSummary or the AllFusion PM Release Summary.Change in Database Support PolicyThe following are the changes in the database support policy for AllFusionModel Manager r7:Additional database version supportDatabases no longer supportedAdditional Database Version SupportAllFusion Model Manager has added support for additional databases. TheAllFusion MM Connection Manager dialog now supports the followingadditional database:Microsoft SQL Server 2005Databases No Longer SupportedThe AllFusion Model Manager has dropped support for some databases. TheAllFusion MM Connection Manager dialog no longer displays the followingdatabase:Informix。