Nios® V/II Embedded Design Suite (EDS)
Support for Embedded Development Tools, Processors (SoCs and Nios® V/II processor), Embedded Development Suites (EDSs), Boot and Configuration, Operating Systems, C and C++
12690 Discussions

Creating SYSLIB sets all files read-only

Altera_Forum
Honored Contributor II
1,005 Views

For our project, all the Quartus/Verilog code is in one directory tree (C:\Verilog), and the NIOS C code is in another tree (C:\MyProject). (Running on Windows 2000.) 

 

In order to use the C2H accelerator, in the NIOS project we create a SYSLIB by referring to the PTF file under the other tree -- C:\Verilog\nios_0.ptf. 

 

When we then do a build, it sets all files under c:\Verilog to read-only. 

 

Then when we try to accelerate one of the C functions, and the build tries to re-compile the hardware description, it fails because everything is read-only. 

 

Is setting everything read-only the expected condition if you build a Syslib by referencing a PTF file in another directory tree? Should we combine everything into a single tree in order to support C2H accelerators? Is there another setting we can change to fix this? 

 

Thanks for any assistance. So far C2H has been annoying!
0 Kudos
0 Replies
Reply