EEPROM Memory - Store Anything - Arduino101 

Me too!

Thank you, but it was just to make an exampel of how to use the EEPROm.write function. If I use it in the void loop for that simple example, it would write it over and over again. In a read scenario, you would make an if() and decide to write or not to the EEPROM probably.

@@ELECTRONOOBS Yea! That seems good! Thanks for the great video! :)

Also you could read the value from a POT and save it in the EEprom and just use the update. Have a print value in the setup so every time the power is connected you'll see the last value

Just delete the line EEPROM.write(0, 25); from the setup loop and upload again before you run for a second time.

​@@k0pR0LiTh0s or use the 'update' function in the reference at 6:00, the one that only updates the value if it's not already there.

Interfacing those NAND and NOR flash require special hardware that comes with STM32. They offer FMC specific to interface those type of storage beside the QSPI and OctaSPI flash system

Christ

I was also wondering about this issue. But don't understand how to handle it

You just need to know the size of everything you are storing and make sure that none of it would overlap and probably create a diagram or map to know where everything is, another way would be to have the address auto increment by the size of the data to be stored but that is most useful if you are writing a sequence or set of data sequentially and reading it sequentially.

Glad to hear that! What's your max RPM with it?

@@ELECTRONOOBS It was around 10500 RPM , I used 1100KV motor with 3S lipo. And truly you are a genius to bring up a project like this to enlighten us. Thank you so much bro.

I usually solve this by only writing a single union struct to eeprom with a single first static integer version - if the version doesn’t match my constraints - als eprom data is erased

You don't have to keep in mind that because the EEPROM.get function dose that automataically. If you write EEPROM.get(0, brightness); and you defined the brightness variable as int, the function will automatically know to read 2 bytes. If you define brightness as float, it would read 4 bytes and so on. On the other side, yes, if you put 2 bytes on address 0 and 1 and then you put 1 more byte on address 0, it will overwrite it, that's obvious.

@@ELECTRONOOBS im not a programmer. Does that mean, that when i write an integer (2 bytes) to adress 0 that the next integer has to be written on adress 2 or does it not matter how long an integer or float is meaning i can put one integer on address 0 and then the next float on address 1 and the next integer on address 2? basically like this: Address 0: Integer Address 1: Float Address 2: Integer Address 3: Integer Address 4: Float

Hahahaha

Sir i want to make Arduino project but I didn't know about coding . How to start it can you please explain it .

@@technicalgaming7056 Look up tutorials, its not difficult to find information about arduino.

EEPROM is more used for storing settings or data that wont change for a while, not like for writing once a second, flash devices like emmc or SD cards or SPI flash have less write cycles than EEPROM, but they are bigger so wear levelling can be used to greatly increase their lifespan. I also think you may be confusing EEPROM and flash, they are similar but they are not the same. SBCs with built in storage usually use EMMC, which I think you probably mean rather than EEPROM, they are very similar to SD cards and in a lot of cases are actually more reliable than SD cards.

@@conorstewart2214 I did mean EEPROM. With a SoC you often get a small amount of EEPROM as well as flash, and the EEPROM is supposed to have about ten times the write life. The sort of thing you may want to do a lot of writes is say when you want to record the time you switched the system off or perhaps when it crashes and you want the most up to date time or possibly other varying data. I do not have an EMMC in the Soc I use but do have and SDIO interface.

@@Andrew-rc3vh "I need a lot of flash so I now use and SD card", you went from talking about EEPROM to flash and SD cards. Lots of modern microcontrollers and probably SoCs too dont have EEPROM, they just emulate it using flash, so you lose most of the benefits of using EEPROM, I know STM32 does this, I know teensy does this, the rp2040 doesnt have it either. You also talk about memory controllers and EEPROM, I've never seen that before, and you talk about fresh blocks of memory, which sounds a lot like flash, so you can probably see why I thought you may be confused. You also stated that sd cards never fail, they actually have a very high failure rate compared to other types of memory, for example in my phone I use an SD card for storing things like photos and about once a year the whole card fails so that it becomes unwritable, I can only read it from then on, and I use good main brand cards. If you look at forums and similar you will see that SD cards fail very often compared to the likes of EEPROMs, SPI flash, EMMC etc, it does have the advantage of being easily replaceable but it still fails faster.

@@conorstewart2214 Hmm, it seems odd that it fails more often if it is the same memory. Perhaps that might have something to do with the connections. Actually given the choice I would have liked the small bit of memory to cope with a lot of writes because I had it so arranged that it would still work without the SD card and write to internal flash if it were not inserted. Anyhow this has to write the time once a second, so now i arrange it so the part of the memory it writes to advances as the log records data. It's a complicated thing to explain fully, but it does work 100% reliably now. I used to need to store various pointers, but that's all taken care of in the new scheme.

Andrew it’s really not all that complicated to explain, you are pretty much just creating a log file, just recording data and moving through the storage writing it sequentially one after the other. Unless there is something else you are doing too.

EEPROM update reads the current address and compare it with the value to be stored. Of they are the same, no write shall be done.

They will probably change size depending on how they were manufactured. Older EEPROMs will most likely use larger transistors than newer ones. Its also not really relevant information as it can change and it doesnt really change the implementation at all, might effect things like density and power consumption though.

Did you live under a stone during the last two years? Covid? Ever heard of it?

Yes, on address 4, otherwise you would overwrite the previous data

@@ELECTRONOOBS thank you

What do you mean interference between the motor and nrf? I take it by 3 phase motor you mean BLDC, I have built drones and RC cars and never had any interference. If you are powering the ESC from the same 5V as the arduino and nrf24 then you probably shouldnt be, the ESC should be powered direct from the battery and the NRF24 and arduino should be powered from a 5V converter connected to the battery, thats the only way I can see you having problems with interference, either that or your converter is very poorly designed and doesnt have capacitors.

@Conor Stewart I'm thinking of emf, what can bother the receiver because the receiver has 2 communication wires and such pulses can be strong enough for the signal to be noisy enough not to work as intended, im watched a lot of video about this to understand about how it works together, but this interfearing variable is a litlebit confuseing me. Anyway thanx the information about this knowlage what u have!

@@erikkalmar4965 Have you actually built it and tried it? If you havent built it and are worrying about it then you are probably worrying about something that wont make any difference at all.

@@conorstewart2214 Yes I build it and tried it, and the resoult is interesting. It is working nincely but i dont know why some times the signal is looks like a litle bit noisy. The servo is delayed if its happening, and the motor speed control is delayed too, i dont know it is just because the noise, or someting else cause this Actualy the powersuply is not a problem i use the esc power output for this, and if i try this with battery or anythig else, same thing happening, i gues if some how the communication line get more gnd wrapped around it with a thicker cable can solve the problem, but now i dont have thicker cable sadly for this. So i need to look around and see if i found something usefull for this purpose. So sorry if im not realy understandable in english😅

@@erikkalmar4965 What signals look noisy? Are you looking at the SPI signal using an oscilloscope? The ESCs 5 V output may be the problem, especially if it is a cheap ESC. I find it surprising you have problems when I havent had any, and I used a cheap chinese fake without twisted wire pairs or anything with its wires right beside my ESC power wires and the nrf24 right beside the three wires that go to the motor and had no problem at all. Your nrf24s may be fake and that may be why you are having issues, especially if they were really cheap. Your problem with delays could be because of the arduino, depending on your code it might be too slow or if you use a lot of blocking functions, you might miss data packets. Are you using the ones with the external antenna or a built in antenna because I've heard that the cheap fakes that have the pcb antenna have a really terrible range.

That is also permanent, yes. But that is for a different video...

@@ELECTRONOOBS thanks for the reply!

there's no humor in science, only science hahahaha just kidding, I'll try!

@@ELECTRONOOBS i like your narration style

Meow

That happens with EEPROMs that have address and data pins that you access in parallel, rather than I2C or SPI EEPROMs.