Hi,
On Wed, Aug 24, 2022 at 11:58 PM Xiang Xiao
wrote:
> On Wed, Aug 24, 2022 at 11:38 AM Nathan Hartman
> wrote:
>
> > On Tue, Aug 23, 2022 at 8:33 PM Alan Rosenthal >
> > wrote:
> >
> > > Hello NuttXers,
> > >
> > > I recently posted an issue to the NuttX Github page:
> > > https://github.co
Hello,
I am trying to use gcov with NuttX simulator, to have code coverage reports
generated.
I have enabled CONFIG_ARCH_COVERAGE and the executable is properly build
and run.
The .gcno files are properly generated.
However, the needed .gcda files are not generated.
Usually these are generated w
But there is no way to terminate the simulator gracefully.
Doesn't this work
nsh> poweroff
On the simulator, that should lead to exit() being called which is a
"normal" termination.
Ah, yes. I didn't have CONFIG_BOARDCTL_POWEROFF enabled, so I didn't see
this command.
Nevertheless, it is still not working.
Indeed the simulator exits, but the .gcda files are not generated.
On Thu, Aug 25, 2022 at 4:52 PM Gregory Nutt wrote:
> > But there is no way to terminate the simulator
On Thu, Aug 25, 2022 at 10:05 PM Fotis Panagiotopoulos
wrote:
> Ah, yes. I didn't have CONFIG_BOARDCTL_POWEROFF enabled, so I didn't see
> this command.
>
> Nevertheless, it is still not working.
> Indeed the simulator exits, but the .gcda files are not generated.
>
>
Try this tools:
https://gith
Hmm, indeed a call to __gcov_dump() is missing.
After calling this, I get the .gcda files generated. And the reports seem
correct.
Shall I add this call to host_abort()?
Apart from manual control through NSH, it would be nice to have the files
generated as the simulator exits.
It is the "standard
On Thu, Aug 25, 2022 at 10:52 PM Fotis Panagiotopoulos
wrote:
> Hmm, indeed a call to __gcov_dump() is missing.
> After calling this, I get the .gcda files generated. And the reports seem
> correct.
>
> Shall I add this call to host_abort()?
>
Yes, it's a good improvement.
> Apart from manual
HI Alan,
Yes, that is true, some are really good - SAME70 will work that way but no
USB. And yes, MEMS is not there yet.
In this case, my BOM was wrong - X1 DNP - so I got enough running to make
progress anyhow (tested a lot of HW).
The most interesting aspect of this F103 finding for me is that
On Wed, Aug 24, 2022 at 8:05 PM Lee, Lup Yuen wrote:
>
> NuttX now supports 64-bit Arm Cortex-A53 with Multi-Core SMP... Will it run
> on Pine64's PinePhone? This article explores how we might run NuttX on a
> real phone...
>
> https://lupyuen.github.io/articles/arm
Thank you for this article! T
