On Fri, 8 Feb 2019 at 08:34, Chris Johns <chr...@rtems.org> wrote: > On 8/2/19 9:13 am, Vijay Kumar Banerjee wrote: > > On Fri, 8 Feb 2019 at 00:15, Chris Johns <chr...@rtems.org > > <mailto:chr...@rtems.org>> wrote: > > > > On 7/2/19 7:17 pm, Vijay Kumar Banerjee wrote: > > > I'm trying to do this ... > > > > > > =========== > > > diff --git a/tester/rtems/testing/bsps/leon3-sis-cov.ini > > > b/tester/rtems/testing/bsps/leon3-sis-cov.ini > > > index d60257c..e450b60 100644 > > > --- a/tester/rtems/testing/bsps/leon3-sis-cov.ini > > > +++ b/tester/rtems/testing/bsps/leon3-sis-cov.ini > > > @@ -38,4 +38,4 @@ tester = %{_rtscripts}/run.cfg > > > target = sparc-rtems5 > > > bsp_run_cmd = > %{rtems_tools}/%{bsp_arch}-rtems%{rtems_version}-sis > > > bsp_run_opts = -leon3 -nouartrx -r -tlim 200 s -cov > > > -bsp_covoar_cmd = -E %{cov_explanations} -f TSIM > > > +bsp_covoar_cmd = -S %{bsp_symbol_path} -p %{project_name} -E > > > %{cov_explanations} -f TSIM > > > > Can the common options be moved to coverage part of qemu.cfg? > > > > Since I'm trying with the sis. I added it to the run.cfg like this > > > > # > > # Coverage > > # > > %if %{defined coverage} > > %define covoar_cmd -S %{bsp_symbol_path} -p RTEMS-%{rtems_version} -E > > %{cov_explanations} > > %endif > > > > Ahh, I wonder if this should be in a coverage.cfg file you include and > this way > it can be shared? > > That's a good idea.
> > > When I print the macros from the config.py I see this macro created like > this... > > > > coverage: 'none' 'none' '1' > > covoar_cmd: 'none' 'none' '-S > > > /home/lunatic/development/rtems/rtems-tools/tester/rtems/testing/coverage/leo > \ > > n3-sis-symbols.ini -p > RTEMS-5 -E > > /home/lunatic/development/rtems/rtems-tools/tes \ > > > > ter/rtems/testing/coverage/Explanations.txt' > > > > The only problem now is to expand it from coverage.py which is giving > error. > > If I print the macros list from the coverage.py , I see that the list is > missing > > this and some other macros. How to get the 'complete' list of macros? :/ > > Sorry I am not sute, can you see the config object from the coverage code? > > I would need to review the code and figure it out and I do not have the > time. > > I can attempt to figure it out with some help :) Meanwhile, do we want to push this patch in the current working state, with the options added to the BSP file? I will send a v3 of this patch with the changes. Chris >
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel