Readme for SATI 3.2

ATTO Ethernet Suite for FastFrame 3® 10/25/40/50/100GbENetwork Adapters with ATTO 360 Tuning, Monitoring, andAnalyticsRelease v3.00 – Linux®1. General Release InformationThese product release notes define the new features, changes, known issues and release details that apply to the FastFrame3® 10/25/40/50/100GbE Network Adapter product, ATTO 360 Tuning Software for Linux, and Linux driver v2.10 that was released on May 12th 2021. This information pertains to the following operating systems: CENTOS/Red Hat Enterprise Linux (versions 7.6, 7.8, 7.9, 8.2, 8.3) and Ubunto (version 18.04 LTS, and 20.04 LTS)2. Changes•Version 3.00 (Released 5/12/2021)o New Features/Enhancements▪Added iSER and NFS over RDMA presets▪Added RDMA stats counters in both app and Prometheus▪Added RDMA options to Linux installer▪Added alert to detect missing components when selecting RDMA profile▪New alerts to detect RX miss conditions and RDMA out of order conditions▪Update Grafana to 7.4.1 and Prometheus to 2.24.1▪Allow overriding the default retention policy for Prometheus▪Added stats reset button in app▪Added Readme▪Get version for RHEL / CentOS release▪Install Podman from ATTO repo▪Install additional OFED dependencies on Linux installs▪Upgraded OFED driver to 5.3-1.0.0.▪Removed the MFT tools from the Linux installer as they are now bundled with the OFED driver▪App no longer requires gtk-launch to launch from command line •Version 2.00 (Released 2/4/2021)o New Features/Enhancements▪Fix race condition when determining performance mode state▪Added missing separator line from lro in nic info.▪Fix null reference in GetPCIGeneration() error path▪Ensure `python3-distutils` and `dkms` are present on Ubuntu▪Removed autoscrollbar from Diagnostic table▪Added scrollbar to transceiver information popup.▪Devices not found on CentOS 8.3▪Added Ubuntu 18.04 / 20.04 support▪Move initialization of platform tool locations▪Fixed visibility of lines separating switch objects.▪Upgraded WinOF2 to 2.60.50000 and WinMFT to 4.16.0.105▪Add support for CentOS 7.9 and CentOS 8.3▪Added Ubuntu 18.04 / 20.04 support▪Added Autodesk profile•Version 2.00 (Released 10/22/2020)o New Features/Enhancements▪Now Included with ATTO 360 Tuning, Monitoring, and Analytics software V2.00 bundled with driver installer•Version 1.00 (Released 1/7/2019)o New Features/Enhancements3. Known Issues/Advisementso Please refer to ATTO 360 User manual at https:///pdfs/PRMA-0495-000.pdf for information and helpful hints on how to utilize ATTO 360 software4. Affected ProductsProduct Name SKUFastFrame3 N322 FFRM-N322-DA0FastFrame3 N351 FFRM-N351-DA0FastFrame3 N352 FFRM-N352-DA0FastFrame3 N311 FFRM-N311-DA0FastFrame3 N312 FFRM-N312-DA05. Contacting ATTO SupportATTO Technology, Inc. is renowned for its technical support services. ATTO’s goal is to provide you the quickest response possible for your technical support needs. Please visithttps:///support/ for hours of operation.ATTO Technical Support can be contacted via phone or email:•Phone: 716.691.1999 ext. 242•E-Mail: ************************。

系统部分：可以选择RHEL或者SLESCaliber需要安装在特定的系统下，不然会出现如下警告：WARNING: This linux release is not supported for use with caliber products.解决方法：选择合适的Linux系统，图中列出了支持的Linux系统按照提示安装SLES，安装过程中确认主语言是英语，副语言是简体中文，从而使EDA工具和openoffice都不会出错！独立显卡的驱动安装：拷贝驱动文件到家目录，然后按Ctrl+Alt+F1，使用root登陆，之后输入init 3，之后找到驱动并运行，等安装完毕，输入init 5，返回图形界面。

Openoffice安装方式：下载地址：/download/解压，并进入rpm文件夹，打开终端并输入rpm –ivh *.rpm进入desktop-integration文件夹，运行freedesktop对应的rpmSLES 11 SP2支持自动加载NTFS格式移动存储介质的方法：先用root终端进入/etc/hal/fdi/policy，然后使用vim新建10-ntfs-3g-policy.fdi并输入以下内容：<?xml version="1.0" encoding="UTF-8"?><deviceinfo version="0.2"><device><match key="volume.fstype" string="ntfs"><merge key="volume.fstype" type="string">ntfs-3g</merge><merge key="volume.policy.mount_filesystem" type="string">ntfs-3g</merge><append key="volume.mount.valid_options" type="strlist">locale=</append></match></device></deviceinfo>然后再建立preferences.fdi并输入以下内容：<?xml version="1.0" encoding="UTF-8"?> <!-- -*- SGML -*- --><!--Some examples how to use hal fdi files for system preferencesYou can either uncomment the examples here or put them in a seperate .fdifile.--><deviceinfo version="0.2"><!--The following shows how to hint gnome-volume-manager and other programsthat honor the storage.automount_enabled_hint to not mount non-removable media.--><device><match key="storage.hotpluggable" bool="false"><match key="storage.removable" bool="false"><merge key="storage.automount_enabled_hint" type="bool">false</merge></match></match></device></deviceinfo>最后运行如下代码：/etc/init.d/haldaemon restart去下载最新的ntfs-3g源文件包ntfs-3g_ntfsprogs-****.tgz 解压，进入到解压文件夹并开启终端，在终端中依次输入：./configuremakemake install （此命令必须以root执行）等执行完毕，NTFS格式的移动硬盘就能像U盘一样自动挂载！IC5141部分：需要：base包和USR6 update包IC5141_bse包：ed2k://|file|Cadence.Base.IC5141.Lnx86.3CDs[.ck].rar|1201102747|A4DE108A291CC6BDD86D8E46D3E5 A677|h=PWYDUTUBIMHDVZ2EDLNMRNAKGAVIWJFA|/USR6_update包：/viewthread.php?tid=219912&highlight=USR6安装软件：解压和放置IC5141_base包和USR6_update包到/home/kury/cadence_install，文件夹分别命名为base和update。

RTCM3.2格式数据查看
借助RTKLIB工具查看RTCM数据。
一、打开 rtknavi

二、点击“I”（输入）
三、配置rover type –》file format –》rtcm3，选择数据文件

点击“OK”
四、点击“□”，打开RTK monitor

选择rover 和 RTCM3
点击“start”

可查看RTCM3.2文件内容，如上1074、1084、1094报文，分别对应GPS、
GLONASS、BDS卫星数据。类似方法亦可举一反三，查看其它格式数据内容。

Getting Started instructions for a Tracker 3200S using the Huntron Workstation 4.3 software1-1 Recommended Controller (PC)The following are provided to assist you in purchasing the correct computer system to use with the Huntron Workstation software.•Multi-core processor; Intel i7 or similar recommended•Microsoft Windows 10•8GB+ RAM•Solid state hard drive•1920x1080 video resolution•DVD drive•Keyboard and Mouse•Internet Connection•One available USB port1-2 Installing the Huntron Workstation SoftwareNOTE: Install the software before connecting the Tracker 3200S to the PC.1. Power up your computer. Insert the software DVD into the optical drive.2. If your drive was configured for Auto-run, a menu will be displayed. Click theWorkstationSetup item. If no menu is displayed, run the WorkstationSetup.exe program located on the DVD.3. A Huntron License Agreement form is displayed. If you agree, select the “I acceptthe license agreement” option. Click Next. The readme.txt file on the DVD willbe displayed. Click Next4. The default destination folder is C:\Program Files\Huntron Workstation. ClickNext if you do not want to change the default folder.5. Select the options for desktop and taskbar icons.6. Click Next to begin installation.7. If you will not be connecting your Tracker 3200S to an Access Prober, answer NOto the questions regarding Access Prober related Camera and NI Visioninstallations.8. Click Finish when the “Huntron Workstation has been successfully installed”window is displayed.Do not run the software at this point. The hardware must now be installed to complete the installation.1-3 CONNECTING THE TRACKER 3200SNote for Windows 64bit users: The device driver may attempt to auto install and fail. After following the steps below (they may not all occur), open Device Manager and look under Huntron devices for the Tracker 3200S with a yellow exclamation point. Update this driver by right clicking on them. Select the install DVD for the source of the driver if needed.1. Connect the Tracker 3200S power cord to a power outlet.2. Connect the USB cable to the Tracker 3200S and the PC.3. Turn on the Tracker 3200S power4. An Add New Hardware wizard prompts you to install a “Huntron Tracker Model3200S”. If prompted to find driver on the Internet select No and Click Next.5. If the wizard prompts you to automatically find drivers, click Next.6. When a message appears, indicating that the driver has not passed Windows Logotesting, click “Continue anyway”. Then click Finish.7. Install any other equipment to be used with the Huntron Workstation software.8. Remove your Huntron Workstation DVD. You are now ready to use the software.9. A Huntron Workstation icon was created on your windows desktop. Double clickthis icon to start the software.10. The Huntron Workstation Activation dialog is displayed. This software is onlylicensed to be used on one Tracker 3200S. The activation codes are generated by Huntron and are specific to the Tracker 3200S serial number. Activation codes are printed on the software DVD. If you do not know the activation codes, call Huntron technical support (425-743-3171) and provide the serial number for the Tracker3200S. Tracker 3200S serial numbers start with a 32S.1-4 CONFIGURING THE TRACKER 3200S1. When the Workstation main screen is displayed, on the main menu, select Tools->Options->Hardware. Set the Tracker to Tracker 3200S. Set the Tracker Port toUSB.2. Set the Prober settings as needed (refer to Prober Getting Started document).3. Click the connect buttons for the Tracker and Prober if used.4. Click the Save button.5. NOTE: The Tracker 3200S is already calibrated at the factory. However, if you areconnecting a Tracker 3200S to a Prober, you will need to calibrate it as a complete system.6. Connect the Tracker 3200S to your Prober, follow the steps below to calibrate thesystem.7. Tracker 3200S Calibration for ProberTo access the calibration window, click Tools->Maintenance->Tracker3200S Diagnostics.Do not click the Verify Hardware button. This routine requires special hardware and test procedures.Click the Alignment button. Ensure that all cables are connected. The calibration routine will run for a few minutes. Do not power off any of the instruments during this process. After a successful calibration, click the Verify Alignment button. If you get a “successful verification”, click Close to exit the Diagnostic window. If you get a “Verification Failed” message, Re-run the Alignment routine and run the Verify Alignment again. If it still fails, call Huntron Technical support.Return to Tools->Options->Hardware and click the Connect button(s) for the appropriate hardware.1-5 Follow the software tutorial.A software tutorial is included in the software DVD Documents folder and in the default installed folder (C:\Program Files\Huntron Workstation 4.3\Documents). The tutorial can also be accessed via the Help menu in the software. If you purchased an Access Prober follow the Workstation Tutorial.pdf, otherwise follow the Workstation Tutorial Tracker 3200S.pdf. The tutorial will enable a new user to get acquainted with most of the software features. The help menu in the software will also assist you.Whenever you need detailed information, click Help in the appropriate screens.All user’s manuals are located in the Manual CD (06-5217) included in your package. Use the Tracker 3200S Manual.pdf file to view or print the manual.If you need further assistance, call the Huntron Technical support at1-(800)-426-9265 or (425)-743-3171email:****************--------end of document--------。

FEATURE OVERVIEWUsing TRACE32 for IEC 62304TRACE32 for IEC 62304 at a Glance• TRACE32 Tool Qualification Support-Kit streamlines TRACE32 tool qualification effort and costs.• TRACE32 TQSK is fully featured, field proven and ready to cover new use casesand requirements.• TRACE32 TQSK Customer Interface provides full support and service around tool qualification.• All test suites run in the target environment and are fully multicore aware.• Test Suite Coverage includes statement, decision, condition, function and call coverage, as well as MC/DC.• TRACE32 Instruction Simulator, TRACE32 Debug and Trace Tools, USB Debug and Trace provide comprehensive tool support throughout all project phases.Website-LinksTRACE32 Trusted Tools for Functional Safety /trusted_tools.htmlTQSK Customer Portal /register_tqsk.htmlTRACE32 Code Coverage /coverage.htmlTRACE32 Instruction Set Simulator /sim.htmlThe TRACE32 Tool Qualification Support-Kit (TQSK) provides everything needed to qualify use in safety-related software projects.Figure 1: The 2-stage qualification processCertification ArtifactsDocumentsTest SuiteTool Verification and Validation Supplement for Integration toOperational EnvironmentTest Suite DocumentsTest ReportTesting in Operational EnvironmentTest Report Testing inTSSTCTest Suite Simulator TriCore(paid)DSMDeveloper SafetyManualTSCTest Suite Coverage(free)TSDTest Suite Debug(free)$$TSSATest Suite Simulator Arm(paid)Test Suite SimulatorUpon customer request, Lauterbach also provides test suites for its Arm and TriCore Instruction Set Simulators. A qualified instruction set simulator is an accepted test environment in the software module testing phase of the project (see also figure 3) and offers the following advantages:• Product software qualification can start before product hardware is available.• The qualification of the product software can be well organized even in a distributed team, becauseeverything necessary is purely software-based.• If bottlenecks occur during this phase due to a lack of development hardware or debug/trace tools, additional test benches can be easily equipped with simulators.Test Suite DebugThe Test Suite Debug includes all basic debugging functionality such as target configuration, programming onchip and NOR flashes, loading programs, setting breakpoints and reading/writing of memory and variables.Figure 3: TRACE32 tool use in code coverage qualification。

Matrox® Release Notes Matrox® Extio 3 SeriesSoftware version 3.02.0320265-401-0009November 5, 2021OverviewThis document describes the current release (version 3.02.03) of the Matrox Extio 3 firmware, OSD (On-Screen Display), and the Extio Central Manager software.Matrox provides these notes to describe new features, bug fixes, and improvements to Extio 3 Series hardware and software.First-time setup of point-to-point modeWhen using your devices out of the box and setting them up for the first time, theon-screen display (OSD) on the Receiver (Rx) device show an initial log-in screen.To enable point-to-point mode, click Enable Point-to-Point mode on the log-inscreen. (Point-to-point uses a direct link between the Transmitter (Tx) and Receiver (Rx) devices, without going through a network switch.) Selecting this option reboots your devices to complete the configuration process.For more information on performing a configuration reset, see your Matrox Extio 3 Series User Guide.What’s n ewIn this section, you will find the fixes done in the 3.02.03 packages.Fixes and improvements⏹ A problem with UPnP detection found in the 3.02.00 release has been fixed.⏹ A problem with a specific NFC card reader model was found and fixed.⏹ A problem with a specific touchscreen model was found and fixed.Notes and limitations⏹Absolute mouse position (operating system limitation) - As of theMicrosoft Windows 10 updates released in May 2021, the absolute mouseposition feature is broken. This feature allows Matrox Extio 3 to supportmulti-monitor systems in aggregator mode. This operating system limitationaffects Matrox Extio 3 when using two or more independent displays from asingle host/Tx as part of an aggregation. You will not be able to access anydisplay except the primary of each host/Tx. This limitation does not impactmulti-monitor systems running in stretched desktop mode.⏹OSD languages– English is the only language currently supported in theOSD. The Keyboard Language allows support for non-English keyboards.2 Matrox® Release Notes – Matrox® Extio3 Series⏹Touch screen – Once the displays are configured, it is recommended to notchange the physical USB ports on the Rx, since this may cause the loss oftouch functionality.⏹Touch screen– It is recommended that you disable the USB powermanagement feature of the USB hub that the Tx unit is connected to. This isto prevent some touch screens from losing USB communication due to theUSB hub going into a power management state.⏹Aggregator mode– The Link Redundancy feature isn’t currently supportedwhile using aggregator mode.⏹Guest connections–With guest connections, the following aren’t currentlysupported: RS232, audio Line In and microphone.⏹Firmware Updater– To update the firmware, the UpdaterFromHost.exe fileinstalls a USB mass storage device on the Extio 3 transmitter unit. On certain systems, the Group Policy Object (GPO) may prevent theUpdaterFromHost.exe file from installing the USB mass storage device. Toallow the installation of this Matrox device, you may need to apply anexception to your GPO rules (for example, by addingUSBSTOR\DiskMatrox__Virtual_Storage_1.00). For more information onmodifying your GPO rules, contact your system administrator.⏹Firmware– Update your Tx and Rx devices to firmware version 3.02.03before using your devices. To update new units or units already configured in networked mode, use UpdaterOverNetwork.exe to update your units. If you’re updating units already configured in point-to-point mode, useUpdaterFromHost.exe to update your units.⏹Firmware– To ensure proper functioning of your devices, the firmwareversion installed on your Tx and Rx devices must match.⏹Firmware– When updating your firmware, make sure your Extio 3 setup isusing either point-to-point mode or networked mode, and not a mix ofoperating modes. [2277]1⏹Firmware– ASMedia 3.1 USB controllers may cause issues with thefirmware update in Point-to-Point. For systems that have an ASMedia 3.1USB controller, we recommend using one of the other host USB controllers,such as Intel.⏹Firmware – When performing a firmware downgrade from 3.02.03 to 3.01.00in Point-to-Point, you will have to manually reset and reconfigure Point-to-Point.1 Tracking reference numberMatrox® Release Notes – Matrox® Extio 3 Series 3⏹The following features are n’t yet enabled:▪Local output support (Video out) on the Tx device is expected in anupcoming release.▪The USB connectors on the front of the Tx device are currentlydisabled.⏹Matrox Mura IPX Series– T his firmware release isn’t compatible withMura IPX Series software version 3.00.00 or older.⏹If all of your devices are seen and configurable in Extio Central Manager, butthe OSD of an Rx device doesn’t reflect the connections that were configuredin the Connection Broker, verify that the devices all have a valid IP addressand that the network ports are accessible.▪If your devices are on a unicast network, on multiple subnets, or on a WAN network, use the new Transmitter Discovery option (in ExtioCentral Manager) to detect devices that may not be automaticallydiscovered.⏹Dell™ Precision™ Rack R7920 Workstation or PowerEdge™ R740 – Ifyour XTO3-N3408CTX or XTO3-N3208CTX card is installed in PCIe slot 1,that slot may not work. We recommend using a slot other than slot 1. If youneed to use slot 1, you need to disable that slot. To disable the slot, enter theSystem Bios, then click Integrated Devices→Slot disablement, and makesure the slot is marked as Disabled. When you’re done, save your change s andreboot your system. [803]⏹USB devices– Some older keyboard and mouse combos that use a Bluetooth®mini-receiver are n’t supported in networked mode. These devices may beused in point-to-point mode but need the manufacturer’s device drivers.[1262]⏹On some GPUs, outputs may have temporal dithering enabled. This mayresult in blocky images. To avoid this, make sure your GPU settings areconfigured to use RGB as the output color format and the maximum level (i.e.Full) as the output dynamic range. [1632]⏹Hot plugging SFP modules isn’t supported. A reboot may be required afteradding an SFP module to your device to ensure proper detection andfunctionality. [1963]⏹Random loss of Sync while in point-to-point mode– You may lose monitorsync briefly if the display refresh rate reported in the OSD of your Extio 3receiver does n’t match the refresh rate of your monitor. For example, this mayoccur if the GPU reports a refresh rate of 59 Hz. Setting the refresh rate to 60Hz should solve the issue.4 Matrox® Release Notes – Matrox® Extio 3 Series⏹If you’re using an adapter to connect your monitor to your Extio 3 device,o nly active adapters (sold separately) are supported. Passive adapters aren’tsupported.⏹When using aggregator mode and switching via keyboard shortcut, the mousepointer will remain visible on all displays in the last position before the USBwas switched. [2355]⏹When using some 2560x1600, 2560x1440, and 2560x1080 monitors with theDVI input of the display in Point-to-Point, you will need to verify that theOptimized Video Mode option is checked in the OSD, otherwise you mayexperience black screens.⏹Windows 7 only– When using aggregator mode and mouse position, werecommend using either a single independent desktop or a stretched desktop.For more information, see “Aggregator mode compatibility.” [2349]⏹Wake-on-LAN– N3408CTX and N3208CTX cards support wake-on-LAN. Known issues⏹After adding a new Tx device and configuring it using Extio Central Managersoftware, it can take up to 45 seconds for the new Tx device to appear in theOSD as an available connection option for the Rx.⏹USB – Switching while using USB 2.0 devices (i.e. USB keys, hard drives,scanners, etc…) isn’t supported and may result in lost data or devices (need tounplug/replug device to redetect). We recommend stopping all USB 2.0transfers before switching.⏹USB – Loss of connection between a Tx and an Rx (power interruption,network failure or fiber failure) while doing USB 2.0 transfers may result inlost devices (need to unplug/replug device to redetect) or lost data.⏹Firmware Updater– When the Updater has completed, a message mayappear stating that not all Extio 3 Series devices were properly updated. If thisoccurs, close the updater and re-launch it. If the devices report that they needan update, proceed with the update. If the update fails again, please contactMatrox Technical Support.⏹After updating your firmware, one of the displays connected to your Rx maybe lost. To fix this, we recommend you turn off the monitor and then turn it onagain.⏹After rebooting your Tx or Rx, one of your displays may be lost. To fix this,we recommend you turn off the monitor, and then turn it on again.Matrox® Release Notes – Matrox® Extio 3 Series 5⏹Point-to-point mode– When rebooting your source system or host system,the connection between the Tx and Rx devices may be lost. To fix this, werecommend you use the Refresh connection option in the OSD.⏹Wake-on-LAN– When using the wake-on-LAN feature with an N3408CTXor N3208CTX card installed in HP Z440 workstations, the devices maybecome unresponsive and require the system to be rebooted. [1819]6 Matrox® Release Notes – Matrox® Extio 3 SeriesAggregator mode compatibility2 While using USB switching, the mouse position is limited to the first display.3 While using USB switching with a 4x1 monitor layout, the mouse pointer is visible on all four (4)displays.4 Certain limitations may occur (for example, the mouse pointer may disappear).5With the Microsoft Windows 10 updates released in May 2021, the absolute mouse position feature isbroken. This limitation affects Matrox Extio 3 when using two or more independent displays from asingle host/Tx as part of an aggregation. You will not be able to access any display except the primary of each host/Tx.Matrox® Release Notes – Matrox® Extio 3 Series 78 Matrox® Release Notes – Matrox® Extio 3 SeriesContact usThe Matrox web site has product literature, press releases, technical material, a sales office list, trade show information, and other relevant material. Visit us at/video.If you have any questions or comments about our products or solutions, contact us at /en/video/contact.Matrox values your business and offers professional support for your Matroxproduct. For more information, contact your Matrox representative or our technicalsupport at *********************.Matrox® Release Notes – Matrox® Extio 3 Series 9DisclaimerInformation in this document may contain technical inaccuracies or typographicalerrors. Information may be changed or updated without notice. Matrox reserves the right to make improvements and/or changes in the products, programs and/orspecifications described in this information at any time without notice. Alltrademarks and trade names, service marks and logos referenced herein belong totheir respective owners.Bluetooth is a registered trademark of Bluetooth SIG, Inc.Dell, Precision, and PowerEdge are trademarks or registered trademarks of Dell Inc.or its subsidiaries.Linux is a registered trademark of Linus Torvald in the United States and in othercountries.MacOS is a trademark of Apple Inc., registered in the U.S. and other countries.Microsoft, Windows, and Active Directory are registered trademarks of MicrosoftCorporation in the United States and/or other countries.Copyright © 2021 Matrox is a trademark of Matrox Electronic Systems Ltd. Allrights reserved.10 Matrox® Release Notes – Matrox® Extio 3 SeriesMatrox Graphics Inc.1055 Saint Regis Boulevard Dorval, Quebec, CanadaH9P 2T4(514) 822-6000 **************** /video。

SkyEye用户手册SkyEye-1.3.2维护者：Michael.Kang邮件：blackfin.kang@修订记录目录Table of Contents第一章SkyEye的介绍和安装 (5)1.1 介绍 (5)1.2 安装 (5)1.2.1 二进制的rpm包安装 (5)1.2.2 源代码安装 (5)1.3 安装后的目录和文件 (6)第二章SkyEye快速入门 (7)2.1 运行SkyEye的命令行应用程序 (7)第三章、SkyEye命令列表 (10)3.1 调试相关的命令 (10)3.1.1 break (10)3.1.2 list-bp (10)3.1.3 show-step (10)3.1.4 stepi (10)3.1.5 show-step (10)3.1.6 x (11)3.1.7 disassemble (11)3.1.8 info registers (11)3.2 显示目标板及运行环境 (12)3.2.1 list-options (12)3.2.2 show-map (12)3.2.3 show-pref (13)3.2.4 list-modules (13)3.2.5 list-machines (14)3.3 目标板控制命令 (14)3.3.1 start (14)3.3.2 run (15)3.3.3 continue (16)3.3.4 stop (16)3.3.5 quit (16)3.4 其它杂项命令 (16)3.4.1 help (16)第四章SkyEye配置文件 (18)4.1、skyeye的配置文件skyeye.conf (18)4.2、skyeye.conf文件的格式 (19)4.3、skyeye.conf中的不同选项 (20)4.3.1 arch 选项 (20)4.3.2 cpu选项 (20)4.3.3 mach选项 (20)4.3.4 mem_bank选项 (20)4.3.5 网络选项 (21)4.3.6 lcd 选项 (22)4.3.7 uart 选项 (22)4.3.8 load_addr选项 (22)4.3.9 load_file 选项 (23)4.3.10 uart_16550 (23)第五章、在SkyEye上运行和调试不同的程序（暂无） (25)码 (26)第六章、代覆盖率分析码绍 (26)6.1、代覆盖率介6.2、配置文件选项 (26)6.3 代码覆盖率数据文件 (26)6.4 利用SkyEye进行代码覆盖率统计 (27)6.4.1 添加配置选项 (27)6.4.2生成数据文件 (27)6.4.3 数据文件转换 (27)6.4.4 测试结果验证 (27)第八章、性能分析模块 (29)8.1 介绍 (29)8.2 使用 (29)第九章gdb远程调试 (30)9.1介绍 (30)9.2 用法 (30)9.2.1 在SkyEye这一端的操作 (30)9.2.2 编译对应平台的gdb (30)9.2.3 调试程序 (30)9.2.4 演示截图 (31)第一章SkyEye的介绍和安装1.1 介绍skyeye是一个支持多架构，多核，并且高度可扩展的硬件仿真平台，当前主要由核心库libcommon.so和基于核心库的一系列插件组成。

...the world's most energy friendly microcontrollersLow Energy UARTAN0017 - Application NoteIntroductionThis application note demonstrates how to use the Low Energy UART (LEUART™)module on the EFM32 microcontrollers. The LEUART is able to run full UART communication even when the device is in deep sleep mode EM2. Together withintelligent interrupt functions and flexible DMA integration, this enables simple andenergy friendly communication .This application note includes:•This PDF document•Source files (zip)•Example C-code•Multiple IDE projects1 LEUART Theory1.1 General theoryThe EFM32 LEUART is a unique Low Energy UART that offers two-way communication on a very strict power budget. Only a 32.768 kHz clock source is needed to allow UART communication up to 9600 baud/ s. This means that the EFM32 LEUART can operate in deep sleep mode EM2, and wait for an incoming UART frame while consuming extremely little energy. When a UART frame is completely received by the LEUART, the CPU can quickly be woken up. Alternatively, multiple frames can be transferred to memory by the DMA before waking up the CPU. The EFM32 LEUART also incorporates functionality to handle higher level communication protocols, e.g. the option to block incoming frames until a configurable start frame is detected, and to detect a configurable signal frame (to indicate e.g. the end of a transmission). In the same way as received, data can be transmitted in EM2 either on frame by frame basis with data directly from the CPU, or in larger groups of frames trough the DMA. The EFM32 LEUART includes all needed hardware support to make asynchronous serial communication possible with minimum software interference, while consuming extremely small amounts of energy.The advantage of the LEUART is the ability to operate in EM2, while most other modules are turned off for energy conservation. The option to enable low energy serial communication, in combination with the DMA's ability to read and write from memory without CPU intervention, offers wide functionality for system designers using the EFM32 in low energy applications.Figure 1.1. LEUART two link full duplex connection2 LEUART Configuration2.1 Frames, Transmission & ParityThe LEUART relates to frames for data transmission. A LEUART frame consists of a start bit, 8 or 9 data bits, an optional parity bit, and 1 or 2 stop bits (Figure 2.1 (p. 3) ). A transmission is initiated by a start bit that pulls the line down from its idle high state. After that the data and parity bits are sent sequentially until the frame transmission is ended by the stop bits that holds the line high. Then the line either enters its high idle state, or a new start bit is sent. Technically, when a frame is ready to be transmitted, it is transferred from the transmit register to a shift register where the bits are sent one by one, least significant bit first. The entire frame format can be inverted, to e.g. allow use of low idle state. The parity bit at the end of the data transmission is an optional method for light error detection. Three different parity modes are available: that is no parity, even parity and odd parity. All parity generation and checking are done in hardware, and interrupt flags are available to indicate if parity error in the frame is detected. The frame format wanted is set during initialization of the selected LEUART. The emlib offers a initialization function that defines all the necessary settings to start communication using the LEUART. All parties of the communication channel must agree on the frame format for communication to be possible. For more extensive information on the LEUART registers and opportunities, refer to the reference manual for the device.Figure 2.1. LEUART frame formatS0*******[8]S top S tart or idleS top or idle[P]2.2 Clock SourcesThe LEUART, like other LE peripherals in the EFM32 microcontrollers, can be driven by three different clock sources, the Low Frequency RF Oscillator (LFRCO), the Low Frequency Crystal Oscillator (LFXO) and the High Frequency Core Clock divided by 2 (HFCORECLK_LE/2). The HFCORECLK_LE can in turn be driven by either the High Frequency RC Oscillator (HFRCO), High Frequency Crystal Oscillator (HFXO) or even any of the LF oscillators mentioned. This flexibility in assigning clocks, gives the system designer a wide range of possibilities for using the LEUART features. This means that beside running on a LF clock source during low energy operation in EM2, the LEUART can also be utilized as a supplement to the UART when more UART communication channels are needed. However for the LEUART to achieve baud rates above 9600 baud/s, the chosen clock source must be the HFCORECLK_LE/2 which is only available in EM1-EM0.2.3 Baud ratesThe selected LEUART clock source defines the baud rates that are obtainable through the LEUART. In standard Low Energy operation, the LEUART offers baud rates between 300 to 9600 baud/s on a 32.768 kHz clock. For details on which baud rates are supported, refer to the reference manual for the device. The emlib also includes methods for calculating which baud rates are available, extracting the current baud rate, and setting the baud rate. With the HFCORECLK_LE/2 selected as th LEUART clock source, higher baud rates are obtainable, but this also implies that the LEUART it will not operate below EM1 and more energy is needed. In addition, since one of the HF clock need to be running, both the UART and USART are also available.2.4 DMA IntegrationThe LEUART has full DMA support even in EM2. In integration with the LEUART, the DMA is a very powerful tool to minimize the need for CPU interference.•The LEUART can be configured to request DMA for data either when the transmit buffer is empty or if both the transmit buffer and the shift register are empty.•The LEUART can be configured to request the DMA to read when the receive buffer is full.•When a frame of parity error is detected in the receive register, the ERRSDMA bit in the LEUARTn_CTRL register can be set to omit the read request to the DMA.When operating in EM2, the DMA controller must be powered up in order to perform the transfer. This is automatically performed for read operations if RXDMAWU in LEUARTn_CTRL is set and for write operations if TXDMAWU in LEUARTn_CTRL is set. To make sure the DMA controller still transfers bits to and from the LEUART in low energy modes, these bits must be configured accordingly. In EM2 the DMA runs off the HFRCO which is also woken up and shut off automatically. The DMA must also be enabled and configured correctly to handle the LEUART data. For more information on how to initialize an interaction between the LEUART and DMA, see the supplied software examples and the reference manual for the device.2.5 Pulse Generator and ExtenderThe LEUART has an optional pulse generator for the transmitter output, and a pulse extender on the receiver input. It will change the input and output format of the LEUART from NRZ to RZI. The width of the pulses from the pulse generator can be configured from 31.25 µs to 500 µs. At 2400 baud/s or lower, the pulse generator is also able to generate RZI pulses compatible with the IrDA physical layer specification.2.6 InterruptsA wide variety of interrupts are available, both during receive and transmit, to support the low energy advantages of interrupt driven applications. An interrupt can be triggered when the receive or transmit registers are empty, or if any errors are detected during transmit. Also there is the ability for the LEUART to trigger an interrupts when specific configurable frames are detected. This allows the construction of higher level communication protocols on top of the LEUART. A special multi processor mode is even available to enable individual addressing and trigger only the desired MCU to receive and act on the data sent. This is a useful feature in systems where multiple UART ICs are communicating on the same channel. In this way the desired receiver can be addressed by starting and ending the transmission with certain frames that will only trigger an interrupt in the desired receiver. In the software examples supplied, the Signal Frame Interrupt functionality is used to wake the CPU only when a specific frame is detected. All other frames are loaded into the memory by the DMA and do not generate any response from the CPU until the preconfigured Signal Frame is detected by the LEUART.2.7 Freeze Mode and LF Domain SynchronisationSynchronization into the low frequency (LF) domain is necessary to modify some of the LEUART registers. To avoid unnecessary stalling when multiple registers are to be modified, all register writes should be done inside a block initiated by void LEUART_FreezeEnable(LEUART_TypeDef *leuart, bool enable) where enable is set true, and ended by the same function call where enable is set false. In this way all register modifications will be performed during a single synchronisation. See the reference manual for the device for more information on accessing and modifying asynchronous registers.2.8 Half-Duplex OperationThe LEUART offers an option to locally loopback the transmitted data to the receive pin. This is useful for debugging, as the LEUART can receive the data it transmits, but it is also used to allow the LEUART to read and write to the same pin, which is required for some half duplex communication modes. When doing full duplex communication, two data links are provided, making it possible for data to be sent and received at the same time. In half duplex mode, data is only sent in one direction at a time. There are several possible half duplex setups. Both single and double data-links, or with an external driver. When communicating over a single data-link, the transmitter must be tristated whenever data is not transmitted. The LEUART can automatically tristate the transmit pin whenever the transmitter is inactive, if the AUTOTRI pin in the LEUARTn_CTRL register is set.2.9 GPIO and RoutingThe LEUART modules have the ability to route its TX and RX pins to some different predefined locations on the MCU pinout. The LEUARTn_ROUTE register must be set to enable and route the pins to the desired location.To enable the LEUART to interact with any external system components, like the RS232 port or another peripheral IC, the GPIO I/O pins must be configured accordingly. The GPIO has a variety of different pin modes available, and in the supplied code examples the TX pins are configured as push-pull output. The RX pins are enabled as inputs with a pull-up. The pull-up helps to define the input state in case line is not driven to a defined value by the other part. This can happen if you enable the RX module before the TX module. Refer to the application note "AN0012 GPIO" more examples on GPIO mode setting.3 Software ExamplesThe following software examples demonstrates a way to achieve full UART communication, using the LEUART functionality of the EFM32.3.1 Listening and Receiving in EM2.In this example, LEUART communication is initialized using the DMA to transfer received data from the LEUART receive register to the system memory. When a preconfigure signal frame is received, the LEUART generates a interrupt, and the CPU wakes up and writes all the received data from the memory to the LCD.3.1.1 Example 1: Receiving on DVKThis DVK can receive data both trough RS232, and directly through the pinout on the Prototype Board. This means that the example can be run in a variety of different setups, receiving data both from another DVK, a STK or a PC trough the RS232 port on the DVK. The LEUART1 RX pin is located on pin J10 on the DVK Prototype Board, and needs to be connected to the TX pin on the transmitting DVK or STK, or trough a RS232 cable to a PC. Note that the sender and received must have same ground and supply voltage when connecting the RX and TX lines directly without using the RS232 port.3.1.2 Example 2: Receiving on STKOn the STK the data can be received trough the pinout located along the rim of the board. The LEUART1 RX pin is located on the PC7 pin on the bottom row.3.2 Transmitting in EM2.In this example, LEUART communication is initialized using the DMA to transfer data from a location in the local system memory to the LEUART, on given RTC(Real Time Clock) interrupts. Every other second, the RTC interrupt initializes the DMA to start feeding the LEUART TX transmit register with data, and returns to EM2. One of two predefined strings is then transmitted trough the LEUART to anyone listening. The two strings will alternate.3.2.1 Example 3: Transmitting from DVKThe DVK can send data both directly through the pinouts on the Prototype board, and through the RS232 port provided. The example can in this way be set up and run in several different setups, both transmitting to another DVK, a STK or a PC. The LEUART1 TX pin is located on the pin J9 on the DVK Prototype Board, and needs to be connected to the RX pin on any receiving device, or to a PC through the use of a RS232 cable to a PC. Note that the sender and received must have same ground and supply voltage when connecting the RX and TX lines directly without using the RS232 port.3.2.2 Example 4: Transmitting from STKOn the STK the data can be transmitted through the pinout located along the rim of the board. The LEUART1 TX pin is located on the PC6 pin on the bottom row.4 Revision History4.1 Revision 1.082013-09-03New cover layout4.2 Revision 1.072013-05-08Added software projects for ARM-GCC and Atollic TrueStudio.4.3 Revision 1.062012-11-12Adapted software projects to new kit-driver and bsp structure.4.4 Revision 1.052012-08-13Adapted software projects to new peripheral library naming and CMSIS_V3.4.5 Revision 1.042011-11-15Updated transmit examples to use DMA callback to allow sleeping while transmitting.4.6 Revision 1.032011-10-21Updated IDE project paths with new kits directory.4.7 Revision 1.022011-05-18Updated projects to align with new bsp version4.8 Revision 1.012010-11-16Changed example folder structure, removed build and src folders.Updated chip init function to newest efm32lib version.Updated register defines in code to match newest efm32lib release.4.9 Revision 1.002010-09-24Initial revision.A Disclaimer and TrademarksA.1 DisclaimerSilicon Laboratories intends to provide customers with the latest, accurate, and in-depth documentation of all peripherals and modules available for system and software implementers using or intending to use the Silicon Laboratories products. Characterization data, available modules and peripherals, memory sizes and memory addresses refer to each specific device, and "Typical" parameters provided can and do vary in different applications. Application examples described herein are for illustrative purposes only. Silicon Laboratories reserves the right to make changes without further notice and limitation to product information, specifications, and descriptions herein, and does not give warranties as to the accuracy or completeness of the included information. Silicon Laboratories shall have no liability for the consequences of use of the information supplied herein. This document does not imply or express copyright licenses granted hereunder to design or fabricate any integrated circuits. The products must not be used within any Life Support System without the specific written consent of Silicon Laboratories.A "Life Support System" is any product or system intended to support or sustain life and/or health, which, if it fails, can be reasonably expected to result in significant personal injury or death. Silicon Laboratories products are generally not intended for military applications. Silicon Laboratories products shall under no circumstances be used in weapons of mass destruction including (but not limited to) nuclear, biological or chemical weapons, or missiles capable of delivering such weapons.A.2 Trademark InformationSilicon Laboratories Inc., Silicon Laboratories, the Silicon Labs logo, Energy Micro, EFM, EFM32, EFR, logo and combinations thereof, and others are the registered trademarks or trademarks of Silicon Laboratories Inc. ARM, CORTEX, Cortex-M3 and THUMB are trademarks or registered trademarks of ARM Holdings. Keil is a registered trademark of ARM Limited. All other products or brand names mentioned herein are trademarks of their respective holders.B Contact InformationSilicon Laboratories Inc.400 West Cesar ChavezAustin, TX 78701Please visit the Silicon Labs Technical Support web page:/support/pages/contacttechnicalsupport.aspx and register to submit a technical support request.Table of Contents1. LEUART Theory (2)1.1. General theory (2)2. LEUART Configuration (3)2.1. Frames, Transmission & Parity (3)2.2. Clock Sources (3)2.3. Baud rates (3)2.4. DMA Integration (4)2.5. Pulse Generator and Extender (4)2.6. Interrupts (4)2.7. Freeze Mode and LF Domain Synchronisation (4)2.8. Half-Duplex Operation (5)2.9. GPIO and Routing (5)3. Software Examples (6)3.1. Listening and Receiving in EM2. (6)3.2. Transmitting in EM2. (6)4. Revision History (7)4.1. Revision 1.08 (7)4.2. Revision 1.07 (7)4.3. Revision 1.06 (7)4.4. Revision 1.05 (7)4.5. Revision 1.04 (7)4.6. Revision 1.03 (7)4.7. Revision 1.02 (7)4.8. Revision 1.01 (7)4.9. Revision 1.00 (7)A. Disclaimer and Trademarks (9)A.1. Disclaimer (9)A.2. Trademark Information (9)B. Contact Information (10)B.1. (10)List of Figures1.1. LEUART two link full duplex connection (2)2.1. LEUART frame format (3)。

Rev. 1, 8/2021_______________________________________________________________________S32G eMMC 应用：GP ，RPMBbyJohn Li(nxa08200)目前S32G 的BSP(BSP29)的eMMC 启动，是将U-Boot 的镜像放在eMMC 的user partition 中,可以考虑将储存boot image 的部分配置为GP ，这样的损坏可能性要小一些。

另外一种办法是将U-Boot 储存在外部QSPI NOR 中。

由于目前S32G2的Rom codes 不支持从eMMC Boot Partition 启动，所以Boot Partition 的内容以后如果有更新的芯片支持，再做讨论。

另外也会说明一下如何使用eMMC RPMB 的应用。

通常情况下，对eMMC 的烧录都需要通过烧录工具，在S32G 上，可能是通过网络的OTA 升级，所以是需要在烧录工具的镜像中实现以下功目录1 eMMC 的分区情况 ......................................................2 2S32G+BSP29上默认的eMMC 启动 ............................ 3 2.1 eMMC 硬件设计 .................................................. 3 2.2 eMMC 的镜像烧写办法与启动 ............................. 6 2.3 增加MMC 内核测试工具 .................................... 10 3 eMMC GP 功能的测试 .............................................. 10 3.1 eMMC GP 功能的说明 ....................................... 10 3.2 eMMC GP 功能的测试 ....................................... 11 4 eMMC RPMB 功能的测试 ......................................... 13 4.1 eMMC RPMB 功能的说明 ................................. 13 4.2 eMMC RPMB 功能的测试 (15)S32G eMMC GP RPMB21eMMC 的分区情况大部分eMMC 都有类似如下的分区，其中BOOT 、RPMB 和UDA 一般是默认存在的，GPP 分区需要手动创建。