ContributionsMost RecentMost LikesSolutionsRe: Nios II Software Build Tools for Eclipse (Intel Quartus Prime 22.1 std lite edition) Installation re Okay... Have you tried something along the lines of what's described here: https://www.annabooks.com/Articles/Articles_FPGA/Intel-FPGA-Tools-Setup-Rev1.1.pdf It seems to have pretty thorough coverage for what you're attempting to do....I know it's not for exactly the version you're attempting to use, but as Nios V existed by then...I doubt the instructions have changed much between the versions in the linked PDF and what you're attempting to do (perhaps, a more recent version of Eclipse, etc., but otherwise it should look very similar). BTW, does it work to build (and run) via the command line? On any platform I'm testing, I check to ensure the CLI works before I attempt to bring up and IDE. At the CLI, I can debug low-level things like JTAG connectivity (using "jtagconfig -d" for example) and (for Nios II) make use of nios2-download and nios2-terminal. You can access most (if not all) necessary commands by entering a "Nios II Command Shell". It sets up your $PATH so that all the Nios II commands are accessible as well as some common Quartus II commands. With respect to your specific question...yes, I suppose a "funked up" WSL installation could cause issues. I think it makes sense to get CLI "stuff" working, first, and then move onto using the IDE (Nios II SBT for Eclipse). Regards, Andor Re: Nios II Software Build Tools for Eclipse (Intel Quartus Prime 22.1 std lite edition) Installation re Hi Manu30, I can't directly relate to installation on Windows or the particular version that you are using, but I have gotten the Nios II IDE to function in Linux with the 23.1std version of the tools. I would recommend updating to that version...if you can... As an additional note, I'd recommend using Nios V for any designs. It's supported going forward. Nios II is deprecated and, frankly, hasn't had adequate support for the better part of 10 years. I'd only use Nios II, these days, if it were my only option. Can you point to exactly which installation instructions you tried to follow please? I might have to rope someone in who actually uses Windows to help on the "funky" Windows installation fun. Best Regards, Andor Re: NIOS is big or little endian Okay. It's still a deprecated core and I wouldn't recommend using it, unless....you have no other option. Period. With respect to Endianness, the BSP generation will follow what you've set in the system. If you configured your Nios II to be Big Endian, then the BSP will follow suite and be Big Endian...automatically. - There should be an option in the Nios II component when instantiating it to choose Endianness. - I'm not setup to test it myself (and have no time to do so), but I do see it in the "altera_nios2_hw.tcl" files for both the "classic" and "gen2" versions of this softcore IP though. These reside in the ..../ip/altera/nios2_ip/altera_nios2 and .../ip/altera/nios2_ip/altera_nios2_gen2 subdirectories. There is also an option during BSP generation to override the "auto endian match" behavior with an option called This is in the NIos II Software Developer's Handbook. As it has been a LONG time since I've worked with this stuff and I have no incentive to do so any longer, I just cannot recall how it all works and have ZERO desire to revisit it! I do know that Big Endian was never as well tested or supported as Little Endian on Nios II, so... GOOD LUCK if that's that path you choose or must choose. 😉 Regards, Andor Re: NIOS is big or little endian Hi ZhiqiangLiang, [Update: noticed you tagged Nios II. That's deprecated IP. I recommend against starting a new project using it!] Nios V is Little Endian. Regards, Andor