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++
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
12748 Discussions

Extracting Used HAL Library Files

Altera_Forum
Honored Contributor II
1,636 Views

I am currently working on a project that is to be certified to level C per DO-178b by the FAA. In order to do this, all of the source files that are used in the compilation of the program need to have project requirements associated with them. I am looking for an easy way to extract all of the library files used into a separate singular project (not using the associated syslib project). This way I can have a project that contains only source files I need that is not managed in anyway by the NIOS II syslib environment. Does anyone have suggestions on how to extract the library files that are used? Or at least a list of all used files and their locations? Life becomes much easier for me if I can build the same project without the IDE managing the syslib for me. I am currently using NIOS II IDE Ver 9.0SP2. Thanks in advance!

0 Kudos
5 Replies
Altera_Forum
Honored Contributor II
961 Views

you are talking about listing all the Nios II GCC newlib library files, and all the HAL driver source file for you project. I don't think this is an easy process.  

 

If you really need this, read the makefile in your syslib & project directory.  

Or upgrade to Version 9.1 and read the makefile in your BSP & APP folder. 

_www_.altera.com/products/ip/processors/nios2/tools/ni2-development_tools.html_
0 Kudos
Altera_Forum
Honored Contributor II
961 Views

Yeah, that is exactly what I am looking to do. I suspected that it wasn't trivial but was hoping otherwise. With 9.1, would the BSP project be any more help to me? Or for my situation, do the syslib and the BSP projects pose the same problems? I ask because I am not familiar with what organizational changes result from ditching the syslib project in 9.0 for the BSP project in 9.1.

0 Kudos
Altera_Forum
Honored Contributor II
961 Views

Using the BSP flow would be easier. As one of the first steps in the build process, the BSP flow copies necessary source files into the BSP directory before building. As a result, I think you get much closer to what you're looking for. Additionally, once you've gone through the flow once, you "own" it....it's just a Make-based project. 

 

Cheers, 

 

- slacker
0 Kudos
Altera_Forum
Honored Contributor II
961 Views

Great. I think I'll upgrade to 9.1 and give the BSP route a try. Thanks kee020041 and slacker for the helpful info.

0 Kudos
Altera_Forum
Honored Contributor II
961 Views

I am still attempting to strip out all of the Nios II GCC newlib library files and HAL driver files for certification purposes and have run into a brick wall. There are two files included in the project that are called lib2-divmod.c and lib2-mul.c that have a few# includes (tconfig.h, auto-host.h, tsystem.h, coretypes.h and tm.h) that do not exist anywhere. Does anyone know anything about these header files? From my research it seems that these are either part of a .a file somewhere or they are transient files that come and go upon building a project (mkconfig.sh??). Any insight anyone can lend would be greatly appreciated.

0 Kudos
Reply