You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I'm trying to run the Aquila release of cFS.
I've installed the following:
cFE 6.7.0, CFS_CI-1.5, CFS_IO_LIB-1.5, CFS_TO-1.5, osal-5.0.0, PSP-1.4.0, SCH-2.2.2, cFS-GroundSystem-2.2.0-rc1
Issue
When I build the software the sch_def_schtbl.tbl and the to_config.tbl time are not loading.
What I've tired
I've looked at issue #7 (#7 ). In that solution the assumption is that the files are being generated but placed in the cf folder. In my case there are no .tbl files being generated at all.
I've looked through the hidden cf folder located in [...]build/exe/cpu folder and the only item that appear is the cfe_es_startup.scr ci.so, io_lib.so, sample_app.so, sample_lib.so, sch.so, to.so.
I've tried using the elf2cfetbl tool to build the *.tbl files but it doesn't seem to work.
I followed the instructions in the README.txt file and the system is still unable to find the tool in the tools folder
I may also have an issue with seeing the correct error call outs.
I'm unsure of what to try next.
The text was updated successfully, but these errors were encountered:
JALondonSpace
changed the title
sch_def_schtbl.tbl not generate at all
sch_def_schtbl.tbl not generated at all
Aug 17, 2022
I've found the problem.
I forgot to add the add_cfe_tables( ) function in the CMakeLists file.
The table files are now generated but still end up in the cf folder and not the cf/app folder. I'll update the sch_platform_cfg.h file to fix this, I'm unsure of how to fix this mismatch for the to application.
Hello,
I'm trying to run the Aquila release of cFS.
I've installed the following:
cFE 6.7.0, CFS_CI-1.5, CFS_IO_LIB-1.5, CFS_TO-1.5, osal-5.0.0, PSP-1.4.0, SCH-2.2.2, cFS-GroundSystem-2.2.0-rc1
Issue
When I build the software the sch_def_schtbl.tbl and the to_config.tbl time are not loading.
What I've tired
I may also have an issue with seeing the correct error call outs.
I'm unsure of what to try next.
The text was updated successfully, but these errors were encountered: