econjack
Member

@wwatson: You're right. There was a FILE reference buried in the code that I didn't see. Thanks for the clue!!

@nwplouff: I worry about incremental writes for fear of messing the offsets up. Given the wear level being done, I'm going to stick with the put() method. If the EEPROM ever gets flaky, it's years down the road and they...

@defragster: Yep, have things working correctly now. The keyboard code is already written, just waiting for some parts to come in. Great minds, you know! If you're interested, go to Amazon and search B09WYP1ST8, click...

defragster: The project I'm working on is Software Defined Transceiver for amateur radio. There are about 40 parameters that I track (calibration and IQ settings, power output, CW-SSB transmission, filter settings,...

defragster, Paul: That's kinda what I am seeing so this just confirms it. Clearly, put() is easier to use and has the same effect. Thanks to you both.