Re: MTD device aggregation, questions for other developers

Hi, Sebastian, I think you need to use the UnionFS (fs/unionfs).  It basically lets you mount two file systems at the same location with the content combined. There is an example at apps/examples/unionfs: 140   ret = mount(MOUNT_DEVNAME_A, CONFIG_EXAMPLES_UNIONFS_TMPA, "romfs", 141  

MTD device aggregation, questions for other developers

Hello, For history our board need 128 Mbit of flash, but the 128 Mbit parts are slw and have gigantic erase blocks. So as an alternative our plan was to have two 64 Mbit SST parts (fast and small erases) and aggregate them in software, so that we can present the other drivers a single 12

Support for multiple SST26 devices on a SPI bus

...has been submitted and hopefully will be ok. https://github.com/apache/incubator-nuttx/pull/4924 Sebastien

Re: MTD partition check error

On Tue, Nov 30, 2021 at 9:53 AM Sebastien Lorquet wrote: > > Hello > > new board has a new flash part that is smaller than the previous one. > > however without changing the rest of my code, the creation of a > partition that is too large for the new small device was accepted. > > I noticed that e

MTD partition check error

Hello new board has a new flash part that is smaller than the previous one. however without changing the rest of my code, the creation of a partition that is too large for the new small device was accepted. I noticed that erase sector numbers were compared to write blocks (calculated specifi

Re: Kernel ticking and progmem writes

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

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. -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 Panagi

Re: Kernel ticking and progmem writes

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

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 per

Re: Kernel ticking and progmem writes

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 indepen

Kernel ticking and progmem writes

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 independent watchdog timer. I have enabled the watchdog automonitor using a timer (