spra958f

On-board XDS100TMS320F28027Pins Emulator4. ControlSUITE 介绍和 LED 闪烁例程开发仿真调试C2000 的开发工具软件包 (controlSUITE) 可以创建开放式平台，提供特定于器件的外设配置包，它包含基础软件和示例，可帮助您立即开始项目开发。

运行 ControlSUITE安装程序并选择想要使用的软件包，所有相关项都将自动下载和安装。

具体介绍可参照安装后目录下的 controlSUITE™ Getting Started Guide 和 ControlSUITE™ Software 文档。

与 ControlSTICK 配套的开发包（controlSTICK Software ）同样可以从TI 的网站免费下载，安装后在目录..\Piccolo controlSTICK 下找到软件示例项目、完整硬件文档和参考应用文档。

在..\Piccolo controlSTICK\<project name> 的目录下可以找到 <project name>.pdf 文档，其介绍了ControlSTICK 的配置和应用。

启动 CCSV4.1 软件 (Start->All Program->Texas Instruments->Code Composer Studio V4.1.2)用 Project->Import Legacy CCSv3.3 Project 打开..\Piccolo controlSTICK\Timer – BlinkingLED\ BlinkingLED.pjt 项目工程文件。

如前一节所描述建立对应的 XDS100V1 目标配置文件 File->New->Target Configuration File 。

用 Project->Rebuild All 编译和连接源文件生成目标代码 <project name>.out 。

CORONA 2.4GHz Spread Spectrum (FASST COMPATIBLE)Receiver Instruction Manual for R4FA‐SB and R6FA‐SB Compatibility:The CORONA 2.4GHz Spread Spectrum FASST Compatible Receiver is designed for use with FUTABA’s FASST 2.4GHz transmitters; including the 3PM,3PKS,3VCS,3GR,4PK(S),TM7, TM8, TM10, TM14 and the T6EX‐2.4G, 7C‐2.4G, 8FG, 10CG, 12FG. The R4FA‐SB and R6FA‐SB receivers supply a more useful mode for users. Both the R4FA‐SB and R6FA‐SB support FUTABA’s FASST air system and surface system. The R4FA‐SB supports 7‐channel with continuous PPM (positive and negative) output ,RSSI output and S.BUS output, R6FA‐SB supports 6 channel high speed PPM(HS) mode to optimize helicopter response control and S.BUS output.Under S.BUS output mode, both R4FA‐SB and R6FA‐SB supply 12 proportional channels and 2 DG channels. Therefore, the R4FA‐SB or R6FA‐SB becomes 14‐channel receivers when using S.BUS output.Specifications:Operating Current: 50mA maxOperating Voltage: 3.6 ~10VLatency: R4FA‐SB’s description14mS for independent 4 channel output and S.BUS output @ FASST multi‐channel mode21mS for Continuous PPM output and RSSI output@ FASST multi‐channel mode16mS for independent 4 channel output and S.BUS output @ FASST 7ch mode24mS for Continuous PPM output and RSSI output@ FASST 7ch mode14mS for independent 3 channel output@ FASST surface system C1 CODE modeR6FA‐SB’s description7mS for independent 6 channel (HS) output@ FASST multi‐channel mode14mS for independent 7 channel (LS) output and S.BUS output @ FASST multi‐channel mode 8ms for independent 6 channel (HS) output@ FASST 7ch mode16mS for independent 7 channel (LS) output and S.BUS output @ FASST 7ch mode14ms for independent 3 channel output@ FASST surface system C1 CODE modeSensitivity: about ‐100dBmOperation temperature:‐10~80 deg CSetup:Bind procedure:∙Turn on the FASST transmitter∙Connect the battery to the receiver while pressing the receiver’s F/S button.∙The Dual‐color LED’s will continuously cycle through the following:o Red LED light (searching radio signal)o Green LED light (acquired the radio signal)o Red LED off (bind ok)o Green LED flashes 10 times (ID stored in memory)o Green LED lights solid (normal operation)Note: FASST surface systems take a bit more time to complete the bind procedure.Fail‐safe setting:There are two ways to set the Failsafe setting on the CORONA 2.4GHz Spread Spectrum FASST Compatible Receiver;1.TX‐failsafe feature: This method sets the failsafe on the FASST transmitter and has priority (works onchannel 3 only under FASST 7ch mode or on multiple‐channels under FASST multi‐channel mode) while the receiver is on, just like FUTABA receivers (only available on FASST air system).2.RX‐failsafe feature: Turn on the FASST transmitter and then turn on the CORONA 2.4GHz Spread SpectrumReceiver, put all the sticks and switches to control inputs you want if the receiver looses signal and Press the F/S button down for about 5 ‐ 6 seconds while the Green LED lights solid (Rx in normal operation), then release the button. You will see the Red LED will flash for about 4 ‐ 5 seconds. (Note: The Red LED will FLASH high speed to indicate the RX‐failsafe is turned on OR FLASH low speed to indicate the RX‐failsafe is turned off). If you press the F/S button a second time while the Red LED is flashing, the receiver will change its RX‐failsafe status (on / off), then the LED will return to Green solid again. If you not press the F/S button, nothing will be changed and the LED will return to solid Green. If you want to cancel the RX‐failsafe feature (not just turn it off), you can do so by binding the receiver again. After binding operation the receiver will be back to factory settings without any failsafe feature.Note: If you do not set a failsafe setting, the receiver will hold all controls at the position of the last command received before signal was lost. When RX‐failsafe is turned on, the receiver will initiate the RX‐failsafe settings after loosing signal for over 1 second and the receiver will hold the last received positions until the failsafe takes over. When the RX‐failsafe and TX‐failsafe feature are both turned on, the receiver will use the TX‐failsafe command.We highly recommend you set failsafe feature before flying your models. An example of a minimal useful, failsafe setting would be to shut down the model’s throttle, so that it does not fly or drive away uncontrolled.Output mode setting (only available on FASST air system):Turn off the transmitter, connect the battery to the receiver, you will see the Red LED light flashing. The RED LED flashes at high speed to indicate the receiver is in the special output mode OR a Low speed indicates the receiver is under (LS) low speed PPM normal output mode, press the F/S button for 5‐6 seconds while the Green LED is off (Rx in signal searching status), then release the button. You will see the Green LED flash for about 4 ‐ 5 seconds. (Note: The Green LED will FLASH high speed under special mode OR FLASH low speed under normal output mode). If you press the F/S button a second time while the Green LED is flashing, the receiver will change its output mode status (special/normal), if you do not press the F/S button the output mode will not be changed and the Red LED will flash at its original speed.Note: Output mode function is described in the form below,R4FA‐SB R6FA‐SBnormal Ch1~CH4 independent PPM output normal Ch1~CH7 independent PPM outputCH1 Neg CPPM out(FUTABA trainer FUNC)^1 CH2 Pos CPPM out for special user^2 CH1~CH6 independent high speed(HS)PPM out for helicopter fast response controlCH3 RSSI PWM out for FPV()^3 specialCH4 S.BUS output for compact system specialCH7 S.BUS output for compact systemNote: ^1 refer the signal description picture below^2 refer the signal description picture below^3 refer the signal description picture belowRSSI PWM out define: Pulse width from about 900uS~ 2100uS to indicate RSSI strength from ‐100dBm~‐40dBm.Important Note: If you are using analog servos in your model you must keep your receiver under the factory settings (normal output mode) or your analog servo will get hot and possibly burn out. As well you cannot use a non S.BUS servo on a channel while S.BUS signal output present.LED status indicated under normal working status:RED LED GREEN LED Statusflash off No signal searchedoff solid Signal is very goodSometime flash solid Signal is not very goodflash flash Signal is weak。

TMS320F2809, TMS320F2808, TMS320F2806, TMS320F2802, TMS320F2801TMS320C2802, TMS320C2801，and TMS320F2801x DSPs数据手册著作编号：SPRS230J2003年-2007年9月修正除非有其他说明，本文档中包含了自发布日起的产品数据信息。

同时，产品也与德州仪器的每期标准规范说明书一致。

对产品的处理不包括所有参数的测试。

目录修订历史1 F280x,C2801x,C280x DSPs1.1特点1.2商标2 介绍2.1 引脚分配2.2 信号描述3 功能概况3.1 内存映射3.2 简单描述3.2.1 C28X CPU3.2.2 存储器总线（哈佛总线结构）3.2.3 外设总线3.2.4 实时JTAG接口和分析3.2.5 FLASH存储器3.2.6 ROM存储器3.2.7 M0,M1 SARAMs3.2.8 L0,L1,H0 SARAMs3.2.9 BOOT ROM3.2.10 安全性3.2.11 外设中断扩展（PIE）模块3.2.12 外部中断（XINT1,XINT2,XNMI）3.2.13 振荡器和锁相环（PLL）电路3.2.14 看门狗3.2.15 外部时钟3.2.16 低功耗模式3.2.17 外设框架3.2.18 通用输入输出(GPIO)复用引脚3.2.19 32位CPU定时器（0，1，2）3.2.20 控制外设3.2.21 串口外设3.3 寄存器映射3.4 器件仿真寄存器3.5 中断3.5.1 外部中断3.6 系统控制3.6.1 OSC和PLL模块3.6.2 看门狗模块3.7 低功耗模式模块4 外设4.1 32位CPU定时器0/1/24.2 增强型PWM模块（ePWM1/2/3/4/5/6）4.3 高精度PWM（HRPWM）4.4 增强型CAP模块（eCAP1/2/3/4）4.6 增强型AD转换模块4.6.1 ADC不用时引脚连接4.6.2 ADC寄存器4.7 增强型CAN模块（e-CAN-A和eCAN-B）4.8 SCI模组（SCI-A,SCI-B）4.9 SPI模组（SPI-A,SPI-B,SPI-C,SPI-D）4.10 I2C总线4.11 GPIO复用引脚5 器件支持5.1 器件和开发工具名称5.2 文档支持6 电路规范6.1 绝对最大额定值6.2 推荐运行条件6.3 电气特性6.4 电流消耗6.4.1 减小电流消耗6.4.2 电流消耗图表6.5 DSP无信号缓冲区时的引脚冲突连接6.6 时序参数模型6.6.1 时序参数的一般注意事项6.6.2 测试负荷电路6.7 时钟要求和特性6.8 上电时序6.8.1 电源管理和监控电路解决方案6.9 通用输入输出(GPIO)多路复用器6.9.1 GPIO-输出时序6.9.2 GPIO-输入时序6.10 增强型控制外设6.10.1 增强型脉宽调制（ePWM）时序6.10.2 Trip-Zone 输入时序6.10.3 外部中断时序6.10.4 I2C电路特性和时序6.10.5 串行外设接口（SPI）主动模式时序6.10.6串行外设接口（SPI）被动模式时序6.10.7 片上模-数转换器6.10.7.1 ADC上电控制位时序6.11 详细描述6.12 FLASH时序6.13 ROM时序（仅适用于C280x）7 从F280X到C280X的移植7.1 移植方法8 机械数据图形列表2-1 TMS320F2809，TMS320F2808 100-pin PZ LQFP（Top V iew）2-2 TMS320F2806 100-pin PZ LQFP（Top V iew）2-3 TMS320F2802，TMS320F2801，TMS320C2802，TMS320C2801，100-pin PZ LQFP（Top V iew）2-4 TMS320F2801x 100-Pin PZ LQFP（Top V iew）2-5 TMS320F2809，TMS320F2808，TMS320F2806，TMS320F2802，TMS320F2801，TMS320F28016，TMS320F28015，TMS320C2802，TMS320C2801 100-ball GGM and ZGM MicroStar BGA(Bottom View) 3-1 原理框图3-2 F2809内存映射3-3 F2808内存映射3-4 F2806内存映射3-5 F2802，C2802内存映射3-6 F2801, F28015,F28016,C2801内存映射3-7 外设中断资源3-8 使用外设中断模块时的中断复用3-9 时钟和复位电路3-10 OSC和PLL 方块图3-11 3.3V外部晶振的使用3-12 1.8V外部晶振的使用3-13 内部晶振的使用3-14 看门狗模块4-1 CPU定时器4-2 CPU定时器中断信号和输出信号4-3 280x系统的多路PWM模块4-4 ePWM4-5 eCAP功能方块图4-6 eQEP功能方块图4-7 ADC模块方块图4-8 使用内部参考时的ADC引脚连接4-9使用外部参考时的ADC引脚连接4-10 eCAN方块图和接口电路4-11 Ecan-A存储映射4-12 Ecan-B存储映射4-13 串行通信接口模组方块图4-14 SPI模组方块图（被动模式）4-15 I2C接口设计4-16 GPIO复用引脚方块图4-17 使用取样窗口的条件5-1 TMS320X280X器件命名举例6-1 典型的运行电流相对频率（F2808）6-2 典型的运行电流相对频率(F2808)6-3 无信号缓冲时的硬件连接6-4 3.3V测试负荷电路6-5 时钟时序6-7 热复位6-8 有效写入PLLCR寄存器的举例6-9 通用输出时序6-10 采样模式6-11 通用输入时序6-12 空闲进入和退出时序6-13 备用进入和退出时序6-14 使用通用IO口的中断唤醒6-15 PWM HI-Z特性6-16 ADCSOCAO or ADCSOCBO 时序6-17 外部中断时序6-18 SPI主动模式外部时序（CLOCK PHASE = 0）6-19 SPI主动模式外部时序（CLOCK PHASE = 1）6-20 SPI被动模式外部时序（CLOCK PHASE = 0）6-21 SPI被动模式外部时序（CLOCK PHASE = 1）6-22 ADC上电控制位时序6-23 ADC 模拟输入阻抗模式6-24 单通道模式时序6-25多通道模式时序表单列表2-1 硬件特性（100MHZ器件）2-2 硬件特性（60MHZ器件）2-3 信号描述3-1 F2809的FLASH段地址3-2 F2808的FLASH段地址3-3 F2802、F2806的FLASH段地址3-4 F2801、F28015、F28016的FLASH段地址3-5 使用代码保护模式的影响3-6 等待状态3-7 自举模式选择3-8 外部frame0寄存器3-9 外部frame1寄存器3-10 外部frame2寄存器3-11 器件硬件寄存器3-12 PIE外部中断3-13 PIE配置和控制寄存器3-14 外部中断寄存器3-15 PLL,Clocking,Watchdog,and Low-Power Mode 寄存器3-16 PLLCR寄存器位定义3-17 可能的PLL配置模式3-18 低功耗模式4-1 CPU定时器0，1，2配置和控制寄存器4-2 ePWM控制和标准寄存器4-4 eQEP控制和标准寄存器4-5 ADC寄存器4-6 3.3V eCAN收发器4-7 CAN寄存器MAP4-8 SCI-A寄存器4-9 SCI-B寄存器4-10 SPI-A寄存器4-11 SPI-B寄存器4-12 SPI-C寄存器4-13 SPI-D寄存器4-14 SPI-C寄存器4-15 GPIO寄存器4-16 F2808 GPIO复用表6-1 系统时钟为100MHZ时TMS320F2809,TMS320F2808的电流消耗6-2系统时钟为100MHZ时TMS320F2806的电流消耗6-3系统时钟为100MHZ时TMS320F2802，TMS320F2801的电流消耗6-4系统时钟为100MHZ时TMS320C2802，TMS320C2801的电流消耗6-5各种外设的典型电流消耗（100MHZ时）6-6 TMS320x280x时钟表和命名（100MHZ器件）6-7 TMS320x280x时钟表和命名（60MHZ器件）6-8 输入时钟频率6-9 XCLKIN时序要求-PLL enabled6-10 XCLKIN时序要求-PLL disabled6-11 XCLKOUT 开关特性（PLL bypassed or enabled）6-12 电源管理和监控电路解决方案6-13 Reset(XRS)时序要求6-14 通用输出开关特性6-15 通用输入时序要求6-16 IDLE模式时序要求6-17 IDLE模式开关特性6-18 STANDBY模式时序要求6-19 STANDBY模式开关特性6-20 HALT模式时序要求6-21 HALT模式开关特性6-22 ePWM时序要求6-23 ePWM开关特性6-24 Trip-Zone 输入时序要求6-25 高精度PWM特性（SYSCLKOUT=(60~100MHZ)6-26 eCAP时序要求6-27 eCAP开关特性6-28 eQEP时序要求6-29 eQEP开关特性6-30 外部ADC启动转换开关特性6-31 外部中断时序要求6-32 外部重点开关特性6-34 SPI主动模式外部时序（Clock Phase=0）6-35 SPI主动模式外部时序（Clock Phase=1）6-36 SPI被动模式外部时序（Clock Phase=0）6-37 SPI被动模式外部时序（Clock Phase=0）6-38 ADC电器特性（通过推荐运行条件验证）6-39 ADC上电延时6-40 不同ADC配置时的电流消耗（ADCCLK=12.5MHZ）6-41 单通道模式时序6-42 多通道模式时序6-43 Flash耐性6-44 SYSCLKOUT=100MHZ时的Flash参数6-45 Flash/OTP进入时序6-46 不同频率时的最大最小要求Flash/OTP等待状态6-47 ROM/OTP进入时序6-48不同频率时的最大最小要求ROM/OTP等待状态8-1 F280x Thermal Model 100-pin GGM Results8-2 F280x Thermal Model 100-pin PZ Results8-3 C280x Thermal Model 100-pin GGM Results8-4 C280x Thermal Model 100-pin PZ Results8-5 F2809 Thermal Model 100-pin GGM Results8-6 F2809 Thermal Model 100-pin PZ Results版本历史注意：早期版本的页码可能和当前版本页码有所不同该数据手册自SPRS230I到SPRS230J修正该文档因保证技术的准确性，已经被再次审阅。

Cat ®548/548 LLForest MachinesThe 548 and 548 LL feature ultimate machine efficiency coupled with enhanced performance. Cat ®components, purpose built upper and lower frames, and application specific linkage confi gurations increase machine up time and lower machine operating costs.Effi ciency• Engine, hydraulics, and work tool integration are optimized to minimize power losses and increase overall machine ef fi ciency • S t eady state high idle speed and U.S. EPA Tier 4 Final technology reduce fuel consumption• Larger hydraulic pumps allow engine to operate at lower rpms with increased per f ormance to maximize ef fi ciency• Component layout and back-to-back main hydraulic control valve reduce oil flow restrictions and aid in greater fuel economy • Machine designed for integration and optimization with Cat grapples • Power f ul, multi-functioning hydraulics, combined with strong machine per f ormance ensure work tools function quickly and smoothly to complete work fasterPerformance• Cat 152 kW (2 0 4 hp) C7.1 ACERT ™ Tier 4 Final engine with increased horsepower maintains maximum per f ormance under load • S t rong hydraulic horsepower for ef fi cient implement per f ormance and greater productivit y• An increase in swing torque of 19 percent on General Forestr ymodels and 18 percent on Log Loader models, provides added power to move trees, which enables more ef fi ciency and productivit y • Heav y lif t mode features increased lif t capacit y to handle larger payloads with improved control• 9 8 9 L (2 61 gal) counter w eight fuel tank for ex t ended machine operation and maximum uptime• Machine width and track length designed for s t abilit y in varied logging applicationsApplication Versatility• Boom arrangements and hydraulic systems for specific applications enable more ef f ective road building, loading, processing, shoveling, or millyard stacking• New track options meet shovel logging and low ground pressure application requirements• Ground saw hydraulics are available for log loader applications • Two premium rear entr y cab choices, available on the Log Loader, include a 1219 mm (4 8 in) or a 182 9 mm (72 in) cab for w ard riser • Purpose built processor cab option that includes 19 mm (0.75 in) front windowsReliability and Durability• Variable pitch, reversing cooling fan maintains optimum fluid temperature in heav y dut y fores t r y applications• Cooling capabilit y increased 12 percent for trouble-free operation • Purpose built upper frame, high-wide carbody, robust linkage configurations, and heav y -dut y enclosures are reinforced with thick doubler plates, ex t ra gussets, and other reinforcements for structural integrit y in severe applications• Large, 216 mm (8.5 in) pitch (3 3 6 HE X ), grease lubricated tracks, provide excellent life in variable fores t r y working conditions • Validated and proven excavator technologies ensure overall machine reliabilit yServiceability• One-piece engine hood design, with t w o opening angles, allowseasy access to engine and cooling compar t ments• Side-by-side engine and hydraulic coolers are easy to access for cleaning, while reduced cooling fins per inch allows bet t er debris flow-through and reduced clogging potential • 0.5 6 m 3 (19.8 f t 3) of s t orage space at ground level, provides ready access to tools, equipment , and supplies that operators use dailyOperator Comfort and Technology• Premium fit and finishes to maximize operator experience • Fully adjustable, air ride cab seat that includes heating and cooling capabilit y for comfor t and reduced operator fatigue • LED lights increase visibilit y• Rear entr y cab option provides improved access on a fully lit plat f orm through the use of a key FOB• Rear entr y cab window design improves visibilit y for shovel logging and other applications• Rear entr y cab includes a new innovative cab lock down system that minimizes transpor t time and improves uptime• Tool control sof t w are as standard equipment for swapping and selecting tools quickly and ef fi ciently• Cat Product Link™ allows for remote location of a machine and enables tracking of fuel consumption and other eventsCat® 548/ 548 LL Forest MachinesEngine Model Cat C 7.1 ACER T Gross Power at 1, 800 rpm 152 kW 20 4 hp Engine SpeedOperation 1, 600 rpmTravel 1, 800 rpm Displacement 7.01 L 42 8 in3 Number of Cylinders 6Estimated Operating Weight without At t achment5 48 (General Forestr y, Processor) 3 5 3 54 kg 7 7,9 42 lb5 48 LL (Log Loader, U/ U) 3 8 15 3 kg 8 4,113 lbMaximum Speed (tur t le) 2.6 km /h 1.6 mph Maximum Speed (rabbit) 4 .8 km /h 3.0 mph Maximum Drawbar Pull 313 kN 70, 32 0 lbf Swing Torque – 5 48 (GF )8 7.4 kN·m 6 4, 441 lbf-f t Swing Torque – 5 48 LL 9 9.9 kN∙m 73, 677 lbf-f t Maximum Swing Speed – 5 48 (GF )9.3 rpm Maximum Swing Speed – 5 48 L L9.3 rpmMain Pumps Maximum Flow (per pump) 2 26 L /min 59.7 gal/min Main Pumps Maximum Flow (both pumps) 4 52 L /min 119.4 gal /min Maximum System PressureImplements 3 5 0 00 kPa 5, 076 psi Travel 3 5 0 00 kPa 5, 076 psi Swing – 5 48 (GF ) 3 0 5 00 kPa 4, 424 psi Swing – 5 48 LL 3 4 0 00 kPa 4, 931 psi Heav y L i f t Mode 3 8 0 00 kPa 5, 511 psi Auxiliar y Pump – U/ U and O/ U (5 48 L L)Maximum F l ow 4 8 L /min 12.8 gal /min Maximum Pressure 10 3 35 kPa 1, 499 psi Auxiliar y Pump – Reach w/ R otate (5 48)/Power Clam /B nt (5 48 LL)Pump Drive Gear Ratio 1.2 8:1Maximum Flow 12 9 L /min 3 4.1 gal /min Maximum Pressure 10 3 35 kPa 1, 499 psi Fuel Tank – C W T9 89. 3 L 261.4 gal DEF Tank 4 6.0 L 12 .2 gal Engine Crankcase 24 .0 L 6.3 gal Cooling System 3 0.0 L 7.9 gal Final Drive – Each 11.0 L 2 .9 gal Hydraulic Tank 175.0 L 4 6.2 gal Hydraulic System – Total 2 85.0 L 75. 3 gal Swing Drive 9.0 L 2 .4 galUndercarriage Pitch 215.9 mm 8.5 in Track Gauge 2 809 mm 110.6 in Track Length 5 035 mm 19 8.2 in Ground Clearance 7 74 mm 3 0.5 inGeneral Fores t r y – 5 48 Processor(boom stretched out)Height of Tilted Side Entr y Cab 3 479 mm 13 7.0 in Boom Height 3 74 5 mm 147.4 in Overall Height 416 6 mm 16 4.0 in Overall Length (Reach) 12 5 92 mm 4 95.7 in Tail Swing Radius 3 501 mm 13 7.8 in Distance Bet w een Idlerand Sprocket Centerline4 019 mm 15 8.2 inTrack Length 5 035 mm 19 8.2 in Ground Clearance 7 74 mm 3 0.5 in Track Gauge 2 809 mm 110.6 in Width with 70 0 mm (2 8 in) Shoes 3 509 mm 13 8.1 in Log Loader – 5 48 L L Under/ U nder(boom stretched out)Height of Tilted Side Entr y Cab 3 479 mm 13 7.0 in Boom Height 2 864 mm 112.8 in Overall Height 4 928 mm 19 4.0 in Overall Length (U/ U) 15 14 3 mm 59 6.2 in Tail Swing Radius 3 501 mm 13 7.8 in Distance Bet w een Idlerand Sprocket Centerline4 019 mm 15 8.2 inTrack Length 5 035 mm 19 8.2 in Ground Clearance 7 74 mm 3 0.5 in Track Gauge 2 809 mm 110.6 in Width with 70 0 mm (2 8 in) Shoes 3 509 mm 13 8.1 inF o r more complete infor m ation on Cat product s, dealer ser v ices, and indus t r y solutions, v i sit us on the web at © 2 018 CaterpillarAll rights reser v edMaterials and speci fi cations are subject to change wi t hou t not i ce. Feat u red machines in photos may include addi t ional equipment . See your Cat dealer for available opt i ons .C A T, C A T E R PIL L A R, S A F E T , their respective logos, “Caterpillar Yellow ” and t h e “Power Edge” trade dress, as well as corporate and product iden t i t y used herein, are trademarks of Caterpillar and may not be used wi t hout permission. AE X Q 2231 (01-2018)(NACD, ANZ)。

RVN4126 3.59100-386-9100-386/T DEVICERVN41772-CD2-3.5MCS/MTSRVN41821-CD2-3.5XTS3000/SABER PORTABLE YES RKN4046KHVN9085 3.51-20 R NO HLN9359 PROG. STAND RVN4057 3.532 X 8 CODEPLUG NO3080385B23 & 5880385B30 MDVN4965 3.59100-WS/T CONFIG KITRVN4053 3.5ASTRO DIGITAL INTERFACE NO3080385B23RVN41842-CD RKN4046A (Portable) 2-3.5ASTRO PORTABLE /MOBILE YES3080369B73 or0180300B10 (Mobile) RVN41831-CD3080369B732-3.5ASTRO SPECTRA MOBILE YES(Low / Mid Power)0180300B10 (High Power) RVN4185CD ASTRO SPECTRA PLUS MOBILE NO MANY OPTIONS; SEESERVICE BRIEF#SB-MO-0101RVN4186CD ASTRO SPECTRA PLUS MANY OPTIONS;MOBILE/PORTABLE COMB SEE SERVICE BRIEF#SB-MO-0101RVN4154 3.5ASTROTAC 3000 COMPAR.3080385B23RVN5003 3.5ASTROTAC COMPARATORS NO3080399E31 Adpt.5880385B34RVN4083 3.5BSC II NO FKN5836ARVN4171 3.5C200RVN4029 3.5CENTRACOM SERIES II NO VARIOUS-SEE MANUAL6881121E49RVN4112 3.5COMMAND PLUS NORVN4149 3.5COMTEGRA YES3082056X02HVN6053CD CT250, 450, 450LS YES AAPMKN4004RVN4079 3.5DESKTRAC CONVENTIONAL YES3080070N01RVN4093 3.5DESKTRAC TRUNKED YES3080070N01RVN4091 3.5DGT 9000 DESKSET YES0180358A22RVN4114 3.5GLOBAL POSITIONING SYS.NO RKN4021AHVN8177 3.5GM/GR300/GR500/GR400M10/M120/130YES3080070N01RVN4159 3.5GP60 SERIES YES PMLN4074AHVN9128 3.5GP300 & GP350RVN4152 3.5GP350 AVSRVN4150 3.5GTX YES HKN9857 (Portable)3080070N01(Mobile) HVN9025CD HT CDM/MTX/EX SERIES YES AARKN4083/AARKN4081RiblessAARKN4075RIBLESS NON-USA RKN4074RVN4098H 3.5HT1000/JT1000-VISAR YES3080371E46(VISAR CONV)RVN4151 3.5HT1000 AVSRVN4098 3.5HT1000/ VISAR CONV’L.YES RKN4035B (HT1000) HVN9084 3.5i750YES HLN-9102ARVN4156 3.5LCS/LTS 2000YES HKN9857(Portable)3080070N01(Mobile) RVN4087 3.5LORAN C LOC. RECV’R.NO RKN4021ARVN4135 3.5M100/M200,M110,M400,R100 includesHVN9173,9177,9646,9774YES3080070N01RVN4023 3.5MARATRAC YES3080070N01RVN4019 3.5MAXTRAC CONVENTIONAL YES3080070N01RVN4139 3.5MAXTRAC LS YES3080070N01RVN4043 3.5MAXTRAC TRK DUPLEX YES3080070N01RVN4178CD MC SERIES, MC2000/2500DDN6124AW/DB25 CONNECTORDDN6367AW/DB9 CONNECTOR RVN41751-CD Rib to MIC connector 1-3.5MCS2000 RKN4062BRVN41131-3.5MCS2000RVN4011 3.5MCX1000YES3000056M01RVN4063 3.5MCX1000 MARINE YES3000056M01RVN4117 3.5MDC/RDLAP DEVICESRVN4105 3.5MOBILE PROG. TOOLRVN4119 3.5MOBITEX DEVICESRVN4128 3.5MPT1327-1200 SERIES YES SEE MANUALRVN4025 3.5MSF5000/PURC/ANALOG YES0180355A30RVN4077 3.5MSF5000/10000FLD YES0180355A30RVN4017K 3.5MT 1000YES RTK4205CRVN4148 3.5MTR 2000YES3082056X02RVN4140 3.5MTRI 2000NORVN41761-CD MTS2000, MT2000*, MTX8000, MTX90001-3.5*programmed by DOS which is included in the RVN4176RVN4131 3.5MTVA CODE PLUG FIXRVN4142 3.5MTVA DOCTOR YES3080070N01RVN4131 3.5MTVA3.EXERVN4013 3.5MTX800 & MTX800S YES RTK4205CRVN4097 1-CD MTX8000/MTX9000,MTS2000,MT2000*,* programmed by DOS which is included in the RVN4176HVN9067CD MTX850/MTX8250MTX950,MTX925RVN4138 3.5MTX-LS YES RKN4035DRVN4035 3.5MX 1000YES RTK4203CRVN4073 3.5MX 800YES RKN4006BHVN9395 P100, P200 LB, P50+, P210, P500, PR3000RVN4134 3.5P100 (HVN9175)P200 LB (HVN9794)P50+ (HVN9395)P210 (HVN9763)P500 (HVN9941)PR3000 (HVN9586)YES RTK4205HVN9852 3.5P110YES HKN9755A/REX1143 HVN9262 3.5P200 UHF/VHF YES RTK4205RVN4129 3.5PDT220YVN4051 3.5PORTABLE REPEATER Portable rptr.P1820/P1821AXRVN4061C 3.5PP 1000/500NO3080385B23 & 5880385B30 RVN5002 3.5QUANTAR/QUANTRO NO3O80369E31RVN4135 3.5R100 (HVN9177)M100/M200/M110/M400YES0180358A52RVN4146 3.5RPM500/660RVN4002 3.5SABER YES RTK4203CRVN4131 3.5SETTLET.EXEHVN9007 3.5SM50 & SM120YESRVN4039 3.5SMART STATUS YES FKN5825AHVN9054 3.5SOFTWARE R03.2 P1225YES3080070N01HVN9001 3.5SOFTWARE R05.00.00 1225LS YES HLN9359AHVN9012 3.5SP50RVN4001N 3.5SPECTRA YES3080369B73 (STANDARD)0180300B10 (HIGH POWER) RVN4099 3.5SPECTRA RAILROAD YES3080369B73RVN4110 3.5STATION ACCESS MODULE NO3080369E31RVN4089A 3.5STX TRANSIT YES0180357A54RVN4051 3.5SYSTEMS SABER YES RTK4203BRVN4075 3.5T5600/T5620 SERIES NO3080385B23HVN9060CD TC3000, TS3000, TR3000RVN4123 3.5VISAR PRIVACY PLUS YES3080371E46FVN4333 3.5VRM 100 TOOLBOX FKN4486A CABLE &ADAPTORRVN4133 3.5VRM 500/600/650/850NORVN4181CD XTS 2500/5000 PORTABLES RKN4105A/RKN4106A RVN41002- 3.5XTS3000 ASTRO PORTABLE/MOBILERVN4170 3.5XTS3500YES RKN4035DRIB SET UPRLN4008E RADIO INTERFACE BOX (RIB)0180357A57RIB AC POWER PACK 120V0180358A56RIB AC POWER PACK 220V3080369B71IBM TO RIB CABLE (25 PIN) (USE WITH XT & PS2)3080369B72IBM TO RIB CABLE (9 PIN)RLN443825 PIN (F) TO 9 PIN (M) ADAPTOR (USE W/3080369B72 FOR AT APPLICATION) 5880385B308 PIN MODULAR TO 25 PIN ”D” ADAPTOR (FOR T5600 ONLY)0180359A29DUPLEX ADAPTOR (MOSTAR/TRAXAR TRNK’D ONLY)Item Disk Radio RIB Cable Number Size Product Required Number Item Disk Radio RIB Cable Number Size Product Required NumberUtilizing your personal computer, Radio Service Software (RSS)/Customer Programming Software (CPS)/CustomerConfiguration Software (CCS) enables you to add or reprogram features/parameters as your requirements change. RSS/CPS/CCS is compatible with IBM XT, AT, PS/2 models 30, 50, 60 and 80.Requires 640K RAM. DOS 3.1 or later. Consult the RSS users guide for the computer configuration and DOS requirements. (ForHT1000, MT/MTS2000, MTX838/8000/9000, Visar and some newer products —IBM model 386, 4 MEG RAM and DOS 5.0 or higher are recommended.) A Radio Interface Box (RIB) may be required as well as the appropriate cables. The RIB and cables must be ordered separately.Licensing:A license is required before a software (RVN) order is placed. The software license is site specific (customer number and ultimate destination tag). All sites/locations must purchase their own software.Be sure to place subsequent orders using the original customer number and ship-to-tag or other licensed sites; ordering software without a licensed customer number and ultimate tag may result in unnecessary delays. To obtain a no charge license agreement kit, order RPX4719. To place an order in the U.S. call 1-800-422-4210. Outside the U.S., FAX 847-576-3023.Subscription Program:The purchase of Radio ServiceSoftware/Customer Programming/Customer ConfigurationSoftware (RVN & HVN kits) entitles the buyer/subscriber to three years of free upgrades. At the end of these three years, the sub-scriber must purchase the same Radio Service Software kit to receive an additional three years of free upgrades. If the sub-scriber does not elect to purchase the same Radio Service Software kit, no upgrades will be sent. Annually a subscription status report is mailed to inform subscribers of the RSS/CPS/CCS items on our database and their expiration dates.Notes:1)A subscription service is offered on “RVN”-Radio Service Software/Customer Programming/Customer Configuration Software kits only.2)“RVN” software must only be procured through Radio Products and Services Division (RPSD). Software not procured through the RPSD will not be recorded on the subscription database; upgrades will not be mailed.3)Upgrades are mailed to the original buyer (customer number & ultimate tag).4)SP software is available through the radio product groups.The Motorola General Radio Service Software Agreement is now available on Motorola Online. If you need assistance please feel free to submit a “Contact Us” or call 800-422-4210.SMART RIB SET UPRLN1015D SMART RIB0180302E27 AC POWER PACK 120V 2580373E86 AC POWER PACK 220V3080390B49SMARTRIB CABLE (9 PIN (F) TO 9 PIN (M) (USE WITH AT)3080390B48SMARTRIB CABLE (25 PIN (F) TO 9 PIN (M) (USE WITH XT)RLN4488ASMART RIB BATTERY PACKWIRELESS DATA GROUP PRODUTS SOFTWARERVN4126 3.59100-386/9100T DEVICES MDVN4965 3.59100-WS/T CONFIG’TN RVN41173.5MDC/RDLAP DEVICESPAGING PRODUCTS MANUALS6881011B54 3.5ADVISOR6881029B90 3.5ADVISOR ELITE 6881023B20 3.5ADVISOR GOLD 6881020B35 3.5ADVISOR PRO FLX 6881032B30 3.5BR8506881032B30 3.5LS3506881032B30 3.5LS5506881032B30 3.5LS7506881033B10 3.5LS9506881035B20 3.5MINITOR III8262947A15 3.5PAGEWRITER 20008262947A15 3.5PAGEWRITER 2000X 6881028B10 3.5TALKABOUT T3406881029B35 3.5TIMEPORT P7308262947A15 3.5TIMEPORT P930NLN3548BUNIVERSAL INTERFACE KITItem Disk Radio NumberSize Product。

HOME > 製品情報 > 油圧用パッキン > SKYパッキン製品一覧を見る特徴SKYパッキン最もポピュラーな油圧シリンダ用のパッキンです。

ピストンおよびロッド用のいずれにも使用でき、一体みぞに装着が可能のため部品点数の削減、 コンパクト設計などコスト低減に効果を発揮します。

●パッキンは上図のように方向性があります。

装着方向にご注意ください。

●装着みぞの位置によっては一体みぞに装着できない場合があります。

その場合は分割みぞ構造にしてください。

●SKY-18未満は分割みぞにしてください。

●φD H9／f8は軸受方式により変わります。

ウェアリングまたはエスリーブ併用の場合は、各寸法表をご参照ください。

※バックアップリングを併用しないときの（φd2）寸法は、シールのはみ出し限界曲線をご参照ください。

※仕上記号の表面粗さの標準数列については、こちらをご参照ください。

SKYパッキン寸法表パッキンおよびみぞ寸法 (単位：mm）指示コードSKYパッキン併用バック （PT111）dDH G A G B D 1d 1 (参考)L標準 （RN 906）耐熱用 （RF 905） （RF 907）耐寒用 （RN 903）HNBR (RP902)(RP903)10185 5.7 6.71710.431.5SKY- 0010001N906TBC- 0010007T111パッキンおよびみぞ寸法 (単位：mm）指示コードSKYパッキン併用バック （PT111）dDH G A G B D 1d 1 (参考)L標準 （RN 906）耐熱用 （RF 905） （RF 907）耐寒用 （RN 903）HNBR (RP902)(RP903)12205 5.7 6.71912.43 1.5SKY- 0012001N906 TBC- 0012003T11112.5205 5.7 6.71912.93 1.5SKY-12.5TCS- 20×12.514225 5.7 6.72114.43 1.5SKY-14SKY-14F●●TCS- 22×1416245 5.7 6.72316.43 1.5SKY-16SKY-16F● TCS- 24×1617255 5.7 6.72417.43 1.5SKY- 0017001N906TCS- 25×1718265 5.7 6.72518.43 1.5SKY-18SKY-18F● TCS- 26×1820285 5.7 6.72720.43 1.5SKY-20SKY-20FSKY-20NTCS- 28×202030678.52920.43 1.5SKY- 0020001N906TBC- 0020006T11122305 5.7 6.72922.43 1.5SKY-22SKY-22F ●●TCS- 30×2222.4305 5.7 6.72922.83 1.5SKY-22.4SKY-22.4F ●●TCS- 30×22.423.531.55 5.7 6.730.523.93 1.5SKY-23.5SKY-23.5FTCS- 31.5×23.524325 5.7 6.73124.43 1.5SKY- 0024002N906TCS- 32×2425335 5.7 6.73225.43 1.5SKY-25SKY-25FSKY-25NTCS- 33×2526345 5.7 6.73326.43 1.5SKY- 0026001N906 TBC- 0026005T11127355 5.7 6.73427.43 1.5SKY- 0027001N906TCS- 35×272835.55 5.7 6.734.528.43 1.5SKY-28SKY-28FSKY-28N●●TCS- 35.5×2828365 5.7 6.73528.431.5SKY-28ATCS- 36×2830385 5.7 6.73730.5 3.53SKY- 0030001N906TBC- 0030005T1113040678.53930.5 3.53SKY-30SKY-30F SKY-30NTCS- 40×3031.541.5678.540.5323.53SKY-31.5SKY-31.5FTCS- 41.5×31.53242678.54132.5 3.53SKY-32TCS- 42×323545678.54435.5 3.53SKY-35SKY-35FSKY-35NTCS- 45×35併用バック （PT111）dDH G A G B D 1d 1 (参考)L標準 （RN 906）耐熱用 （RF 905） （RF 907）耐寒用 （RN 903）HNBR (RP902)(RP903)35.545678.54436 3.53SKY-35.5SKY-35.5FSKY-35.5N●●TCS- 45×35.535.545.5678.544.5363.53SKY-35.5A TCS- 45.5×35.53646678.54536.5 3.53SKY-36SKY-36F●TCS- 46×363848678.54738.5 3.53SKY- 0038001N906TBC- 0038003T1114050678.54940.5 3.53SKY-40SKY-40F SKY-40N TCS- 50×404555678.55445.5 3.53SKY-45SKY-45F SKY-45N TCS- 55×454556789.55545.5 3.53SKY-45A SKY-45AF SKY-45AN ●●TCS- 56×455060678.55950.5 3.53SKY-50SKY-50F SKY-50NTCS- 60×505363678.56253.6 3.53SKY-53SKY-53FTCS- 63×535565678.56455.6 3.53SKY-55SKY-55F SKY-55NTCS- 65×555666678.56556.6 3.53SKY-56SKY-56F●●TCS- 66×565868678.56758.6 3.53SKY- 0058001N906TBC- 0058004T1116070678.56960.6 3.53SKY-60SKY-60F SKY-60NTCS- 70×606071789.57060.6 3.53SKY-60ASKY-60AFTCS- 71×606171678.57061.6 3.53SKY- 0061001N906TC-パッキン 指示コード6373678.57263.6 3.53SKY-63SKY-63F SKY-63N ●TCS- 73×636575678.57465.6 3.53SKY-65SKY-65F SKY-65NTCS- 75×656777678.57667.6 3.53SKY-67SKY-67F●●TCS- 77×677080678.57970.6 3.53SKY-70SKY-70F SKY-70N●●TCS- 80×707180678.57971.6 3.53SKY-71SKY-71F●TCS- 80×717585678.58475.6 3.53SKY-75SKY-75F SKY-75N TCS- 85×758090678.58980.6 3.53SKY-80SKY-80FSKY-80N●●TCS- 90×80併用バック （PT111）dDH G A G B D 1d 1 (参考)L標準 （RN 906）耐熱用 （RF 905） （RF 907）耐寒用 （RN 903）HNBR (RP902)(RP903)8595678.59485.6 3.53SKY- 0085002N906TBC- 0085001T11185100910129885.644SKY-85SKY-85FSKY-85N●●TCS- 100×85861008.59.511.59886.644SKY-86SKY-86FTCS- 100×86891049101210289.644SKY- 0089001N906 TBC- 0089001T11190100678.59990.644SKY- 0090001N906TBC- 0090013T111901059101210390.644SKY-90SKY-90F SKY-90N●TCS- 105×90951109101210895.644SKY-95SKY-95FTCS- 110×95961119101210996.644SKY- 0096001N906TBC- 0096001T111981128.59.511.511098.644SKY-98SKY-98FTCS- 112×9810011591012113100.644SKY-100SKY-100FSKY-100N●●TCS- 115×10010512091012118105.644SKY- 0105002N906TBC- 0105001T1111061208.59.511.5118106.644SKY-106SKY-106FSKY-106NTCS- 120×10611012591012123110.644SKY- 0110003N906●●TBC- 0110001T1111121258.59.511.5123112.644SKY-112SKY-112F TCS- 125×11211212591012123112.644SKY-112ASKY-112AF●●TCS- 125×1121151308.59.511.5128115.644SKY- 0115002N906SKY- 0115001N903 TBC- 0115002T1111181328.59.511.5130118.644SKY-118SKY-118FSKY-118NTCS- 132×1181191338.59.511.5131119.644SKY- 0119001N906 TBC- 0119001T11112013591012133120.644SKY- 0120002N906TBC- 0120001T11112514091012138125.644SKY-125SKY-125FSKY-125N●●TCS- 140×12513014591012143130.644SKY- 0130001N906TBC- 0130001T1111321458.59.511.5143132.644SKY-132SKY-132FTCS- 145×132併用バック （PT111）dDH G A G B D 1d 1 (参考)L標準 （RN 906）耐熱用 （RF 905） （RF 907）耐寒用 （RN 903）HNBR (RP902)(RP903)1361508.59.511.5148136.644SKY-136SKY-136F TCS- 150×13614015591012153140.644SKY-140SKY-140F●●TCS- 155×14014516091012158145.644SKY-145SKY-145F SKY-145NTCS- 160×14515016591012163150.644SKY-150SKY-150F TCS- 165×15015517091012168155.644SKY-155SKY-155F TCS- 170×15516017591012173160.644SKY-160SKY-160F ●●TCS- 175×16016518091012178165.644SKY-165SKY-165FTCS- 180×16517018591012183170.644SKY- 0170001N906TBC- 0170001T11117519091012188175.644SKY-175SKY-175F TCS- 190×175180200121315.5198180.855SKY-180SKY-180F●●TCS- 200×180185205121315.5203185.855SKY- 0185001N906TBC- 0185001T111190*********.5208190.855SKY- 0190003N906SKY- 0190001F905 TBC- 0190004T111195215121315.5213195.855SKY- 0195001N906TBC- 0195006T111200*********.5218200.855SKY-200SKY-200F TCS- 220×200204224121315.5222204.855SKY-204SKY-204FTCS- 224×204210230121315.5228210.855SKY- 0210002N906SKY- 0210001F905 TBC- 0210004T111215235121315.5233215.855SKY- 0215001N906 TBC- 0215003T111220*********.5238220.855SKY- 0220001N906TBC- 0220003T111224244121315.5242224.855SKY-224SKY-224F TCS- 244×224230*********.5248230.855SKY-230SKY-230FTCS- 250×230235255121315.5253235.855SKY- 0235001N906 TBC- 0235001T111237257121315.5255237.855SKY- 0237001N906TC-パッキン 指示コード併用バック （PT111）dDH G A G B D 1d 1 (参考)L標準 （RN 906）耐熱用 （RF 905） （RF 907）耐寒用 （RN 903）HNBR (RP902)(RP903)240260121315.5258240.855SKY- 0240003N906SKY- 0240001F905 TBC- 0240001T111245265121315.5263245.855SKY- 0245001N906TBC- 0245004T111250*********.5268250.855SKY-250SKY-250FTCS- 270×250260280141518278260.855SKY-260SKY-260F TCS- 280×260280300141518298280.855SKY-280SKY-280FTCS- 300×280290310141518308290.855SKY- 0290001N906TBC- 0290001T111295315141518313295.855SKY-295SKY-295FTCS- 315×295300320121316318300.855SKY- 0300003N906 TBC- 0300003T11131033014151832831155SKY- 0310001N906 TBC- 0310002T11131533514151833331655SKY-315 TCS- 335×31533535514151835333655SKY-335 TCS- 355×33535537514151837335655SKY-355TCS- 375×35538040014151839838155SKY-380SKY-380FTCS- 400×38040042014151841840155SKY-400 TCS- 420×40043045014151844843155SKY-430 TCS- 450×43045047014151846845155SKY-450 TCS- 470×45048050014151849848155SKY-480 TCS- 500×48050052517182152250155SKY- 0500001N906 TBC- 0500002T11154056014151855854155SKY- 0540001N906 TBC- 0540001T11155057013141756855155SKY- 0550001N906 TBC- 0550001T11161063014151862861155SKY- 0610001N906 TBC- 0610001T11163065517182165263155SKY- 0630001N906TBC- 0630001T111併用バック （PT111）dDH G A G B D 1d 1 (参考)L標準 （RN 906）耐熱用 （RF 905） （RF 907）耐寒用 （RN 903）HNBR (RP902)(RP903)66069018192268766155SKY- 0660001N906 TC-パッキン 指示コード77080018192279777155SKY- 0770001N906TC-パッキン 指示コード≪2012年5月 更新≫★ご注文・お問い合わせは、指示コードにてご指示ください。

TMS320F2812中FLASH寄存器的配置问题解答问：我使用的是TI ２０００系列芯片中的２８１２！我使用的是汇编语言对其进行开发，目前主程序已经完成，需要烧写到ＦＬＡＳＨ中运行，但烧写过后发现在ＦＬＡＳＨ中运行的速度和在ＲＡＭ中用仿真器仿真的速度差不多！这样就太慢了，我设置的ＰＬＬ倍频到１５０ＭＨＺ，后来发现是有关ＦＬＡＳＨ的一些配置寄存器没有进行配置，我想在ＦＬＡＳＨ中运行速度过慢的原因可能是这个造成的吧！我查看了ＴＩ的说明文档，其中关于ＦＬＡＳＨ寄存器的介绍中，有如下的一段：Note: Flash configuration registers should not be accessed while anaccess is in progress in flash or OTP memoryThe flash registers should not be accessed from code that is running fromOTP or flash memory or while an access may be in progress. All register accessesto the flash registers should be made from code executing outsideof flash/OTP memory and an access should not be attempted until all activityon the flash/OTP has completed. No hardware is included to protect for this.You can read the flash registers from code executing in flash/OTP; however,do not write to the registers.从上面的一段看出，如果需要配置ＦＬＡＳＨ的寄存器，必须执行ＦＬＡＳＨ以外存储空间的程序才可以实现，我又发现这些寄存器是受ＥＡＬＬＯＷ和ＣＳＭ保护的，所以我按照以下步骤试图重新配置寄存器：１，在执行存放于ＦＬＡＳＨ中的主程序段时，将一段存于ＦＬＡＳＨ中的初始化ｆｌａｓｈ配置寄存器的程序完全复制到片内Ｌ０ＳＡＲＡＭ中，该初始化程序如下：MOVW DP,#DP_FLASH ;指向FLASH寄存器所在的页面EALLOWMOV AL,#01HMOV @FOPT,AL ;使能FLASH流水线模式MOV AL,#03HMOV @FPWR,ALMOV AL,#0FFHMOV @FSTDBYWAIT,ALMOV AL,#0FFHMOV @FACTIVEWAIT,ALMOV AL,#0203HMOV @FBANKWAIT,ALMOV AL,#06HMOV @FOTPWAIT,ALEDISLB FLASH_RET ；FLASH_RET 是我这段程序需要返回到的地址2，我配置了CSM模块的寄存器，使得器件不受CSM的保护3，用MOVL XAR7，#8300H ；200H是初始化程序复制到RAM中的地址LB *XAR7从FLASH跳转到RAM中执行该段初始化FLASH的程序4，从RAM中返回到FLASH中的主程序继续执行但发现这段程序烧写到片子里面后，不能按照我的意图执行，FLASH寄存器没有得到重新配置，请问这是什么原因呢？我上述的几个步骤对不对呢？请问，如果在程序烧写到片内FLASH中，在执行该程序时，想调到RAM中执行另一段程序，这种情况应该如何实现呢？应该有哪些需要注意的地方呢？如果那位有配置FLASH寄存器的例子的话，请发给我一份做一下参考吧！======================================================== 答：在flash中怎么能运行配置属于flash的寄存器呢？自己改变自己是不行的。

F2812 Flash烧写步骤参考文档：TI手册：spra958f《Running an Application from Internal Flash Memory on the TMS320F28xx DSP》CCS帮助文档:TMS320F28xx On-Chip Flash ProgrammerSEED合众达电子论坛上的官方说明：使用F2812开发时需注意的问题最近有部分用户咨询：为何编译程序没有问题，可是烧录不进去，或者烧录成功了无法运行需要注意的问题：1，CMD：F2812与别的器件不同，在调试过程中使用的一般是对于SRAM的定义，编译一个SRAM.CMD，所以调试的时候没有问题，但是烧写FLASH的时候需要重新编写一个针对FLASH分配的FLASH.CMD文件，然后进行烧录。

注意：这个文件不能load到ram里面去。

2，lib：我们产品里面提供的lib文件是基于CCS2.2上面的，所以需要烧写的时候要求你的库文件随着CCS 的版本更新而更新库，否则无法烧录。

3，API：根据F2812的版本不同，烧写插件不同，需要注意一下，目前主要有CC, CE, CG，否则烧写一半会报错，然后CCS不能操控了。

调试过程总结：最开始直接参照CCS帮助文档的烧写步骤将开发板上的仿真例程直接烧录，天真的离谱！开始上网搜索FLASH.CMD，最终找到一个版本，并确认基本没有问题；2007-12-191.以合众达开发板SCI程序为模板：2.更换库文件为rts2800_ml.lib；3.更换链接文件为flash.cmd文件4.添加0x3F7FF6处的自动跳转汇编命令：spra958f第26页的CodeStartBranch.asm（代码同样可以在TI网站上免费下载），在CCS SCI 工程中将该文件添加到Source文件夹里即可；5.编译有Warning（待修改，Flash寄存器操作部分）[SCI_TEST.c] "C:\CCStudio_v3.3\C2000\cgtools\bin\cl2000" -g -k -q -fr"C:/CCStudio_v3.3/MyProjects/SCI/Debug" -d"_DEBUG" -d"LARGE_MODEL" -ml -v28 -@"Debug.lkf" "SCI_TEST.c"[Linking...] "C:\CCStudio_v3.3\C2000\cgtools\bin\cl2000" -@"Debug.lkf"<Linking>>> warning: load address of uninitialized section ramfuncs ignoredBuild Complete,0 Errors, 1 Warnings, 0 Remarks.6.参照CCS帮助文档:TMS320F28xx On-Chip Flash Programmer烧写步骤，注意的是CCS V3.3版本已自带最新的烧写插件Flash2812_API_V210版本，无需再去TI网站下载，只需按照帮助文档操作就可以了，网上也有徐工网友的翻译版操作流程。

XAAR 、Spectra、Konica 和精工SPT喷头到底有什么区别呢？可能很多朋友在购买喷绘机的时候注重的大多是喷绘机的性能和机器价格，但是其实购买喷绘机还有一个你非常需要去关注的方面，那就是喷绘机使用的是什么喷头呢？在市场上目前出现做多的solvent喷头XAAR 、Spectra、Konica 和精工SPT喷头，那么这几个喷头到底有什么区别呢？接下来请大家详细阅读我按照经验写下来的这些资讯。

详细介绍全球四大喷绘机喷头1.英国XAAR喷头XAAR公司生产的主要喷头有XAAR128、XAAR500、XAAR126与XAAR380、XAAR760等型号。

A.XAAR128喷头是赛尔公司最早也是市场所使用的最广泛的打印头，有三个型号：XAAR128-200，200dpi， 0.54米/ 秒XAAR128-360，360dpi， 0.39米/ 秒XAAR128XL，360dpi， 0.59米/ 秒此型号喷头有128个管道，内部滤网的网孔较大，墨点颗粒很大为80PL 左右，并且此喷头对外界适应性较差，不能够因温度变化而通过软件来控制喷头电压，故其使用寿命与其他喷头相比而大大缩短。

B.XAAR500是目前赛尔喷头使用性、稳定性和可操作性最佳的喷头，其宽副为70mm，有500个管道，其分辨模式有两种：XAAR500-180 型的速度可以达到 0.51米/ 秒，墨滴大小为80PLXAAR500-360 型的速度可以达到 0.56米/ 秒，墨滴大小为40PLXAAR500是继XAAR128之后开发出来的高集成喷头，制作工艺上也得到很大改进，喷孔数量与使用寿命较XAAR128提高近4倍，并且XAAR500增加具有电子式切换不同墨水的能力，同一个喷头可以依序由不同的供墨系統印出不同的颜色，它的优点还表现于安装容易，套色简单，因其具备两种分辨模式，使其具备不同的灰阶，但其市场售价较高，国内零售为20000元/只，国产机器中彩神在采用XAAR500系列方面做的相当成功，但因与国内喷绘市场价格冲突较大，故其市场份额也相对较小。

Application ReportSPRA958H – September 2008 Running an Application from Internal Flash Memory on theTMS320F28xxx DSP David M. Alter DSP Applications - Semiconductor GroupABSTRACTSeveral special requirements exist for running an application from on-chip flash memoryon the TMS320F28xxx DSP. These requirements generally do not manifest themselvesduring development in RAM since the Code Composer Studio™ debugger can maskproblems associated with initialized sections and how they are linked to memory. Thisapplication report covers the requirements needed to properly configure applicationsoftware for execution from on-chip flash memory. Requirements for both DSP/BIOS™and non-DSP/BIOS projects are presented. Some performance considerations andtechniques are also discussed. Example code projects are included that run from on-chipflash on the eZdspF2812™, eZdspF2808, and eZdspF28335 development boards. Codeexamples that run from internal RAM are also provided for completeness. These codeexamples provide a starting point for code development, if desired.Project collateral and source code discussed in this application report can be downloadedfrom the following URL: /sc/techlit/spra958.zip.Note that the issues discussed in this application report apply directly to current membersof the TMS320F28xxx DSP family, specifically: F2810, F2811, F2812, F2801, F2801-60,F2802, F2802-60, F2806, F2808, F2809, F28015, F28016, F28044, F28232, F28234,F28235, F28332, F28334, and F28335 devices. Applicability to future devices in theTMS320F28xxx family, although quite likely, is not guaranteed. In addition, the code andtechniques presented in this application report for DSP/BIOS projects were developed onCode Composer Studio v3.3.81.5 using C-compiler v5.1.0 and DSP/BIOS v5.33. It isalways suggested that the reader upgrade to the latest version. However, keep in mindthat future versions of DSP/BIOS may have differences that make some of the itemsdiscussed in this report unnecessary (although in all likelihood backwards compatibility willbe maintained, so that the techniques discussed here should still work).Finally, this application report does not provide a tutorial on writing and building code forthe F28xxx DSP. It is assumed that the reader already has at least the main framework oftheir application code running from RAM, probably using the Code Composer Studiodebugger to perform the code download. This report only identifies the special items thatmust be considered when moving the application into on-chip flash memory.Code Composer Studio and DSP/BIOS are trademarks of Texas Instruments.eZdsp is a trademark of Spectrum Digital Incorporated.Trademarks are the property of their respective owners.1SPRA958HContents1Introduction (3)2Creating a User Linker Command File (3)2.1Non-DSP/BIOS Projects (3)2.2DSP/BIOS Projects (4)3Where to Link the Sections (4)3.1Non-DSP/BIOS Projects (5)3.2DSP/BIOS Projects (7)4Copying Sections from Flash to RAM (9)4.1Copying the Interrupt Vectors (non-DSP/BIOS projects only) (9)4.2Copying the .hwi_vec Section (DSP/BIOS projects only) (10)4.3Copying the .trcdata Section (DSP/BIOS projects only) (10)4.4Initializing the Flash Control Registers (DSP/BIOS and non-DSP/BIOS projects) (12)4.5Maximizing Performance by Executing Time-critical Functions from RAM (14)4.6Maximizing Performance by Linking Critical Global Constants to RAM (15)4.6.1Method 1: Running All Constant Arrays from RAM (15)4.6.2Method 2: Running a Specific Constant Array from RAM (18)5Programming the Code Security Module Passwords (19)6Executing Your Code from Flash after a DSP Reset (23)7Disabling the Watchdog Timer During C-Environment Boot (25)8C-Code Examples (27)8.1General Overview (27)8.2Directory Structure and File Utilizations (28)8.3Additional Information (35)References (38)Revision History (39)FiguresFigure 1.Specifying the User Init Function in the DSP/BIOS Configuration tool (11)Figure 2.Specifying the Link Order In Code Composer Studio (17)Figure 3.DSP/BIOS MEM Properties for CSM Password Locations (22)Figure 4.DSP/BIOS MEM Properties for CSM Reserved Locations (22)Figure 5.DSP/BIOS MEM Properties for Jump to Flash Entry Point (24)TablesTable 1.Section Linking in Non-DSP/BIOS Projects (Large memory model) (6)Table 2.Section Linking In DSP/BIOS Projects (Large Memory Model) (7)Table 3.Example Code File Directories (28)Table 4.F2812 Example Code File Inventory and Utilization (29)Table 5.F2808 Example Code File Inventory and Utilization (31)Table 6.F28335 Example Code File Inventory and Utilization (33)2Running an Application from Internal Flash Memory on the TMS320F28xxx DSPSPRA958H1 IntroductionThe TMS320F28xxx DSP family has been designed for standalone operation in embeddedcontroller applications. The on-chip flash usually eliminates the need for external non-volatilememory and a host processor from which to bootload. Configuring an application to run fromflash memory is a relatively easy matter provided that one follow a few simple steps. This report covers the major concerns and steps needed to properly configure application software forexecution from internal flash memory. Requirements for both DSP/BIOS and non-DSP/BIOSprojects are presented. Some performance considerations and techniques are also discussed.Note that the issues discussed in this application report apply directly to current membersof the TMS320F28xxx DSP family. The term F28xxx here, and throughout the remainderof this document, refers specifically to the F2810, F2811, F2812, F2801, F2801-60,F2802, F2802-60, F2806, F2808, F2809, F28015, F28016, F28044, F28232, F28234,F28235, F28332, F28334, and F28335 devices. Applicability to future devices in theTMS320F28xxx family, although quite likely, is not guaranteed. In addition, the code andtechniques presented in this application report for DSP/BIOS projects were developed onCode Composer Studio v3.3.81.5 using C-compiler v5.1.0 and DSP/BIOS v5.33. It isalways suggested that the reader upgrade to the latest version. However, keep in mindthat future versions of DSP/BIOS may have differences that make some of the itemsdiscussed in this report unnecessary (although in all likelihood backwards compatibility willbe maintained, so that the techniques discussed here should still work).Finally, this application report does not provide a tutorial on writing and building code for theF28xx DSP. It is assumed that the reader already has at least the main framework of theirapplication code running from RAM, probably using the CCS debugger to perform the codedownload. This report only identifies the special items that must be considered when moving the application into on-chip flash memory.2 Creating a User Linker Command File2.1 Non-DSP/BIOS ProjectsIn non-DSP/BIOS applications, the user linker command file will be where most memory isdefined, and where the linking of most sections is specified. The format of this file is no different than the linker command file you are currently using to run your application from RAM. Thedifference will be in where you link the sections (to be discussed in Section 3). More information on linker command files can be found in reference [9]. The non-DSP/BIOS code projects thataccompany this application report contain linker command files that can be used for reference.The DSP281x, DSP280x, DSP2804x, and DSP2833x peripheral header files contain linkercommand files named DSP281x_Headers_nonBIOS.cmd, DSP280x_Headers_nonBIOS.cmd, DSP2804x_Headers_nonBIOS.cmd, and DSP2833x_Headers_nonBIOS.cmd respectively (see references [15-18]). These files contains linker MEMORY and SECTIONS declarations forlinking the peripheral register structures. Simply add the appropriate one of these linkercommand files to your code project in addition to your user linker command file.Running an Application from Internal Flash Memory on the TMS320F28xxx DSP 3SPRA958HIn general, the order of the linker command files is unimportant since during a project build, CCS evaluates the MEMORY section of every linker command file before evaluating the SECTIONS section of any linker command file. This ensures that all memories are defined before linkingany sections to those memories. However, advanced users may need manual control over the order of linker command file evaluation in some rare situations. This can be specified withinCCS on the Project → Build_Options, Link_Order tab.2.2 DSP/BIOS ProjectsThe DSP/BIOS configuration tool generates a linker command file that specifies how to link all DSP/BIOS generated sections, and by default all C-compiler generated sections. When running your application from RAM, this linker command file may be the only one in use. However, when executing from flash memory, there will likely be a need to generate and link one or more user defined sections. In particular, any code that configures the on-chip flash control registers (e.g.flash wait-states) cannot execute from flash. In addition, one may want to run certain timecritical functions from RAM (instead of flash) to maximize performance. A user linker command file must be created to handle these user defined sections.CCS supports having more than one linker command file in a project. Hence, all one needs to do is add both the user linker command file, as well as the DSP/BIOS generated linkercommand file, to their project. In general, the order of the linker command files is unimportant since during a project build, CCS evaluates the MEMORY section of every linker command file before evaluating the SECTIONS section of any linker command file. This ensures that allmemories are defined before linking any sections to those memories. However, advanced users may need manual control over the order of linker command file evaluation in some raresituations (for example, to preempt and override DSP/BIOS linkage of a section). This can be specified within CCS on the Project → Build_Options, Link_Order tab.The DSP281x, DSP280x, DSP2804x, and DSP2833x peripheral header files contain linkercommand files named DSP281x_Headers_nonBIOS.cmd, DSP280x_Headers_nonBIOS.cmd, DSP2804x_Headers_nonBIOS.cmd, and DSP2833x_Headers_nonBIOS.cmd respectively (see references [15-18]). These file contains linker MEMORY and SECTIONS declarations for linking the peripheral register structures. Simply add the appropriate one of these linker command files to your code project as well.3 Where to Link the SectionsTwo basic section types exist: initialized, and uninitialized. Initialized sections must contain valid values at device power-up. For example, code and constants are found in initialized sections.When designing a stand-alone embedded system with the F28xxx DSP (e.g., no emulator ordebugger in use, no host processor present to perform bootloading), all initialized sections must be linked to non-volatile memory (e.g., on-chip flash). An uninitialized section does not contain valid values at device power-up. For example, variables are found in uninitialized sections.Code will write values to the variable locations during code execution. Therefore, uninitialized sections must be linked to volatile memory (e.g., RAM).4Running an Application from Internal Flash Memory on the TMS320F28xxx DSPSPRA958H It is suggested that the -w linker option be invoked. The -w option will produce a warning if the linker encounters any sections in your project that have not been explicitly specified for linking ina linker command file. When the linker encounters an unspecified section, it uses a defaultallocation algorithm to link the section into memory (it will link the section to the first definedmemory with enough available free space). This is almost always risky, and can lead tounreliable and unpredictable code behavior. The -w option will identify any unspecified sections(e.g., those accidentally forgotten by the user) so that the user can make the necessary additionto the appropriate linker command file. The -w option can be selected in CCS on the Project →Build_Options menu, Linker tab, select the Advanced category, and then check the -w optionbox. It is checked by default for new projects.CAUTION:It is important that the large memory model be used with the C-compiler (asopposed to the small memory model). Small memory model requires certaininitialized sections to be linked to non-volatile memory in the lower 64Kw ofaddressable space. However, no flash memory is present in this region on anyF28xxx devices, and this will likely be true for future F28xxx devices as well.Therefore, large memory model should be used. In Code Composer Studio, thelarge memory model is on the Project → Build_Options menu. Select theCompiler tab, choose the Advanced category, and check the -ml option box. Fornon-DSP/BIOS projects, one should include the large memory model C-compilerruntime support library into their code project. For the fixed-point devices, thisis library rts2800_ml.lib (as opposed to rts2800.lib, which is for the smallmemory model). For the floating-point devices, this is file rts2800_fpu32.lib forplain C code, or rts2800_fpu32_eh.lib for C++ code (there are no small memorymodel libraries for the floating-point devices). For DSP/BIOS projects,DSP/BIOS will take care of including the required library. The user should notinclude any runtime support library in a DSP/BIOS project.3.1 Non-DSP/BIOS ProjectsThe compiler uses a number of specific sections. These sections are the same whether you are running from RAM or flash. However, when running a program from flash, all initialized sections must be linked to non-volatile memory, whereas all uninitialized sections must be linked tovolatile memory. Table 1 shows where to link each compiler generated section on the F28xxx DSP. Information on the function of each section can be found in reference [5]. Any usercreated initialized section should be linked to flash (e.g., those sections created using theCODE_SECTION compiler pragma), whereas any user created uninitialized sections should be linked to RAM (e.g., those sections created using the DATA_SECTION compiler pragma).Running an Application from Internal Flash Memory on the TMS320F28xxx DSP 5SPRA958H6 Running an Application from Internal Flash Memory on the TMS320F28xxx DSPTable 1. Section Linking in Non-DSP/BIOS Projects (Large memory model) Section Name Where to Link.cinit Flash.cio RAM.const Flash.econst Flash.pinit Flash.switch Flash.text Flash .bss RAM.ebss RAM .stack Lower 64Kw RAM.sysmem RAM.esysmem RAM.reset RAM 1Table 1 Notes:1The .reset section contains nothing more than a 32-bit interrupt vector that points to theC-compiler boot function in the runtime support library (the _c_int00 routine). It generally is not used. Instead, the user typically creates their own branch instruction to point to the starting point of the code (see Sections 6 and 7). When not in use, the .reset section should be omitted from the code build by using a DSECT modifier in the linker command file. For example:/********************************************************************* User's linker command file********************************************************************/SECTIONS{.reset : > FLASH, PAGE = 0, TYPE = DSECT}SPRA958HRunning an Application from Internal Flash Memory on the TMS320F28xxx DSP 73.2 DSP/BIOS ProjectsThe memory section manager in the DSP/BIOS configuration tool allows one to specify where to link the various DSP/BIOS and C-compiler generated sections. Table 2 indicates where the sections shown on each tab of the memory section manager should be linked (i.e., RAM or FLASH). Note that this information has been tabulated specifically for DSP/BIOS v5.33. Later versions of DSP/BIOS, although quite likely to be the same, may have some differences. The reader should check the version they are using and simply be aware of potential differences while proceeding. To check your DSP/BIOS version from within CCS, go to the Help → About menu, click the Component_Manager button, and view the TMS320C28XX DSP/BIOS version under the Target_Content_(DSP/BIOS) tree.Table 2. Section Linking In DSP/BIOS Projects (Large Memory Model) Memory Section Manager TAB Section NameWhere to Link Segment for DSP/BIOS ObjectsRAM General Segment for malloc()/free()RAM Argument Buffer Section (.args)RAM Stack Section (.stack)Lower 64Kw RAM DSP/BIOS Init Tables (.gblinit)Flash TRC Initial Values (.trcdata)RAM 1 DSP/BIOS Kernel State (.sysdata)RAM BIOS Data DSP/BIOS Conf Sections (*.obj)RAM BIOS Code Section (.bios)Flash Startup Code Section (.sysinit)Flash Function Stub Memory (.hwi)Flash Interrupt Service Table Memory (.hwi_vec)PIEVECT RAM 2 BIOS Code RTDX Text Segment (.rtdx_text)Flash Text Section (.text)Flash Switch Jump Tables (.switch) Flash C Variables Section (.bss) RAM C Variables Section (.ebss) RAM Data Initialization Section (.cinit)FlashCompiler Sections C Function Initialization Table (.pinit) FlashSPRA958H8 Running an Application from Internal Flash Memory on the TMS320F28xxx DSP Constant Section (.econst)Flash Constant Section (.const)Flash Data Section (.data)Flash Data Section (.cio)RAM Load Address - BIOS Code Section (.bios)Flash 3 Load Address - Startup Code Section (.sysinit)Flash 3 Load Address - DSP/BIOS Init Tables (.gblinit)Flash 3 Load Address - TRC Initial Value (.trcdata)Flash 1 Load Address - Text Section (.text)Flash 3 Load Address - Switch Jump Tables (.switch)Flash 3 Load Address - Data Initialization Section (.cinit)Flash 3 Load Address - C Function Initialization Table (.pinit)Flash 3 Load Address - Constant Section (.econst)Flash 3 Load Address - Constant Section (.const)Flash 3 Load Address - Data Section (.data)Flash 3 Load Address - Function Stub Memory (.hwi)Flash 3 Load Address - Interrupt Service Table Memory (.hwi_vec)Flash 2 Load Address Load Address - RTDX Text Segment (.rtdx_text) Flash 3Table 2 Notes:1 The .trcdata section must be copied by the user from its load address (specified on theLoad_Address tab) to its run address (specified on the BIOS_Data tab) at runtime. See Section4.3 for details on performing this copy.2 The PIEVECT RAM is a specific block of RAM associated with the Peripheral InterruptExpansion (PIE) peripheral. On current F28xxx devices, the PIE RAM is a 256x16 block starting at address 0x000D00 in data space. For other devices, confirm the address in the device datasheet. The memory section manager in the DSP/BIOS configuration tool should already have a pre-defined memory named PIEVECT. The .hwi_vec section must be copied by the user from its load address (specified on the memory section manager Load_Address Tab) to its run address (specified on the memory section manager BIOS_Code Tab) at runtime. See Section4.2 for details on performing this copy.3The specific flash memory selected as the load address for this section should be the same flash memory selected previously as the run address for the section (e.g., on the BIOS_Data, BIOS_Code, or Compiler_Sections tab).SPRA958H 4 Copying Sections from Flash to RAM4.1 Copying the Interrupt Vectors (non-DSP/BIOS projects only)The Peripheral Interrupt Expansion (PIE) module manages interrupt requests on F28xxxdevices. At power-up, all interrupt vectors must be located in non-volatile memory (i.e., flash), but copied to the PIEVECT RAM as part of the device initialization procedure in your code. The PIEVECT RAM is a specific block of RAM, which on current F28xxx devices is a 256x16 block starting at address 0x000D00 in data space.Several approaches exist for linking the interrupt vectors to flash and then copying them to the PIEVECT RAM at runtime. One approach is to create a constant C-structure of function pointers that contains all 128 32-bit vectors. If using the DSP28xx peripheral structures (see references [15-18]), such a structure, called PieVectTableInit, has already been created in thecorresponding file DSP28xxx_PieVect.c. Since this structure is declared using the const typequalifier, it will be placed in the .econst section by the compiler. One simply needs to copy this structure to the PIEVECT RAM at runtime. The C-compiler runtime support library contains amemory copy function called memcpy() that can be used to perform the copy task. Thisfunction is used as follows:/********************************************************************* User's C-source file********************************************************************//********************************************************************* NOTE: This function assumes use of the DSP28xxx Peripheral Header* File structures (see References [15-18]).********************************************************************/#include <string.h>void main(void){/*** Initialize the PIE_RAM ***/PieCtrlRegs.PIECTRL.bit.ENPIE = 0; // Disable the PIEasm(" EALLOW"); // Enable EALLOW protected register access memcpy((void *)0x000D00, &PieVectTableInit, 256);asm(" EDIS"); // Disable EALLOW protected register access }The above example uses a hard coded address for the start of the PIE RAM, specifically0x000D00. If this is objectionable (as hard coded addresses are not good programmingpractice), one can use a DATA_SECTION pragma to create an uninitialized dummy variable,and link this variable to the PIE RAM. The name of the dummy variable can then be used inplace of the hard coded address. For example, when using any of the DSP28xxx deviceperipheral structures, an uninitialized structure called PieVectTable is created and linked overthe PIEVECT RAM. The memcpy() instruction in the previous example can be replaced by:memcpy(&PieVectTable, &PieVectTableInit, 256);Note that the length is 256. The memcpy function copies 16-bit words (as opposed to copying 128 32-bit words).Running an Application from Internal Flash Memory on the TMS320F28xxx DSP 9SPRA958H4.2 Copying the .hwi_vec Section (DSP/BIOS projects only)The DSP/BIOS .hwi_vec section contains the interrupt vectors, and must be loaded to flash but run from RAM. The user is responsible for copying this section from its load address to its run address. This is typically done in main(). The DSP/BIOS configuration tool generates globalsymbols that can be accessed by code in order to determine the load address, run address, and length of the .hwi_vec section. These symbol names are:hwi_vec_loadstarthwi_vec_loadendhwi_vec_runstartEach symbol is self-explanatory from its name. Note that the symbols are not pointers, butrather symbolically reference the 16-bit data value found at the corresponding location (i.e., start or end) of the section. The C-compiler runtime support library contains a memory copy function called memcpy() that can be used to perform the copy task. A C-code example of how to use this function to perform the section copy follows. Note that the PIEVECT RAM is EALLOWprotected. Therefore, inline EALLOW and EDIS assembly instructions must bracket the memory copy of the .hwi_vec section, as shown./********************************************************************* User's C-source file********************************************************************/#include <string.h>extern unsigned int hwi_vec_loadstart;extern unsigned int hwi_vec_loadend;extern unsigned int hwi_vec_runstart;void main(void){/*** Initialize the .hwi_vec section ***/asm(" EALLOW"); /* Enable EALLOW protected register access */ memcpy(&hwi_vec_runstart,&hwi_vec_loadstart,&hwi_vec_loadend - &hwi_vec_loadstart);asm(" EDIS"); /* Disable EALLOW protected register access */ }4.3 Copying the .trcdata Section (DSP/BIOS projects only)The DSP/BIOS .trcdata sections must be loaded to flash, but run from RAM. The user isresponsible for copying this section from its load address to its run address. However, unlike the .hwi_vec section, the copying of .trcdata must be performed prior to main(). This is becauseDSP/BIOS modifies the contents of .trcdata during DSP/BIOS initialization (which also occurs prior to main()).10Running an Application from Internal Flash Memory on the TMS320F28xxx DSPThe DSP/BIOS configuration tool provides for a user initialization function which can be utilized to perform the .trcdata section copy prior to both main() and DSP/BIOS initialization. This can be found in the project configuration file under System - Global Settings Properties, as shown in Figure 1.Figure 1. Specifying the User Init Function in the DSP/BIOS Configuration toolWhat remains is to create the user initialization function. The DSP/BIOS configuration toolgenerates global symbols that can be accessed by code in order to determine the load address, run address, and length of each section. These symbol names are:trcdata_loadstarttrcdata_loadend trcdata_runstartEach symbol is self-explanatory from its name. Note that the symbols are not pointers, butrather symbolically reference the 16-bit data value found at the corresponding location (i.e., start or end) of the section. The C-compiler runtime support library contains a memory copy function called memcpy() that can be used to perform the copy task. A C-code example of a user init function that performs the .trcdatasection copy follows. Check this box Enter yourfunction namehere (note theleading underscore)/********************************************************************* User's C-source file********************************************************************/#include <string.h>extern unsigned int trcdata_loadstart;extern unsigned int trcdata_loadend;extern unsigned int trcdata_runstart;void UserInit(void){/*** Initialize the .trcdata section before main() ***/memcpy(&trcdata_runstart,&trcdata_loadstart,&trcdata_loadend - &trcdata_loadstart);}4.4 Initializing the Flash Control Registers (DSP/BIOS and non-DSP/BIOS projects)The initialization code for the flash control registers, FOPT, FPWR, FSTDBYWAIT,FACTIVEWAIT, FBANKWAIT, and FOTPWAIT, cannot be executed from the flash memory or unpredictable results may occur. Therefore, the initialization function for the flash controlregisters must be copied from flash (its load address) to RAM (its run address) at runtime.CAUTION:The flash control registers are protected by the Code Security Module (CSM). Ifthe CSM is secured, you must run the flash register initialization code from CSMsecured RAM (e.g. L0 through L3 SARAM, see the device data sheet for yourspecific device) or the initialization code will be unable to access the flashregisters. Note that the CSM is always secured at device reset, although theROM bootloader will unlock it if you are using dummy passwords of 0xFFFF.The CODE_SECTION pragma of the C compiler can be used to create a separately linkable section for the flash initialization function. For example, suppose the flash register configuration is to be performed in the C function InitFlash(), and it is desired to place this function into alinkable section called secureRamFuncs. The following C-code example shows proper use of the CODE_SECTION pragma along with an example configuration of the flash registers:。

Unique in its versatility!• Non-tiring work thanks to particularly low weight.• Fast-fix spindle stop for quick and easy saw blade changing.• Virtually splinter-free cuts on both sides thanks to thesplinterguard on the guide rail and the attachable splinterguard.The Expert in Guidance.• Clean, splinter-free cuts thanks to the guide system with the splinterguard.•Dead-straight results when sawing and routing with the guide rail.•Convenient use of professional accessories thanks to the second groove.Combi-bevelfor mounting in the 2nd groove on the guide rail, makes precise angled cuts between 0° and 180° possibleFS-KS,Order no. 491588Return stop/Guide stopis inserted into the 2nd groove on the guide rail and overlaps the base plate of the circular saw for TS 55, ATF 55, AP 55, AT 65, AP 65, AP 85FS-RSP, Order no. 491582Sliding surfaceSpare sliding surface for guide rail, 10 m rollFS-GB 10M, Order no. 491741Quick-action clampfor clamping and positioning the Festool guide railsScope of delivery: blade clamps, fixed clamps Qty. in pack: 1FS-RAPID,Order no. 489790Lever clampQuick and easy clamping Fitting width: 60 mmFS-HZ 160,Order no. 491594Screw clampsPolished steel versionFitting width: 120 mm, Qty. in pack: 2 FSZ 120,Order no. 489570Fitting width: 300 mm, Qty. in pack: 2 FSZ 300,Order no. 489571Connectorfor connecting two guide rails for long workpieces, Qty. in pack: 1FSV,Order no. 482107Deflectorprevents the suction hose and the cable getting tangled on the end of the guide rail.FS-AW,Order no. 489022SplinterguardSpare splinterguard for guide rail Length: 800 mmFS-SP 800,Order no. 488468Length: 1400 mmFS-SP 1400,Order no. 483164Length: 3000 mmFS-SP 3000,Order no. 488467Adhesive sole plateSpare adhesive sole plate for guide rails, 10 m rollFS-HU 10M,Order no. 485724Description and applicationParallel stop/table widener for TS 55Bilateral parallel stop, also usable as table widenerPA-TS 55,Order no. 491469Cover/false joint stop for TS 55Cover for enhanced dust extraction, eg when sawing MDF, also usable as a false joint stop for sawing false jointsABSA-TS 55,Order no. 491750Splinterguard for TS 55For splinter-free cuts, splinter-free on both sides when used with guide rail Qty. in pack: 5 x splinterguards,1 x locking screw SP-TS 55, Order no. 491473Description and application1011。

DSP28335—CMD解读（1）在DSP28335工程文件里（不用BIOS产生CMD文件），手写CMD文件一般有两个，在RAM里调试时用的两个CMD文件分别为DSP2833x_Headers_nonBIOS.cmd和28335_RAM_lnk.cmd，烧写到flash里时用的两个CMD文件分别为DSP2833x_Headers_nonBIOS.cmd和F28335.cmd，其中DSP2833x_Headers_nonBIOS.cmd文件可以在所有工程文件中通用，主要作用是把外设寄存器产生的数据段映射到对应的存储空间，可以跟DSP2833x_GlobalVariableDefs.c文件对照一下看看。

下面通过一个简单例子，比如向CpuTimer0Regs. TIM.all写数据，来解读一下CMD文件是如何把寄存器里的值准确映射到所在存储器的位置的。

先在DSP2833x_GlobalVariableDefs.c文件里找到以下几行代码：#ifdef __cplusplus#pragma DATA_SECTION("CpuTimer0RegsFile")#else#pragma DATA_SECTION(CpuTimer0Regs,"CpuTimer0RegsFile");#endifvolatile struct CPUTIMER_REGS CpuTimer0Regs;由上可知CpuTimer0Regs是一个结构体变量名（其定义在DSP2833x_CpuTimers.c文件里），通过预处理命令#pragma 为这个结构体定义了一个名称为CpuTimer0RegsFile的数据段。

接着在DSP2833x_Headers_nonBIOS.cmd文件里找到如下代码：SECTIONS{PieVectTableFile : > PIE_VECT, PAGE = 1DevEmuRegsFile : > DEV_EMU, PAGE = 1FlashRegsFile : > FLASH_REGS, PAGE = 1CsmRegsFile : > CSM, PAGE = 1AdcMirrorFile : > ADC_MIRROR, PAGE = 1XintfRegsFile : > XINTF, PAGE = 1CpuTimer0RegsFile : > CPU_TIMER0, PAGE = 1......}红字体代码的作用就是，通过SECTIONS伪指令把CpuTimer0RegsFile数据段装载到名称为CPU_TIMER0的存储空间。

for users regarding software and hardware updates(following the NAMUR recommendation 53)Field Xpert SMT70 1.02.00New software version is released1 Type of ProductSoftware/hardware for device configuration/tablet/handheld/device drivers etc.Modem/interfaceManufacturer : Endress+Hauser Process Solutions AGProduct : Field Xpert SMT70Type and order code : SMT702 SoftwarePrevious software version : 1.00.00, 1.00.02, 1.01.00New software version : 1.02.00How can the previous software version number be identified? : Inside the current software version under menu item (Help) -> License -> VersionDescription of the modification in comparison with the predecessor version Main changes to the software are:•Automatic DTM UpdateDTM’s will be automatically downloaded andinstalled. With that the Field Xpert stays always up-to-date.•Fieldgate SFG250 support (Ethernet-HART)•Fieldgate SWG70 support (WirelessHART)•Tank scanner NXA820 support•mobiLink support for HART and FF•RFIDRead and write Endress+Hauser RFID TAGs (needsoptional RFID Reader)Get asset information with one click after readingthe RFID tag•Usability improvementsWhere to get the new Software? If there is a valid maintenance period (Software Update Service) of the tablet and an Internet connection is detected, the Field Xpert SMT70 software automatically recognizes a new software versionfor users regarding software and hardware updates(following the NAMUR recommendation 53)and downloads the software.The user then can execute the installation or skip it.If the maintenance period of the tablet has expired, we kindly askyou to contact the Endress+Hauser sales. (Topic: Field XpertSMT70 Software-Update Contract, Software Update Service)The communication DTMs und device DTMs and additional thenew drivers can be downloaded at the Endress+Hauser softwareportal:https:///Additionally, we recommend to keep the Microsoft Windowsoperating system up-to-date.3 CompatibilityIs the new product software compatible with the previous version?YesNo, reason:Is a software update generally recommended?Yes, reason:It is recommended to update to the new software version of the Field Xpert SMT70. Thisensures that Field Xpert can operate with newer field devices. Furthermore, the functionalityhave been extended and found issues have been solved.No, reason:for users regarding software and hardware updates(following the NAMUR recommendation 53)4 Instruction manualIs a new instruction manual necessary due to the software modification?YesNoThe manual that corresponds to the current version is:Product Document Document identifierField Xpert SMT70 Operating Instructions (BA) BA01709S/04/EN/02.18 The instruction manual can be downloaded from the Internet:https:///SMT70-> Tab “Documents / Manuals / Software ”5 PriceIs there a change in price in comparison with the predecessor version?Yes, new list price and update costsNo。

1. DSP编程技巧到底有什么好资料?话说专门深入讲解这个的资料并不是太多，因为大部分DSP书籍都是讲解算法或者寄存器是怎么使用的，那尽量罗列一下(如有遗漏请在评论区补充)，有：(1)《DSP C2000程序员高手进阶》这本书是当年笔者学习DSP的时候看了好几遍的，讲的非常深入、透彻，可惜早就卖光了并且没有再版。

需要的网友可以考虑去图书馆看看，图书馆里最不缺少的就是老版本的书籍了。

(2)EEPW牛人业话我们EEPW首页的牛人业话里，已经有大量这方面的总结了，链接太多就不一一列举了，请到/news/articlelist/type/39中阅读。

(3)官方资料最权威的当然还是官方资料，特别是《TMS320C28x Optimizing C/C++ Compiler User’s Guide》和《TMS320C28x Assembly Language Tools User’s Guide》。

不足之处就在于，它们都像教科书，严谨有余，活泼不足，特别是初入门的人看起来会比较累。

(4)参加一些培训好的培训一般都是要付费的，这个要根据自己的实际情况进行取舍了。

2. 答疑解惑哪家强?经验的积累，除了自己努力的自学之外，有时候一些难关还是得有别人的帮助才行，可能你花3天搞不定的问题，他一看就想起来是什么原因了。

如果是企业客户，那直接联系官方技术支持，很容易就搞定了。

或者也可以去官方论坛提问，然后等待解答。

对于广大网友来说，直接获得技术支持可能有一定的难度。

我们EEPW的论坛的人气充足，对问题的响应速度也是迅雷不及掩耳的，所以有关DSP的问题尽可以到/forum/29/1下提问。

前面这两个无关具体技术，但是能起到―源头‖的作用。

接下来就是具体的技术问题了，有几十个，我们慢慢来看吧。

3. 作为入门者，创建一个最基本的工程需要做哪些事情?最简单的入门方法是从现有的例子上入手，比如购买开发板的话，一般都会附送十几到几十个上手用的例子工程，把它们研究一遍，基本上入门这关就过了。