e a spi flash driver, and change its read/erase/write
routines (and initialization) by copying code from a spi eeprom driver.
Sebastien.
Le 14/12/2023 à 19:13, Tim Hardisty a écrit :
Question first, then explanation.
How do I use losetup (which is what I think I need) with a character
memory devic
d initialization) by copying code from a spi eeprom driver.
>
> Sebastien.
>
> Le 14/12/2023 à 19:13, Tim Hardisty a écrit :
> > Question first, then explanation.
> >
> > How do I use losetup (which is what I think I need) with a character
> > memory device and moun
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
spi flash driver, and change its read/erase/write
routines (and initialization) by copying code from a spi eeprom driver.
Sebastien.
Le 14/12/2023 à 19:13, Tim Hardisty a écrit :
Question first, then explanation.
How do I use losetup (which is what I think I need) with a character
memory
Question first, then explanation.
How do I use losetup (which is what I think I need) with a character
memory device and mount an FS on it? SPI EEPROM and LittleFS specifically.
Yes, it's a bad idea, probably, but I just want to have a play and lack
of NuttX/POSIX/Linux knowledge has b
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
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
d have sworn I had this working a year or 2 ago but it's stumped me
>> today...
>>
>>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.
&g
35:00 UTC, Tim Hardisty a écrit :
>Could have sworn I had this working a year or 2 ago but it's stumped me
>today...
>
>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 an
Could have sworn I had this working a year or 2 ago but it's stumped me today...
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.
Unlike at25_initialize, the ee25xx_initi
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:
H
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
Thanks Vadim – that’s pretty much the conclusion I had come to.
Tim.
Subject: Re[2]: SPI EEPROM
Hi Tim,
You could search for any spi device being initialized. Search for spi_dev_s
being declared in boards folder for some board, use it as an example and do the
same
il.com >
>Reply to: < dev@nuttx.apache.org >
>Date: Tuesday, 24 August 2021 at 20:11
>To: < dev@nuttx.apache.org >
>Subject: Re: SPI EEPROM
>
>
>
>
>
>That’s AT24 I2C not AT25 SPI EEPROM unfortunatel, and from a quick look it
>“just worked” ☹
>
>
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
devices such
as nor flash or SPI EEPROM have only minimal support and, more importantly, no
documentation that’s worth using.
I will just have to keep struggling, googling, grepping, and hoping to hit
lucky. I will add to the documentation once I have it working. If I get it
working.
And this
, you need to enter in the
water, just start in the shallow place: stm32 + sdcard spi for
example.
BR,
Alan
On 8/24/21, Tim Hardisty wrote:
> That’s AT24 I2C not AT25 SPI EEPROM unfortunatel, and from a quick look it
> “just worked” ☹
>
>
>
>
>
>
>
> From: Alan
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"
of documentation somewhere. All I seem to end up doing is
> searching every single file for some kind of clue as to what to do!
>
>
>
> I have an SPI EEPROM device. Menuconfig allows me to set it up, lovely! I
> end up with
>
> CONFIG_EEPROM=y
>
> CONFIG_SPI_EE_2
The more time I spend with nuttx the more I think I just haven't found some
treasure trove of documentation somewhere. All I seem to end up doing is
searching every single file for some kind of clue as to what to do!
I have an SPI EEPROM device. Menuconfig allows me to set it up, lovely!
22 matches
Mail list logo
