interfaces communications
149 TopicsHow to install the Windows* Subsystem for Linux* (WSL) on Windows* OS?
Description Starting with the Nios® II EDS in the Intel® Quartus® Prime Pro Edition Software version 19.2 and Intel® Quartus® Prime Standard Edition Software version 19.1, the Cygwin component in the Windows* version of Nios II EDS has been removed and replaced with WSL. Resolution The procedure for installing WSL is: Follow standard instructions from Microsoft® to install Ubuntu* 18.04 LTS for WSL. Refer to https://docs.microsoft.com/en-us/windows/wsl/install-win10. The recommended OS would be Windows* 10 build version 16215.0 or higher. NIOS II currently does not support WSL 2. Remember: In Windows Features, ensure to turn on the Windows Subsystem for Linux option. After the installation is successful, launch the Ubuntu 18.04 app. Install the additional distro packages that are required for Nios® II EDS using the following commands: a. sudo apt update b. sudo apt install wsl c. sudo apt install dos2unix d. sudo apt install make e. sudo apt install build-essential Note: Ensure that all package dependencies, repositories lists, and Internet connections for WSL are set correctly. For Nios II Command Shell, launch the Windows executables of the command line tools by adding ".exe" (for example eclipse-nios2.exe or jtagconfig.exe). Nios II BSP and application projects from the previous Intel Quartus Prime release are not compatible with the WSL solution. You are required to regenerate your projects. This information now included in the Nios II Software Developer Handbook1.3KViews0likes0CommentsWhat is the Adjusted Peak Performance (APP) for the Nios II Processor?
Description APP is an adjusted peak rate at which "digital computers" perform 64-bit or larger floating point additions and multiplications. APP is expressed in Weighted TeraFLOPS (WT), in units of 10**12 adjusted floating point operations per second. Below is an outline of how the "APP" is calculated : n number of processors in the "digital computer" i processor number (i,....n) ti processor cycle time (ti = 1/Fi) Fi processor frequency Ri peak floating point calculating rate Wi architecture adjustment factor 1. For each processor i, determine the peak number of 64-bit or larger floating-point operations, FPOi, performed per cycle for each processor in the "digital computer". Note: In determining FPO, include only 64-bit or larger floating point additions and/or multiplications. All floating point operations must be expressed in operations per processor cycle; operations requiring multiple cycles may be expressed in fractional results per cycle. For processors not capable of performing calculations on floating-point operands of 64-bits or more the effective calculating rate R is zero. 2. Calculate the floating point rate R for each processor Ri = FPOi/ti. 3. Calculate APP as APP = W1 x R1 W2 x R2 … Wn x Rn. 4. For "vector processors", Wi = 0.9. For non-"vector processors", Wi = 0.3. The first determination an exporter must make is whether the computer is capable of performing 64-bit or larger floating-point arithmetic. If it is not, the WT value is zero. The APP (Adjusted Peak Performance) for a single Nios II processor equals 0, since the Nios II does not have native 64-bit floating point support. However, keep in mind that the APP should be considered somewhat of a systems metric, and its value is dependent on how the overall system is designed. For example, if you create a custom instruction to add 64-bit floating point support to a single Nios II, or if you were to use multiple Nios II's on your chip to build 64-bit floating point support, or if you add multiple FPGAs to your board each with a different memory for the processors in it to create 64-bit floating point support, then, you would probably end up with a different non-zero APP value for each case. Therefore, due to the many possible variables that need to be considered in the APP calculation that are outside of Altera's direct knowledge or control, the actual APP value for an end system can only be correctly calculated and determined by the designer or user of the particular system. But for most designs solely composed of Nios II processors, the APP should usually be well below the 0.75 WT (Weighted Tera-Flops) value that the United States Department of Commerce is worried about. For more information, refer to the "Practitioner's Guide To Adjusted Peak Performance" document, which is provided by the United States Department of Commerce Bureau of Industry and Security: http://www.bis.doc.gov/hpcs/app-wtpractitionersguidefeb22with-cover.pdf500Views0likes0CommentsNios® II Boot from EPCQ or EPCS in Quartus® II 13.1
Description Due to a problem in the Quartus II software, the Quartus Programmer must be used to program EPCQ devices using a generated .jic file in order to enable 4 bytes addressing mode. The nios2-flash-programmer is then required to program the EPCS/EPCQ device with the .flash file generated by the sof2flash tool in order to include the header information required by the new Nios II bootcopier. The new Nios II bootcopier introduced in Quartus® II 13.1 requires a new work flow. Resolution To enable the Nios II processor to load software from EPCS / EPCQ after power cycle or reset in the Quartus II software version 13.1 and later follow the steps below: 1. Add the following 2 lines in your <project>.qsf file. a. set_global_assignment -name STRATIXV_CONFIGURATION_SCHEME "ACTIVE SERIAL X1" b. set_global_assignment -name ENABLE_INIT_DONE_OUTPUT ON 2. Delete the “db”, “incremental_db” and “qsys generated folders” in your project directory. 3. Make sure the Nios II’s Reset Vector is pointing at EPCS/EPCQ Controller. 4. Make sure the Nios II’s Exception Vector is pointing at onchip_memory or some other memory devices. 5. Generate in Qsys. 6. Compile in Quartus II. 7. Note: If the design is not targeting EPCQ device, skip this step Generate the .jic file with “Convert Programming File” tool. a. Select .jic file for “Programming file type”. b. Select the correct EPCQ device for “Configuration device”. c. Make sure “Active Serial” is selected for “Configuring device mode”. d. Click on “Flash Loader”, then click on “Add Device” to select the device you’re using then clicks “Ok”. e. Click on “SOF Data”, and then click on “Add File” to select the .sof file generated by Quartus II compilation. f. Click on the .sof file you have just added, click on “Properties” and enable the “Compression” from there. g. Click on “Generate” to generate the .jic file. h. Program the EPCQ with the .jic file generated with Quartus Programmer and power-cycle the board. 8. Generate the .flash files for the .sof and .elf files with: a. sof2flash --input=hw.sof --output=hw.flash --XX –verbose Note: Replace XX with EPCS for EPCS device and replace XX with EPCQ for EPCQ device b. elf2flash --input=sw.elf --output=sw.flash --epcs --after=hw.flash –verbose 9. Use nios2-configure-sof or Quartus Programmer to configure the FPGA with the .sof file then program the EPCQ device with the Nios II Flash Programmer as follow: a. nios2-flash-programmer --epcs --base=<base address of EPCQ device> hw.flash Note: The EPCQ need to be programmed with the .flash file even if it had been programmed with Quartus Programmer earlier in .jic format b. nios2-flash-programmer --epcs --base=<base address of EPCQ device> sw.flash500Views0likes0Commentsnios2-elf-gcc.exe: error: CreateProcess: No such file or directory
Description Due to a recent Windows update from Microsoft®, the Nios® II build flow using Windows Subsystem for Linux (WSL) is presenting issues during project compilation and download. The failure has been identified in computers running Windows 10 Version 1903 and later. The failure is not presented in Windows 10 Version 1809 or earlier. Some of the error messages include: nios2-elf-gcc.exe: error: CreateProcess: No such file or directory nios2-elf-g .exe: error: missing argument to '-msys-lib=' wslpath: /...........elf.srec: No such file or directory Resolution Patches to fix this problem are available for the Intel® Quartus® Prime Pro and Standard Editions. For Pro versions: Download patch for Intel® Quartus® Prime Pro Edition Software version 20.3 Download patch for Intel® Quartus® Prime Pro Edition Software version 20.2 Download patch for Intel® Quartus® Prime Pro Edition Software version 20.1 Download patch for Intel® Quartus® Prime Pro Edition Software version 19.4 Download patch for Intel® Quartus® Prime Pro Edition Software version 19.3 Download patch for Intel® Quartus® Prime Pro Edition Software version 19.2 For Standard versions: Download patch for Intel® Quartus® Prime Standard Edition Software version 20.1 Download patch for Intel® Quartus® Prime Standard Edition Software version 19.1 This problem is fixed starting with the Intel® Quartus® Prime Pro Edition Software version 20.4 and the Intel® Quartus® Prime Standard Edition Software version 20.1.1.399Views0likes0CommentsNicheStack TCP/IP Stack - Nios II Edition Does Not Support TFTP
Description The Nios II documentation should include the following information: Versions of the NicheStack TCP/IP Stack other than the Nios II Edition include optional Trivial File Transfer Protocol (TFTP) client and server applications. However, the TFTP client and server are not thread safe. They cannot be used in systems with the MicroC/OS-II RTOS. TFTP is not available with the NicheStack TCP/IP Stack - Nios II Edition. The TFTP client and server features are disabled.399Views0likes0CommentsWhy does printf() not return when using a JTAG UART as the stdout device in a Nios II system?
Description If a host-side (PC host) is connected, there is no problem. However, if the host-side is disconnected, there are two reasons why printf() would block: 1. The user is using a reduced ("small") device driver. - Checkbox for "Reduced device drivers" is checked in System Library Properties page in the Nios II IDE. - The reduced device driver assumes that the host-side is always connected. 2. The user is using the default device driver, for the JTAG UART, but has no "system timer" defined (In the SOPC Builder system/In the System Library properties page). The default device driver does support "device/jtag_uart timeouts", but requires a "system timer" to implement this. Resolution: (If necessary) change to the default device driver and be sure that you have a system timer in your SOPC Builder system and defined in your System Library.300Views0likes0CommentsHow to compile the discontinued Nios® II processor IP core in future Quartus® Prime Software?
Description The discontinued Nios® II processor IP core is rendered unavailable in the Quartus® Prime IP Catalog after Last Time Shipments. Interested parties are encouraged to refer to the Nios® II Processor Product Discontinuation Notice (PDN2312). The recommended action is to implement Nios® V processor IP with equivalent functions in new designs. Alternatively, the discontinued Nios® II processor IP core supports design compilation with pre-generated IP files. Resolution On the Nios® II hardware flow: In the last Quartus® Prime Software version (that supports Nios® II processor IP core), Open the Platform Designer system. Click Generate HDL. Convert the Nios® II processor IP Core into a generic component. Select the processor. Navigate to the Component Instantiation tab. Select Implementation Type as Blackbox. Click Apply. Save the Platform Designer system . The system is ready for regeneration and recompilation in the latest or future Quartus® Prime Software (that does not support Nios® II Processor IP core). Note: Nios® II processor license is required in the Quartus® Prime software. On the Nios® II software flow: Nios® II Software Build Tools for Eclipse are last supported in, Quartus® Prime Pro Edition Software version 23.4, and Quartus® Prime Standard Edition Software version 23.1. Users must continue Nios® II software development (Nios® II Board Support Package and Application projects) in these software versions or earlier. Please take a look at the requirements and limitations to implement the workaround. You are required to, Preserve the Nios® II processor .ip file and its generated RTL folder (it should have the same name as the Nios® II processor .ip file). Preserve the SOPCINFO file. Configure the Quartus® Prime Software. Navigate to Assignment > Settings > Board and IP Settings > IP regeneration policy, select Never regenerate design files for IP cores. Upon Generating HDL, disable Clear output directories for selected generation targets in Generation > Output Directory. If quartus_ipgenerate command is applied, remove --clean or –clear_ip_generation_dirs. You are limited to, Fixed generic Nios® II processor component. Due to the preserved IP files, any changes made onto the Nios® II processor are not reflected. Fixed IP cores or connections to the Nios® II processor. This is to maintain the host-agent services between the Nios® II processor and other IP cores. Fixed Nios® II SOPCINFO files for BSP files generation. This is constrained by the above limitations.300Views0likes0CommentsHow can I migrate my Nios II processor design to the Nios II Gen 2 processor?
Description The Nios ® II Gen 2 processor is introduced in the Quartus ® II software version 14.0. A migration script is provided for users to migrate from the Nios II processor to the Nios II Gen 2 processor. Resolution To migrate your existing Qsys design to the Nios II Gen 2 processor, follow these steps: Download “nios2_gen2_migration.tcl" and put the script in your project directory Run Nios II Command Shell in Window system or Console in Linux System Browse to your project directory and run below command: qsys-script --script= nios2_gen2_migration.tcl --system-file=<qsys_file>.qsys Regenerate Qsys and recompile your project after appling the TCL script in Quartus II and run “generate bsp-editor” in Nios II EDS. Related Articles How can I migrate the Nios II processor /s core to an equivalent Nios II Gen 2 processor /f core ?299Views0likes0CommentsWhy does niosv-download fail with a non-pipelined Nios® V/m processor at JTAG frequency 24MHz or 16Mhz?
Description This issue may be seen in Quartus® Prime Pro Edition Software version 23.3 and later when downloading Nios® V processor software into a non-pipelined Nios® V/m processor. This is due to processor limitation, affecting the non-pipelined Nios® V/m processor only. Other processors below are not affected by this limitation: Pipelined Nios® V/m processor Nios® V/g processor Resolution To work around the problem, follow the steps below: 1. Use the command to set the JTAG clock frequency to 6Mhz: jtagconfig --setparam 1 JtagClock 6M 2. Re-download the Nios® V processor .elf file.299Views0likes0CommentsNios II GCC compiler options: -march, -mbmx, -mno-bmx, -mcdx, -mno-cdx
Description From nios2-elf-gcc 4.9.2 onwards the Nios® II GCC compiler supports new options: -march, -mbmx, -mno-bmx, -mcdx, -mno-cdx These options cannot be used with the publicly released versions of the Nios II processor and are set to off by default. These options are currently intended only for internal Altera use. Altera has developed a version of the Nios II processor with a modified instruction set encoding (known as R2) that is currently only intended for internal Altera use. Both the R1 (original) and R2 (new) instruction set encodings are supported by the same Nios II GCC compiler in order to streamline compiler development and maintenance. The Nios II R2 instruction set is largely assembly-language upward compatible with the Nios II R1 instruction set, but supports additional mandatory and optional instructions. Resolution The following GCC Nios II R2 compiler options/switches are currently only intended for internal Altera use: -march=<arch> This specifies the revision of the target Nios II architecture/ Instruction Set Architecture (ISA) R1/R2 to be used by the compiler. GCC uses this name to determine which instruction set it should use when generating assembly code. Permissible names are: ‘r1’, ‘r2’. The default setting is \'r1\'. The -march=r2 switch is also accepted by the Nios II assembler, for engineers who are assembling without using the compiler. The following switches require –march=r2 to be specified: -mbmx Enable generation of the architecture-optional Nios II R2 BMX (bit manipulation extension) instructions. -mno-bmx Disable generation of BMX instructions. This is the default. -mcdx Enable generation of the architecture-optional Nios II R2 CDX (code density extension) instructions. -mno-cdx Disable generation of CDX instructions. This is the default.299Views0likes0Comments