Re: Kernel ticking and progmem writes

2021-12-02 Thread Fotis Panagiotopoulos
> 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

Re: Kernel ticking and progmem writes

2021-11-30 Thread Gregory Nutt
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

RE: Kernel ticking and progmem writes

2021-11-30 Thread David Sidrane
Is this a dual bank part? Is so you can avoid the bus lock by operating on the other bank. -Original Message- From: Nathan Hartman Sent: Tuesday, November 30, 2021 5:35 AM To: dev@nuttx.apache.org Subject: Re: Kernel ticking and progmem writes On Tue, Nov 30, 2021 at 8:05 AM Fotis

Re: Kernel ticking and progmem writes

2021-11-30 Thread Nathan Hartman
On Tue, Nov 30, 2021 at 8:05 AM Fotis Panagiotopoulos wrote: > I found the issue. > > From the STM32F427 manual: > > > Any attempt to read the Flash memory on STM32F4xx while it is being > written or erased, > > causes the bus to stall. Read operations are processed correctly once the > program

Re: Kernel ticking and progmem writes

2021-11-30 Thread Fotis Panagiotopoulos
I found the issue. >From the STM32F427 manual: > Any attempt to read the Flash memory on STM32F4xx while it is being written or erased, > causes the bus to stall. Read operations are processed correctly once the program > operation has completed. This means that code or data fetches cannot be

Re: Kernel ticking and progmem writes

2021-11-30 Thread Xiang Xiao
On Tue, Nov 30, 2021 at 5:55 PM Fotis Panagiotopoulos wrote: > Hello everyone, > > I have some issues with the watchdogs and possibly the scheduling of the > kernel. > > I am not sure if this is a bug, or if I am miss-using something... > > I am working on an STM32F427, and I am using the