You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nuttx.apache.org by Fotis Panagiotopoulos <f....@gmail.com> on 2021/12/02 22:16:40 UTC
Re: Kernel ticking and progmem writes
> Is this a dual bank part? Is so you can avoid the bus lock by operating on
> the other bank.
Well, eventually this is what I ended up using.
It works perfectly in this configuration.
It is just that memory mapping had to be changed, and this ended up to be
an effort.
> Yes, they are called ramfuncs and are automatically copied to RAM at
> boot time. This does not appear to be implemented for STM32F4, but
> search for referernces to CONFIG_ARCH_RAMFUNCS or ramfuncs in arch/ and
> include/
Hmm, this seems very interesting.
I will spend some time checking on this feature.
Thank you all!
Στις Τρί, 30 Νοε 2021 στις 4:22 μ.μ., ο/η Gregory Nutt <sp...@gmail.com>
έγραψε:
>
> > I think it may be necessary to put some parts of the NuttX kernel into
> RAM
> > so that it can keep executing while the bus is stuck.
> >
> > I don't know off the top of my head whether we currently have a built-in
> > way to do that.
>
> Yes, they are called ramfuncs and are automatically copied to RAM at
> boot time. This does not appear to be implemented for STM32F4, but
> search for referernces to CONFIG_ARCH_RAMFUNCS or ramfuncs in arch/ and
> include/
>
> $ find arch -name *_start.* | xargs grep -i CONFIG_ARCH_RAMFUNCS
> $ grep -r ramfuncs boards
>
>