JTAG Manager 1.90 --------------------------- - added Removable Storage direct Read/Write feature. This is mixed to USB Read/Write page. To access Removable Storage, select "Removable Storage Device" as Source To work as before, with connected Phone to USB, select "USB Bootable Device" as Source. - fixed bug: when reading DISK partitions, parsed with emmc plugin, clicking STOP in the middle didn't work. Now can terminate read operation. - fixed internal bug which could lead to damaging the model names in resurrectors list - fixed bug in reset strategy in some cases when setting Reset Strategy manually - fixed text scrolling problem in logging windows JTAG Manager 1.89 --------------------------- - fixed bug which overwrote real text in first condition checkbox in packages main condition selection dialog (the one which appears when resurrection button is clicked and user is presented with available options) - fixed an issue for some UFS-based firehose loaders, which caused rejection of read commands due to invalid page size parameter on initialization stage Firmware 1.54 --------------------------- - fixed eMMC Erase: any erase (from JTAG Manager eMMC Read/Write page) were performed on User Area Partition, no matter what partition was selected in the JTAG Manager; JTAG Manager 1.88 --------------------------- - global CTRL+A shortcut is added to start eMMC Plugin - global CTRL+E shortcut is added to start Edit Package - Full revisision of Jtag Manager interface is performed. Some visual changes are implemented. - JTAG Manager now supports Windows 10 high-resolution screens (DPI settings from 100 to 300% were tested, and interface looks nice and smooth) - Added 'Recalculate GPT' action to Package (PKG) Manager. Starting from current JTAG Manager version, packages with this action can be created/executed - Added 'Erase Flash Memory via ISP/USB' action to Package (PKG) Manager. Starting from current JTAG Manager version, packages with this action can be created/executed - Added 'Reset USB Loader' action to Package (PKG) Manager. Starting from current JTAG Manager version, packages with this action can be created/executed - "Save to File" button on eMMC Read/Write and USB Read/Write is changed to "Show HEX" button when SHIFT key is pressed. "Show HEX" button will open hex window with data from previous read operations. - added feature to wait for Qualcomm Emergency Download Mode (EDL) when booting devices through this mode; - improved the box firmware update process. Firmware 1.53 --------------------------- - added support for eMMC HS200 speed mode (SD_CLK up to 200MHz) JTAG Manager 1.87 --------------------------- - eMMC Advanced Dialog: [eMMC Write Test] button is added This performs the operation to check if current eMMC is healthy and is not Write Blocked. - Direct button to start eMMC/UFS Plugin is added to Resurrection page - eMMC Advanced Dialog: [Write EXTCSD Reigster] button is functional now: this will write all writtable EXT_CSD fields to the eMMC. - eMMC Advanced Dialog width and height are now variable. User can adjust eMMC Advanced Dialog dimensions - some buttons on the eMMC Advanced Dialog are re-orginized in order to fit the dialog for the lower screen resolutions. - when connecting to eMMC Memory, health status is now displayed too - when connecting to eMMC Memory, 16-byte hex string value of CID and CSD registers is now displayed too - fixed package execution bug, which caused 6th and 7th condition (if present in PKG) to be executed no matter what was selected by user - improved USB booting of MTK devices for both DA types - DAs which report NAND size as 32-bit and DAs which report NAND size as 64-bit integers - USB Mode support for MT6575 is added - improved function of Open eMMC Info File button on the eMMC Advanced Actions form. Now selecting file type on Open File dialog will execute appropriate routine to load the file's contents depending on format of file Same is fixed for the Create PKG operation -> action Access EXT_CSD Register -> Advanced Selection -> [Open eMMC Info File] Firmware 1.52 --------------------------- - improved RIFFBOX1 CPLD Firmware (old version is 0xA1B6, new version is 0xA1B7). JTAG stability improved, fixed some JTAG module issues which were reported to appear after the SDMMC controller was added to CPLD Firmware in 1.48 version. JTAG Manager 1.86 --------------------------- - for MTK USB Mode: now JTAG Manager will use any available DA for current MTK chipID (ignore H/W Version) in case exact match (ChipID & H/W Version) is not found in the AllInOneDA file JTAG Manager 1.85 --------------------------- - added MTK MT6795 support in USB Mode - fixed bug for MTK USB Mode Settings when USB Loader Protocol Field remained disabled with wrong protocol selected JTAG Manager 1.84 --------------------------- - fixed bug which caused firmware update bug which was caused by fixed bug which caused current operation to stop (for example eMMC read operation) in case another riffbox or any supported qualcomm usb device is connected to PC JTAG Manager 1.83 --------------------------- - added support for MTK USB devices; - MTK USB mode is added to PKG editor; - fixed bug which caused current operation to stop (for example eMMC read operation) in case another riffbox or any supported qualcomm usb device is connected to PC JTAG Manager 1.82 --------------------------- - fixed bug when existent PKG's pinout picture was not displayed due to "Interface Pinout" button was hidden - added new pkg licensing scheme, which allows now to use any PKG file createad by any user for any other user. Root PKG License is required for edit permission. To share own PKG file with other users the Root PKG License is not required now. - added altermative method of detecting the storage size for Qualcomm Firehose Loaders which do not support GetStorageInfo command - added USB Action to PKG Editor - added support for Qualcomm DMSS Bootstrapping Protocol. Thus, currently both qualcomm bootstrapping methods are supported: SAHARA (newer MCUs) and DMSS (older MCUs) Firmware 1.51 --------------------------- - fixed RIFF1 firmware bug which caused random box restarts during ISP flashing - fixed RIFF1 firmware bug which caused freezing during consequtive eMMC write operations in single session - fixed RIFF1 & RIFF2 firmware bug which caused erasing the first block of eMMC chip's user area after reading eMMC firmware or reading Samsung Smart Info JTAG Manager 1.81 --------------------------- - added USB mode: it is possible to connect supported devices via USB cable; - added UFS memories suppport via USB interface. - added feature to remember earch partition address and length settings on USB read/write page; - added feature to remember earch partition address and length settings on eMMC read/write page; now when partition is changed, the relevant Address and Length fields are changed to correspond values which were set for selected partition; - fixed an issue with settings when there are no downloaded resurrectors or if there are not all kinds of resurrectors are present; Now informative dialogs are displayed for users to be able to clue out what's to be done. - fixed an issue when user tries to select Resurrectors filter (for example to filter only ISP Resurrectors) and there are no Resurrectors of the selected Filter kind; Now informative dialogs are displayed for users to be able to clue out what's wrong. And deadloop with settings is avoided now. - added information on the Plugins page - in case there are no plugins are downloaded yet, the not experienced user can see information about plugins and how to get them; - revised the "Resurrector Settings" logic: renamed to "Automatic Parameters" and "Manual Parameters by User". When selected "Automatic Parameters", the required connection settings are used from the Resurrector DLL: for all modes - JTAG, eMMC, USB. Please note, any settings (values) present in the ISP Resurrector DLLs are copied when DLL is selected and are not forced not to be changed later by user. Thus for ISP mode, all settings (interface, SD_CLK, voltage and bus width) can be modified anytime, and are not grayed out in the "Automatic Parameters" mode. When selected "Manual Parameters by User", the required connection settings are used from correspondent fields. Additional checks added to eliminate irregularities during connection to the device when incorrect mode DLL is selected in the list. Message dialogs are displayed to inform user what has to be done in order to fix the problems - completely reworked scenarios for cases when "Automatic Parameters" or "Manual Parameters by User" option is selected It now complies to following rules: when "Manual Parameters by User" are selected, the settings block is changed depending to currently active Page. For example, if eMMC Read/Wrte page is active, ISP settings block is displayed, if DCC Read/Write ppage is active, JTAG Custom Settings block is displayed, etc. In case "Automatic Parateres" is selected, no matter what acitve page is selected, the settings block which corresponds to the mode of selected resurrector is displayed. This helps to eliminate illogical scenarios - for eample, when selected resurrector is ISP Resurrector and user tries to Read/Write memory on DCC Read/Write Page. In this case Error Message dialog is displayed for user. - implemented more informative and self-explainable run-time rebuild of the JTAG Manager's settings blocks interface when Automatic Parameters" or "Manual Parameters by User" are selected. JTAG Manager 1.80 --------------------------- - fixed save file bug: After JTAG Manager showed there is no Free Disk Space to save the file, consequtive Save attempts resulted in errors. - fixed keyboard layout switching when RichEdit component is activated (these are forms containing instructions, help, etc - like Resurrection Manual, Useful Plugins description text, etc) - firmware update procedure is impoved Firmware 1.50 --------------------------- - fixed RIFFBOX2 Firmware bug: when reading any data from eMMC Chip, the Data CRC16 was not checked, so even data received with errors was concidered to be valid. Now RIFFBOX2 Firmware detects data CRC16 errors, and guarantees data read from eMMC chip is valid. RIFFBOX1 Firmware is not affected by this bug, but firmware update is required to update to 1.50 version string. - fixed timing bug which prvented to change BOOT and RPMB partitions sizes JTAG Manager 1.79 --------------------------- - added context menu for the PKG editor - right-click on data write actions allows to perform alignment of the selected ation's data. Normally alignment is performed when adding new write memory action. This feature allows to align actions in selectable manner, after all write actions were added to the list. This feature is handy when adding full list of write actions via eMMC Plugin, and when some partitions are required to remain full size, and others are allowed to be cut/aligned - "eMMC/SD Access" Page -> "Data Length" Field, ComboBox with pre-set lengths, 'File Size': when selected, Data Length field is filled with value equal to selected File's size. Now File size is automatically aligned to 0x200. JTAG Manager automatically handles non-aligned to 0x0200 files - the remaining data is filled with 00s. - Added "Load EXT_CSD Register" feature to the eMMC/SD Advanced dialog. It is possible now to load 0x200-byte EXT_CSD register into currently connected eMMC context; Format supported: plain binary format, 0x200 bytes size of file; most often these are files with extentions '*.bin' and '*.extcsd'; - Added "Load CID & CSD Registers" feature to the eMMC/SD Advanced dialog. It is possible now to load CID and CSD registers into currently connected eMMC context; Format supported: log text files made with other boxes. - Revision 1.8 (for MMC v5.1) is no more reported as 'unknown' by the JTAG Manager JTAG Manager 1.78 --------------------------- - (SDK): more functions are now available (exported) for future Resurrector DLLs; - PKG Editor: added button 'Visual Conditional Writes' - which helps sorting write actions into specified groups of conditions Those who have experience in PKG creation will understand the purpose. - fixed SD/MMC voltage list for RIFFBOX1 - fixed corrent partition name logging when reading/writting via Direct EMMC interface JTAG Manager 1.77 --------------------------- - Improved RIFFBOX2 Communication - improved problem which causes the JTAG Manager to freeze in situations when 'Stop' button is clicked in the process of (PC <--> BOX) data communication. JTAG Manager 1.76 --------------------------- - fixed bug which caused distorting ExtCSD register data when browsing through ExtCSD Register Fields in case selected field size was more than 4 bytes ([eMMC/SD Advanced] dialog) - fixed displaying of General Partition Size in eMMC Connect log (when press [eMMC/SD Advanced]/[Read Info From eMMC] or [Check eMMC/SD Card] buttons) - added General Partitions resize dialog ([Configure GP Partitions] button in the eMMC/SD Advanced dialog). - Action [Access eMMC EXT_CSD Register] inf PKG Editor is improved: added option to select multiple EXT_CSD register fields from eMMC Info File (along with their values) - Action [Establish SD/MMC Direct Connection] is updated with recommended parameters of SD/MMC Interface, VCCIO Voltage, SD_CLK Frequency and BusWidth. Note: those parameters have 'recommended' status - they are just copied to proper JTAG Manager fields when the PKG is selected. Firmware 1.49 --------------------------- - fixed eMMC Firmware update bug for RIFF BOXes h/w version 1 (RIFFBOX1) - fixed eMMC Firmware reading bug for RIFF BOXes h/w version 1 and 2. !!!!!!!!!! Please note !!!!!!!!!!!!!!!!!!!! eMMC Firmware files which were read via RIFFBOX1/2 Firmware versions 1.48 are invalid and shall be re-read !!!!!!!!!!!! (these are files like: KMVTU000LM-B503_Firmware[6D432398].riffmmcfw) JTAG Manager 1.75 --------------------------- - fixed RIFFBOX1 bug which caused Resurrectors and Plugins to work only via RJ-45 eMMC Interface. Now DLLs work correctly via the emmc interface selected in JTAG Manager settings - fixed "Samsung eMMC Smart Report" feature bug when reading via RIFF1 JTAG eMMC Interface. - fixed error which caused JTAG Manager to show 'Not Authorized Accesss' in cases when RIFFBOX1 CPLD firmware was failed to be repgrogrammed. Now JTAG Manager correctly sees the CPLD error status and does not block the user to update the RIFFBOX firmware in order to apply possible fixes to CPLD reflashing algorythms in new RIFFBOX1 firmware releases. - fixed bug which caused resetting eMMC Interface Setting back to 'JTAG' when RIFFBOX1 was uplugged. - fixed status showing 'RIFFBOX Online' in JTAG Manager while in real the RIFFBOX1 was unplugged. - improved Register CID write during the eMMC Firmware update stage in case the eMMC chip is started from the TestPointt mode (default name is '000000'); In this case the CID register value is extracted from the firmware file and thus it simplifies for user the restoring of the CID Register value in case there is no original CID value was stored previously. JTAG Manager 1.74 Re-uploaded --------------------------- Firmware 1.48 --------------------------- - new SD/MMC Interface is added for RIFF1: the CPLD is used for data shifting at max 8MHz rate. As the eMMC signals the TDI, TMS, RTCX, and TDO signals on JTAG Connector are used. Read/Write speeds at 8MHz are aprroximately 800KB/sec - read, 365KB/s - write. Since the new SD/MMC Interface shares the JTAG port connector, in the JTAG Manager in the SD/MMC Interface list, it is named as 'JTAG'; - the eMMC Read/Write speeds for GPIO (RJ-45) SD/MMC Interface are increased: 260KB/s - read, 360 KB/s - write (compare with Firmware 1.47: ~198 KB/s - read, 190 KB/s - write) - the eMMC Read speeds for RIFF2 (30PN) SD/MMC Interface are increased: at SD/MMC Clock Speed = 34MHz: ~9.50MB/s - read (compare with Firmware 1.47: ~7.80 MB/s - read) - the eMMC Write speeds for RIFF2 (30PN) SD/MMC Interface are increased more than 20x(!!!) times: at SD/MMC Clock Speed = 34MHz: 6.40MB/s - write (compare with Firmware 1.47: ~390 KB/s - write) - fixed buffer overrun bug in RIFF2 firmware, which caused getting chaotically corrupted data during the eMMC Read operations JTAG Manager 1.74 --------------------------- - ExtCSD Register's fields 177, 179 and 162 (BOOT_BUS_CONDITIONS, PARTITION_CONFIG, and RST_n_FUNCTION) are now displayed in eMMC connection info ("Check eMMC/SD Card" button or eMMC Advanced Actions Dialog's "Read Info from eMMC") - Added selection of SD/MMC H/W Interface: currently are available: > 1. RIFF1 SD/MMC Interface @RJ45 Connector > 2. RIFF1 SD/MMC Interface @JTAG Connector > 3. RIFF2 SD/MMC Interface @30-Pin Connector - added real-time RIFFBOX status (in StatusBar): the BOX revision (RIFFBOX1/RIFFBOX2) and Firmware version - improved switching on-the-fly of the JTAG Manager's specific to RIFFBOX revision parameters, immediately when the new box is connected to PC while JTAG Manager is running. - schematics picture is updated (RIFF JTAG Pinout button on the Resurrection page). Schematics picture is now displayed depending on the box revision - RIFFBOX1 or RIFFBOX2. - added one-time Start Trial Period feature JTAG Manager 1.73 Re-upload --------------------------- - fixed Access Violation bug which happened when JTAG Manager is started when there is none Resurrector DLL or PKG is installed yet. Firmware 1.47 --------------------------- - MassStorage Mount/Dismount support for RIFFBOX1 is added. - Working with special eMMC vendor features (like dedicated Samsung eMMC Chip's commands) is re-organized. Due to high risk of erasing User/Boot areas on the eMMC chips which are not Samsung, the Samsung chips autodetection is completely removed. To access special Samsung eMMC's features (like firmware update, factory reset, etc) User must manually select Vendor Mode. - RIFF1 & RIFF2: Finally!!! The eMMC/SD Erase Operation (for Direct/ISP connection) finally is implemented!!! JTAG Manager 1.73 --------------------------- - MassStorage mount/dismount feature is reworked and improved. Now is possible to Mount/Reconfigure/Dismount the MassStorage via the same dialog. The MassStorage settings are read from the RIFFBOX, so it is much more convenient in case users need to mount/dismount same eMMC Area ocasianlly or to adjust eMMC connection parameters for better stability. - MassStorage Mount/Dismount support for RIFFBOX1 is added. - Working with special eMMC vendor features (like dedicated Samsung eMMC Chip's commands) is re-organized (see the Firmware 1.47 notes) - Finally!!! The eMMC/SD Erase Operation (for Direct/ISP connection) is implemented!!! JTAG Manager 1.72 --------------------------- - new method of resurrectors grouping is added. Setting ISP Resurrectors shows only the ISP available DLLs; Setting ISP Resurrectors shows only the packages (PKG files); setting JTAG Resurrectors shows only the JTAG available DLLs Setting ALL Resurrectors shows all available DLLs same as is done in JTAG Manager 1.71 and lower. - fixed bug for correct setting of the recommended SD/MMC VCCIO voltage for ISP DLLs: when model is selected, the JTAG Manager adjusts the frequency, voltage and other settings to match (if possible) those values, which are hardcoded into resurrector DLL. JTAG Manager 1.71 --------------------------- - firmware update bugs are fixed. Those could cause box not detection errors during firmware update procedure when box is switched from firmware mode into bootcore mode and vice versa - eight new boot mode templates are added to "Set Boot Operation Mode" feature (eMMC/SD Anvanced dialog from eMMC/SD Access page): Broadcom Boot Config, Exynos (RSTn OFF) Boot Config, Exynos (RSTn ON) Boot Config, Hi-Silicon Boot Config, Mediatek Boot Config, Qualcomm 1 Boot Config, Qualcomm 2 Boot Config, Spreadtrum Boot Config JTAG Manager 1.70 --------------------------- - minor bug fixes Firmware 1.46 --------------------------- - fixed incorrect MassStorage Mode behaviour when there is no eMMC/SD device detected on box startup. - fixed bug in MassStorage Mode USB BULK communication Firmware 1.45 --------------------------- - addedd MassStorage Mode for RIFFBOX2 JTAG Manager 1.69 --------------------------- - fixed the bug for General Purpose Partition Sizes - added feature to switch ON/OFF the MassStorage Mode. For this, please connect an eMMC (either via Direct or ISP interface), make sure it is detected (on the "eMMC/SD Card" page), and on the 'eMMC/SD Advanced' dialog click the 'MassStorage Mode ON/OFF' button to setup which partitions are to be mounted. Please note, for stable connection, first of all do reads on the "eMMC/SD Card" page to adjust stable Frequency, BusWidth and Voltage. After you click "MassStorage Mode ON/OFF" button, current settings for Voltage, Frequencty, BusWidth will be written into RIFFBOX non-volatile memory, and while the MassStorage mode is ON, upon each connection to USB the RIFFBOX will additinally to normal Control interface enumarate the MassStorage Disks (as if a FlashStick is connected to PC) Firmware 1.44 --------------------------- - fixed Hynix (and possibly other non-Samsung eMMC chips) bug which caused erase of chip contents during init stage ("Check eMMC/SD Card" button); - changed eMMC autodetection algo for Samsung chips. Now a simple check of Manufacturer ID is used (note, the Samsung eMMC's Manufacturer ID = 0x15) Please note, currently is supported eMMC CID Register Write operation for Samsung chips. Thus, for Samsung eMMC it is possible to change Manufacturer ID byte. In case Manufacturer ID is not equal 0x15, all extended Samsung eMMC's functionality will be disabled (Write CID,CSD, Read/Write eMMC firmware, etc). To enable it, use "Write CID Register" operation with the forced Samsung Mode checkbox checked to write the 0x15 value back to the Manufacturer ID field. JTAG Manager 1.68 --------------------------- - added option "Forced eMMC Samsung Mode" to the "Write CID Register" operation, so the Samsung eMMC chips with not valid Manufacturer ID field (the valid one is 0x15) could be processed. Firmware 1.43 --------------------------- - fixed eMMC Detection bug for RIFF1 hardware JTAG Manager 1.67 --------------------------- - fixed bug (which is related to RIFFBOX2 only), which caused box connection error, after this operation: "Setting new JTAG/eMMC License to the RIFFBOX." - Access Violation bug when trying to open the eMMC Info File (in eMMC/SD Advanced dialog) is fixed JTAG Manager 1.66 --------------------------- - RIFFBOX2 support for new connection mode is added (for new Drivers) - due to new dirvers Read/Write speeds via eMMC interface increased 10 times and more Firmware 1.42 --------------------------- - RIFFBOX connection mode is optimized for better speed, it is no more the CDC. The data transfer speeds are increased more than 10 times. - Fixed bug in handling the erroneous situations during eMMC data read operations. JTAG Manager 1.65 --------------------------- - fixed write EXT_CSD Register Field bug via PKG JTAG Manager 1.64 --------------------------- - fixed Password Recovery feature - fixed bug which caused JTAG Manager crash after clean install and successive downloading of a DLL file while there were no PKG files installed. - improved login interface - the registered email is automatically filled in to the Login field. - JTAG Manager Main Window Width is increased to increase the width of Resurrector Name fields JTAG Manager 1.63 --------------------------- - RIFF2's eMMC Voltages list bug is fixed. - BOX detection is re-worked. No special drivers are required anymore, standard COM Port Windows drivers can be used. - No need to enter COM Port numbers manually for Windows 10. Box is detected automatically as for older Windows versions. - added "Missing Resource" feature. If DLL is missing some resource, for example schematics picture, logs or binary data, the JTAG Manager will popup special dialog so it is possible for custmers to upload data to RIFF Server after which the DLL can be updated with missing data. Active customers will be rewarded with credits. - a feature added to edit registration details (eMail, login, password) in Account Manage dialog: the new button - "Edit Account Details" - cosmetic interface changes Firmware 1.41 --------------------------- - fixed bug in internal communications via DCC channel for ARM7/ARM9 cores, the bug influenced incorrect reading of DCC channel ready bit. This bug was especially harmful during writes on devices with slow memory chips, like CDMA phones with NOR memories Firmware 1.40 --------------------------- - fixed bug for Direct eMMC access when writting EXT_CSD Field 0xB3 via Resurrector DLL caused ignoring the new value. JTAG Manager 1.62 --------------------------- - support for Resurrector DLLs which use ISP/Direct eMMC access is added. - eMMC settings are slightly reorganized (Bus Width is moved to the Voltage and Frequency block) - "Custom Target Settings" is renamed to "Custom JTAG Target Settings" due to introduced ISP/Direct eMMC Access Resurrector DLLs to eliminate ambiguity. - support for Resurrect Settings with ISP PKG selected is added. JTAG Manager 1.61 --------------------------- - improved error handling and extending of expired accounts. - fixed updates window size. JTAG Manager 1.60 --------------------------- - fixed bug related to some Server communication problems - Transfer credits from account to account is simplified, no need to enter the destination Login name, the destination S/N is enough. - link to RIFF Support forum is added on two dialog boxes (which are usually signal errors) JTAG Manager 1.59 --------------------------- - changed the RIFFBOX pinout picture (added eMMC pinout interface on RJ-45) - fixed bug in Package Editor: Flash Memory/Direct eMMC Flash actions, Automatic Parameters, building list of partitons for write via Plugins, was done with invalid lengths of paritions. - [eMMC/SD Advanced]/[Select eMMC for Info & Read]: pictorgrams are added to the list of chips. The pictogram is blue if info file is present, gray - if not present (the one displayed by the Show eMMC Testpoint button). Firmware 1.39 --------------------------- - fixed JTAG bug with the ARM11 cores connection. Now is ok. - fixed JTAG bug with the Cortex cores connection. Now is ok. JTAG Manager 1.58 --------------------------- - added direct eMMC Access Interface on the RIFFBOX RJ-45 port (check pinout picture for CMD, CLK, DAT0, etc pins positions). - added eMMC/SD Access page for Read/Write operations on eMMC/SD card via direct interface - added eMMC/SD Advanced dialog which allows to perform advanced operations with eMMC/SD cards (reading info, browsing through OCR, CID, CSD (and EXT_CSD for eMMC only) registers' fields, edit separate fields and writting back to card, reading/writting eMMC card's MCU's internal firmware, etc) - added convenient information presentation for specific eMMC chips: pinouts for testpoints, manuals how to use testpoints to resurrect dead eMMC, etc). These INFO files (*.riffinfo) are stored in JTAG Manager's Documents folder and can be downloaded via generic operation. - added eMMC Firmware Update option - added eMMC Firmware Reading option (firmware is stored in *.riffemmcfw format) For firmware read need to select chip from the list - *.riffemmcfw eMMC firmware files are now used by RIFF for firmware updates (plain binary files are supported too) - added elapsed time info for eMMC firmware update stages - added eMMC Testpoint info displaying (info files must be downloaded from support and are located in the JTAG Manager's 'Documents' folder. - added CMD42 Lock/Unlock functionality for eMMC. User can set/change/remove password to protect/unprotect (lock/unclock) the User Area Partition - added the User Area Partition Forced Erase to erase Locked User Area Partition and to reset Device lock/unlock state and password (CMD42's consequences) - added Samsung Factory Erase which erases and re-formats the Samsung eMMC chips. - fixed bug displaying wrong SD card size for cards capacity less than 2GB - few small improvements and bug fixes Firmware 1.38 - added direct eMMC Access Interface functionality - improved one thing in the emmc communication - added the CMD42 Lock/Unlock/Pasword reset features - added Forced erase of locked User Area Partition - added Samsung eMMC Factory Format - fixed bug for SD card support - eMMC firmware update feature added JTAG Manager 1.57 --------------------------- - due to the testing phase this version is obsolete in the release world JTAG Manager 1.56 --------------------------- - Added Repair Packs functionality: allows customers to create own resurrectors. Advanced RIFFBOX customers will be able to create own repair modules for local use only, while RIFFBOX customers with special permissions will be able to distribute own repair packs to all RIFFBOX users. - Updates list is re-organized: 1. added feature to sort updates by name and by date, 2. updates not browsed by user are marked with bold font for more convenient distinguish of old/new files, 3. added update files tree view - update files are classified by folders for better convenience, 4. search file name feature is added: press CTRL+F to open Instant Search window. - Timeout if user was deciding which update files to download for too long time is fixed, now there is no timeout, user can do selecting files before clicking Download button for as long time as he wishes. - leading and trailing spaces are removed automatically from login name during registration JTAG Manager 1.55 --------------------------- - Download update files speed is improved - removed PDF open buttons, instead embedded buttons with direct links to support site JTAG Manager 1.54 --------------------------- - password recovery is available during firmware update too. JTAG Manager 1.53 --------------------------- - added recovery password feature - some few irrelevant improvements JTAG Manager 1.52 --------------------------- - RIFFBOX Registration features enforced JTAG Manager 1.51 --------------------------- - added RIFFBOX Registration features - fixed few bugs related to Windows XP systems - fixed bug which caused sometimes to popup Firmware Update dialog while box firmware is already up to date. JTAG Manager 1.50 --------------------------- - firmware update procedure is simplified now. To update box firmware user now has to click single button, no other actions are required!!! (in previous versions update firmware opration caused many questions from unexperienced users). - update server moved to new host. Thus, Check Updates for Updates button will now work correctly. - Numlock key recognition is added so now additional keypad can be used to enter digits 0..9 into decimal fields (like address/length fields) Firmware 1.35 --------------------------- - added support for Cortex-A15 and Cortex-A5 cores. - fixed emergency script issue for multi-cored Cortex MCUs: it was executed after first core was halted. Now it is executed after all core(s) (if specified by reset strategy) are processed (halted). JTAG Manager 1.49 --------------------------- - added support for Cortex-A15 and Cortex-A5 cores. - new Popup balloon is added with hints about 'Dead Body ID is wrong' error. - win8 exe protector is used, so JTAG Manager can be run on that system too. - added "RIFFBOX on the Network" button (BOX Service Page). User can easily visit some main RIFFBOX's internet locations. - some new IDCODES added to the search engine (CTRL+F) JTAG Manager 1.48 --------------------------- - added checking of plugin version before activation of it. - nothing else is changed. New version of compiler used requires to update to 1.48 Please note, with older versions you will not be able to use plugins. Re-download all plugins again from support. JTAG Manager 1.47 --------------------------- - added new more APIs for Resurrector DLLs. These allow more flexible target initialization; - added "PAUSE" feature which allows now JTAG Manager to work be "paused" on command from Remote Helper. Paused JTAG Manager frees RIFFBOX comport and becomes inaccessible until Remote Helper allows it to "unpause" Thus, Remote Helper may work without fear that user may meddle in process. JTAG Manager 1.46 --------------------------- - added IDCODE analize and displaying known MCUs for that IDCODE. Click Analize JTAG Chain to see. - added IDCODE API for Resurrector DLLs; - extended DCC Loaders Read/Write functionality to have separate buffers for read/write; Firmware 1.35 --------------------------- - fixed issue for ARM11 cores: breakpoints in THUMB mode were handled erroneously. JTAG Manager 1.45 --------------------------- - ST-Ericsson NovaThor U8500 MCU support is added; - Updates List is now displayed in alphabetic order ("Check Updates" button on the "Box Service" page); - small cosmetic change to CTRL+F find form: CTRL+V/CTRL+X operations on ID search field starts search immediately; - added "Override Embedded Reset Strategy" feature: is usefull in rare cases when there are some problems with target coming out of reset, etc. The feature is accessible via "Advanced Settings" button on the "Box Service" page; - added "Apply NRST before connecting to target" (to setup click "Advanced Settings" button on the "Box Service" page); This feature is handy for development purposes especially when working with Qualcomm MCUs - after erroneous H/W config (most often is 0x45 error code) MSM locks down, to reconnect need to reset power. Enabling this feature simplifies this. Firmware 1.34 --------------------------- - ST-Ericsson NovaThor U8500 MCU support is added JTAG Manager 1.44 --------------------------- - added support for a set of QUALCOMM Snapdragon S4 MCUs (like MSM8960): these devices are added to Targets list - added "Override Embedded I/O Voltage" feature: in some rare cases users can use this option to stabilize the weak signals by increasing/decresing JTAG I/O voltage levels, thus overriding embedded voltage settings in a DLL. For this: click "Advanced Settings" button on the "Box Service" page and select a desired voltage level. NOTE, "Override Settings" is valid for current session only, and it is automatically disabled upon next JTAG Manager startup. - few minor rearrangments & fixes. Firmware 1.33 --------------------------- - added few more processor controll "HAS" script instructions. - added support for a set of QUALCOMM Snapdragon S4 MCUs (like MSM8960). JTAG Manager 1.43 --------------------------- - added feature to use halt mode from a DLL rather than to use a default one. - added "DCC Loader USB Interface" feature. If selected resurrector (DCC Loader) supports USB communication (RIFF BOX DCCLoader USB Interface Port appears in windows devices list) then, after DCC Loader is started, the JTAG Manager will switch further communication with DCC Loader to the USB port thus data exchange speed will increase. Please note, to use this feature you need to attach USB cable from device to the PC USB port, and install drivers for "RIFF BOX DCCLoader USB Interface Port" on first use. DCC Loader USB Interface is not used during resurrection operations (Resurrection page, Resurrect button). Firmware 1.32 --------------------------- - added MIPS32 architecture support for TAP controllers with IR Length = 05 bit (for exmaple ALI 3329 processor) - added MIPS32 architecture support for TAP controllers with IR Length = 08 bit (for example BCM5352 processor) - some minor improvements for TEGRA2 JTAG Manager 1.42 --------------------------- - added MIPS32 architecture support! - added shortcut key 'CTRL+F' for fast and convenient displaying of "Search for DLL" Window. This works from any JTAG Manager page, it's more convenient alternative to the usual search action when user needs to switch to Resurrection page and click "Search for DLL" button. - added "riffpbin" format support for DCC Read/Write page operations - some minor cosmetic fixes Firmware 1.31 --------------------------- - APQ8060, MSM8260, MSM8660 (3rd generation Qualcomm chipsets) support is added. - fixed ARM7 bug: exit from debug state into THUMB mode was corrupted. - added after-halt "Emergency" script execution for ARM7 cores. JTAG Manager 1.41 --------------------------- - APQ8060, MSM8260, MSM8660 (3rd generation Qualcomm chipsets) support is added. - fixed SettingsCode bug which was spawned after we've transfered to 12-digit wide 64-bit hex numbers representation. JTAG Manager 1.40 --------------------------- - solved the problem with download of updates. Now no more nasty 'Out of Disk Space' error!!! Some users could experience this kind of error during download of large files (30MB and more). - added check if JTAG Manager is running with administrator rights (in case it is installed in Program Files location). This solves issues for older operating systems (Windows XP) which have no UAC and no manifest means controlling elevation of application rights. Thus now if the JTAG Manager is started without administator rights it will restart itself with request to run it "as administrator". - Embedded font for text message window on JTAG Read/Write page. - improved displaying of DLL version information: If FileVersion info is available JTAG Manger will display it rather than the internal version supplied by DLL. This simplifies version tracking for us. JTAG Manager 1.39 --------------------------- *********************** *********************** *** PLEASE NOTE!!! New resurrectors data base format is used in 1.39 version, thus *** upon first start the JTAG MANGER WILL RESTART 1-5 TIMES in order to re-load and re-fresh all existing resurrector DLLs. *********************** *********************** - fixed bug which caused poping-up of 'Out of Free Disk space' window error while real error was just a failed HASH. - eMMC chip size is now represented not only in bytes but additionally, for visual convenience, in Mega/Giga bytes - Addres/Length fields on DCC Read/Write and JTAG Read/Write pages are changed into custom GUI representation: now 12(or 8)-digit hex values are shown in more human 'readable' way. - For more convenient work with the DCC Read/Write page features there was added standard lengths list, so user can set 'human readable' length value instead of manual typing of correct hexadecimal length value. For this just click combo box near Data Length field and select a desired length. - Added balloon hints to suggest what to do in case user has 'DLL was not Accepted' issue. - selected resurrector DLL version is shown in logging windows now along with Model name, for example: Selected Resurrector: [NoName x1234 V1.00] - Added "Search for DLL" button on the Resurrection page: As RIFFBOX grows up on number of supported devices, searching visually through the big lists of supported models for a definite device name became a tiresome procedure. Now user can search for required model simply typing part of model name in the search dialog (for this select "Search for DLL for this Model Name" and type some part of device name you're looking for) Besides this, there is feature to search for resurrectors compatible with specific IDCODE. For example, if you have a not supported device in hands with ID = 0xXXXXXXXX, you can search for DLLs which work with such ID and try to connect your device using one of such 'compatible' DLLs. (for this select "Search for DLL with same IDCODE" and type IDCODE you're looking for) Firmware 1.30 --------------------------- - improved HALT algorithm for ARM11 fused (JTAG diabled) cores for cases when core exits reset till the moment when JTAG is enabled by running firmware code JTAG Manager 1.38 --------------------------- - added feature to disable Target ID check during resurrection If current ID is not supported by a DLL, user can switch off ID check and still be able to try resurrection. Though, we don't recommend it. Do it only if you are sure what you're doing and if you're sure that device with unmatched target ID is still exactly the same model as stated in DLL. Please note, upon JTAG Manager exe startup this option is automatically switched off. - added preset "Erase Full NAND/NOR Memory" (for this use Settings by Code button) Firmware 1.29 --------------------------- - MPCore targets handling is improved. - fixed bug in the ARM7 handling routines: h/w breakpoints were disabled each time any halt operation was performed - added auxiliary instruction which improves GDB Server functionality. JTAG Manager 1.37 --------------------------- - fixed bug which caused not to report improper firmware version of riff box - (SDK): more functions are now available (exported) for future Resurrector DLLs; Firmware 1.28 --------------------------- - added few more H/W script (*.has) instructions; - added some security extensions for Xperia repair; JTAG Manager 1.36 --------------------------- - added fast presets for automatic selection of settings for most common operations on DCC Read/Write page For this click Settings by Code button and select a desired preset from list and then click Apply Settings. For example if user selects "Write Full Image into NAND memory" the valid settings on the DCC Read/Write page for writting full images into devices with NAND memory will be automatically selected - fixed serious bug which caused resurrector DLLs which do upload data into RAM to upload broken data For example DLLs which start Downlad Mode directly use this feature. - added feature to accept text name of memory chip from DCC Loader and display it (currently used to display eMMC memory product name) - fixed bug for resumming interrupted DCC Read: ifvcurrently cached file size was greater than > 2GB (that is if read was interrupted on point when there was already more than 2GB of data read) the new reading data was not appended to the readout file end, but instead the file was corrupted. - fixed bug for saving big files (after reading on DCC Read/Write page): if size exceeded 0x7FFFFFFF bytes JTAG Manager show no free disk space error. - added TEGRA2 chipset selection in the Target list - fixed an issue with the resurrection progress bar: in some cases during resurrection operations the progress bar would always stay at 0%. Firmware 1.27 --------------------------- - added TEGRA2 debugging support (dual-core Cortex-A9) - added new breakpoint type: "address mismatch" which allows geniune single-stepping on Cortex-A8,A9 (CoreSight) targets (thus GDB Server can now perform low-level single step commands) JTAG Manager 1.35 --------------------------- - added an arbitrary feature "Settings by Code" to the DCC Read/Write page. Main purpose is to improve support quality for users: via "Settings Code" string a supporter person sees all settings which were set by user on the DCC Read/Write page. Though, end-user may benefit from this too: Use "Settings Code" string for JTAG Manager to automatically setup all DCC Read/Write settings - fixed data loss during read and save operations in case there is not enough disk space available to store required ammount of data. (for example reading full on DCC Read/Write page, or saving read full, etc). Now available disk space checks are performed prior disk write operations. - fixed bug which blocks JTAG Manager startup in case of language DLL update was downloaded JTAG Manager 1.34 --------------------------- - JTAG Manager Project has been migrated into UNICODE. Main advantage of this - GUI (captions of buttons, labels, etc) can now support all international characters, for example chinese WARNING!!! Due to UNICODE migration old plugin DLLs are not compatible with JTAG Manager 1.34 Simply download new set of plugins which are unicode compatible now. - Multilanguage GUI is implemented (and due to migration to UNICODE even chinese language can be fully supported) You need to download language pack dll, for example Russian.dll. After installation go to BOX SERVICE page and there will be available language selection. Following items are translated into selected language by the language DLL: 1. JTAG Manager interface - labels, captions, etc. 2. JTAG Manager messages which are shown during active operation. 3. Most of messages shown by resurrector DLLs 4. Some of Resurrection Manuals (if current version of language pack does not have translated version of Resurrection Manual, then an original, English version will be shown) - added warning window which will appear on DCC Read/Write page in case user tries to flash full dump with wrong settings. So user can check what he does wrong and thus avoid losing time and making mistakes. - ARM Core Cortex-A9 (Single and MPCore) and Chipset OMAP4430 (Dual-core Cortex-A9) are addred to the supported cores list; - Cortex-A9 core added to the CMM Script Engine: Example: SYSTEM.CPU CORTEXA9 - OMAP4430 core added to the CMM Script Engine: Example: SYSTEM.CPU OMAP4430 - Multicore control is added to the CMM Script Engine (Use CORE.SELECT instructions to switch between cores in multicore targets) For example CORE.SELECT 0 will select core0, CORE.SELECT 3 will select core3 - added access (32-bit Read/Write) to the APB bus of CoreSight-compatible targets (Cortex-A8, Cortex-A9, etc.) through the CMM Script Engine ('APB' segment specifier added) Thus, for example instruction: &Resp=data.long(APB:0x12345678) - will read dword from APB bus at address 0x12345678 - added SYSTEM.CONFIG.RESETTIMEOUT variable to the CMM Script Engine, thus it's now possible to customise reset type and timeout by setting this variable prior SYSTEM.UP command. - fixed bug which caused saving trash after read operaions on DCC Read/Write page in these cases: a) reading was stopped by user b) after JTAG Manager exe restart - DCC Read/Write Page operations now allow 64-bit addressing, thus user can have full access to memory devices which size exceeds 0xFFFFFFFF bytes range. For this, the Address and Length fields have now 10 digits instead of old 8 digits. Be carefull entering values there. UNEXPERIENED USERS PLEASE NOTE: For example 8 digit hex value 0x12345678 entered into 10 digit field IS NOT 0x1234567800 (!!!!!) CORRECT IS 0x0012345678 - TGauge64 component was implemented in order to support full 64-bit range of progress indications (while old progress bars were limited to 31-bit maximum value) - fixed bug with incorrect display of scrollbars during scroling through Model and Manufacturer Lists - fixed bug during erase: if bad block happened, and user choosed Ignore method and checked 'Remember selection' - software would again popup selection dialong on next bad block. - JTAG I/O Voltage (for Custom Target Settings) now has voltages from 1.6V upto 3.30V with resolution 0.05V - just for convenience added button "Target Continue" to the JTAG Read/Write page. This just allows to resume target running from current PC value without need to enter it explicitly into "Address" field as is needed for the "Target GO" button Firmware 1.26 --------------------------- - added support for Cortex-A9 single processor core; - added support for Cortex-A9 multiprocessor cores. Multicore handling rules are following: 1. After target reset (NRST=1-0-1) the Core0 is automatically selected; 2. HALT operation halts only currently selected core (by default core0 is selected); Thus in order to halt other core user has to select required core and then execute halt operation. 3. Reset operation can accept different strategies of reset and halt: - reset, then halt all cores at the very first instruction (for now only for OMAP MCUs) - reset, than halt only core0 at the very first instruction (for now only for OMAP MCUs) - reset, pause, then halt all cores - reset, pause, than halt only core0 4. RUN operation starts only currently selected core. Thus in order to start other core user has to select required core and then execute run operation. For example, if target has 4 cores (Quad-core MCU), then after HALT operation only Core0 is halted. To halt Core2 user has to write script: CORE.SELECT 2 BREAK For example, to run Core3 user has to write script: CORE.SELECT 3 GO - added H/W script (*.has) instruction which enables selection of core for multiprocessor targets; - added script (CMM/HAS) access (32-bit Read/Write) to the APB bus of CoreSight-compatible targets (Cortex-A8, Cortex-A9, etc.) - added support for OMAP4430 Dual-core Cortex-A9 MCU Firmware 1.25 --------------------------- - added 5.0V USB Power On/Off controlling feature - changed sequence for 32-bit write accesses for ARM11 core JTAG Manager 1.33 --------------------------- - Improved connection policy: Resurrection/DCC connection to device is implemented in such way that JTAG speed changes have 2 stages - booting stage and working stage. Booting stage is the one from the connection start and until the DCC Loader upload is complete. Booting TCK/RTCK speed are setup by JTAG Manager no matter what are the TCK settings by user (JTAG TCK Speed field in the JTAG Manager). Booting speed is hardcoded in the DLL. After "booting" stage is complete, the "working" speed is set - the one which is selected by user in the JTAG TCK Speed field. If Booting Speed in resurrector DLL is hardcoded as 'RTCK' the JTAG Manager would always use RTCK mode during booting stage. Now policy is changed that is when user selects a fixed TCK frequency the JTAG Manager will automatically change booting speed to the fixed TCK too. - fixed bug: if "Use End Address" and "AutoFull Flash Size" were checked there was error setting valid length to read. - for Advanced Users: advanced settings are now moved from the DCC Read/Write page ("Notifications...") into separate button on Box Service page (Advanced Settings button) - added 5.0V USB Power On/Off controlling feature For this go to Box Service page, click Advanced Settings: the Notifications dialog will be displayed, go to "Advanced Settings" page and set desired mode for "Enable 5.0V output" checkbox. When enabled, 5.0V power will be on after any "JTAG" operation executed and will remain "ON" until box restart or until "Enable 5.0V output" checkbox is unchecked and any "JTAG" operation is executed. - added optimization for flashing memory devices which are sector-based (like MDOC H3 or MMC/SD memory cards) - if error code 0x3C (write-protect) is received no recover attempts are made. Firmware 1.24 --------------------------- - The Most Annoying RIFF Bug (THE BUG) is Fixed Finally!!! During flashing operations both RIFFBOX and JTAG Manager were frozing while DATA LED was blinking constantly. JTAG Manager 1.32 --------------------------- - Resurrector DLLs can now request current Memory Chip IDs: this is most usefull for NOR-based devices since sometimes such devices require different firmware for different NOR memory chip IDs. Thus resurrector DLLs will be able to perform automatic selection of resurrection data. Firmware 1.23 --------------------------- - added 8/16/32-bit bus read/write access rotuines for ARM7 core - ARM7 debug is now available in ARM/Thumb modes (use the GDBServer for this); JTAG Manager 1.31 --------------------------- - "RUN/STOP" Loaders functionality is added (an alternative to the DCC Loaders) This is required for some ARM7 cores when Debug Communication Channel (DCC) to/from core is not functional (like in MSM6000) Firmware 1.22 --------------------------- - fixed bugs in ARM7 core handling routines JTAG Manager 1.30 --------------------------- - added DISABLE_POLLING request processing from DCC Loader (used by DCC Loaders which have small RAM size available and there is no DCC RX polling is implemented in RIFFBOX firmware for current core); JTAG Manager 1.29 --------------------------- - fixed bug with plugins managing in case there is more than 1 plugin DLL available; - currently selected plugin is remembered now and will stay on next startups; - fixed Access Violation error during software startup in case there is none resurrector DLL present; - added Reset Method selection feature for more precise reset operation when Custom Target Settings is active; - Updates manager & Updates tracking were completely reworked, and now are based not on the system time but on file's hashing. Thus since now on the JTAG Manager's installation folder can be copied/moved/re-installed (whatever else) without need to re-download full set of files again. - (SDK): more functions are now available (exported) for future Resurrector DLLs; - many cosmetic changes; - FINALLY: "healed" the optimized DLL loading scheme: User shall see: "Found and Initialized: XXX New and YYY Old External Repair Pack(s)" where XXX must be always non-zero only on first startup after there were new DLLs downloaded from the support. On following JTAG Manager startups XXX shall be always equal to zero (!!!) For example, after downloading 3 more new DLLs while there were 100 Resurrector DLLs already installed, after JTAG Manager restarts user shall see: Found and Initialized: 3 New and 100 Old External Repair Pack(s) on next and all following restarts user shall see: Found and Initialized: 0 New and 103 Old External Repair Pack(s) - Re-worked balloon hints system - Own (not windows') balloons are shown, so no matter now what are the windows' tray icon settings are. - Added balloon hints for cases when target is not detected, error code 0x45, Device Id = 0x000000E1. Don't forget that balloons hints can be switched on or off from the DCC Read/Write page - click "Notifications..." and select"For Advanced Users" page to see settings - JTAG Manager now has new Icons :) - Improved JTAG Manager restarting during updating itself Firmware 1.21 --------------------------- - added RX-polling feature (debugger-to-target) for PXA3XX DCC transfers. RIFF BOX firmware is able now to wait (if resurrector DLL will request so) for PXA3XX target to be ready to accept next packet over DCC: this feature slows down a little the JTAG-to-Target DCC transfers but guaranties no packets loss for slow clocked targets; Firmware 1.20 --------------------------- - optimised connection to the PXA270 core - added DCC TX channel (host-to-debugger) cleanup (flushing) feature (happens now during DCC Read with 0 timeout parameter) for Cortex-A8 - optimized Cortex-A8 connection establishment after coming out of reset (after NRST signal assertion) - added emergency script processing for Cortex-A8 core (h/w script which is executed immediately after core was halted) JTAG Manager 1.28 --------------------------- - added RAM selft-test right before uploading DCC loader. - added functionality to handle complex memory devices (like MDOC H3) with lengths not necessary to be alighned to MBs; - added DCC TX channel flushing command before starting DCC Loader - thus it is guaranteed that next first DCC read will get DCC Loader's packet and not some residual trash data. - added 1GB and 2GB OneNAND chips to the size autodetection list. - added progress indication during saving files which were read on the DCC Read/Write page Firmware 1.19 --------------------------- - added more H/W script (*.has) instructions; - added HTC security processing functions; JTAG Manager 1.27 --------------------------- - fixied access violation bug upon JTAG Manager startup if there is no RIFF Box detected and Cancel button is clicked. - (SDK): more functions are now available (exported) for future Resurrector DLLs; - added flags for JTAG Manager to be able to retrieve memory chip size from the DCC Loader. - fixed initialization bug for NOR-related DCC Loadererss - ScriptEngine: added options pocessing '/byte', '/word', '/long' to data.save.binary instruction: thus it's possible now to read memory through script using desired bus access width (8-,16-, or 32-bit widths). For example: "data.save.binary c:\myfile.bin 0x00..0x11FF /word" - will read 0x1200 bytes from memory into myfile.bin file starting from address 0x00 using 16-bit bus accesses. Note: "Read Memory" button on the JTAG Read/Write page reads memory using 32-bit bus accesses only. JTAG Manager 1.26 --------------------------- - added MDOC G4 NAND chip size to auto flash size detection list; - (SDK): more functions are now available (exported) for future Resurrector DLLs; JTAG Manager 1.25 --------------------------- - improved again the DCC flashing functionality (for DCC Loaders that work in targets with a small RAM capacity); - (SDK): added condition when resurrectors can order to bypass ID check; Firmware 1.18 --------------------------- - PXA270 debug is now available in ARM/Thumb modes (use the GDBServer for this); JTAG Manager 1.24 --------------------------- - improved fonts handling: now Script Debug window shall correctly display script contents in monospaced font - in case when Resurrector has no DCC Loader the JTAG Manager will now report it correctly and will not allow DCC Read/Write features - (SDK): more functions are now available (exported) for future Resurrector DLLs; Firmware 1.17 --------------------------- - optimized DCC transfers (debugger-to-target) for ARM9 cores (~64,3% speed increase) - added RX-polling feature (debugger-to-target) for ARM9 DCC transfers. RIFF BOX firmware is able now to wait (if resurrector DLL will request so) for ARM9 target to be ready to accept next packet over DCC: this feature slows down a little the JTAG-to-ARM9 DCC transfers but guaranties no packets loss for slow clocked targets; JTAG Manager 1.23 --------------------------- - improved DCC flashing functionality (for DCC Loaders that work in targets with a small RAM capacity); - added 4 very low RTCK Sampling frequencies (20kHz, 40kHz, 60kHz and 80kHz) for some extreme cases - fixed another bug in the optimized DLL loading scheme; - increased ERASE waiting timeout (for slow NOR flash chips) so now erase operation for such chips will go successully and will not result in erase timeout - added "Usefull plugins" page; JTAG Manager 1.22 --------------------------- - fixed bug when resurrector had simultaneous Multi-ID + fast h/w config data; - fixed bug in optimized DLL loading scheme (rejected DLLs were not removed from the list); - fixed optimized DLL loading bug which caused target settings not to be set to the resurrector's values on the main form (Target, I/O Voltage, TAP#) - added LOG saving to the JTAGManger.txt file - Windows Vista and Windows 7 support improved JTAG Manager 1.21 --------------------------- - startup is optimized: DLLs initialization time now is 1 second maximum no matter how many DLLs are present. Firmware 1.16 --------------------------- - code is optimized to avoid deadlocks in ARM11 handling routines; - reset sequence (after NRST assertion) is optimized for ARM11 core; - added 4.2V power supply output (RIFF RJ45 pin 1) controlling feature JTAG Manager 1.20 --------------------------- - added 4.2V power supply output (RIFF RJ45 pin 1) controlling feature For this go to DCC Read/Write page, click "Notifications...", the Notifications dialog will be displayed, go to "For Advanced Users" page and set desired mode for "Enable 4.2V output" checkbox. When enabled, 4.2V line will be powered on after any "JTAG" operation executed and will remain "ON" until box restart or until "Enable 4.2V output" checkbox is unchecked and any "JTAG" operation is executed. - (SDK): exported new SUB_ID_GET_ROM_INFO function for resurrectors; JTAG Manager 1.19 Re-update --------------------------- - fixed Forcing Resrrection Manual reading not to be displayed if it is switched off by an Advanced User JTAG Manager 1.19 --------------------------- - added feature to temprorarily switch off Device ID check for DCC Read/Write page's operations thus it makes possible to test yet not supported board to be compatible with one of existent DLLs For this: when "Resurrector Settings" is active, the DCC Loader Settings button is transformed into 'Special Settings' button. Click it to setup the ID checking on or off. This setting is discarded to "ID Check ON" on each startup of JTAG Manager. - fixed bug which caused 'Data Length' label not to be changed to 'End Address' upon the JTAG Manager startup when the "Use End Address not Length" box was checked; - added hint messages for inexperienced users: short hints about how to solve a problem will popup if some JTAG communication error is encountered for Advanced users there is option to switch off such hints. - added feature to Forcefully display the Resurrection Manual window prior the Resurrection operation for inexperienced users for Advanced users there is option to switch off this feature. JTAG Manager 1.18 --------------------------- - further improved updates displaying when JTAG Manager is installed on FAT/FAT32 file systems - fixed bug which caused PDF buttons (on Box Service page) to stay disabled after first restart of JTAG Manager when a correspondant PDF was downloaded for a first time. Firmware 1.15 --------------------------- - PROBE feature is added JTAG Manager 1.17 --------------------------- - addedd chip size information handling for NOR memories - improved erase operation in case DCC Loader operates with a NOR memory. - implemented ResBreak option (SYSTEM.OPTION RESBREAK ON|OFF) in the Trace32 CMM execution engine - added PROBE feature (Start Probing button on the Box Service page) - added Probing Manual button on the Box Service page - RIFF JTAG Pinout (Resurrection page) is updated with more detailed picture - another very dangerous bug fixed: "Irnored" word misspelling during erase procedures is corrected to the valid "Ignored" one :) JTAG Manger 1.16 --------------------------- - fixed severe bug for PXA targets - sofware hunged during target connection - patched up FAT32 updates displaying issue (complete FAT32 problem is to be revised later) JTAG Manger 1.15 --------------------------- - added extended flash chip info handling for example for NOR memories support by DCC Loaders; - added Resume feature for interrupted writes (which could be performed by WriteMemory button (DCC Page) or by Resurrector DLL): if target loses power, connection is broken or any other malfuntion happens during write operation, software will store current write context; you can reconnect target and start write/resurrection again - software will prompt you whether to start again or to continue write from the interrupted point. This feature is applicable to all write conditions (writes by resurrectors, or manual writes through the DCC Read/Write page features). - added 3 buttons on Box Service page for quick access to the RIFF's manual PDFs; - fixed a not harmfull bug inside of the core reset (when NRST is applied) command sequence; - added feature: if write error appears and 'Ignore' is choosen, user can order software to apply 'Ignore' for further write errors automatically; - added standalone setup dialog for automatic write errors handling; - added BAD Blocks Handling feature using the following algo: If there are data chunks A B C & D to be written into blocks 1 2 3 & 4 respectively, and for example block 3 is found to be BAD, then software will write: data A -> into block 1 data B -> into block 2 --------> block 3 is bypassed (and marked as bad) data C -> into block 4 data D -> into block 5 It's clear that block 5 was not intended to accept the data D. Thus: - if block 5 had some other info then this info will be lost and will be overwritten with the data D. - if block 5 was free for use, then nothing bad happens. So, main conclusions: --------------------- 1. BAD Blocks Handling is IMPOSSIBLE (POINTLESS) for writting FULL images (user can chose only 'Ignore' option) 2. When writting data chunks of length less than full flash size user is prompted to select 2 options: a) Overlap (in example above this would mean to write data D into block 5) b) Cut Excess (in example above this would mean to not touch original 5th block's contents and just discard data D to be written) ************************************************************************************************************************************* NOTE: Bad block handling is allowed by default only through the DCC Read/Write page write. ----- Old Resurrector DLLs were not adapted for this feature, thus Bad Block handling will be implemented only in new DLLs. If you meet a Bad Block Error during resurrection contact support in order to update DLL to a Bad Blocks adapted version. ************************************************************************************************************************************* - solved problem which caused update module to display files for download which were already up-to-date for cases when JTAG Manager was installed on FAT (FAT/FAT32) file systems. - very dangerous bug fixed: "Irnored" word misspelling is corrected to the valid "Ignored" one :) JTAG Manger 1.14 --------------------------- - Increased internal buffers size to support NAND devices with 4KB/256KB Page/Block size which makes possible now to run Samsung S8500 fully functional resurrector; - Added OneNAND 2K/4K pages size selection for DCC Loader setup in Custom Target Settings mode; (make sure you use latest OneNAND standalone DCC loaders; old OneNAND loaders may not start on the 1.14 JTAG Manager version); - Fixed: now OneNAND settings (in DCC Loader Settings) are not discarded to defaults on next software startup. - Improved presets loading sequence; - (SDK): exported new SUB_ID_SET_JTAG_SPEED function for resurrectors; Firmware 1.14 --------------------------- - code is optimized to avoid deadlocks in Cortex-A8 handling routines (deadlocks appear due to communication errors); - Cortex-A8 debug is now available in ARM/Thumb modes (use the GDBServer for this); - ARM946E core support is added (which is mostly a debug access to the CP15 coprocessor); - added new RESET type for ARM9xxx cores: HW_RESET - targets which have dedicated TRST can be halted at the very first instruction core executes after the system reset signal (NRST) was applied. Importance of this: if some harmfull/"unlucky" code is written to a boot zone of a device, which (code) on the device startup results in h/w blocking, jtag disabling, core resetting, etc., then connecting via JTAG to such target becomes an impossible task, since JTAG host has not enough time to halt the target before it becomes unusable by a harmfull code. Using HW_RESET type ensures the target's core does not execute even a single instruction after the reset signal (NRST) was applied. - removed bug which could cause deadlocks of box during a h/w script execution. JTAG Manger 1.13 --------------------------- - Added feature to display FLASH chip capacity information - Added feature 'Auto FullFlash size' to DCC Read/Write page for simplified Full Images reading/writting - Fixed DCC Loader Settings dialog - Added resurrector interface function 'GetChipSize' which now enables resurrector DLL to receive target's memory size for proper data selection for flashing (like in Huawei Modem E1550 64/128MB versions); Firmware 1.13 --------------------------- - fixed ARM9 core debug capabilities when core is in Thumb mode (when ARM9 core was entering debug from Thumb state some CPSR register's flags were lost, same was when core was leaving debug into Thumb mode); - FFFFFFEE instruction was added into HAS scripts processing module; JTAG Manager 1.12 --------------------------- - Added mutlichain options support for CMM scripts - Added advanced multichain setup ("Advanced..." in the TAP# field) - Added Cortex-A8 processor selection - Added BOX pinout button (which is placed on Resurrection page) Firmware 1.12 --------------------------- - Addedd Cortex-A8 core 16-bit and 8-bit bus read/writes (which are be used in scripts mostly) - Addedd CoreSight DAP ROM Table processing for automatic ARM core search. - Addedd advanced MultiChain selection (IRPRE, IRPOST, DRPRE, DRPOST) in case simple TAP number is impossible to select (like in OMAP850) - Addedd feature to set custom timeout after NRST is asserted back to high level (for backward compatibility default timeout for ARM9 is set to 10ms, for other cores - 0ms)