Fido Release Notes Version 1.5.3.12 23-MAR-10 ------------------------------ 1. Copyright and Legal notice changed. 2. Fixed the bug in XTIv3 protocol receiver that caused it to receive garbled data on specific clock frequencies. Specifically, if interval between two nibbles appeared to be 90...110ns, next 1...2 nibbles were received garbled. That in turn lead to occasional errors in trace messages. 3. Fixed the bug in C-STI protocol receiver that caused it to receive garbled data after the Fido had detected a pause exceeding "Maximal pause between message components" in hardware level "STM MCU Command Write" message. 4. Changed the behavior of Fido when it forwards data from external application command connection to traced device. Note that data can't be sent to traced device if external application has not opened the data connection and does not download traces actively from Fido. So, to successfully send the data to traced device, the application has to open data connection first before it starts sending. From now on, when external application reserves data connection and starts to send data to traced device immediately after that via command connection, the command connection (incl. data sending to traced device) will block until the reserved data connection becomes actually opened by external application. 5. Behavior of the command connection is changed in situations when there is too much data to send to external application(s). Previously some alert messages (i.e. Fido state change notifications) might become skipped for particular application if application's TCP/IP buffers overfilled (i.e. application read too slowly from command connection). Now, in such situations, Fido generates pseudo alert messages instead of skipped ones to guarantee that external application can still keep track to what state the Fido has finally changed. 6. Fixed some bugs in Fido box synchronization which caused invalid timestamps when one of the synchronized Fido boxes was connected to a different PC. 7. Fixed some bugs in command handling. Known problems: 1. Two Fido boxes connected to two PC-s and used by Fido SW running on a third PC will not synchronize correctly when automatic target protocol detection is used. The value of the synchronized timestamp may jump back or forward when automatic protocol detection causes Fido boxes to simultaneously reinitialize. This kind of setup (and probably other setups that use at least three PC-s) should thus be avoided, or used with fixed protocols. Version 1.5.2.145 23-FEB-10 ------------------------------ 1. No change in functionality. Copyright and Legal notice fixed. Version 1.5.1.10 03-FEB-10 ------------------------------ 1. Possible deadlock condition in Musti (i.e. Fido predecessor) type commands handling is fixed. The bug was relevant to all the previous Fido versions. Version 1.5.0.1 02-FEB-10 ------------------------------ 1. Support for Fido predecessors' protocols such as STI, C-STI and ST-XTI is added. 2. Fido XTIv3 interface supports 3 calibration modes. a) Calibration OFF. This is default mode and it assumes that target outputs high quality center sampled PTI interface signals. b) Manual calibration. In this mode, user can correct target signals integrity problems (deviations from so called center sampled interface) manually by specifying the most reliable data sampling points himself. c) Auto-calibration. In this mode the Fido itself selects the best data sampling points. In all 3 modes, maximal supported PTI clock frequency is up to 200MHz, though, in calibration OFF mode the targets are expected to limit with much lower frequencies due to signal integrity problems. 3. Traces can be stored in file directly from Fido without relying on external download application. 4. Default XTIv3 STP Endianness is changed from little endian to big endian. It's expected (and suggested) that most targets use big endian STP endianness. This is also in harmony with Fido predecessors settings. 5. Very first variant of Target Emulator support is implemented. Target Emulator is meant to be a (software) module that uses TCP/IP connection instead of physical PTI interface for transferring the trace data to Fido. 6. 2 rank SODIMMs are supported in Fido box (in previous versions, only 1 rank SODIMMs were supported). 7. Fido box new USB driver (version 1.0.0.11) supports both 32 and 64-bit Windows systems. Fido software installation utility checks the system and sets up the appropriate driver files. Fido software itself is a 32-bit program but is fully compatible with a 64-bit operating system. Version 1.3.4.143 08-Sep-09 ------------------------------ 1. Fido box input circuitry reset bug is fixed. See known problems in Fido version 1.3.3.131 For detailed bug description. Version 1.3.3.131 31-Aug-09 ------------------------------ 1. In Fido boxes, the XTIv3 data processing occasionally stalled. Typically this happened during huge interleaved STP burst from different STP Masters/Channels. Fixed in this version. 2. After detecting the "Maximal pause between message components" (default value 100ms) pause in STP packets stream, Fido started to wait for arrival of new STP Master packet, discarding all other packets before that. Note that by STP v1 specification, STP state machine must insert Master packet into STP stream after passing its IDLE state (i.e. after long pause). It was found that some targets do not follow STP v1 specification and do not repeat Master/Channel packets after long pauses. This Fido version is updated to work with such targets as well and now it accepts all incoming STP packets following the pause. If first packet is not Master packet, previous master/channel is assumed. Note that to start tracing, Fido still waits for very first STP Master packet and it discards silently all the other STP packets before that, i.e. Fido does not output traces until it is able to determine the source (master) of trace messages. Fido restarts tracing (waits for STP Master packet) each time it detects the target is (re)attached, i.e. interface reference voltage has dropped to 0V between. 3. Occasionally it was impossible to switch from XTI v2 tracing to XTI v3 tracing - overloading XTIv2 FPGA image in Fido box with XTI v3 image failed occasionally. Fixed in this version. 4. Potential memory corruption bug in Fido software (in XTI v2 and XTI v3 traces processing) is fixed. 5. Several minor Fido Control Panel fixes. 6. Significant improvement of XTI v3 processing. Depending on circumstances, load on CPU is decreased about 30% (from 16% CPU usage to 11% on same throughput). Known problems: 1. When the pause in STP (XTI v3) or XTI v2 stream exceeds the "Maximal pause between message components" setup parameter value (by default 100ms), Fido box resets its input circuitry. Any data arriving to Fido during the next "Minimal pause needed for resynchronization" time period (by default 1ms) is silently ignored. It means that if the pause between STP packets or XTI v2 messages happens to fall exactly into this period (100...101ms by default), the tracing will fail. Version 1.3.2.4 06-Jul-09 ------------------------------ First public Fido release.