|
Release notes CHIPTOOL V4.0.1.8 |
| Here are the release notes of the CHIPTOOL version above. This document lists all modifications, additional features and bugfixes of the current CHIPTOOL version since our last release. The list is sorted by our internal change request numbers "CR Number" and by the "Type" of the change request. We defined three different types of change request: "Defect", "Suggestion" and "Checkup". "Checkup" means a necessary verification and possible improvement of a CHIPTOOL component. The report fields "Component" and "Category" are describing the affected parts of the CHIPTOOL. "Synopsis" and "Description" are used for description of the change request. |
| CR Number: | 879 | |
| Type: | Defect | |
| Component: | Network scan | |
| Category: | Ping option | |
| Synopsis: | Pinging IPC@CHIPs | |
| Description: | Activating the ping option at the network scan window can lead to a hangup of the CHIPTOOL application. | |
| Fix: | Fixed. The ping option was removed. From now on, it is possible to ping a selected IPc@CHIP by using the right mouse click pop menu of the network scan window. |
| CR Number: | 872 | |
| Type: | Defect | |
| Component: | Software update | |
| Category: | Checksum method for serial software updates | |
| Synopsis: | Checksum method must be improved | |
| Description: | The current checksum method is not safe enough. This can lead to undetected incorrect programmed flash images of IPC@CHIPs. We should use CRC16 checksum method instead. |
|
| Fix: | Implemented. CHIPTOOL is able to use old checksum method or CRC16, depending on the bootloader version of the target IPC@CHIP. The bootlader version ,which supports both checksum methods (CRC16 and old checksum method) is V2.24. |
| CR Number: | 189 | |
| Type: | Suggestion | |
| Component: | Command line options | |
| Category: | ||
| Synopsis: | Command line options | |
| Description: | It should be possible to execute direct the following CHIPTOOL features by using command line options: 1. Program flash by serial interface 2. Program flash by TCP/IP UDP 3. Read flash image 4. Program user product data 5. IP configuration |
|
| Fix: | Implemented See CHIPTOOL windows helpfile for more details. |
| CR Number: | 695 | |
| Type: | Suggestion | |
| Component: | Documentation | |
| Category: | CHIPTOOL Help | |
| Synopsis: | Extend the CHIPTOOL Help | |
| Description: | The windows helpfile should describe all features of Chiptool. | |
| Fix: | Implemented: Windows Help-documentation describes now all CHIPTOOL features. |
| CR Number: | 878 | |
| Type: | Suggestion | |
| Component: | Flash images | |
| Category: | Reading full flash images | |
| Synopsis: | Reading full flash images, including files | |
| Description: | Customers should be able to program their IPC@CHIP based products with a complete flash image, which contains the @CHIP-RTOS code and also the files of the flashdisk drive A:. For this purpose it is necessary to read flash image from a "master" IPC@CHIP. |
|
| Fix: | Implemented: Menuitem Flash | Read flash image provides the upload of a complete flash image via the serial RS232 interface.See CHIPTOOL help for more details. It is possible to reprogram other IPC@CHIPs with the uploaded image by usign menuitem Flash | Program flash |
| CR Number: | 876 | |
| Type: | Suggestion | |
| Component: | IP configuration | |
| Category: | User specific TCP/IP device interfaces | |
| Synopsis: | Configuration of User specific TCP/IP device interfaces | |
| Description: | At older CHIPTOOL versions and SC12 @CHIP-RTOS equal or less V1.04 the IP configuration was only made for the default ethernet interface of the SC12. SC13 @CHIP V0.90 allows now the porgramming of own TCP/IP device driver. CHIPTOOL should support the IP configuration of such devices instead of the default ethernet controller. |
|
| Fix: | Implemented. CHIPTOOL supports now the IP configuration of such user programmed TCP/IP devices. See CHIPTOOL windows helpfile for more details. |
| CR Number: | 875 | |
| Type: | Suggestion | |
| Component: | Network scan | |
| Category: | IPC@CHIP detection | |
| Synopsis: | IPC@CHIP detection by serial number | |
| Description: | Because of the new IPC@CHIP products the serial number is no longer a unique key for that detecting IPC@CHIPs at the network. E.g. it can happen, that a IPC@CHIP variant SC13 has the same serial number as a SC12. In that case it is not possible to update the software of an IPC@CHIP over TCP/IP UDP by using the serial number at the "UDP config commands". The probability of such a conflict situation is very slight, but we it is necessary to add a new identify method for the "UDP config protocol". |
|
| Fix: | Implemented: From now on the worldwide unique 12 Byte MAC-Address of the internal ethernet controller can also be used at "UDP config commands" instead of the serial number. The old method (identify by serial number) is still supported, because of compatibility reasons. The UDP config server at SC13 RTOS V0.90, SC12 RTOS V1.10 will now return an extendend hello answer. The extensions are not visible at older CHIPTOOL versions.This extended hello answer contains now the additional informations (among others): Ethernet MAC-address as unique ID, RTOS version, Bootloader version, .... See CHIPTOOL help for other details. The scan window is moved to main window of CHIPTOOL. The colum ! will display possible serial number or IP address conflicts. |
| CR Number: | 873 | |
| Type: | Suggestion | |
| Component: | Software update | |
| Category: | Intel-Hexfile format check | |
| Synopsis: | Avoid download of invalid or corrupted Intel hexfile images | |
| Description: | Before download a Intel Hexfile image to the IPC@CHIP target, CHIPTOOL should check, that the Intel-Hexfile has the correct format and corrrect line checksums. |
|
| Fix: | Implemented. A download of an Intel Hexfile is only possible, if the hexfile has the correct format and correct line checksums. |
| CR Number: | 874 | |
| Type: | Suggestion | |
| Component: | Software update | |
| Category: | Target detection | |
| Synopsis: | Required target detection for different IPC@CHIP targets | |
| Description: | Because of the creation of new IPC@CHIP products (e.g. SC11,SC13), it is necessary to add a target check, before downloading a software image to an IPC@CHIP target. E.g. It should be not possible to upgrade a IPC@CHIP SC13 with a SC12 @CHIP-RTOS version. |
|
| Fix: | Implemented for @CHIP-RTOS versions SC12 V1.10, SC11,SC13 V090 and Bootstraploader V2.24 or higher. Intel-Hexfiles of those version are generated with a target signature (SC12,SC13,..). Before downloading the image to the target, CHIPTOOL will check, if the target IPC@CHIP has the same target signature. Please note: These protection will not work for older CHIPTOOL versions,hexfiles (e.g.SC12 @CHIP-RTOS versions with less or equal V1.04) without such a signature. In those case, it is necessary to repeat the download with a correct @CHIP-RTOS version. |
| CR Number: | 877 | |
| Type: | Suggestion | |
| Component: | User product data | |
| Category: | Serial download of user product data | |
| Synopsis: | Serial download of user product data | |
| Description: | Since SC12 @CHIP-RTOS 1.10 , SC13 RTOS V0.90 we provide a special section of the flash memory of 192 bytes outside of the filesystem. The user is able to program these section with own non-volatile data (e,g, the serial number if his IPC@CHIP named product). CHIPTOOL should support the serail download of such data. |
|
| Fix: | Implemented: Under menu Flash | User product data the user is able to download via the serial interface a max. 192 byte binary file, which contains his data. See CHIPTOOL windows helpfile for more details. |