The NuttX support in OpenOCD relies on post file hooks to get the offsets.
You don't need to reorder them. That's more flexible than tempering with
the TCB.
Other RTOSs that use fixed offsets require a certain configuration to be
used in order to use OpenOCD.
On Mon, Nov 23, 2020, 04:10 Matias N.
Actually I just tried the approach I suggested with a quick hack to both
openocd and nuttx and it seems
to be working. So, this eliminates the need to hardcode offsets. A similar
thing should be done for the size
of the tasklist table, since it also depend on build flags.
Anyway, I think the hand
I am looking to cut the RC0 early this week. There have been a lot of
bug fixes that have gone in in the last few weeks (almost 60 patched
backported), and I have tested quite a few targets on actual hardware.
Unless there is a major issue that pops up I would like to cut the RC0 Tuesday.
https:
On Sun, Nov 22, 2020, at 22:25, Brennan Ashton wrote:
> I generally agree at least for the larger ARM platforms where there is
> overhead. We have some examples that are intentionally small, but for most
> of the reference examples I think we should be making the debugging better
> out of the box.
I generally agree at least for the larger ARM platforms where there is
overhead. We have some examples that are intentionally small, but for most
of the reference examples I think we should be making the debugging better
out of the box.
I also usually reset this to the default when I'm debugging
While trying the integration of openocd with NuttX it was complaining due to
"name" not being defined, which happens when CONFIG_TASK_NAME_SIZE == 0.
Looking at sched/Kconfig the default for this symbol is 31, yet many configs
have this set to zero. Do you think this is due to the default having
Thanks for confirming. I submitted PR #2378
Cheers,
Nathan
On Sun, Nov 22, 2020 at 5:15 PM Alan Carvalho de Assis
wrote:
> You are right, it should be 100Hz instead 100KHz.
>
> On 11/22/20, Nathan Hartman wrote:
> > Is there a mistake in the following comment in include/nuttx/clock.h?
> >
> >
You are right, it should be 100Hz instead 100KHz.
On 11/22/20, Nathan Hartman wrote:
> Is there a mistake in the following comment in include/nuttx/clock.h?
>
> [[[
> /* If CONFIG_SCHED_TICKLESS is not defined, then the interrupt interval of
> * the system timer is given by USEC_PER_TICK. This
Is there a mistake in the following comment in include/nuttx/clock.h?
[[[
/* If CONFIG_SCHED_TICKLESS is not defined, then the interrupt interval of
* the system timer is given by USEC_PER_TICK. This is the expected number
* of microseconds between calls from the processor-specific logic to
*
Hello Alan,
It worked. Thank you very much.
An additional remark: during the link phase on your document, in my
case, it missed the net lib on the command line.
Best regards,
Flavio
Em seg., 16 de nov. de 2020 às 16:24, Alan Carvalho de Assis
escreveu:
>
> Hi Flávio,
>
> A simple band-aid fix
10 matches
Mail list logo
