|
|
 |
 |
Changes and additions for PC-3000 Flash 2.0.1
1. PC-3000 Flash Reader firmware updating.
Attention!
Version 2.0. requires modification of firmware.
The version 2.0. works incorrectly with the previous firmware.
The operation of reprogramming will be executed at the first use of the device.
It's prohibited to disconnect the USB cable in the process of programming!
You need to follow exactly to the instructions in program.
Please, pay special attention to the recommendations of the program to disconnect and connect the device after updating.
2. Speed increase of performing operations.
Absolutely new ideology is realized in PC-3000 Flash version 2.0.
It allows to:
- considerably increase the speed of performing operations
- optimize the usage of the system resources
- enlarge the possibilities of device, as in analysis so in task search.
The time for operations of prior preparation doesn't depend upon the type of operation, size and number of resources. Meanwhile, each created result occupies on the disk no more than 1 Mb.
3. Incompatibility of tasks.
Version 2.0. doesn't support the format of tasks from the previous versions because of the considerable changes. For the migration of tasks you need to create a new task and to use the download of dumps from external files.
4. Conception of memory chip viewing is changed.
- In version 2.0. the initial microchips can be presented in two ways:
— separated microchips (in case if each memory chip has 1 part)
— memory chip tree (in case if each memory chip has 2 or 4 parts).
Parent element of collection is a virtual chip of total size.
When you choose the operation "Read" for the element, the reading of all its parts will be done.
When you create the tasks, basing on the memory chips which are present, you need to indicate a total task capacity and the number of physical memory chips as in the previous versions. While reading each chip, the device automatically defines the number of parts and adds them in task.
If the task is created on the basis of dumps which had been read, so you also need to indicate the total capacity of task and the number of physical memory chips.
You need to use the menu "Add part" command in order to add a part in the chip. The operation which you apply to one chip will be applied to all chips of task. After this you need to download a damp which is appropriate to each part of chip task.
The given modification in the viewing allows to take into account the specific features of chip physical structure in task for the better qualitative decision making when task analysis is being executed. We recommend you form the structure of chip task as precisely as possible while you are creating the task from the earlier read dumps.
- Command "Read chip" is available in menu when the identification of memory chips combines "Read chip ID" and "Read chip". In a case, if you can't find ID in the base of PC-3000 Flash, you will see on the display a window for the input of reading parameters.
In version 2.0. each memory chip is an independent result and you can individually apply any of the search modes or of prior preparation.
5. Support for chips with the size of pages which are not multiple of 528.
In version 2.0. we implemented the support for chips with the size of pages are not multiple of 528 bytes. (The most of new chips rate to such kind).
The reading of similar chips is completely identical to reading standard chips and you can do it automatically.
6. Statistical error reading processing. Autoverification.
In version 2.0. we implemented control mode and reading error correction mode of unstably readable pages. Processing is performed with the use of statistical methods.
When you select the option, each page is read 2 times and when it detects a discrepancy between the results of reading, device performs multiple recalculation to determine the most probable value.
You can activate the mode using the proper flag of dialog box for selecting reading parameters of memory chips. We recommend you to use this mode when you read chips, because it allows to correct a significant number of errors, thereby increases the reliability and quality of restored data.
The mode is enabled on default. The number of attempts to read can be changed arbitrarily. (The number of attempts is equal to 3 on default.). You should remember that the great values of the parameter will lead to a significant slowdown in the process of reading.
Information on the ratio of detecting and correcting errors is displayed in the protocol on the completion of reading. Managing the switch of protocol detailing, you can observe the way of correcting errors during the process of reading.
7. Representation of read data.
In version 2.0. we brought about the possibility to evaluate visually the correctness of the data during the process of reading. To activate the possibility you need to increase the detailing of the protocol.
The extracts from read data are derived into the protocol 3 times per second. During the time between the inputs, the software executes control on the availability of page which is filled with data is not equal to "all 0xFF".
This mode allows you to evaluate the availability of useful data on the memory chip while you are reading.
8. Conversion graph.
In version 2.0. we implemented a new idea of the prior preparation chronology. operations and results are combined in "Conversion graph" (from the graph. - somehow interconnected sequence of elements).
Each line represents an elementary operation of prior preparation. The name of the appropriate operation and its parameters are indicated on the right side of the line.
The collection of results which you get at the end of this operation (or a synonym - at this step) is represented on that line like separated rectangles. Ideologically each rectangle is the result of prior preparation.
The conversion graph represents the symmetry of operations executed under all chips of task. It emulates a similar process of data distribution when controller works normally. The use of easy-to-understand visual presentation helps you to study the task mush easier, and it also simplifies and avoids errors in performing the same operation when you have to deal with a larger number of chips.
The conversion graph dynamically adjusts itself when you add any operation in any place of it (in the middle, to the end, or beginning) at any operation. I. e. when you add for example, "inversion", in the middle of already existing operations, all the following lines "take into account" this additional operation.
You can run all the available methods of investigation and prior preparation at any line of the conversion graph. In the case if one result presents in the line, you can run the Autodetection method and directly apply this method to this line.
The operations of the prior preparation, methods of search, analysis algorithms are applied to the line entirely. I.e. you apply them to all results which are on the selected line. If the operation involves the participation of 2 initial results, so this operation will be applied to each successive pair of results at the selected line.
It is possible to move results in the line limits in order to change the order in which they appear in subsequent transformations. You can do this displacement of results in the line using "Move to the right" and "Move to the left" commands which are taken from the context menu, one from results of line.
You can use memory chips as sources to build up conversion graph as well as any other number of results of prior preparation.
To do this, you need to highlight either the desired outcome of prior preparation or node "memory chips" and execute "Add conversion graph".
The same set of sources can be the basis for several conversion graphs.
9. Simultaneous viewing of two results.
In the framework of "Conversion graph" mode we brought about the possibility of simultaneous viewing of two results. To do so, you should hold down "Ctrl" and highlight the desired results on the line using the right mouse button and execute the "Service data for selected pair" command of menu.
The window of the mode is a dual synchronous "Service data" mode for selected results. In this mode you can use:
- Editor of sector;
- Simultaneous viewing of service data and the content of sectors;
- Go to any of the 2 results in order to search;
- "Map" mode.
Mode is very useful to determine visually the sequence of the operations of prior preparation for studying the principles of data distribution within chips of task. Especially, in a case when you have a great number of initial chips or intermediate results.
10. Additions in methods of prior preparation (Changing the page format).
We added "Change the page format" method of prior preparation. The goal of method is to make the page which is not multiple of 528 bytes to the standard sector size, i.e. 512 bytes of user data + 16 bytes of service data.
In most cases the increase of page size is conditioned by the need to increase the service area. Because flash memory drive uses standard file systems and user data area which must be multiple by sector, i.e. 512 bytes. Error correction codes (ECC) occupy the largest part of the service data.
The described method of prior preparation converts the sector to the standard type exactly in expenses of "cutting" nonexistent part of the service data. After the execution of the operation, the given result has a modified sector. After this the sector is available for study and data recovery.
The parameters of the method:
- Frequency (the frequency interval). i.e. the minimum amount of data which periodically repeats during the dump. Usually, it is equal to the size of page of memory chip.
- Structure. It describes the distribution of data in the frequency interval in the following format:
If the interval is composed of several sectors, they are described one after another.
Each sector consists of:
Area of user data - the total size of 512 bytes,
+ Area of service data - the total size of 16 bytes.
Each area may consist of arbitrary number of elements. Element is described in following way:
The offset in the frequency interval - the size of data;
Symbols "-" between the offset and size, and ";" at the end of the described element - are binding.
For example, the standard representation of sector, i.e. 512 +16 will look:
— Frequency: 528
— Structure :0-512, 512-16;
The structure of the sector 2048 +64 may be modified to the standard when you use following transformation:
— Frequency: 2112
— Structure: 0-512, 2048-16, 512-512, 2064-16, 1024-512, 2080-16, 1536-512, 2096-16;
There are two available and the most frequent conversions to select. We also brought about the possibility of their own conversion on the basis of their own descriptions of the data sector structure.
11. Additions in interface.
- When you conduct methods of research which are long enough, you are allowed to skip the current method, if there is confidence that it will not give a positive result, you can move to the next one.
To execute this operation, click "Skip" on the toolbar of process.
- We added two functional buttons: "Invert" and "Order of Bytes" in " Service information" modes and "Search GREP" on the control panel.
The buttons determine the mode of result representation.
When you hold the buttons in "Search GREP" mode, the search will be carried out simultaneously in the initial result and the result which is transformed accordingly.
If "Inversion" button is pressed, then the search will take place in the inverted and in direct results.
The same principle is applied to "Order of Bytes" button. When you hold the button, the result is presented in the view when the neighboring bytes are reversed. You search the initial result and changed result at the same time.
12. Adding a translator.
We added possibility to add translation table based on any of the results of the prior preparation, thus we artificially created "Logical drive" result.
This mode is useful if you have found a translation table in the tested result for building up a bank, but an algorithm for decoding it is absent or table is damaged. Thus you need to make the necessary adjustments manually.
Also in the case if algorithm is unknown, but you defined the sequence of blocks during the process. You use this mode to form own translation table and get the image of the initial disk.
If you need to add a translator it is necessary to mark the desired result (if you need to add to the node "memory chips", you should execute prior preparation method - "Copy into the results of the processing"), and run "Add translator" command of context menu. Several tables can be set up for each source.
When you create a translation table you should indicate the following parameters:
- Block size (in sectors). Size of block in the current result. You can apply "Detection the size of block" search method in order to determine.
- The number of banks. This parameter determines the number of blocks in each bank i.e. size of bank in the blocks will be equal to = (the size of results / number of banks) / block size;
The limits of banks are calculated while the translator is being created on the basis of these data. The limits are not modified for the given translator in the future.
Translation table is a combination of edited cells, each of them is addressing an array of data. The array is equal to the size of block. The value of each cell can be arbitrarily changed.
In version 2.0. table, you can:
- Do full load from files,
- Use the initial result as a source of sector,
- Form manually.
13. Added algorithms.
We added the algorithm for controllers iCreate i5128-LG ( "Translator Type 8"). It is available in the "Translator" group. We also implemented special mode of aoutodetection of parameters for the algorithm.
We implemented the algorithm for controllers SM325QF AB ( "Translator Type 9"). It is available in the "Translator". We built in special mode of auotodetection of parameters for the algorithm.
14. Autodetection of algorithm's parameters.
In addition to already existing modes, we realized the autodetection of the parameters in the algorithms:
- Translator Type 8
- Translator Type 9
If you have a flag "Define parameters automatically" activated, so the analysis and an attempt to identify the necessary parameters will be brought about. If you can't move it to the protocol, the relevant information about possible alternatives or issues will be displayed.
15. Recovery via controller.
We added support of the following new controllers:
- AU6980 C41-GDL-NP A660859-100 06421C1
- AU6982 E41-GHL-NP A689858-1F 0724
- AU6982 E41-GHL-NP A690466-11F 0745
- CBM2080 B35419-20
- CBM2090 B81791-12E
- CHIPSBANK 874712-04E
- OTI002168 AVJ0478N. 10448C
- SM262A AC A20744 0428 G2A
- SM262A AC A21570 0422 G2A
- SM264AF AG P3C05.1 0728
- SM266BF AB B35790 0614 S7D
- SM268BF BB QN1385.1 0723 T7D
- SM268BF BB QS0074.1
- SM321DF BB H11497 0633 S8D
- SM324QF BC A95571 0815 S8T
- SM324QF BC A85239 0735
- SM324GF BC A93662 0-08
- U20TWG0D 0528 D1T8S-010GTFI
- U20TWG0D 0528 D1SWT-010GTFI
- UT163-L4 APD0170 J718 A1B
- UT163-L6 APD 0144 0717 A1B
- UT164-L4 APD0170 0718 A1B
- UT166 PAA020 0452FA A4
- UT166 PBC005 0509FA
- OTI 002168I-G BF271586.10550T
- FC1697 QF-9C A75070 0712
- FC1693-TC-AD P0SS9-010 0505
Complete version 2.0.1. of PC-3000 Flash is available now!
Attention!
Those users who have installed the beta version 2.0.1. must download and install the complete version 2.0.1!
The list of eliminated errors:
- the error of collecting information mode. This error in the previous version didn't allow to collect data in the task with the chips which consist of several parts.
- the bug that occurred when you used the built logical drive.
- incorrect display of last sector result.
Note:
- You need to start with the first empty memory chip task in order to do the loading of external dumps.
|
|
|
|
 |
|
|
|
|
