Nios® II Embedded Design Suite (EDS)
Support for Embedded Development Tools, Processors (SoCs and Nios® II processor), Embedded Development Suites (EDSs), Boot and Configuration, Operating Systems, C and C++
Announcements
Intel Support hours are Monday-Fridays, 8am-5pm PST, except Holidays. Thanks to our community members who provide support during our down time or before we get to your questions. We appreciate you!

Need Forum Guidance? Click here
Search our FPGA Knowledge Articles here.
12452 Discussions

nios project for cycloneIII starter board

Altera_Forum
Honored Contributor II
1,020 Views

Does anyone have instructions for building the fpga image for the nios example for the cyclone 3 starter board. 

I can build the 'my first fpga' image (not tried to download it). 

qsys has converted the sopc file, but I can't generate the fpga image - I think loads of files are missing, starting with sys_pll.v. 

The altera doc assumes you are going to run a pre-built image. 

I was hoping to use it to write/test some custom instructions. 

Using a small dev board will give much faster complatioon times that using one of our own boards. 

 

FWIW I'm hoping to run on linux (rather than windows), the tools (13.1.1) seem to be running fine - apart from the qsys window 

not being movable from the top left corner!
0 Kudos
2 Replies
Altera_Forum
Honored Contributor II
141 Views

The main project is missing all the qsys generated files.... 

 

It looks like all the [file join $::quartus(qip_path) "foobar"] are failing as if qip_path has never been set. 

Perhaps a problem with the conversion of the project from 'sopc' to 'qsys', maybe an issue with case sensitive filenames (some strings have "SOPC" others "sopc"). 

I'm not sure what would set qip_path, the only references I can see are in 'file join' requests.
Altera_Forum
Honored Contributor II
141 Views

Solved by getting one of our HW guys to convert the project to 13.0 on a windows system and then copy the files over. 

 

I've also managed to move the qsys window from (0,0) - the 'workspace switcher' will let you move the window even though its title bar is hidden being the ubuntu window managers global title bar. 

I guess that the window is being explicitly placed at (0,0) instead of letting the window manager choose the location.
Reply