I will look at lomtd, thanks. But if littlefs is not suitable (a quick
look and it seemed it might be a reasonably choice for a 16KiB EEPROM?)
is there an FS in NuttX that is suitable? "Out there" I find NASA's EEFS
and one or two others I could try (and submit to NuttX; depending on
licensing
On Fri, Dec 15, 2023 at 5:17 PM Sebastien Lorquet
wrote:
> Hi,
>
> I dont think you can use losetup to create a mtd device. loop devices
> are regular block devices.
You can use lomtd to setup a mtd device loop:
https://github.com/apache/nuttx-apps/blob/master/nshlib/nsh_fscmds.c#L1144-L1306
Hi Tim,
What is the P/N# of your SPI EEPROM?
As Sébastien said the best option is adding support to your SPI EEPROM as
MTD.
I used char dev EEPROM in the past with a circular packet buffer. It was
used to store tracking data before sending it to the cloud. It was faster
than using MTD in the dev
Hi,
I dont think you can use losetup to create a mtd device. loop devices
are regular block devices. This will only work if littlefs can mount a
block device (no idea if thats possible)
what you need is an adaptation layer that will implement a mtd device on
an eeprom.
You can duplicate a
Thanks for replies.
Alan – your video (which I had watched!) is for AT24 I2C EEPROM and it can’t be
done in the same way for SPI EEPROM with no device ID to read back We had this
same conversation a year or 2 ago when I was very new to NuttX, and I even
found an archived email saying I’d sor
On 5/25/2023 10:35 AM, Tim Hardisty wrote:
I have an SPI EEPROM device on my board, and use "ee25xx_initialize" to
register it as /dev/at25. That works fine.
But I can't do anything with it.
Sure you can. That is a character device, not an MTD or block driver,
and it should behave like the wh
Hi Tim,
There are two ways to access EEPROM on NuttX, one is using this
character driver that you are using and the other is accessing it as a
MTD.
I created a video tutorial some years ago explaining how to do it:
https://www.youtube.com/watch?v=qzjf2JtgYN0
Keep in mind that using MTD with I2C
Hi,
This eeprom is not an mtd device, it is too small for any filesystem, usually.
So it's just a character device that makes the eeprom appear as a fixed size
file.
If you need an eeprom mtd, the driver could be extended to make it behave as a
mtd device.
Sebastien
Le 25 mai 2023 16:35:00 U
pported in NuttX. AT25 is SPI and is what I
have (AT25128) and it is not well supported, with no example code or
boards
that support it (that I can find)
From: Gregory Nutt
Reply to:
Date: Tuesday, 24 August 2021 at 20:11
To:
Subject: Re: SPI EEPROM
That’s AT24 I2C not AT25
Thanks Alan – all my SPI pins are configured. That was easy to work out :)
I will follow this tomorrow and I’m sure it will all seem easier in the morning!
From: Alan Carvalho de Assis
Reply to:
Date: Tuesday, 24 August 2021 at 20:59
To:
Subject: Re: SPI EEPROM
Hi Tim,
It is very
is well supported in NuttX. AT25 is SPI and is what I
> have (AT25128) and it is not well supported, with no example code or boards
> that support it (that I can find)
>
>
>
>
>
>
>
>
>
> From: Gregory Nutt
> Reply to:
> Date: Tuesday, 24 Aug
AT24 is I2C and this is well supported in NuttX. AT25 is SPI and is what I have
(AT25128) and it is not well supported, with no example code or boards that
support it (that I can find)
From: Gregory Nutt
Reply to:
Date: Tuesday, 24 August 2021 at 20:11
To:
Subject: Re: SPI EEPROM
That’s AT24 I2C not AT25 SPI EEPROM unfortunatel, and from a quick look it
“just worked” ☹
There is support for the AT24 in other SAM boards. Search for AT24 in
defconfigs, I find
boards/arm/samv7/same70-xplained/
boards/arm/samv7/samv71-xult/
boards/arm/xmc4/xmc4500-relax
There is eve
is not aimed at you, Alan, as I know you are trying hard to help.
From: Alan Carvalho de Assis
Reply to:
Date: Tuesday, 24 August 2021 at 19:42
To:
Subject: Re: SPI EEPROM
Hi Tim,
The process to get AT25 SPI is similar, but for SPI you need to get
the CS pin configure besides
Carvalho de Assis
> Reply to:
> Date: Tuesday, 24 August 2021 at 18:01
> To:
> Subject: Re: SPI EEPROM
>
>
>
> Hi Tim,
>
>
>
> You are right, Documentation is one of our "Achilles tendon".
>
>
>
> But, of course, some times it is also the user
That’s AT24 I2C not AT25 SPI EEPROM unfortunatel, and from a quick look it
“just worked” ☹
From: Alan Carvalho de Assis
Reply to:
Date: Tuesday, 24 August 2021 at 18:01
To:
Subject: Re: SPI EEPROM
Hi Tim,
You are right, Documentation is one of our "Achilles tendon"
Hi Tim,
You are right, Documentation is one of our "Achilles tendon".
But, of course, some times it is also the user search fault, maybe
they don't have the Google-fun skills yet (please don't take it as
personal).
If you search for NuttX EEPROM Tutorial
It will returns this tutorial:
https://
17 matches
Mail list logo
