ZDS II - Z8 Encore! Family 4.11.0 (Build 08052301) ============================================================================== Thank you for purchasing a Zilog Z8 Encore! family development kit. The following features are provided in this release: - Z8 Encore! language tools including C compiler, assembler, linker/locator, and librarian - Instruction set simulator and disassembler - Zilog Standard Library (ZSL) - In-Circuit Z8 Encore! Flash MCU debugger and programmer - USB Smart Cable, Ethernet Smart Cable, and Serial Smart Cable support The technical documentation supplied on this CD-ROM is available in PDF format. This format requires that Acrobat Reader or equivalent be installed on the host machine. Acrobat Reader is available on this CD-ROM and is available free on the Adobe website at www.adobe.com. In the event of a component problem, please complete the Problem Report Form and submit it with your request. The form is located on the CD and in the installation directory of your hard drive. Our staff will use the information to diagnose or log the problem. Contact Information -------------------------------------------------------------------------- Zilog Inc. Web Site: http://www.Zilog.com Technical Support Channel: http://support.Zilog.com Table of Contents -------------------------------------------------------------------------- A. Changes from Previous Releases B. Compatibility C. System Requirements D. Applications and Other OS issues E. Precautions and Limitations F. Closed Change Requests G. Open Change Requests A. CHANGES FROM PREVIOUS RELEASES ============================================================================== Refer to the 'Migrating from a Previous Release' section of the FAQ for information and pointers related to migrating/converting ZDS projects and targets from releases prior to version 4.10.0. (to 4.11.0) - Removed the support for the Z8F640K CPU family. - Product Re-Grouping: Old Series New Series ---------------------------------------------------------------- Z8Encore_XP_F0830_Series Z8Encore!_F0830_Series Z8Encore_XP_F083A_Series Z8Encore!_F083A_Series Z8Encore_F0823_Series Z8Encore!_XP_F0823_Series Z8Encore_4K_Series Z8Encore!_XP_F0823_Series Z8Encore_F0823_8Pin_Series Z8Encore!_XP_F0823_8Pin_Series Z8Encore_4K_8Pin_Series Z8Encore!_XP_F0823_8Pin_Series Z8Encore_XP_F08XA_Series Z8Encore!_XP_F082A_Series Z8Encore_XP_4K_Series Z8Encore!_XP_F082A_Series Z8Encore_XP_F08XA_8Pin_Series Z8Encore!_XP_F082A_8Pin_Series Z8Encore_XP_4K_8Pin_Series Z8Encore!_XP_F082A_8Pin_Series Z8Encore_8K_Series Z8Encore!_XP_F0822_Series Z8Encore_64K_Series Z8Encore!_XP_F64XX_Series - Added a compiler option to pass parameters in registers for improved code efficiency. - Compiler error and warning messages have been improved. This may lead to new warnings being reported in projects that previously built without warnings. We recommend that you investigate any new warnings in your projects, as they may be indicating potential problem areas in your code. - Added a new "_monitor" function type to support development of RTOS systems using the Encore processors. - Included updated documents. - Change Requests have been addressed. Refer to the Closed Change Requests section for more details. - Added support for Z8F642/Z8F322 devices - Added support for Z8F082A and Z8F0823 CPU families rev CA silicon - Removed the support for the following Z8F1680 devices: Z8F2481xx, Z8F1681xx, and Z8F0881xx - Included updated documents - Added USB Smart Cable support for Vista 64bit machines. Note: The default installation for Vista 64bit is: C:\Program Files(x86)\ZiLOG\ (to 4.10.1) - Added preliminary support for the Z8 Encore! XP F1680 series of parts. - Added option to use page-erase before programming flash during debugger downloads (Project > Settings > Debugger tab > User page-erase before flashing). - Pre-4.10.0 'uartcode' application source code is now available at \applications\Z8Encore!_uartcode. - Support for structures in assembly code has been added. See the new section "Structures and Unions in Assembly Code" in the ZDS II User Manual for details. - Added script commands: FillMem, SaveMem and LoadMem (CR 9043) - Change Requests have been addressed. Refer to the Closed Change Requests section for more details. B. COMPATIBILITY ============================================================================== Devices -------------------------------------------------------------------------- Z8 Encore! F0830 Series: Z8F013x, Z8F023x, Z8F043x, Z8F083x, Z8F123x Z8 Encore! F083A Series: Z8F043A, Z8F083A Z8 Encore! XP F082A Series: Z8F082A, Z8F042A, Z8F022A, Z8F012A Z8F081A, Z8F041A, Z8F021A, Z8F011A 8-pin*: Z8F082AXB, Z8F042AXB, Z8F022AXB, Z8F012AXB Z8F081AXB, Z8F041AXB, Z8F021AXB, Z8F011AXB Z8 Encore! XP F0823 Series: Z8F0823, Z8F0423, Z8F0223, Z8F0123 Z8F0813, Z8F0413, Z8F0213, Z8F0113 8-pin*: Z8F0823XB, Z8F0423XB, Z8F0223XB, Z8F0123XB Z8F0813XB, Z8F0413XB, Z8F0213XB, Z8F0113XB Z8 Encore! XP F0822 Series: Z8F0822, Z8F0812, Z8F0422, Z8F412 Z8F0821, Z8F0811, Z8F0421, Z8F411 Z8 Encore! XP F64XX Series: Z8F6423, Z8F4823 Z8F6422, Z8F4822, Z8F3222, Z8F2422, Z8F1622 Z8F6421, Z8F4821, Z8F3221, Z8F2421, Z8F1621 Z8 Encore! XP F1680 Series 8K*: Z8F0880 Z8 Encore! XP F1680 Series 16K*: Z8F1680 Z8 Encore! XP F1680 Series 24K*: Z8F2480 Z8 Encore! MC Series*: Z8FMC16100, Z8FMC08100, Z8FMC04100 Z8 Encore! 640 Family: Not Supported. Please use Ver: 4.10.1 *Requires USB Smart Cable, Opto-Isolated USB Smart Cable, or Ethernet Smart Cable Please refer to the Project>Settings>General>CPU selection for the latest supported devices. In-Circuit Debuggers/Programmers -------------------------------------------------------------------------- USB Smart Cable, version 1.0 or later: ~ Supports target frequencies from 32KHz to 20MHz ~ Supports target voltages from 2.7V to 3.6V ~ Requires 2mA from the target Opto-Isolated USB Smart Cable, version 1.3: ~ Supports target frequencies from 32KHz to 20MHz ~ Supports target voltages from 2.7V to 3.6V ~ Requires 2mA from the target Ethernet Smart Cable, version 1.0 or later: ~ Supports target frequencies from 32KHz to 20MHz ~ Supports target voltages from 2.7V to 3.6V ~ Requires 2mA from the target Serial Smart Cable for Z8 Encore!, version 6.04.03 or later: ~ Supports target frequencies from 153.6KHz to 20MHz ~ Supports target voltages from 3.0V to 3.6V ~ Requires 35mA at 3.3V from the target USB device drivers and installation instructions can be found in the following locations: \device drivers\USB\ The firmware and upgrade instructions can be found in the following directory: \bin\firmware\ Please visit Zilog's website for latest versions. http://www.zilog.com/software/zds2.asp C. SYSTEM REQUIREMENTS ============================================================================== Supported Operating Systems -------------------------------------------------------------------------- Windows Vista Business, XP Professional, Windows 2000 SP4, Windows 98 Se Recommended Host System Configuration -------------------------------------------------------------------------- Windows XP Professional Pentium III 500MHz processor or higher 128 MB RAM or more 135 MB hard disk space (includes Application and Documentation) Super VGA Video Adapter CD-ROM for installation USB High-Speed port (when using USB Smart Cable) RS232 communication port with hardware flow control Internet browser (Internet Explorer or Netscape) Minimum Host System Configuration -------------------------------------------------------------------------- Windows 98 Se Pentium II 233MHz processor 96 MB RAM 35 MB hard disk space (only includes Application) Super VGA Video Adapter CD-ROM for installation USB Full-Speed port (when using USB Smart Cable; Windows 98 Se only) RS232 communication port with hardware flow control Internet browser (Internet Explorer or Netscape) USB Smart Cable -------------------------------------------------------------------------- Hi-Speed USB (Fully compatible with Original USB) Root (direct) or self-powered hub connection *The USB Smart Cable is a high power USB device Opto-Isolated USB Smart Cable -------------------------------------------------------------------------- Hi-Speed USB (Fully compatible with Original USB) Root (direct) or self-powered hub connection *The USB Smart Cable is a high power USB device Ethernet Smart Cable -------------------------------------------------------------------------- Ethernet 10Base-T compatible connection Serial Smart Cable for Z8 Encore! -------------------------------------------------------------------------- RS232 Communication port with hardware flow and modem control signals *Some USB to RS232 devices are not compatible because they lack the necessary hardware signals and/or they use proprietary auto-sensing mechanisms which prevent the Smart Cable from connecting. D. APPLICATION AND OTHER OS ISSUES ============================================================================== 1. Apply the latest Windows updates to the host system when appropriate. 2. ZDS II will terminate an active target connection when the host goes into Stand by or Hibernate. 3. Some systems with one or more other USB devices connected may not boot properly after connecting the USB Smart Cable. Workaround: Connect the USB Smart Cable after the system has started. E. PRECAUTIONS AND LIMITATIONS ============================================================================== Debugger & Programmer -------------------------------------------------------------------------- 1. The Debugger's memory window for RData shows internal Data Memory range 0-Edata limit of selected device. 2. The Z8F08200100KITG and Z8F64200100KITG development boards are shipped with a 18.432MHz clock which requires the host to communicate with it at a rate greater than 36Kbit/s. The minimum and maximum target communication frequencies are determined by MIN = Fsysclk / 512 and MAX = Fsysclk / 8. For more information about OCD Auto-Baud limits, please refer to the "On-Chip Debugger" section in the Z8 Encore! device's product specification. 3. Selecting "No" when prompted with the flash option bit write warning during a code memory fill operation does not stop the operation. 4. The Watch Dog Timer (WDT) must be disabled when in run mode or executing code. The WDT will cause the processor to perform a reset and the debug mode will not be enabled upon reset. Therefore the debugger will lose control of the processor. 5. The STOP command is not supported by ZDS II. The ZDB interface utilizes the internal clock to communicate with the processor and this command causes the internal clock to stop terminating communication with ZDS II. See FAQ "Why does the debugger exit STOP mode without the occurrence of STOP mode recovery event?" for additional information. 6. If the target device system clock frequency is designed to change during program execution, the matching configuration should be assigned in the Setup Target dialog prior to the target connection. Otherwise target communication may be lost during program execution. 7. -Purposedly deleted - 8. When using the RS232 Smart Cable, a connection attempt may fail if the previous attempt was made with an invalid communication rate. 9. The debugger does not support arrays with more then 6 dimensions. 10. When using the USB or Ethernet Smart Cable with the Z8 Encore! XP F042A development kit (Z8F04A28100KIT) or the Z8 Encore! XP F082A development kit (Z8F08A28100KIT) board revisions A and B, apply the following hardware changes: a. Solder a 10K resistor between pins 5 and 4 of U7 (LT1129) b. Solder a 15K resistor between pins 4 and 3 of U7 (LT1129) Otherwise, the target may not come out of reset and ZDS will fail to connect. When applying power to the XP F082A and F042A board with the USB or Ethernet Smart Cable connected to the DBG port, the 3.3V power LED will normally flicker (on then off). Performing a connect or reset in the IDE will power the board and illuminate the 3.3V LED. 11. ZDS may hang for a long period of time if the NVDS memory window is open during a debug session -- run-control operations and general user interface updates will be slow. If ZDS can not reestablish a connection because the NVDS window was open during the last debug session; change the target to Simulator, start a debug session, and close the NVDS window. 12. When Debugging user NVDS memory read/write functions it is important not to issue an asynchronous break request that interrupts the read/write function while in Run Mode. The debugger can not tell if the read/write operation is complete. For write operation a break request may interrupt the NVDS erase-write cycle. If the internal read/write operation is interrupted before completion, the NVDS may be erased and all NVDS data may be lost. 13. The USB Smart Cable is required to implement the following unique connection procedure for the Z8 Encore! XP 8-pin device: 1. Assert the Reset line 2. Send a key on the DBG line to unlock the debug mode 3. Start a break condition on the DBG line 4. Release the Reset line 5. Stop the break condition 6. Initialize the target and continue normal debug operations The reset line will be released at the end of this procedure even if the target initialization fails. The target initialization will fail if the Smart Cable is not physically connected or the or power is not supplied to the target. Cycle the target power if the target is not in reset, debug mode, or failed to initialize prior to starting this procedure. The USB Smart Cable will assert the Reset line if it detects a target power loss. 14. The Serial Smart Cable may not be able to communicate with a target at baud rates of 19200 and less. Use a baud rate greater than 19200. 15. If the Serial Smart Cable is used for debugging, ZDS will enable and select the target's system clock source after performing a reset. If the USB Smart Cable is used for debugging, ZDS will not attempt to change the target's system clock source after performing a reset. The Project>Settings>Debugger>Setup>Clock information may be used at build time and will be referenced during a debug session. 16. Debugging or programming a device that uses the external clock signal (CLKIN) option is not supported when using the Serial Smart Cable. As a workaround, apply the external clock signal to the XIN pin or use the USB Smart Cable. The Serial Smart Cable is not compatible with a Z8 Encore! XP derivative target system that uses CLKIN system clock source because ZDS is not aware of the Z8 Encore! XP CLKIN option and, with the serial (TIM and Smart Cable), attempts to select the system clock source. As a workaround the user may apply the external clock source to the XIN pin instead of the CLKIN pin and operate ZDS as if the target was using an external crystal like one would with the other Z8 Encore! devices. This will allow ZDS to select a “functioning” clock source. Another workaround would be to use the USB Smart Cable because ZDS with the USB Smart Cable won’t enable and select the system clock source. 17. The Z8 Encore! XP F082A and F0823 series 8-pin samples target the simulator and may be used on actual hardware. The Z8 Encore! XP F042A series 8-pin development kit (PN: Z8F04A08100KIT) and its sample project may be used to evaluate the Z8 Encore! XP F082A and F0823 series 8-pin development environment. A project that targets the Z8 Encore! XP F082A or F0823 8-pin device may be used with Z8 Encore! XP F042A 8-pin development kit board but the device feature limitations such as reduced program space will apply. 18. The simulator does not support UART input. 19. The simulator treats halt/sleep instruction as a NOP. 20. ZDS opens a UDP port to search for Ethernet Smart Cables and should be allowed to do so through an active firewall that stands between ZDS and the Ethernet Smart Cable. The firewall may be disabled or configured to grant ZDS the right to open a local UDP port. The local port number is assigned by the host and the foreign port number is 3000. 21. The USB and Ethernet Smart Cables will hold the reset line low if it detects a target power loss. If you need to test the Power On Reset circuit, first disconnect the debug tool from your target and then apply power. 22. Page Erase of internal Flash memory is used as the default to protect user data or programs (i.e. Boot Loaders) in Flash. The user can select mass erase by removing the check mark from the Project > Settings > Debugger tab "Use Page Erase Before Flashing". When Page Erase is selected, note that the debugger will erase all pages within the program's address range prior to programming Flash. The address range is determined by the lowest and highest addresses contained in the .LOD file and those pages and all the pages in between are erased in one step to speed the download process. If the program overlaps a page by a single byte the entire page will be erased. (i.e. For ROM Address Range: 0-38, 8000-FF00, the .LOD download will erase the Flash from 0-FFFF). The Flash Loader can be used if you need to download non-overlapping .HEX files in non-sequential order because the ZDS linker will sort the addresses when the file is created and the Flash Loader can then determine the exact pages to erase. (i.e. For ROM Address Range: 0-38, 8000-FF00 the .HEX download will erase 0-1FF (entire page) and 8000-FFFF). 23. Flash option bits cannot be modified via the Special Function Registers debug window. Please use the Rom Memory Window to change option bits. 24. Due to CPU Families re-grouping, opening projects from previous versions may result to errors due to missing target. Please select or create a new target as a work-around. Compiler, Assembler, Linker/Locator, & Librarian -------------------------------------------------------------------------- 1. The compiler now disallows declaring functions near or far. This usage was previously allowed when static frames were in use, but was never properly supported and its use has not been recommended for some time. A review of the status of this feature found that the unresolved implementation and testing issues surrounding the feature are such that it is best to remove it from the supported compiler interface at this time. Run-Time Library -------------------------------------------------------------------------- 1. The Zilog default startup files startups.asm and startupl.asm have been modified to allow user code to begin at an arbitrary origin (because it can now be located independently of the interrupt vectors). In general, users can continue to use these startup files without any impact from the modifications, because the linker places the start of user code at a safe location. Any user who wishes to ensure that his user code begins at a specific address should use the LOCATE linker directive to do so. For example, to locate the startup at 38H, add the following in Project->Settings->Linker->Input->Add Directives: locate startup at $38 2. In release 4.10.0, the C standard library typedef size_t was redefined to be of type int, no matter which memory model is in use. In earlier releases, size_t was defined to be char in the small model and int in the large model. Because of the importance and ubiquity of size_t in standard library functions, this caused a variety of subtle bugs. Because of this change, modules and libraries built with pre-4.10.0 releases of the tools will not be compatible with code that is compiled using 4.10.0 or later. Specifically, if your application uses the small model and calls any functions (such as many of the standard library functions) that pass or return a size_t value, the code will not interoperate correctly with older libraries or modules. It is recommended that you rebuild all parts of your application with the 4.10.0 or later tools. IDE -------------------------------------------------------------------------- 1. Options available via Project > Settings... have been reworked for more efficient and correct use. Note that some options that existed in the multiple settings tabs have been moved to the General tab, most notably Generate Debug Information. Refer to the ZDS User Manual, Online Help and FAQ for assistance. 2. The Simulator is now a Debug Tool option, where previously it was a target. This allows the Simulator to better operate more correctly by using target configuration settings. 3. If Tools > Options > General tab > Always rebuild after configuration activated is not enabled but both the previous and new active configurations use the same location for the Project > Settings > General tab > Intermediate Files Directory option, the first build after selecting the new configuration will result in the reprocessing of all of the project’s source files (a rebuild). 4. The Motorola S-record format is not supported. Utilities exist to convert files to the S-Record format from one or more of the formats supported by ZDS II. These may be acquired via the Internet using an Internet search site such as Yahoo or Google. ZSL -------------------------------------------------------------------------- 1. The following device series are not supported by ZSL: - Z8 Encore! F0830 Series - Z8 Encore! F083A Series Target Hardware -------------------------------------------------------------------------- 1. Earlier builds of the Z8FMC160100KIT board may exhibit erratic operation when switching from IPO to external clock using ceramic resonator. This may be because C4 and C5 were populated. Remove capacitors C4 and C5 to avoid this behavior. F. CLOSED CHANGE REQUESTS ============================================================================== IDE -------------------------------------------------------------------------- (Fixed in 4.11.0) CR 10693 Toolbars are not restored properly after each ZDS session. CR 10012 FLASH BURN REPEAT command does not querry for next device in the command processor. CR 9780 Error when connecting to the target for the first time with USB FW 1.6. CR 9476 Added support for the F4 locating error feature that exists in Visual Studio 6. CR 2720 Some Assembly instructions are not syntax-hightlighted in the source window. CR 1496 Symbol Window does not correspond with the map file. CR 11869 Added support for Z8F082A CPU Family rev CA Assembler -------------------------------------------------------------------------- (Fixed in 4.11.0) CR 8058 Assembler crashes if length of include path is over 1024 characters. CR 6976 If no file is provided after a .debug "C" statement, assembler reports internal error. Compiler -------------------------------------------------------------------------- (Fixed in 4.11.0) CR 11476 Internal error reported when comparing sizeof a struct to a constant. CR 11364 For the following statement: *gptr() = 0x12; Function gptr is called twice. CR 11130 The compiler generates internal error in small model for statements like: "if (bmout & *pOut)" where both the operands to & are char. CR 11057 P1 internal error when an enum definition comes after at least one function definition has already occurred. CR 11022 P2 internal error when explicitly comparing the address of a struct member to 0, as in "if (&str->member == 0)". CR 10982 Internal error reported for certain invalid initialization statements. CR 10756 P2 internal error for a particular combination of case and printf statements. CR 10697 Internal error on accessing structure members through near structure pointer in large model. CR 10496 Debugger reports "Illegal address prefix specified" due to compiler not creating proper debug information for certain functions taking char* arguments. CR 10495 Object file grows larger when debug is NOT selected, due to configuration file calling for assembly level debug info. CR 10075 Compiler improperly optimizes out read of the volatile variable i in this code: if (i){} -- ONLY when the body between the {} braces is blank. CR 10063 Overly aggressive optimization due to optimizer not recognizing that volatile variables may be updated in function calls. CR 9997 Compiler hangs when compiling a switch-case for which the default case is an empty while(1) loop. CR 9966 Overly aggressive optimization removing pre-increment of variable in complex conditional expression. CR 9961 Overly aggressive optimization removing an instance of dereferencing a volatile pointer. CR 9871 P2 internal error results when there are multiple named aliases of pointer variables used in a context that expects an address. CR 9772 Character arays with explicit size are supposed to be initializable by a string literal with exactly that many characters, the \0 being quietly squeezed out. CR 9654 The .lis file should be placed in the Intermediate Files Directory rather than the associated source file's directory. CR 9445 Request: Add #warning directive, which will continue build and link as opposed to #error. CR 9390 Case labels sometimes being incorrectly treated as signed values. CR 9376 Structure member not updated correctly when its offset is > 256 bytes and it is both read and written in the same line of C code. CR 9374 Casting an address to long in global data initialization does not work. CR 9332 Optimization request: struct member which is a function pointer is unnecessarily reloaded if used on successive lines. CR 9186 Read of a volatile improperly optimized away when it is associated only with an unnamed temporary, as in the expression (*(unsigned char volatile near *)0xE260. CR 8966 Internal error in a particular case where a preprocessor constant is passed as a function argument. CR 8775 Overly aggressive optimizing away of loops when global variable is used as the loop index. CR 8713 Optimization request: inefficient code when using exclusive OR to do bitwise toggling of a byte-sized bit-field structure. CR 8689 Incorrect conversions of large floating-point constants to integers when signed long integer overflow occurs. CR 8627 The map file displays useless information for CALL GRAPH when dynamic frames are in use. CR 8555 Internal error on for loop whose body is unreachable due to the test condition in the for(;;) expression. CR 8503 Compiler doesn't always optimize additions of ascii char constants with numeric constants, such as 'A' + 10. CR 8467 The compiler does not allow declaring a pointer to reentrant function in certain cases. CR 8393 Read of a volatile peripheral control register optimized out when the value read is not used later in the function. CR 8048 Optimization request: allow a "non-ANSI multiply", multiplying two chars to get an int result, to use the Encore's MULT instruction for greater efficiency. CR 8047 Optimization request: add more "code helpers" to carry out commonly used tasks. CR 8041 Over-aggressive optimization in some cases for nested if statements. CR 7958 Optimization request: add option to pass parameters in registers. CR 7081 Compiler does not handle mixed bit-field types in a single structure. CR 6281 Compiler reports internal error when length of user include path exceeds 2000 characters. CR 5174 Declaring a function with the return type repeated twice (e.g., "int int foo()") generates no errors. CR 3899 Compiler should issue a warning when it sees an extern with no storage class to define the expected type. CR 2220 Feature request: add a "monitor" function type to support RTOS development. CR 1805 Enum initializer value which uses sizeof gives garbage initialization. Librarian -------------------------------------------------------------------------- (Fixed in 4.11.0) CR 4690 The librarian fails when given a command line longer than 16K characters, due to many modules with long path names. Linker -------------------------------------------------------------------------- (Fixed in 4.11.0) CR 10040 "Illegal address prefix specified", related to newly fixed compiler CR 10496. CR 4896 Linker should give warning message when RAM initialization actually tries to initialize variables in flash. Run-Time Libraries -------------------------------------------------------------------------- (Fixed in 4.11.0) CR 10383 TEMPCALL and TEMPCALH register names are not supported on Z8F1680. CR 9270 Sprintf formatted output is sometimes not printing the correct number of digits after the decimal point. CR 8456 The assert macro calls the function fprintf, which is not included in the library. G. OPEN CHANGE REQUESTS ============================================================================== IDE -------------------------------------------------------------------------- CR 7918 During the loading of large projects (those with a large number of files and/or file dependencies), the ZDS user interface may become non-responsive. CR 5519 External dependencies generation/display ignores project preprocessor defines. CR 5517 Unable to watch large EQU symbols on the watch window. CR 4431 IDE will not provide a warning that the hex code file is larger than the project device size when using Load from File on the code memory window. CR 3852 In assembly files, the ".r" or ".rr" designators are not correctly chroma coded. CR 3711 Hex files that use \r as a line ender are not supported. CR 3210 Local watch window does not display negative values CR 2731 When the program is running in the debugger, the program counter indicator (yellow arrow) is still displayed at previous location. CR 1650 After single-stepping through a function call, the program counter indicator returns to the calling line instead of the next executable line. CR 1638 Customized workspace not restored properly. Appears to be reset when application restarted. CR 1397 Double-clicking on the error sometimes places the cursor in the incorrect location. CR 1177 Resizing the debug windows is difficult and behaves inconsistently. Assembler -------------------------------------------------------------------------- CR 11760 SCOPE directive doesn't work properly on forward-referenced labels (those which are defined later in the program).