WinCE Target Control调试介绍
Eaton XSOFT-CODESYS V3.5.2 用户指南说明书
ManufacturerEaton Automation AG Spinnereistrasse 8-14CH-9008 St. Gallen Schweiz SupportRegion North America Eaton CorporationElectrical Sector1111 Superior Ave. Cleveland, OH 44114United States877-ETN-CARE (877-386-2273) Other regionsPlease contact your local distributor or send an e-mailto:********************Original instructionsEnglishRedactionDaniel LenherrBrand and product namesAll brand and product names are trademarks or registered trademarks of the owner concerned. Copyright© Eaton Automation AG, CH-9008 St. GallenAll rights reserved, also for the translation.None of this documents may be reproduced or processed, duplicated or distributed by electronic systems in any form (print, photocopy, microfilm or any other process) without the written permission of Eaton Automation AG, St. Gallen.Subject to modifications.Contents1XSOFT-CODESYS V3.5.2 (4)1.1Release information (4)1.2Version information (5)1.3Features (6)1.4Documentation (6)1.5Known restrictions (7)1.6Addressed Defects and Changes (9)2Migration guide (10)2.1Introduction (10)2.2Migration from CODESYS V2 to CODESYS V3 (10)1XSOFT-CODESYS V3.5.21.1Release informationProduct XSOFT-CODESYS-3Release 3.5.2Profile specification XSOFT-CODESYS V3.5.2Build 2092Setup Setup_XSOFT_CODESYS_V3.5.2Product Management H. HeckTest Management A. SchmidQuality Management P. Zuber1.2Version information1.2.1Programming system1.2.2Target firmwarefirmware.exe3.5.4 -RTS for XC-202btsxc202_v030504.bin1.2.3Target systemsXV-4xx 3.5.2.0 -XVS-4xx 3.5.2.0 -XC-202 3.5.2.0 -XC-152 3.5.2.0 -1.3FeaturesSince this is an initial release of a new generation of XSOFT-CODESYS, there are a lot ofenhancements and new features both in the programming and the runtime system. Pleaserefer also to CODESYS 3.x documentation.1.4DocumentationThe target system specific programming manuals are not part of this distribution. They arepublished on our web site in order to provide you the latestversion.1.5Known restrictionsdiagnostic message which is pending before start will not detected.1341 Target system XV-1xx, XVS-4xx and XC-152, SWD-DP-Gateway: If a reset operation isperformed with a quickly following start operation, the connection to the gateway cannotalways be established.→Workaround: Until this issue is fixed, use a longer break between reset and startoperation1315 Target system XV-1xx, XVS-4xx and XC-152, SWD-DP-Gateway: On initialization withbaud rate 9600 bit/s and 19200 bit/s communication problems can occur.1313 CAN: gc_bReadQueueSize has no effect on XV-1xx, XV-4xx, XC-152 => fixed value of256 is used for Input-Queue-Sizes1316 1272 Target visu, alarm management: On alarm tables, line breaks are not displayed correctly.1269 Data server: If the PC has multiple network adapters, the connection to data server does not work as documented in the online help.→The best way to get a connection is to search the target device by a network scan and to configure the specified node name of the device as data source.Please note: In the log file of the PLC with the configured data server you can seeif the connection is established or with which error it fails.1262 Target visu: Alarm management uses lot of system resources.→It is not recommended to use the alarm management with this release of the software..1261CDS-32587Target visu: Not all tables are refreshed automatically.1247CDS-31975Profibus DP Editor: Controls stay disabled after online mode1241 CDS-27947 Modbus Slave Device: Bit-Access function codes (Coils) are not implemented yet. →It is recommended to use register function codes instead.1240 CDS-28362 Modbus Slave: Unable to write Holding Register→Holding registers are defined as Input Channels. Therefore the local slave application can only read these data, but is unable to update the value of theholding registers. To enable this, the register shall be mapped to a global variable.1237CDS-31957Device Editor: Controls with parent control stay disabled after online mode1234 Target visu: Color Gradient is not supported yet1233 CANopen Inputs of missing nodes keep their values and are not set to default values1213 CDS-30962Target visu: Under the following condition, a bitmap will not be shown: The image is contained within an explicitly inserted image pool with name "ImagePool" that is located in the POUs and is used in the visualization.→Workaround: Until this issue is fixed, the following simple workarounds can be used: Move the ImagePool to the application and rename the image pool.1208 XSOFT-CODESYS is working only with 96 DPI display size properly. 1207 Target system XV-4xx, Profibus DPV1 functionality is not supported yet.1178 CDS-31968 Libraries SysFile23/SysFileAsync23, function SysFileClose(): PLC runtime system crashes if using function SysFileClose()1162 Udp network variables: If acknowledgment is selected, the response messages are missing1161 Target system XV-1xx, XV-4xx, XVS-4xx and XV-152, support of onboard flash is not yet included. The functions Sys_FlashInit(), Sys_FlashErase(), Sys_FlashWrite() andSys_FlashRead() are not supported yet.1148 RTS WinCE: GUI not yet refactored1147 CAN configuration: Support of 2nd CAN interface is not supported yet1143 CDS-31058 Retain Persistent Array with constant index: A compiler error appears if Retain Persistent Array with constant index was renamed afterwards.Workaround: Delete the object PersistentVars to fix this bug1108 CDS-27358Libraries SysFile23/SysFileAsync23, function SysFileRead(): PLC runtime system crashes if using function with invalid file handle (0).1105 On PLC reset, the handles are not closed automatically. 1094 Various documentation not yet included1079 CDS-30769Compile: The calculated size of persistent data is not always correct. Reorganization of persistent variables with Clean All required.1044 IOassistant not yet included1.6Addressed Defects and ChangesIt is an initial release version, there are no addresses defects and changes.2Migration guide2.1IntroductionIf you migrate projects from CODESYS V2 to CODESYS V3 take a few minutes to review thefollowing information.For further information, please refer also chapter "Known restrictions" (see chap. 1.5).2.2Migration from CODESYS V2 to CODESYS V32.2.1Retain data handlingManagementTicket 1115The retain data handling is not compatible to CODESYS V2.3. On the same hardware 44 bytes areless available.Variable declarations with keyword "PERSISTENTTicket 1186, 1197Variable declarations with keyword "PERSISTENT" are not supported.Use keyword "RETAIN PERSISTENT"2.2.2Library SysDir23Function SysDirOpen()Ticket 1109Function is not compatible to CODESYS V2.3. If an error occurs, it returns -1 instead 0.2.2.3Library SysFile23Various function blocksTicket 1177, CDS-4369Output parameter bDone and bError are not compatible to CODESYS V2.3.Function SysFileDelete()Ticket 1176Output parameter wErrorId is not compatible to CODESYS V2.3.Function SysFileOpen()Ticket 1173Function is not compatible to CODESYS V2.3. It is possible to open a file multiple times with mode"write".Ticket 1171, CDS-22259Function is not compatible to CODESYS V2.3. It is not possible to open a file with mode "append".Use the file open function and set the file pointer to EOF to append file data.Ticket 1106Function is not compatible to CODESYS V2.3. If an error occurs, it returns -1 instead 0.Function SysFileEOF()Ticket 1172, CDS-31922Function is not compatible to CODESYS V2.3. It returns true at different position.2.2.4Library SysFileAsync23Various function blocksTicket 1177, CDS-4369Output parameter bDone and bError are not compatible to CODESYS V2.3.Function SysFileDelete()Ticket 1176Output parameter wErrorId is not compatible to CODESYS V2.3.Function SysFileOpen()Ticket 1173Function is not compatible to CODESYS V2.3. It is possible to open a file multiple times with mode"write".Ticket 1171, CDS-22259Function is not compatible to CODESYS V2.3. It is not possible to open a file with mode "append".Ticket 1106Function is not compatible to CODESYS V2.3. If an error occurs, it returns -1 instead 0.Function SysFileEOF()Ticket 1172, CDS-31922Function is not compatible to CODESYS V2.3. It returns true at different position.2.2.5Library SysTask23Function SysTaskGetInfo()Ticket 1170, CDS-31774Function is not compatible to CODESYS V2.3. Return values SysTaskInfo.dwId andSysTaskInfo.wIECTaskNr are always 0.→Use library SysTask and CmpIECTask2.2.6Library SysTaskInfo23Function block TaskInfo()Ticket 1111, CDS-29769, CDS-30577Function block is not compatible to CODESYS V2.3. Return values of output parameters arealways 0.→Use library SysTask and CmpIECTask2.2.7Library SysGetAddress23Function SysLibGetAddress()Ticket 1110Function is not compatible to CODESYS V2.3. It returns wrong values.Function SysLibGetSize()Ticket 1110Function is not compatible to CODESYS V2.3. It returns wrong values.2.2.8Library SysCom23Function SysComRead()Ticket 1104Function is not compatible to CODESYS V2.3. If buffer is empty and the timeout is 0, the functionreturns after 2000 ms.2.2.9Library CanUserThe CODESYS V2.3 library CanUser is available with limited functionality. Migrated functions andfunction blocks are available in library EA23_CanUser.Function block CanUser_DiagInfo()Ticket 1098Function block is not compatible to CODESYS V2.3. It is available with limited functionality. Thefunctionality cannot be represented with the same interface on the CANopen stack of CODESYS V3.Function block CanUser_ReadImage()Ticket 1098Projects based on plc target system XC-202, function block is not compatible to CODESYS V2.3.Output parameter xReady is also FALSE if no new data are available.Function block CanUser_ReadQueue()Ticket 1098Projects based on plc target system XC-202, function block is not compatible to CODESYS V2.3.Output parameter xReady is also FALSE if no new data are available.Output parameter iStatus = 4 is not supported (Queue full).Function CanUser_Write()Ticket 1098Function is not compatible to CODESYS V2.3. If a queue overflow occurs, the function returns withvalue 17.2.2.10Library CanUser_MasterThe CODESYS V2.3 library CanUser_Master is available with limited functionality. Migrated functionsand function blocks are available in library EA23_CanUser.Function block CanUser_DiagMaster()Ticket 1098Function block is not available anymore. The functionality cannot be represented with the sameinterface on the CANopen stack of CODESYS V3.Function block CanUser_DiagNode()Ticket 1098Function block is not available anymore. The functionality cannot be represented with the sameinterface on the CANopen stack of CODESYS V3.Function CheckPDOconfig()Ticket 1098Function is not available anymore. The functionality cannot be represented with the same interfaceon the CANopen stack of CODESYS V3.Function block CanUser_GetEmergency()Ticket 1098Function block is not compatible to CODESYS V2.3. Function block is available with limitedfunctionality. The functionality cannot be represented with the same interface on the CANopen stackof CODESYS V3.Functions CanUser_StartNode() / CanUserStartAllNodes()Ticket 1098Functions are not compatible to CODESYS V2.3. Functions are available with limited functionality.The functionality cannot be represented with the same interface on the CANopen stack of CODESYSV3.Function block CanUser_SDOuploadBlock()Ticket 1098Projects based on target system XV-1xx, XV-4xx or XC-152, the function block is not compatible toCODESYS V2.3. Input parameter dwLenMax must be set 7 bytes bigger than the current data lengthof the received data dwLen.2.2.11Library CanUser_SyncTicket 1100The CODESYS V2.3 library CanUser_Sync is not available anymore. The functionality cannot berepresented with the same interface on the CANopen stack of CODESYS V3.2.2.12Library CanUser_DeviceTicket 1099The CODESYS V2.3 library CanUser_Device is not available anymore. The functionality cannot berepresented with the same interface on the CANopen stack of CODESYS V3.2.2.13Library SysLib_AddTicket 1161The CODESYS V2.3 library SysLib_Add is available with limited functionality. Migrated functions andfunction blocks are available in library EA23_SysLib_Add.On target system XV-1xx, XV-4xx, XVS-4xx and XV-152, support of onboard flash is not yet included.The functions Sys_FlashInit(), Sys_FlashErase(), Sys_FlashWrite() and Sys_FlashRead() are notsupported yet.2.2.14Library SysLibDPV1HilscherThe CODESYS V2.3 library SysLibDPV1Hilscher is not supported yet.2.2.15Library BusdiagProjects based on target system XC-202, only one instance of each FB is allowed.2.2.16Library SysLibPlcCtrlFunction SysEnableScheduling()Function is not supported yet.Function SysWdgEnable()Function is not supported yet.2.2.17Library SymArtiLibTicket 1087The CODESYS V2.3 library SymArtiLib is not available anymore.2.2.18Library TcpUdpLibTicket 1085The CODESYS V2.3 library TcpUdpLib is not available anymore.2.2.19Library SysLibSocketAsyncTicket 1084The CODESYS V2.3 library SysLibSocketAsync is not available anymore.2.2.20Library UdpUserThe CODESYS V2.3 library UdpUser is not available anymore.2.2.21CAN network variablesTicket 1049The functionality of CODESYS V2.3 CAN network variables is not available anymore.2.2.22Profibus-DP configurationModule parameter SwapIOModeTicket 1135The module parameter SwapIOMode is not available anymore. According to specification, onProfibus DP the values of word variables are sent in Motorola byte order (Siemens-compatible).Since our controllers work in Intel format, the values of word variables are swapped automatically inthe driver, so in the application the values are available on Intel byte order.If you use XION modules, select "LSB first" instead "MSB first".Highest Station AddressTicket 1248The Highest Station Address (HSA) is now 125. User cannot select 126 anymore.2.2.23PLC resetTicket 1105On PLC reset, the handles are not closed automatically.2.2.24Target visuObject trendIf a CODESYS V2 project contains trend objects and it is converted to CODESYS V3, the trendobjects are missing. The object trend is not available anymore.→Use object trace insteadVariable name CurrentVisuIf a CODESYS V2 project contains the variable CurrentVisu and it is converted to CODESYS V3, thevariable CurrentVisu is missing.→Replace the variable name CurrentVisu with the variable name VisuElems.CurrentVisu. 2.2.25IO mappingAddress alignmentTicket 1343The address alignment of IOs can be different.→If the CODESYS V2 project contains variables which are manually mapped to IO addresses(bValue AT %IB x : BYTE;), it is necessary to check the manually mapped IO addresses.。
嵌入式系统概述
软件系统
实时监控程序 专用系统 通用系统
IA & Embedded System
Information Appliance
An appliance specializing in information : Knowledge, facts, graphics, images, video, or sound. An information appliance is designed to perform activity, such as music, photography, or writing. A distinguishing feature of information appliance is the ability to share information among themselves. (Don Norman)
Microcontroller: includes I/O devices, on-board memory.
Digital signal processor (DSP): microprocessor optimized for digital signal processing.
Typical embedded word sizes: 8-bit, 16bit, 32-bit.
Chip Board Circuit
CPU Core Interrupt Controler
Timer DMA
CPU BCU
I/O Port A/D
Connection for Debugging
Connecting SRAM
Connecting DRAM
QNX 产品介绍 2012版
昂正湖 Daniel Ang 新加坡动力科技公司
公司和产品介绍
公司介绍 • 历史 • 目标市场 • 客户 • 合作伙伴 • 产品链 • 为什么选择QNX?
技术介绍 • 系统构架 • 系统特性 • 多核 • 互联 • 图形/中间件 • 硬件支持 • 开发工具
销售模式 • 开发费用 • 授权费 • 其他产品 • 支持与服务
硬实时性
硬实时性能严格保证快速响应 最大中断延时 • QNX: 0.000008 seconds • Linux: 1 second 特性 • 基于优先级可抢占线程(256 优先级) • 可抢占的内核 • 多种调度算法 (FIFO/Round Robin) • 基于优先级的并可嵌套的中断 • 中断由用户线程或定制的ISR处理 • 优先级继承 • 防止优先级反转
Better CPU efficiency with adaptive partitioning
多核
• • • • • 微内核分散负载 多核优化工具 超过14年的多核经验 关注未来发展 SMP和 BMP多重处理方式
军工国防
Confidential Information of QNX Software Systems Limited
12
Secure, proven: On land and in space
客户案例
客户案例
GE Energy
QNX 合作伙伴
生态系统
• 广泛的合作伙伴群体 • 专注在: – 垂直（工业）市场 – 平行市场 • 汽车电子市场一流的生态系统网络
Peripheral I/O • PCI / PCIe • I2C / I2S • SPI • GPIO • UART • USB
gdbServer调试
gdbServer调试调试android上的c/c++程序一直是个难题，以前我经常靠输出log来解决问题，对于稍复杂一些的工程，这几乎是个不可能完成的任务，尤其有些错误，在wincewindows下都没事，只在android上出现，就更难找了。
后来看了些资料，知道可以用gdbserver来调试，今天决定必须把这个先弄清楚，不然以后干活效率实在是太低了，找了很多网站，终于成功了。
这里把整个过程整理一下，以备以后查阅。
1.准备gdbserver。
android1.0代码刚对外开放到时候，里面并没拎gdbserver，有些强人就自己编程了gdbserver去采用。
不过现在不好了，android的新源码里已经涵盖了gdbserver，就在prebuilt目录下。
如果想要在android1.0里使用，可以到如下地址下载：准备工作把它放到/system/bin，这样它就在预设的path里了。
启动模拟器后:adbpushgdbserver/system/bin如果提示信息文件系统不容写下的话，继续执行一下“adbremount”，因为预设就是用所读模式装载的。
2.编译程序。
targetexecutable:libomstts(out/target/product/generic/obj/executables/libomstts_intermediates/linked/libomstts)prebuilt/linux-x86/toolchain/arm-eabi-4.2.1/bin/arm-eabi-g++-nostdlib-bdynamic-wl,-t,build/core/armelf.x-wl,-z,nocopyreloc-wl,-dynamic-linker,/system/bin/linker-wl,--gc-sections-oout/target/product/generic/obj/executables/libomstts_intermediates/linked/libo mstts-lout/target/product/generic/obj/lib-wl,-rpath-link=out/target/product/generic/obj/lib-llog-lcutils-lutils-landroid_runtime-lnativehelper-lstdc++-lz-lc-lstdc++-lmout/target/product/generic/obj/lib/crtbegin_dynamic.oout/target/product/gene ric/obj/executables/libomstts_intermediates/src/tts.oout/target/product/generic/obj/executables/libomstts_intermediates/src/ttswrap per.oout/target/product/generic/obj/lib/crtend_android.otargetnon-prelinked:libomstts(out/target/product/generic/symbols/system/bin/libomstts)ou t/host/linux-x86/bin/acpout/target/product/generic/obj/executables/libomstts_intermediates/linked/libo msttsout/target/product/generic/symbols/system/bin/libomsttstargetstrip:(out/target/product/generic/obj/executables/libomstts_intermediates/libomstts) out/host/linux-x86/bin/soslim--strip--shady--quiet--outfileout/target/product/generic/symbols/system/bin/libomsttsout/target/product/generic/obj/executables/libomstts_intermediates/libomsttsin stall:out/target/product/generic/system/bin/libomsttslibomstts-fptout/host/linux-x86/bin/acp-fptout/target/product/generic/obj/executables/libomstts_intermediates/libomsttsou t/target/product/generic/system/bin/libomstts生成的可执行文件是libomstts，可以看到，初次链接的目标文件是“out/target/product/generic/obj/executables/libomstts_i ntermediates/linked/li bomstts”，然后拷贝到“out/target/product/generic/symbols/system/bin/libomstts”，strip后的文件是“out/target/product/generic/obj/executables/libomstts_intermediates/libomstts”和“out/target/product/generic/system/bin/libomstts”。
各类BOOTLOADER的介绍
各类BOOTLOADER的介绍BOOTLOADER是硬件启动的引导程序，是启动OS的全然要进行烧录BOOTLOADER时要从主板的JTAGG口进行烧录，运算机端要用JTAG调试器和应该安装JTAG的驱动程序！在运算机端安装JTAG的驱动方式是：1、将JTAG头接到运算机的并口上2、NBOOT_DEBUG要紧通过网络EBOOT启动的引导第一要将NBOOT_DEBUG通过JTAG烧录到NANDFLASH 的第0块。
具体方式是：1、将JTAG调试器与运算机的并口连接，另外一端与主板的JTAG调试口相连接，这时打开电源。
2、运行NBOOT_DEBUG的目录中的文件3、如图，执行第0项，以后会显现：4、如图，再次执行第0项，以后屏幕会显现：5、现在要选择往FLASH中的什么位置写入文件，目前NBOOT_DEBUG要烧录到FLASH的第0块。
6、这时输入“0”现在在运算机屏幕上会显现EPPPPPPPPP的进度条，当进度条终止时请把电源断电。
7、以后要进行下一步工作，因为每一个BOOTLOADER要与不同的程序相配合，全数烧录完成以后才能够正常启动。
注：每一次烧录一个文件以后最好都从头断电后再次上电以后能够进行下一步工作。
这时要将EBOOT通过JTAG烧录到NANDFLASH 的第2块，这是能够进行WINCE的网络下载测试程序，用来测试PLATFROM BUILDER编辑出来的WINCE是不是能够正常利用。
程序是不是能够利用。
具体方式是：1、将JTAG调试器与运算机的并口连接，另外一端与主板的JTAG调试口相连接，这时打开电源。
2、运行EBOOOT的目录中的文件3、如图，执行第0项，以后会显现：4、如图，再次执行第0项，以后屏幕会显现：5、现在要选择往FLASH中的什么位置写入文件，目前EBOOT要烧录到FLASH的第2块。
6、这时输入“2”现在在运算机屏幕上会显现EPPPPPPPPP的进度条，当进度条终止时请把电源断电。
【教程】minicom使用教程
【教程】minicom使⽤教程简介Linux下的Minicom的功能与Windows下的超级终端功能相似，可以通过串⼝控制外部的硬件设备.适于在linux通过超级终端对嵌⼊式设备⾏管理.同样也可以使⽤minicom对外置Modem 进⾏控制.Minicom的配置第⼀次启动时：需对minicom进⾏配置： minicom -s启动出现配置菜单：1. +-----[configuration]------+2. | Filenames and paths |3. | File transfer protocols |4. | Serial port setup |5. | Modem and dialing |6. | Screen and keyboard |7. | Save setup as dfl |8. | Save setup as.. |9. | Exit |10. | Exit from Minicom |11. +--------------------------+选serial port setup进⼊串⼝配置输⼊A配置串⼝驱动为/dev/ttyUSB0(说明/dev/ttyUSB0 对应为你连接开发板的端⼝，因为我是笔记本电脑的，所以⽤了USB转串⼝⼯具，⾄于连接到哪个设备，可以通过 ls -l /dev/ttyUSB*查看)1. mystery@lcw:/var/lock$ ls -l /dev/ttyUSB*2. crw-rw---- 1 root dialout 188, 0 Apr 4 14:49 /dev/ttyUSB0输⼊E配置速率为115200 8N1输⼊F将 Hardware Flow Control 设为 NO(这⼀步很重要，不然可能连接不上)回车退出1. +-----------------------------------------------------------------------+2. | A - Serial Device : /dev/ttyUSB0 |3. | B - Lockfile Location : /var/lock |4. | C - Callin Program : |5. | D - Callout Program : |6. | E - Bps/Par/Bits : 115200 8N1 |7. | F - Hardware Flow Control : No |8. | G - Software Flow Control : No |9. | |10. | Change which setting? |11. +-----------------------------------------------------------------------+12. | Screen and keyboard |13. | Save setup as dfl |14. | Save setup as.. |15. | Exit |16. | Exit from Minicom |17. +--------------------------+由于我们使⽤minicom作为超级终端控制路由器等设备, ⽽不是控制modem, 所以需要修改Modem and dialing, 将Init string, Reset string, Hang-up string设置为空.1. +--------------------[Modem and dialing parameter setup]---------------------+2. | |3. | A - Init string ......... |4. | B - Reset string ........ |5. | C - Dialing prefix #1.... ATDT |6. | D - Dialing suffix #1.... ^M |7. | E - Dialing prefix #2.... ATDP |8. | F - Dialing suffix #2.... ^M |9. | G - Dialing prefix #3.... ATX1DT |10. | H - Dialing suffix #3.... ;X4D^M |11. | I - Connect string ...... CONNECT |12. | J - No connect strings .. NO CARRIER BUSY |13. | NO DIALTONE VOICE |14. | K - Hang-up string ...... |15. | L - Dial cancel string .. ^M |16. | |17. | M - Dial time ........... 45 Q - Auto bps detect ..... No |18. | N - Delay before redial . 2 R - Modem has DCD line .. Yes |19. | O - Number of tries ..... 10 S - Status line shows ... DTE speed |20. | P - DTR drop time (0=no). 1 T - Multi-line untag .... No |21. | |22. | Change which setting? (Return or Esc to exit) |23. +----------------------------------------------------------------------------+设置完成后选择Save setup as dfl将当前设置保存为默认设置.在配置菜单选Save setup as df1保存（⼀定要记得这⼀步）选Exit退出1. +-----[configuration]------+2. | Filenames and paths |3. | File transfer protocols |4. | Serial port setup |5. | Modem and dialing |6. | Screen and keyboard |7. | Save setup as dfl |8. | Save setup as.. |9. | Exit |10. | Exit from Minicom |11. +--------------------------+下次在输⼊minicon 即可直接进⼊。
三平台下操作SD卡接口总结
Linux,Symian,j2me操作SD卡接口总结学习体会通过一段时间对Linux,Symbian,和j2me的学习和编程，使得对整个Linux,Symbian，两个系统了有了一定程度的了解，感觉上每个Linux因为可以使用C的一些函数，所以编程起来比较容易上手，但是对系统的把握和开发环境的搭建还有Linux下的数据传输都是比较的繁琐的，特别是搭建嵌入式的交叉编译环境和在开发板上运行，开发板的调试等等。
有种牵一发而动全身的感觉，虽然最后也都都搞定了，但是回过头来细细品味一下，还是很耐人寻味的。
在谈谈Symbian下的首先就是它那结构编程的思路，如果是一开始什么就开始看一些实例程序，估计会郁闷一下子，虽然Symbian编程使用的语言是用的C++ (高兴啊)，但是有与Symbian对资源的分配和回收还有错误处理机制，还是够我研究一番的了。
简单总结一下在Symbian下的对手机SD卡的操作，还是环境的搭建这个环境跟在Linux下的完全不一样，因为开发Symbian的IDE和SDK的搭配有很多总组合，同样的SDK可以在VC6.0,carbide,vs2005,codewarrior等等，不同的SDK对应的机型又是不一样的，因为我用的是n73进行测试的，通过查询资料才得知需要S60_3rd_fp1的版本，还有的就是对bld.inf 和.mmp文件的研究。
Symbian的编程写法以及一些相关的概念。
在Symbian下编程给我的感觉是“工欲善其事，必先利其器”，一些基础的知识是一定少不了的。
最后来简单谈谈j2me 的总结，通过以上的一些经验和教训使我了解到了，不是很多的东西都像在windows下开发这样的“幸福”，启动vc6.0的IDE什么东西都不用操心饿，什么编译，连接，排错，等等感觉一切都是这样的方便（很怀念开发winCE时的美好时光,虽然也有很多的坎坷，但是毕竟可以使用vc6.0的小弟evc进行开发）。
TI-am335x_处理器全面介绍(AM3358-AM3359-AM3354-AM3352)
• Home/Building/Industrial automation
• Consumer Electronics • Control Solutions • Educational consoles
4
AM335x Cortex™-A8 based processors
Benefits
• • High performance Cortex-A8 at ARM9/11 prices Rich peripheral integration reduces system complexity and cost
Full function and low cost development platforms fit your evaluation and cost requirements
3
AM335x microprocessors are ideal for:
• Portable Navigation • Advanced toys • Connected vending machines Network Connectivity Graphical User Interface Interface Options Affordable Tools Design Flexibility
EMAC 2port 10/100/1G w/1588 & switch (MII,RMII, RGMII)
Power Estimates
Schedule and packaging
• Samples: Today; Production: 2Q’12 • Dev. Tools: Today • Docs: Today • Packaging: 13x13, 0.65mm via channel array 15x15, 0.8mm
BLDK的简单介绍
一、BLDK是什么？The Intel®BLDK is a software development toolkit that enables rapid development of platform boot loaders for designs that require basic platform initialization.The development kit is compatible with most embedded software development tools and is configurable for specific hardware designs.二、BLDK产品的组成BLDK is comprised of the following:Integrated Development Environment (IDE) ComponentFirmware ComponentUser Documentation1.Integrated Development Environment(IDE)for building and customizing target Boot Loader ImagesBased on the GNU* Build T oolchainGNU* Compiler Collection (GCC) v4.1.2.GNU* Make and Bin utilitiesMain FeaturesGraphical User Interface (GUI)Project Wizard 项目向导Build EnvironmentEnable/Disable FW FeaturesBinary ConfigurationConfigure Feature Settings配置功能的设定Source Code Editor w/ Syntax Highlighting2.Firmware Component ：它提供特定CRB的加载引导程序相关固件的实施方式，该组件可作为出发点，以生成或自定引导加载程序。
ParkerCompax3 伺服驱动器 伺服控制器
Compax3: 开放与灵活
Compax3: 开放与灵活
灵活的维护
用于Compax3S的操作模块
背光插入式模块，双行16-字符文本显示 用4个导航的简单菜单 显示状态值 清晰的错误文本信息 用于改变参数和手动操作 在不使用PC的情况下，实现完全的上载、下载和设备交换 多种语言的对话控制
控制技术
实时信号处理
无过采样 有过采样
速度实际值
过采样速度和电流信号，可以： 降低量化杂波。 增加信号分辨率。
标度： 速度 = 50μm/s 时间 = 3.8ms/Div
用在线反馈误差补偿修正偏移和增益误差。 信号分辨率可达14位 对正余弦反馈信号进行插补。 通过观测器确定速度。 控制器带宽加倍。 采用负载转矩观测器原理。
Compax3S 兼容安全标准如“安全停止” 不用开发与试验客户专用的安全程序 经认证的集成安全标准
Parker Hannifin‘s 在把PLCopen 运动控制模块完全集成进 Compax3方面已经取得成功 IEC61131-3 - 不需要专门的知识就能使用运动控制功能 PLC 编程器包括运动编程以及逻辑运算 运动和逻辑合并为一个功能单元
简单配置
用 PC机并借助 Compax3 ServoManager即可 进行配置。 将配置程序安装在您的PC机上，用RS232 电缆 (在附件中列出)将PC与Compax3进行连接。
不同的运行模式选择: +/-10V-输入
±10V - 输入 ±10V 速度给定 带等效编码器输出
±10V 电流给定 带等效编码器输出 和可设定的停止功能
Compax3
Compax3S
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
ARM-WinCE的专栏
copy Bookmark http://space.itpub.net/16912323
空间管理 您的位置: ITPUB个人空间 » ARM-WinCE的专栏 » 日志
WinCE Target Control调试介绍
上一篇 / 下一篇 2008-12-12 10:23:27 / 个人分类：windows嵌入式开发
查看( 130 ) / 评论( 0 ) / 评分( 0 / 0 )
Target Control是一种基于命令行的调试工具，在WinCE启动以后，可以在
Platform. Builder中启动Target Control，通过命令行来调试WinCE。Target Control支持
很多强大的命令，通过这些命令可以查看内存，启动进程等。
1. 配置Target Control
如果想在WinCE中支持Target Control功能，那么在编译WinCE系统之前要进行
一些设置，首先在WinCE的组件中选择“Target Control Support”，如图：
默认情况下，Target Control调试是基于KITL的，所以要在菜单中选择
“Project”，选择“Properties”，弹出属性对话框，然后选择“Build Options”，选择
“Enable KITL”编译选项。
2. 启动Target Control
在重新编译WinCE系统之后，将WinCE image下载到目标板上并运行，等
WinCE启动后，在VS2005的菜单中选择“Target”，然后选择“Target Control”会弹
出一个命令行窗口，如图：
在命令行窗口中可以看到“Windows CE>”提示符，可以先键入问号(?)然后回车
来查询目前所支持的命令。
3. Target Control命令
这里将对Target Control所支持的命令进行介绍：
？：列出所支持的命令
格式：?
dd：打印某一段内存的数据
格式：dd Address [Size]
Address： 内存地址
Size： 内存大小
df：将某一段内存的数据保存到文件
格式：df Filename Address Size
Filename： 文件名
Address： 内存地址
Size： 内存大小
Dis：强迫操作系统交换出内存中所有丢弃的内存页
格式：Dis
gi：获得进程及线程有关模块，临界区和事件的信息
格式：gi proc | thrd | mod | delta | all
proc： 列出系统中所有的进程
thrd： 列出系统中所有的线程
mod： 列出所有被加载的模块
delta： 列出随处理器时间变化的线程
all： 列出所有
Kp：结束一个进程
格式：Kp Pid | Pindex
Pid： 进程的PID
Pindex： 进程的索引号，这个索引号是通过
gi proc命令得到的
log：显示和设置Celog事件跟踪子系统的区域
格式：log [logoption] [HexWindowsCEZone [ HexUserZone
[ HexProcessMask ]]]
logoption： 手动设置
Celog的信息
-bufsize： 用于Celog
的Buffer大小
-clear： 清除Celog
的Buffer
-flush Filename.log： 将Celog的Buffer
中的数据存到文件中
HexWindowsCEZone： WinCE系统的Log区域掩码
HexUserZone： 用户定义的Log区域
掩马
HexProcessMask： 需要被记录日志的进程
Mi：显示内存信息
格式：Mi kernel | full
Kernel： 显示内核内存信息
full： 显示系统中所有进程的内存
信息
prof：控制kernel profiler，只有系统支持profiling功能时，该命令才有用
格式：prof on | off [ Datatype ] [ Storagetype ] [Otheroptions]
on： 启动kernel profiler
off： 停止kernel profiler
Datatype： 描述要收集的数据类型
-m： 收集蒙特卡洛profiling的相关数据
-s： 收集系统调用的相关数据
-k： 收集内核调用的相关数据
Storagetype： 如何存储收集的数据
-b： 带Buffer的存储模式
-u： 不带Buffer的存储模式
-l： 发送数据到Celog事件跟踪子系
统
Otheroptions： 设置如何收集数据
-buf size： 设置Celog的Buffer的大小
-clear： 清除Celog的Buffer
-flush Filename.clg：停止kernel profiler，把数
据存到文件中
-i： 控制profiler的采样时间
s：启动一个进程
格式：s ProcessName
ProcessName： 进程的名字
run：运行一个批处理文件
格式：run BatchFileName
BatchFileName：批处理文件名
win：列出目前在目标设备上的显示的窗口列表
格式：win
priority：改变shell线程的优先级
格式：priority [N]
N： 线程的优先级
suspend：挂起设备
格式：suspend
tp：设置或查询线程的优先级
格式：tp
tid： 线程的ID
prio： 线程的优先级
Break：打断kernel debugger程序
格式：Break
相关阅读:
•
WinCE中的Debug Zone调试 (唐勉_itpub, 2008-12-10)
•
在WinCE5.0和WinCE6.0下，编译选项介绍 (iwinembed, 2008-12-10)
•
WinCE中的console重定向 (iwinembed, 2008-12-10)
•
WinCE中telnet,FTP及网络共享的使用方法 (iwinembed, 2008-12-10)