In-Target System Analyzer for Altera Nios =============== Overview =============== The In-Target System Analyzer is a hardware-based debugger that supports the Nios-16 and Nios-32 cores with OCI(tm) debugging extensions. The ISA-Nios In-Target System Analyzer works with On-chip Instrumentation (OCI) debugging extensions. Both on-chip and off-chip trace capabilities are integrated into the cores. The ISA-Nios system analyzer is contained in a compact chassis that connects to the target system using a standard 10-pin JTAG connector or 38-pin Mictor connector. The 10-pin version supports on-chip trace only. The Mictor version can support either on-chip or off-chip trace features. In off-chip trace capture mode, the system streams data off the SoC device and it is captured and stored in special hardware in the FS2 system analyzer. The system runs on a Windows® 98/Me/NT/2000/XP PC over an IEEE-1284 EPP/ECP high-speed parallel port or Altera ByteBlaster cable. It also runs on a Linux PC over an IEEE-1284 EPP high-speed parallel port or Altera ByteBlaster cable. Please contact FS2 for more information or assistance in selecting the System Analyzer product for your application. =============== MDILib Support for MDI Applications =============== The FS2 MDILib for Nios software allows a third-party source-level software debugger to interface with the FS2 In-Target System Analyzer for Nios cores. Contact FS2 for vendor support information. See the vendor's documentation for details on connecting to MDILib drivers. =============== Installation =============== To install the Windows version, run the setup program, setup.exe. If you have downloaded the software from FS2's website, the setup file will be called nios-XXXX.exe, where XXXX is the software version. Two different versions of the install exist. One is the developer's version which includes the MDI support files and documenation. The other version is the normal user's version which includes all the files needed to run the FS2 cli console. Which version is installed is determined by the entered password. The install first checks to see if Altera's SOPC builder is available and then prompts if you want the embedded FS2 files updated. Next it searches for codelab Debug and asks the update question. Then it asks whether you want the FS2 standalone console installed. Finally you are asked if you would like the Altera's jtagserver driver installed that allows use of the FS2 ISA-NIOS(/T) probe with Altera's Quartus. The Linux version is distributed as a password-protected ZIP file. If obtaining the software directly from FS2's website, first unzip the file using the password obtained from FS2. The setup file will be called nios-XXXX-install, where XXXX is the software version. Only one version of the install exists, the normal user's version. The install does not prompt for any questions, it copies all the files to /usr/local/fs2/nios2 and creates links in the Quartus directory to a shared library in /usr/local/fs2/nios2/lib. To setup the software, log in as 'root' and run the install program. For example: # ./nios-1970-install WARNING: The Linux installation alters the Quartus installation. You must first have a working version of Quartus 5.1 on your Linux system before running the FS2 install program. In particular, the FS2 install program 1) adds the symlink $QUARTUS_ROOTDIR/linux/libjtag_hw_fs2.so to /usr/local/fs2/nios2/bin/libjtag_hw_fs2.so, and 2) renames $QUARTUS_ROOTDIR/bin/jtagd to $QUARTUS_ROOTDIR/bin/jtagd-orig and adds a new version of the file $QUARTUS_ROOTDIR/bin/jtagd. =============== Getting Started =============== On Windows, there is an icon on the Start Menu, under the FS2 group, to the Getting Started manual. On Linux, the manual is installed by default in /usr/local/fs2/nios2/doc. It is in Abode PDF format. You should get familiar with the FS2 hardware by running through the Getting Started manual using the ISA-Nios Debugger Console. On Windows, the Console is accessible from the Start Menu, FS2 group. On Linux, the Nios 2 Console is accessible by running the clinios2 executable (installed by default in /usr/local/fs2/nios2/bin). NOTE: Each Linux user that wants to use the ISA-Nios Debugger with the Quartus SLD server must must have the environment variable QUARTUS_ROOTDIR set to the Quartus installation path (e.g., "export QUARTUS_ROOTDIR=/opt/altera/quartus5.1"). NOTE: Each Linux user that wants to use the parallel port must be added to the 'lp' group. For example, to add the user 'fs2' in Red Hat Linux, change the line in /etc/group from "lp:x:7:daemon,lp" to "lp:x:7:daemon,lp,fs2". =============================================================== Updating your FS2 Nios /T probe for the latest Nios II features =============================================================== * Start the FS2 console using the NIOS II bash shell "nios2-console" command. * Issue the following commands: closeport openport lpt1 * Click the Yes button to update the hardware and when the update is complete, type Exit. Then power cycle the FS2 box. =============== Release Notes =============== Version 1.9.8.0 --------------- - Rohs SNAV probes require a different jnet_niosx.flash. - Fixed bug in calculating timestamps if trace background process is stopped before it can finish. Version 1.9.6.3 ---------------- - MdiDoCommand no longer requires CBOutput to support "one way" control - hwinfo output changed to better display connection type information - Install now creates fs2.ini if none exist. - Fixed problem with trigger window not correctly knowing which triggers the hw is curently supporting. Version 1.9.6.2 ---------------- - Fixed a problem with the trigger window and the usb-blaster connection. - Added support to updating EDGE with the install. - New Mdi routines added to allow mdi clients to get/set possible connection types without having to call a *foreign* dialog box (i.e. MdxFs2ConnectDialog). See mdxfs2nios.h. Version 1.9.6.1 ---------------- - Sysnav connections now use download drivers, memory accesses are now 4 times faster! - MDISetBp now supports MDIBPT_HWInstruction breakpoints with trace on/off actions. - Sysnav-sld connections now work without the flushDelay added in previous release. - With Quartus 4.2SP1 and Quartus 5.0, clearing of the performance counter values is broken (perfmon clear). User must use a reset command to clear the counter value. Version 1.9.5.3 ---------------- - Driver files not being installed in 1.9.5.1 - Fixed problem with NIOS II IDE and the automatic connection type. - Added NIOS II Evaluation board type to MdxFs2ConnectDialog - To get sld-sysnav connection working with NIOS II IDE there's a new fs2.ini entry "FlushDelay" that adds delays to the sysnav jtagserver driver. This is only needed for the NIOS II IDE so the install will add "flushDelay=0" to fs2.ini. For NIOS II IDE flushDelay=5 is needed. Version 1.9.5.1 ---------------- - Several missing sysnav support files missing from 1.9.5.0 Version 1.9.5.0 ---------------- - Added support for sysnav usb and ethernet connections. - Changed the Fs2MdiConnectDialog to include these new connections. Version 1.9.4.0 ---------------- - Fixed trace full then halt problem of frame count changing. - Fixed some trigger presenter issues. Version 1.9.3.5 ---------------- - when using the ISA-Nios II or ISA-Nios II /T probe with the Altera Nios II IDE, be sure to check the “Trace and watchpoint support via FS2 console window” checkbox in the “Debugger Options” area of the Debugger tab pane of the Debug window. For more details refer to section 6.1 of the Nios2-HW-Reference.pdf manual. - a bug exists in the Performance Monitor hardware. When the event selection is "Hit Data Breakpoint 0" or "Hit Data Breakpoint 1" for either Counter 1 or 2, the hardware counts three times the number of actual events that occur when the event is defined as a write cycle to peripheral memory (Avalon bus). (The mis-count does not occur for other memory spaces or for peripheral read cycles). - Altera's system.h file format changed slightly, modify peripheral window files to handle both old format and new. - Documenation changes to match Altera's 1.1 release changes. - Changed how trace interrupt messages are handled. Version 1.9.3.4 ---------------- - Shortened polling timeout for MR when using an sld connection to timely handle a dead cpu. - Added SP1 features to testmdinios?.exe - Fixed some issues in mdi that mdi testing found. - Trace Window: format changes and fixed search errors. - Tk window settings saved to fs2.ini are not restored until window is opened. Memcache is the only exception. - Documentation changes including splitting up manuals. Version 1.9.3.3 ---------------- - Tk window fixes. - Low level trace find changes. - Added SW to handle switching hw trigger state back to level 0. - With memcache support dq'r can now print trace while still emulating. Version 1.9.3.2 ---------------- - Added SP1 features. This includes: off-chip stop trace when full off-chip timestamp support cli/abi/mdi support for trigger sequencing trace search execution triggers - MDI clients should use new MdxFs2SetBp routine to set breakpoints. - Include fixes from 1.9.2.3 Version 1.9.2.3 ---------------- - Undid change #2 of 1.9.2.2 so cli window isn't visible to users if console option off. - Allow altlptx connections for ByteBlaster type in MdxFs2ConnectDialog dialog box. - Added USB support for NIOS II. Version 1.9.2.2 ---------------- - Combined nios and nios2 sections in the fs2.ini file. Just use the nios section. - Changed how the mdi connects to the target when the fs2 console is requested. - Fixed the problem some PCs were having with nios2-terminal and fs2 mdi connections with eclipse using the fs2-sld connection. Version 1.9.1.1 ---------------- - Gray out non supported NIOS2 members of the MdxFs2ConnectDialog. Version 1.9.0.9 ---------------- - Removed different trace view options from trace window. Only dasm mode is now supported. - More documentation changes. - Link to Getting Started manual added under console's help menu. Version 1.9.0.8 ---------------- - Change default symbol file extension back to .fs2. - Fixed some problems with the off-chip trace and sld/FS2 connection. - Added three different sld connect options to MdxFs2ConnectDialog. Version 1.9.0.7 ---------------- - Paired data triggers no longer need license. - Change default symbol file extension to .objdump. Version 1.9.0.6 ---------------- - Include user.tcl in startup procedure. - Updated documention. Version 1.9.0.5 ---------------- - This is a NIOS2 windows only release. - Onchip trace is now supported. - Memory caching added including a presenter. - Changed sld memory reads to use AJI batch processing. - Updated documention. Version 1.9.0.4 ---------------- - Initial release of Linux port of FS2 cli console and MDILib (NIOS 2 only). - This is a Linux-only release. - ByteBlaster connection from FS2 cli is supported. - Parallel port connection from FS2 cli to FS2 probe is supported. - Connection to the FS2 probe directly from Altera JTAG server is not yet supported. Version 1.9.0.3 ---------------- - sldDev/node ini entries now *updated* by connect routine. - OCI monitor changes to work better with fast download. - OCI monitor now initializes the caches if return address matches reset address. Version 1.9.0.2 ---------------- - NIOS 2 release only. NIOS not tested! - sldDev/cable/node ini entries *updated* by connect routine. - PM support added. New cli command "perfmon" and new performance monitor GUI "perfmonwindow". Version 1.9.0.1 ---------------- - Release of NIOS with all branch changes merged in. Includes: - Fixed problem with flash operations using usb connection - Sld with fs2 probe should work for all TDO positions. - Extended Mdi functions renamed to MdxFs2... (old names left for backwards compatibility issues). fs2.dll renamed fs2nios.dll (again fs2.dll still around for now). - Added fs2.ini entry "memoryaccesssize" to allow MDI clients to specify the accessSize outside the MdiWrite/Read objSize. Version 1.8.0.X (Internal NIOS II releases) ---------------- ... Version 1.7.5.4 --------------- Usb performance increases. Fixed problem with openport sld with fs2 probe with MAX. NOTE: This solution will only work when the non-selected device is the one closest to TDO on the chain (as is the case with the MAX switched in on the Apex board). This will not work when the non-selected device is in any other position. This note only applies to AJHI driver related connections (i.e.: sld with fs2 probe). Version 1.7.5.3 --------------- Full support for openport sld with fs2 probe. Modifications to Installation procedure. Added usb support. Version 1.7.5.2 --------------- Improved handling of multiple Nios cores in a chain of jtag devices. Improved MDI data breakpoint masking. Revised installation procedure to include third party debugger updates. =============== Contacting FS2 =============== Please contact FS2 with any comments or questions: First Silicon Solutions, Inc. 4000 SW Kruse Way Place, Bldg 3, Suite 210 Lake Oswego, OR 97035 (503) 489-0311 voice (503) 489-0315 fax http://www.fs2.com Sales support: info@fs2.com (503) 489-0311 Technical support: support@fs2.com (503) 489-0311 x104 Copyright (c) 1998-2004 First Silicon Solutions, Inc.