file on the host which is organized like NOR
FLASH (256b write pages, 4k erase).
-Alexander
On Fri, Jan 27, 2023 at 9:58 PM Ken Pettit wrote:
Hey Guys,
Yes, I had SmartFS running in the simulator at one point, but it was
backed by a big char array. But I'm trying to understand th
t approach and use SmartFS, I also wrote
a FUSE filesystem for Linux that allows it to natively mount a SmartFS
filesystem contained in a file.
Ken
On 1/27/23 11:55 AM, Alan C. Assis wrote:
Hi Alexander,
Some time ago Ken Pettit wrote a SmartFS simulator.
If I'm not wrong it could be used
s the low level
format.
fs->fs_llformat.sectorsize:2048
fs->fs_llformat.availbytes:2043
fs->fs_llformat.nsectors:8192
fs->fs_llformat.nfreesectors:8183
fs->fs_llformat.flags:1 '\001'
fs->fs_llformat.namesize:16 '\020'
Thanks
Daniel Pereira de Carvalho
Em qua.
Hi Daniel,
The SmartFS FS *can* work with devices greater than 16M Bytes. I have
used it with a 256MBit / 32M Byte SPI flash before quite successfully.
But you have to ensure the logical sector size is large enough. One
limitation of the SMART MTD (and therefore SMART FS) implementation is
On 11/22/21 5:38 AM, Tim wrote:
Thanks Alan - I do agree it isn't a custom feature. The subsystem has "Feature Units"
which includes "AUDIO_FU_EQUALIZER" as a control. This doesn't seem to be implemented for
any processors or boards that I can see, nor is there any generic code for this; just t
Hi Tim,
:) Yeah, I was answering the subject and ignoring the body :)
Actually SmartFS will work with 256MBit (32MByte) FLASH. You just have
to get the sector sizes setup correctly. But it sounds like NXFSS will
work just fine for you.
Ken
On 8/25/21 11:01 AM, Tim Hardisty wrote:
Hi Ken
Hey Tim,
Selection of filesystem is kind of a personal choice. Each filesystem
has different features / benefits. I have never used NXFFS but I know
it absolutely works with the caveat that you can only have one file open
for writing at a time. Because of this, I wrote SmartFS, which doesn'
Hi Sara,
I'm not sure SmartFS was ever tested with this particular sequence where
the volume is erase and then re-mounted to a different location. If I
get a chance this weekend, I will take a look at it since you have a
very specific test sequence.
Ken
On 8/5/21 3:48 PM, Sara da Cunha Mon
My opinion:
CMake is horrible. Don't do it. It's hard to use for beginners, and
hard to use for anyone who isn't just a strong advocate for it.
Just my opionion.
Ken
On 6/9/21 6:46 AM, Gregory Nutt wrote:
I think that there a lot of people like myself who are opposed to the
CMake change b
Hi Xiang,
I seem to recall some time ago receiving an email requesting signature
of this or a similar agreement, but couldn't remember exacly when or
from whom that was sent. Is this the same agreement I should sign for
the contributions I had made? I recall there was some specific
proceedu
sizeof(input), stdin, stdout);
if (len && input[len-1] == '\n')
{
input[--len] = 0;
}
if (len)
{
spitest->cmd = input[0]; /* First char is the command */
...
}
}
...
}
Ken
On 1/26/21 7:16 AM, Ken Pettit w
but the question remains about why
is it needed and how can I get input echo
Thanks
Grr
El lun, 25 ene 2021 a las 13:30, Ken Pettit () escribió:
Hey Grr,
You need the fflush(stdout) call to be *after* the printf("\nEnter
Command:").
If the printf doesn't end with \n, then t
Hey Grr,
You need the fflush(stdout) call to be *after* the printf("\nEnter
Command:").
If the printf doesn't end with \n, then the stdout won't be flushed.
Ken
On 1/25/21 11:25 AM, Grr wrote:
Hello to all
Is there a way to get stdout without a LF?
I have something like
case INPUT_CMD:
But using tmux, I am able to get pdcurses displays like this (it
actually has color):
File Debug Help
┌───Watch───┐
┌─┐│ │
│ ││ │
│ . *
││
Hey Johnny,
It has been a while since I ran the pdcurses with minicom, but my
recollection is that something sets attributes of the entire display to
blink all the time. Plus when drawing window borders using the VT100 /
ANSI line drawing character, you end up with a bunch of funky characters
Hey Greg,
I actully tried ALL of the emulation modes offered by minicom and each
one behaved the same.
I found that using Linux 'screen' or 'tmux' works, but neither of those
deal with the /dev/tty device "disappearing" suddenly.
Ken
On 1/22/21 2:43 PM, Gregory Nutt wrote:
Now examples
with minicom in
VT102 mode
I'll fix that later
Thanks again
Grr
El vie, 22 ene 2021 a las 14:35, Ken Pettit () escribió:
Looks like changing nuttx/pdcdisp.c:840 from "sp" to just "s" was the
only compile error. Though going through the exercise made me remembe
t use in this
function); did you mean 's'?
but it's a matter of debugging it. Maybe a lacking option, I'll research it
Thanks again
Grr
El vie, 22 ene 2021 a las 13:11, Ken Pettit () escribió:
Grr,
Actually, pdcurses has a mode that will work over serial using
System->Term
n this
function); did you mean 's'?
but it's a matter of debugging it. Maybe a lacking option, I'll research it
Thanks again
Grr
El vie, 22 ene 2021 a las 13:11, Ken Pettit () escribió:
Grr,
Actually, pdcurses has a mode that will work over serial using
System->Ter
Grr,
Actually, pdcurses has a mode that will work over serial using
System->Termcurses. This is a terminal based extension to pdcurses that
I added a few years back. It supports VT-100 / ANSI escape codes. I
haven't tested it in the Apache NuttX framework to validate it still
works though.
On 12/31/20 7:36 AM, Nathan Hartman wrote:
ASCII art could be a good fit for the many README.txt files we have.
Even if it doesn't go in a README.txt, if it's a good diagram then in
the interest of making the information available to everyone, I think
it should be added in documentation first
21 matches
Mail list logo
