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 sorted it, but no record of how I sorted it. My lack of thoroughness :( Sebastien. Of course, it’s a character driver…der. I have been so bogged down in choosing a filesystem for the big NOR flash I lost the plot! Gregory. Loop device – that’s what I used a couple of years ago! Not for real, but just to prove the device could be written to etc without having to do anything clever (i.e. just from an nsh prompt). This device will be used to store a settings struct, so a character driver will work fine – I will probably use a FAT-formatted ram drive as an intermediary storage area to allow access via USB from PCs etc., probably using YAML formatting. Still thinking this all through. From: Tim Hardisty <t...@hardisty.co.uk> Reply to: <dev@nuttx.apache.org> Date: Thursday, 25 May 2023 at 17:35 To: "dev@nuttx.apache.org" <dev@nuttx.apache.org> Subject: SPI EEPROM 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_initialize doesn't return mtd_dev_s, just a success/fail, so I can't then use an FTL etc to allow me to mount it in anyway. How can I get this device mounted with some form of FS on it so I can read/write config data to it? Perhaps FTL isn't the way to go; if so, I've forgotten what is!
