TaskLink 7.52

TaskLink for Windows Ver 7.52 is the latest update in the TaskLink architecture supporting FlashPAK, FLX500, ProLINE-RoadRunner, PS Series FlashCORE, PS Series Optima, Sprint, and UniFamily programmers. For the latest information on TaskLink, visit www.dataio.com.

Device Support Information:

For a list of new devices supported on Sprint programmers, go to www.dataio.com/ftp/device_lists/C2010.PDF

For a list of new devices supported on UniFamily programmers, see the UniFamily CD that shipped with your update.

For a list of all devices supported on Data I/O programming systems, g o to the Data I/O main Device Search on the Web.

# All Programmers:

- No changes to all programmers.

# What's New in FlashPAK:

- Corrected a problem (introduced in TaskLink V 7.50) that caused the Special Data sector to be enabled during a data file scan operation when the data file didn’t contain data for that sector.
- Corrected a problem (introduced in TaskLink V 7.50) in Motorola hex translators (82, 87, and 95) that caused data to be stored in the wrong address in programmer RAM if the I/O Offset was set to a value other than the default and the addresses in the data file were greater than 0x7FFFFFFF.
- Corrected a problem that resulted in a file translation error in FlashCORE systems running TaskLink version 7.50 or later. The problem occurred when three conditions existed simultaneously: the selected data format was not Absolute Binary; the data file did not contain an End of File record; and the data file did not contain data for the "special sector" at the end of the target device memory map. If these three conditions existed and automatic data file scanning was enabled, the special sector would be incorrectly programmed with zeros rather than left unprogrammed.

# What's New in FLX500:

- Corrected a problem (introduced in TaskLink V 7.50) that caused the Special Data sector to be enabled during a data file scan operation when the data file didn’t contain data for that sector.
- Corrected a problem (introduced in TaskLink V 7.50) in Motorola hex translators (82, 87, and 95) that caused data to be stored in the wrong address in programmer RAM if the I/O Offset was set to a value other than the default and the addresses in the data file were greater than 0x7FFFFFFF.
- Corrected a problem that resulted in a file translation error in FlashCORE systems running TaskLink version 7.50 or later. The problem occurred when three conditions existed simultaneously: the selected data format was not Absolute Binary; the data file did not contain an End of File record; and the data file did not contain data for the "special sector" at the end of the target device memory map. If these three conditions existed and automatic data file scanning was enabled, the special sector would be incorrectly programmed with zeros rather than left unprogrammed.

# What's New in ProLINE-RoadRunner:

- Corrected a problem (introduced in TaskLink V 7.50) that caused the Special Data sector to be enabled during a data file scan operation when the data file didn’t contain data for that sector.
- Corrected a problem (introduced in TaskLink V 7.50) in Motorola hex translators (82, 87, and 95) that caused data to be stored in the wrong address in programmer RAM if the I/O Offset was set to a value other than the default and the addresses in the data file were greater than 0x7FFFFFFF.
- Corrected a problem that resulted in a file translation error in FlashCORE systems running TaskLink version 7.50 or later. The problem occurred when three conditions existed simultaneously: the selected data format was not Absolute Binary; the data file did not contain an End of File record; and the data file did not contain data for the "special sector" at the end of the target device memory map. If these three conditions existed and automatic data file scanning was enabled, the special sector would be incorrectly programmed with zeros rather than left unprogrammed.

# What's New in PS Series FlashCORE:

- Corrected a problem (introduced in TaskLink V 7.50) that caused the Special Data sector to be enabled during a data file scan operation when the data file didn’t contain data for that sector.
- Corrected a problem (introduced in TaskLink V 7.50) in Motorola hex translators (82, 87, and 95) that caused data to be stored in the wrong address in programmer RAM if the I/O Offset was set to a value other than the default and the addresses in the data file were greater than 0x7FFFFFFF.
- Corrected a problem that resulted in a file translation error in FlashCORE systems running TaskLink version 7.50 or later. The problem occurred when three conditions existed simultaneously: the selected data format was not Absolute Binary; the data file did not contain an End of File record; and the data file did not contain data for the "special sector" at the end of the target device memory map. If these three conditions existed and automatic data file scanning was enabled, the special sector would be incorrectly programmed with zeros rather than left unprogrammed.
- Added a feature to allow continued downloading of a job in the case where the available free storage space on the programmer may not be adequate (i.e., free space is less than the size of the device being programmed). A warning message (enabled on the System > Options > General tab) is displayed indicating this situation.
- Corrected a problem that prevented the “Help” button on the Task Manager dialog from opening the associated Help topic.

# What's New in PS Series Optima:

- No changes.

# What's New in Sprint:

- No changes.

# What's New in UniFamily:

- No changes.