翻译接龙第四期：Migrating within the controller continuum

斯嘉丽

翻译接龙第4期，敬请参与，本期我们将评出3名优秀译者，每人奖励价值50元卓越购物券。
 
获奖条件：根据译者翻译的精准度、文章长短以及对其他译者的点评、帮助选出。
 
1、As product complexity grows and the need to add new features accelerates, engineers face a challenging task of
migrating applications from 8-bit to 32-bit microcontrollers (MCU). This application note describes how the Flexis family of MCUs eases this task. Although peripherals are identical in this family, there are differences between 8-bit and 32 bit architectures. This document provides a guide on how to develop an application where the same code can be used in both cores without changes.
 
2、This application note covers the architectural differences between 8-bit and 32-bit MCUs. It provides tips and
tricks for writing C applications, ensuring code reuse and an easy migration. Finally, it details the enhancements in
CodeWarrior for Microcontrollers V6.0, describing how the tool simplifies the porting experience between S08 and ColdFire V1.
 
3、Why migrate between 8-bit and 32-bit?

Before deciding to use 8-bit or 32-bit technology, the following reasons should be considered:

4、Common migration headaches

• A difficulty that can be found when migrating from applications between 8-bits and 32- bits is the use of different software tools. The time it takes to learn features and functionality can be significant, depending on how different the tools are. Derivatives and libraries might need updating when switching among devices. Hardware tools are commonly different; this implies extra cost and development time.
• The change in software implies the use of different documentation, register naming and of course peripherals. The configuration of peripherals can get as complicated as the complexity gap between an 8 and a 32-bit architecture.
• Simple factors like differences in debugging tools and debugging modules of both devices can impact the development.
• Regarding the pin-out, peripherals and supply pins might be located in different areas of the silicon.The supply voltage might be different and extra hardware might be required. The assignment of signals can vary creating conflict when building the new board.
• Different power modes can be found because they depend on the architecture.

All these differences lead a designer to re-write software, from peripherals to the variations in memory maps and changes in exception handling. These migration headaches could be the difference between a failing and a successful project.

5 Building using Freescale Controller Continuum

A Freescale Controller Continuum is an 8-bit to 32-bit compatible device that shares a common set of peripherals and tools.

It is important for a developer to know an array of products that range in performance and allow different options for different applications. Designs evolve and applications demand more performance and functionalities. Process technology improvements push costs down on 32-bit MCUs making them more affordable.

6、Migrating across continuum of performance and price options are not easy or quick when different bit architectures require re-coding and different tools.

Freescale is breaking bit boundaries to provide a simple and seamless path performance between 8-bit and 32-bit MCUs.

阅读全文

斯嘉丽

7、The Flexis Series of Microcontrollers

The controller continuum “Connection Point”

A number of factors contribute to a seamless transition from an 8-bit to a 32-bit architecture. The improvements start at the core and involve peripherals and packaging as well as development tools.

8、The ColdFire instruction set architecture (ISA) has changed since its initial implementation over a decade ago. It has changed from an optimization philosophy for 32-bit operands. It now expands and improves support for handling 8-bit and 16-bit operands. For the V1 class of applications, this is particularly important for users migrating from 8-bit and 16-bit applications. At the processor core level, it is important for the implementation of the instruction set to directly address some of the issues that involve efficient handling of 8-bit and 16-bit operands.

9、The V1 core microarchitecture has improved the V2 ColdFire regarding the 8-bit and 16-bit operands. In applications with data referenced to 8-bit and 16-bit operands, the instruction support and fast execution time for those instructions provides a considerable performance improvement.

10、The continuum takes advantage of existing peripherals. Peripheral blocks connect to a common bus
structure and complete reuse of the S08 is ensured. As a result, the 8-bit projects can be re-usable.

The Flexis series of microcontrollers have:

• Single development tool to ease migration between 8-bit (S08) and 32-bit (CFV1). The same
CodeWarrior versions support both cores.
• Common peripheral set to preserve software investment between 8-bit and 32-bit.
• Practical pin compatibility wherever to maximize hardware reuse when moving between 8-bit and 32-bit.

11、Industry’s first 8-bit and 32-bit compatible MCUs

S08 and ColdFire V1are the industry’s ultra low power flexis devices first 8-bit and 32-bit pin, peripheral and tool compatible MCUs. They make the design process quick, easy and limitless.

12、Evident advantages can be found using Flexis. The Software re-investment and design cycle time is drastically reduced. Peripheral and tools compatibility makes the transition between 8-bit and 32-bit fast and simple.

Table 2 recommends when to use the S08 and ColdFire V1 separately and together.

13、 Hardware comparison

Most of the competitions´ MCUs do not have the flexibility to migrate an application from an 8-bit MCU to a 32-bit MCU. These hardware architectures are not sharing important things such as peripherals.

14、Figure 2 shows the hardware architecture the S08 and ColdFire V1 share. This sharing makes the migrations an easy practice for applications engineers and developers

moonstar1214

一如既往支持

康桥人

挺有意思的一个活动，以前没有看到，试试。
1.随着产品的复杂程度增加以及对产品新功能需求速度的加快，工程师们面临着移植程序的挑战：从8位单片机到32位单片机。下面的这份文档描述了Flexis家族中的单片机是如何减轻这种程序移植的任务。Flexis家族中的单片机虽然片内外设是一样的，但是8位是与32位单片机在结构体系上还有差别的。这份文档将告诉我们如何在这两种内核中去开发一个相同的应用程序。
2.这份文档涵盖了8位与32位单片机在体系结构上的差异。它提供了编写C语言应用程序的技巧与窍门，从而确保了程序的可重复利用与方便移植性。最后，它详细的说明了CodeWarrior6.0的增强功能，描述了如何使用它的工具去简化在S08与Clodfire V1之间的移植。

霜筠

5 Building using Freescale Controller Continuum
A Freescale Controller Continuum is an 8-bit to 32-bit compatible device that shares a common set of peripherals and tools.
It is important for a developer to know an array of products that range in performance and allow different options for different applications. Designs evolve and applications demand more performance and functionalities. Process technology improvements push costs down on 32-bit MCUs making them more affordable.

使用飞思卡尔控制器联合体建设

飞思卡尔“控制器联合体（Controller Continuum）”是一个8位至32位的兼容设备，它共享着外围设备和工具的公用设置。
对开发者来说，了解一批不同性能的产品并且对不同的应用程序使用不同的选项是很重要的。设计演化发展，应用软件需要更多的性能和功用。工艺技术的改进促使32位微程序控制器的成本降低，使它们变得可以负担。

6、Migrating across continuum of performance and price options are not easy or quick when different bit architectures require re-coding and different tools.
Freescale is breaking bit boundaries to provide a simple and seamless path performance between 8-bit and 32-bit MCUs.

当不同的位架构需要重新编码和不同的工具时，通过性能和价格选项的综合考虑，进行移植并不简单快捷。
飞思卡尔打破了位的界限，提供了一种在8位和32位微程序控制器之间简单的天衣无缝的捷径。

7、The Flexis Series of Microcontrollers

The controller continuum “Connection Point”

A number of factors contribute to a seamless transition from an 8-bit to a 32-bit architecture. The improvements start at the core and involve peripherals and packaging as well as development tools.

Flexis系列微控制器

控制器联合体的“连接点”
多项因素影响着8位到32位架构的完美转换。改进从核心开始，涉及到外围设备、包装以及开发工具。

8、The ColdFire instruction set architecture (ISA) has changed since its initial implementation over a decade ago. It has changed from an optimization philosophy for 32-bit operands. It now expands and improves support for handling 8-bit and 16-bit operands. For the V1 class of applications, this is particularly important for users migrating from 8-bit and 16-bit applications. At the processor core level, it is important for the implementation of the instruction set to directly address some of the issues that involve efficient handling of 8-bit and 16-bit operands.

自从十多年以前开始实施，ColdFire指令集结构（ISA）已经发生了改变。它从优化哲学变成了32位运算。如今它进行了扩展，改善了对处理8位和16位运算的支持。对于V1级别的应用软件，用户从8位和16位软件进行移植尤为重要。关于处理器核心的水平，执行命令集直接对有效地处理8位和16位运算的问题进行解决是非常重要的。

9、The V1 core microarchitecture has improved the V2 ColdFire regarding the 8-bit and 16-bit operands. In applications with data referenced to 8-bit and 16-bit operands, the instruction support and fast execution time for those instructions provides a considerable performance improvement.

V1核心微构架在8位和16位运算方面改进了V2 ColdFire。在应用关于8位和16位运算的数据的过程中，指令支持和快速的执行命令的时间有了相当可观的性能方面的改善。

康桥人

3．为什么要在8位与32位之间移植程序?
在决定使用8位或者32位技术之前,如下因素是我们必须考虑的。
4．当我们在8位与32位单片机之间移植应用程序的时候，我们会发现因使用不同的开发软件而引起的困难。这将要求我们花时间去了解他们的特性与功能，而所花费时间的长短由他们具体的不同之处所决定。而且他们使用的硬件开发工具一般情况下也是不同的，这意味着增加额外的成本与开发时间。
使用不同的软件意味着使用不同的文件、不同的寄存器名称和不同的外设，而外围设备配置将会和8位32位的体系结构一样的复杂。
简单的因素，比如两种设备之间的调试工具的不同和调试模式的不同，都影响着开发环节。

斯嘉丽

康桥人也来参加了，支持下！

flashman911

先发一点试试。呵呵
1、随着产品复杂度的增加和对增加新功能的需求，工程师要面对一个具有挑战性的任务：从8位到32位微控制器产品的转变。这篇应用笔记讲述了Flexis系列微控制器怎么简化了这个任务。
2、这篇应用笔记讲解了8位和32位微控制器结构上的区别。本文还介绍了很多编写C程序用用上的建议和技巧。最后，还详细介绍了微控制器V6.0版本的CodeWarrior增强的地方，并讲解了工具是如何简化了S08和Coldfire V1之间移植的经验。
3、为什么要从8位转移到32位转变
在决定使用 8位或者32位技术前，要考虑到下面的原因。
4、转变中常见困扰
当将产品从8位转变位32位的时候会发现一个难题就是所使用的工具软件的不同。熟悉工具软件的特性和功能所用的时间十分重要。这取决于工具之间差别有多大。在选择芯片的时候派生物和库文件可能需要更新。区别最大的是硬件工具。这就意味着额外的花费和开发时间。
软件上的变化意味着使用不同的文档、不同的寄存器命名以及外围设备。外围设备的构造会像8位与32位结构间复杂的差距一样复杂。
像在仿真工具和在仿真模块方面上的差别这样的简单因素都能影响产品开发。
关注一下输出管脚：外设管脚和供电管脚可能被分配到芯片的不同区域。供电电压可能会不同，而且可能可能还需要额外的硬件。信号的不同的任务可能会在搭建新电路板的时候产生冲突。
由于芯片的结构，可以有不同的电源模式。
所有的这些不同点使得设计人员重新编写软件。这些软件涵盖了从外部设备一直到各种各样的
5、采用飞思卡尔控制器联合体设计
一个飞思卡尔控制器联合体是一个兼容8位和32位的设备。他可以共享一些列公共的外设和工具。
对于开发人员获知一系列的产品的性能以及产品所针对的不同的应用，这是是很重要的。设计的改进和应用要求更高的性能和功能。处理技术的改进降低的32位微控制器的花费，这使得他们更多地被选购。

霜筠

到现在都没结束开奖啊~~那我再加一段支持支持吧~~

10、The continuum takes advantage of existing peripherals. Peripheral blocks connect to a common bus structure and complete reuse of the S08 is ensured. As a result, the 8-bit projects can be re-usable.
The Flexis series of microcontrollers have:
• Single development tool to ease migration between 8-bit (S08) and 32-bit (CFV1). The same CodeWarrior versions support both cores.
• Common peripheral set to preserve software investment between 8-bit and 32-bit.
• Practical pin compatibility wherever to maximize hardware reuse when moving between 8-bit and 32-bit.

这种连续性有利于现有的外围设备。周围的块连接到一个共同的总线构架，保证可以完成S08的再利用。因此8位的方案是可以再利用的。


Flexis系列微控制器拥有：

单一的开发工具使8位(S08)和32位 (CFV1)之间的移植变得很轻易。同样的CodeWarrior版本同时支持两个内核。

通用的外围设备保证8位和32位软件的投入使用。

无论什么情况下，当在8位和32位之间移动时，实用的插头兼容性使硬件的再利用最大化。

最后,希望斑竹早日发奖吧~~鞠躬

霜筠

人气不行啊，只能自己翻完了 等开奖。。。



11、Industry’s first 8-bit and 32-bit compatible MCUs

S08 and ColdFire V1 are the industry’s ultra low power flexis devices first 8-bit and 32-bit pin, peripheral and tool compatible MCUs. They make the design process quick, easy and limitless.

业界第一个8位和32位兼容的微控制器

S08和ColdFire V1是业界尖端的低功耗Flexis系列设备里首款8位和32位引脚、外设和工具兼容的微控制器。他们让设计过程更快、更简易、更少限制。

12、Evident advantages can be found using Flexis. The Software re-investment and design cycle time is drastically reduced. Peripheral and tools compatibility makes the transition between 8-bit and 32-bit fast and simple.
Table 2 recommends when to use the S08 and ColdFire V1 separately and together.

使用Flexis系列的优势是明显的。软件的再投资和设计周期时间大大减短。外设和工具的兼容性让8位和32位之间的转换变得快速简便。
表格2介绍了什么时候可以单独和共同使用S08 和 ColdFire V1。


13、 Hardware comparison

Most of the competitions´ MCUs do not have the flexibility to migrate an application from an 8-bit MCU to a 32-bit MCU. These hardware architectures are not sharing important things such as peripherals.

硬件比较

大多数竞争的微控制器不具备从8位微处理器移植一个应用软件到16位微处理器的弹性。这些硬件构架不分享诸如外设之类的重要东西。

14、Figure 2 shows the hardware architecture the S08 and ColdFire V1 share. This sharing makes the migrations an easy practice for applications engineers and developers

图2显示了S08和ColdFire V1共享的硬件构架。对应用软件工程师和开发者来说，这种共享让移植变成一种简单的实践。