Is anyone opposed to linking the workshop videos from the NuttX website?
I think it might be a good thing to have a page per workshop (this
year's, last year's, etc) with the links to the videos, and to have
the latest one mentioned on the front page.
Cheers,
Nathan
Thanks Sara – I’m having a problem with your emails…via my work server they are
rejected, and my personal email marks them as spam, but delivers them and
messes up the formatting.
I can see you have some good suggestions so I will try and unravel it all and
reply tomorrow.
From: Sara da
2. If using FAT, as Greg suggested, take care of respecting the 8.3
convention name:
https://en.wikipedia.org/wiki/8.3_filename#:~:text=An%208.3%20filename%20(also%20called,for%20compatibility%20with%20legacy%20programs
.
That should not be necessary, the NuttX FAT supports long file name,
m
Em qua., 25 de ago. de 2021 às 15:12, Sara da Cunha Monteiro de Souza <
saramonteirosouz...@gmail.com> escreveu:
> Hy Tim,
>
> 1. PTAL at:
> https://www.mail-archive.com/dev@nuttx.apache.org/msg06767.html and see
> if the issues you found with SMARTFS
> can be solved with the proper configurations
Hy Tim,
1. PTAL at: https://www.mail-archive.com/dev@nuttx.apache.org/msg06767.html
and see if the issues you found with SMARTFS
can be solved with the proper configurations and commands.
2. If using FAT, as Greg suggested, take care of respecting the 8.3
convention name:
https://en.wikipedia.org
I am only just getting the point of having the luxury to think about what FS to
use lol. My 1st thought was indeed FAT and USB MSD for sure…but I made the
randome decision to put a USB-C connector and FUSB controller on the board and
haven’t got that working yet.
The beauty of NuttX is it gi
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
To answer your question – which was the original intent of this help request,
the aim is fundamentally data logging. Users will log data (at 20Hz, say;
multiple parameters) then occasionally pull them off for external analysis,
delete, and start again. So I don’t think wear levelling is actu
> >> * Register a mtd driver and mount a Little FS over it.
> I assume that is a typo in the original file? "Little FS"
>
Yes. Should be: * Register a mtd driver and mount a NXFFS over it.
Thanks Greg – and apologies for the wrong thread subject.
I have seen references in the code to FTL but stupidly thought it was some
other kind of FS. A non-Linux/Posix/Unix background means I am not totally
across the mtd/block driver terminology etc. I did use Unix, but that was
around 45
Hi Ken,
You fell for my 100% unintentional trap…thread title didn’t match content! I’d
started one message, saved it as a draft, then changed my mind on what to ask
but didn’t change the title. Doh!
I did try SmartFS and really like the sound of it, but it didn’t work “out of
the box”. I
Just to update and close this conversation with a better understanding of
my problem
and providing solution:
I basically had 2 problems:
1.
When calling *smart_initialize() *and *nx_mount()* , I had "no low level
format" error.
To fix that, I needed to force format using the following command:
*m
You won't have the block drive unless you do what Greg suggested.
But for mounting nxffs on an MTD partition you don't need the block driver.
Thanks, Sara.
Yes, we double faulted on that. The sequences of operations would not
produce a block driver BUT a block driver is not needed.
The s
Please, remove the #if def ...
Em qua., 25 de ago. de 2021 às 14:44, Sara da Cunha Monteiro de Souza <
saramonteirosouz...@gmail.com> escreveu:
> You won't have the block drive unless you do what Greg suggested.
> But for mounting nxffs on an MTD partition you don't need the block driver.
> The s
You won't have the block drive unless you do what Greg suggested.
But for mounting nxffs on an MTD partition you don't need the block driver.
The snippet you pasted are with some typos.
Try it:
/
* Name: format_nxffs
*
m25p_initialize() does not generate a block driver. I creates an MTD
driver. To get a block driver, you have to wrap the MTD driver
instances in an FTL (FLASH Translation Layer) instance. These should be
examples:
$ find . -name "*.c" | xargs grep -l ftl_initialize | xargs grep -l
nxffs_in
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'
I seem to have got over most of my SPI flash and EEPROM issues now and my
256Mb SPI flash is properly recognised.
I think I am at the last hurdle. Here is the console output, along with my
question of the day :)
Successfully initialized M25P SPI
m25p_initialize: dev: 0x2005b970
m25p_readi
s/right/write/
Sorry for the typo
On 8/25/21, Alan Carvalho de Assis wrote:
> Hi Tim,
>
> Congratulations! We are happy to see your progress with NuttX.
>
> If you want to help future "Tim"s please right a small documentation about
> it.
>
> You can create it at:
>
> Documentation/guides/eeprom_
Hi Tim,
Congratulations! We are happy to see your progress with NuttX.
If you want to help future "Tim"s please right a small documentation about it.
You can create it at:
Documentation/guides/eeprom_spi.rst
BR,
Alan
On 8/25/21, Tim Hardisty wrote:
> My board is now correctly registering th
My board is now correctly registering the SPI instance and binding the
relevant SPI and CS to the SPI Flash driver.
It was an uphill struggle, but thanks to all your various suggestions I
have got there and learned more than I wanted to!
Next hurdle is to trawl through other boards to learn
That isn't quite right, Alan, as the mtd at25_initialize routine is for
SPI FLASH not SPI EEPROM - it tries to read an ID.
I have replied to my other thread with the solution for AT25 SPI EEPROM,
for others to refer to if they want
On 24/08/2021 20:59, Alan Carvalho de Assis wrote:
Hi Tim,
There is support for MT25Q128 and I have now added the MT25Q256
It is in nuttx/drivers/mtd/m25px.c and I will add to the list of PRs once I
have everything sorted on my board.
Subject: Re: nxfss on MT25Q nor flash
BTW, do we have a driver for MT25Q? I can't see one. Is it compatible wit
> How difficult should be the porting of the ESP32 processor to NuttX? It
is possible to use one of the Expressif configurations?
Yes it is possible. Most of the configurations should work on any board.
For special configs, if there is an external device required, then
that has to be there of cou
Hi
we have this little board (www.briki.org)
with 2 different cores:
MBC-WB01-BPN:
SAMD211 – ESP322 – EXT 64 Mbit flash3 – PCB Antenna4 – No Crypto5
SAMD211: ATSAMD21G18A ARM® Cortex®-M0+
ESP32: ESP32-D0WD dual-core Tensilica Xtensa LX6 running @240MHz
How difficult should be the porting of
that is the best and usual way to get documentation about nuttx
you need some grep-fu
the system.map trick is a generic debug technique that you can't invent
if someone else doesnt tell you about it :)
sebastien
Le 24/08/2021 à 18:57, Tim a écrit :
No, it's not in the system map. Having now
26 matches
Mail list logo
