On Thu, Apr 29, 2021 at 8:12 AM Flavio Castro Alves Filho <
flavio.al...@gmail.com> wrote:
> Hello Xiang,
>
> Thank you for your quick response.
>
> How do I manage the format of a littlefs 'disk' from programming (not
> nutshell) ?
>
>
If you want to generate the initial littlefs image in host en
Hello Xiang,
Thank you for your quick response.
How do I manage the format of a littlefs 'disk' from programming (not
nutshell) ?
I am looking for something similar to 'mksmatfs' function.
Or only the flash_eraseall function is enough? Or should I add the "-o
autoformat" option on the last para
I am sorting out flexcom support for the SAMA5D2 as there are issues with the
arch files as well as Kconfig. In doing so, I would like to do it “right”.
If flexcoms are assigned as USARTs is the correct philosophy to register them
sequentially or as per flexcom port number? For example,
I am sorting out flexcom support for the SAMA5D2 as there are issues with the
arch files as well as Kconfig. In doing so, I would like to do it “right”.
If flexcoms are assigned as USARTs is the correct philosophy to register them
sequentially or as per flexcom port number? For example, if (o
> I mentioned that this should be backported, not sure if the author saw it:
https://github.com/apache/incubator-nuttx/pull/3613
I've labeled it so. Thanks.
On Wed, Apr 28, 2021 at 2:51 PM Matias N. wrote:
>
> Right, thanks.
>
> I mentioned that this should be backported, not sure if the author
Right, thanks.
I mentioned that this should be backported, not sure if the author saw it:
https://github.com/apache/incubator-nuttx/pull/3613
Best,
Matias
On Wed, Apr 28, 2021, at 10:46, Abdelatif Guettouche wrote:
> > Wasn't the stack restructure behind the 10.1 release?
>
> Yes, but that chan
> Wasn't the stack restructure behind the 10.1 release?
Yes, but that change just exposed an old issue.
On Wed, Apr 28, 2021 at 2:45 PM Matias N. wrote:
>
> Wasn't the stack restructure behind the 10.1 release?
>
> Best,
> Matias
>
> On Wed, Apr 28, 2021, at 09:57, Gustavo Henrique Nihei wrote:
Wasn't the stack restructure behind the 10.1 release?
Best,
Matias
On Wed, Apr 28, 2021, at 09:57, Gustavo Henrique Nihei wrote:
> Hi folks,
>
> I believe we should consider backporting the fix from this PR into the
> 10.1.0 release:
> https://github.com/apache/incubator-nuttx/pull/3614
>
> It
Yes! I just lit the label (backport/10.1)
-Original Message-
From: Gustavo Henrique Nihei [mailto:ghni...@gmail.com]
Sent: Wednesday, April 28, 2021 5:58 AM
To: dev@nuttx.apache.org
Subject: Re: [VOTE] Apache NuttX 10.1.0 (incubating) RC0 release
Hi folks,
I believe we should consider ba
I will look into it ASAP
Regards
Alin
On Wed, Apr 28, 2021, 14:58 Gustavo Henrique Nihei
wrote:
> Hi folks,
>
> I believe we should consider backporting the fix from this PR into the
> 10.1.0 release:
> https://github.com/apache/incubator-nuttx/pull/3614
>
> It fixes a side effect from the refac
Hi folks,
I believe we should consider backporting the fix from this PR into the
10.1.0 release:
https://github.com/apache/incubator-nuttx/pull/3614
It fixes a side effect from the refactoring of the stack architecture
due to a wrong stack alignment for RISC-V chips.
Best regards,
Gustavo.
On M
LittleFS can talk directly with the standard MTD driver, so you just need:
1. Call register_mtddriver in your board file
2. Run mount from nsh like this:
mount -t littlefs -o autoformat /dev/mtd /mnt
On Wed, Apr 28, 2021 at 8:03 PM Flavio Castro Alves Filho <
flavio.al...@gmail
Hello,
Today my application uses SmartFS associated with MX25L SPI Dataflash.
I intend to replace the SmartFS to LittleFS.
In the filesystem section of menuconfig, I can disable
CONFIG_FS_SMARTFS and enable CONFIG_FS_SMARTFS.
But when I go to "Device Drivers" --> "Memory Technology Device (MTD)
13 matches
Mail list logo
