#Windows ce 6.0 image code
As a result, when Windows CE 6.0 OS is operating, simultaneous debugging of algorithms can take place with the help of both JTAG and Code Composer Studio.īut if code debugging is performed without JTAG and Code Composer Studio, the task becomes more complicated as some nonstandard methods will be needed. In the core selection window for debugging, the DSP core can be selected and the debugger can be connected to it without stopping the ARM subsystem. If the developer of an application for DSP has an opportunity to use JTAG and the Code Composer Studio environment, then the debugging process is simple.
![windows ce 6.0 image windows ce 6.0 image](http://img.dxcdn.com/productimages/sku_39391_10.jpg)
This, in turn, allows implementation of communications algorithms that do not normally work in combination with the DSPLinklibrary.ĭevelopers experienced in programming with TI‘s C6000 DSPs would find such an approach more reasonable as it would significantly reduce the time they would have to allocate to this issue. In the implementation used in our projects at Axonim, the OAL has been modified for use in the BSP OMAP-L138 for Windows CE 6.0, where it can be implemented in combination with a tool for complete DSP core manipulation. The problem is that the exchange between ARM and DSP subsystems needs to be arranged independently, as does loading and starting DSP code. In our experience there are quite a few of these. However, this often requires solving a number of problems related to the distribution of sections of a DSP application,such as making sure the correct address of the input point is communicated in order to start a DSP operation. It is also possible to make use of the OMAP‘s DSP capabilities in applications using Windows CE 6.0 OS without necessarily using TI‘s DSP/BIOS or the DSPLink library. Additional settings are not required – it is enough to add a component from the package of DSPLink source codes into the Windows CE 6.0 OS working project. After successful assembly, the resulting files are transferred to the BSP. Assembly of the DSPLink library is not complicated but it does require some time and attention during configuration.
![windows ce 6.0 image windows ce 6.0 image](https://sc04.alicdn.com/kf/HTB1b1xmLVXXXXaKapXXq6xXFXXXU.jpg)
To give the developer as much flexibility as possible this memory needs to be segmented into several partitions, one available only to the ARM core and Windows CE 6.0 OS, another segment available only for DSP core and a third area available to both cores and for the DSPLinklibrary.įigure 10 shows distribution of RAM DDR memory when using DSPLink. This RAM is normally used for Windows CE 6.0 OS for operation of applications, services, drivers, and the ARM processor core. In complex DSP operations where it is necessary to link to the library, the developer needs to modify the mDDR/DDR2 random access memory normally used for data storage, so programs can access the library when needed.
![windows ce 6.0 image windows ce 6.0 image](https://sc04.alicdn.com/kf/H9176939afc5944d096d8bf7265aa25dcL.jpg)
The standard board Windows CE 6.0 board support package (BSP) for the OMAP-L138 SoC (discussed in detail in Part 1 and Part 2) does not include the DSPLink library.
![windows ce 6.0 image windows ce 6.0 image](https://i0.wp.com/cdnlegacy.ubergizmo.com/photos/2009/7/smartq5-mid.jpg)
Part 3: Using the Windows 6.0 Board Support Package