Timeline for EEPROM library throwing errors
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 23, 2016 at 16:41 | answer | added | Michael Stachowsky | timeline score: 2 | |
| Dec 23, 2016 at 16:17 | comment | added | Majenko | I suggest you create an answer to your question. It can then (in a couple of days IIRC) be accepted as the right answer and other people can be helped by it. | |
| Dec 23, 2016 at 16:10 | review | Close votes | |||
| Jan 15, 2017 at 3:02 | |||||
| Dec 23, 2016 at 15:27 | comment | added | st2000 | This will sound odd, but in C++ passing the wrong data type is just like calling a totally different method. The up side, you can, for example, write a number of identically named methods that can handle different data types in unique ways. Obviously, the library authors could have done this, but did not. Maybe that is an improvement you can implement. | |
| Dec 23, 2016 at 15:21 | comment | added | Michael Stachowsky | Actually I figured it out. I was using the wrong data types (my sketch wasn't quite what I had shown). I was sending in an unsigned int to the read/write as the address, but it requires an int and the data type is important. | |
| Dec 23, 2016 at 15:17 | comment | added | st2000 | You need to list your program ("sketch") for us to help. Guessing, (this is actually C++ so it's going to sound more complex than it really is, but) did you instantiate an instance of the EEPROM class? Did you include the header file for this class in your program? | |
| Dec 23, 2016 at 15:05 | history | asked | Michael Stachowsky | CC BY-SA 3.0 |