This release note covers version v10.0r2. It describes the changes and new features of all TASKING 68K/ColdFire products since v9.2. The following parts are described:
The solved and known problems are not part of this release note, they are described in a separate file: Solved_10_0r2.html.
Sometimes hardware test boards have memory areas which are not readable because this influences the debug interface. The result is that all registers seem to be zero in the register window of CrossView Pro and cannot be modified anymore. If this is still the case after a target reset, it is probably because CrossView Pro tried to read one of those memory locations directly after the reset. This happens if the memory window shows an invalid memory area or the stack window is open and the stack pointer contains an invalid address. To overcome this, close all CrossView Pro windows and reset the target. Open the CrossView Pro register window and modify the registers containing an invalid address. Now it is save to reopen other CrossView Pro windows.
All tools have been adapted to support long file names and directory names, which may contain spaces.
File system simulation enables the application on the target board to use system calls (such as open, read, write) that are handled by the host system file I/O services. These files can be read directly from the host system, and output can be written to a file on the host system or in a CrossView Pro window. File system simulation is available for all execution environments.
The low-level I/O functions such as _open(), _close(), _read(), _write() are implemented in the C library to use File System Simulation. These functions redirect high-level I/O calls such as printf() and scanf() type functions through CrossView Pro's FSS feature, allowing you to perform stdin, stdout and stderr stream I/O by just using these standard C library functions.
The libraries have been optimized to only attach the file I/O routines if the application actually uses file I/O. The default I/O streams stdin, stdout and stderr are opened on the fly whenever file I/O is used; this behavior is transparent to the user. It is no longer necessary to inform CrossView Pro about the use of any streams.
There can be some pitfalls when mixing pre v10.0r1 I/O routines (Simulated I/O) with this new FSS feature:
If you have either one of these situations, then do the following:
If your source code interfaces directly on the _simi() and _simo() Simulated I/O functions, then please be aware that the v10.0r1 libraries do not use these functions anymore. They use FSS instead which cannot be mixed with Simulated I/O in any way. Although CrossView Pro still supports Simulated I/O, it would be highly advisable not to use the _simi() and _simo() Simulated I/O functions directly from your source code but use regular ANSI-C printf() and scanf() type functions, instead which ensures portability of your application.
Because FSS buffers its data by default, just as you were used to with Simulated I/O, please beware that you either use the "\n" newline character to terminate the information you are printing with printf() type functions, or use the fflush() function to flush this buffer in order to force FSS to display its information on the CrossView Pro Terminal Windows or to write it into a file. Neither CrossView Pro nor the FSS implementation in the library will perform this operation for you. For example, to clear the entire screen, you can enter:
Please see the section about File System Simulation in the CrossView Pro manual for details on attaching your own streams to certain CrossView Pro Terminal Windows and how to capture and feed the default I/O streams stdin, stdout and stderr.
Version 10.0r1 supports a whole range of new derivatives including the MC68LC040, MC68EC060 and MC68LC060, the Dragonball family and many members of the ColdFire family, MCF5204, MCF5206, MCF5206E, MCF5249, MCF5249L, MCF5272, MCF5280, MCF5282 and MCF5307.
Version 10.0r2 also supports the MCF5214, MCF5216, MCF5232, MCF5233, MCF5234, MCF5235, MCF5270, MCF5271, MCF5274, MCF5275 and MCF5281 of the ColdFire family.
The EDE in v10.0 has been highly improved and reorganized. The menu structure has changed: all items previously included in the EDE menu are now distributed over the other menus. All dialogs for setting the options are now integrated in a single Project Options dialog, accessible from the Project menu.
|IMPORTANT NOTE||The changes in EDE may have some implication for your application. Although EDE converts the settings from your project file of previous versions, it is still recommended to double check your project options.|
You can navigate through the different option dialogs via the expandable tree view as you are familiar with from other Windows based applications. This new way of presenting the options guarantees that you will not lose the complete overview.
The GUI of CrossView has been improved, resulting in a more intuitive and user-friendly interface.
You will be warned if a source file is newer than the download file.
Static variables within a function can be inspected and a hexadecimal display
option in the Data Window has been added.
The performance of the terminal windows has been improved; scrolling and updating of windows has become much faster.
You can use the new File | Compare Application... dialog to check if a file matches the downloaded application. This can be useful when you want to check if the program code has been changed, for example due to uninitialized pointers. The same check can be accomplished through the command window with the dcmp command.
It is now possible to save your profiling results. Either you can use the
commands cproinfo and proinfo from the command window or you can
press the Tools | Profiling | Report | Save... button from the GUI to
save the profile report in a file.
Note that profiling is only available when you use the simulator.
Support for OSEK RADM has been added. CrossView Pro has two additional command line options:
Within EDE choose: Project | Project Options... | CrossView Pro | RTOS Aware Debugging Module. Select OSEK and fill in the name of the ORTI file.
Copyright 2004 Altium BV