There was a section in the TcMenu documentation about selecting the correct EEPROM settings when generating code. I missed that step, and since I had to regenerate, I made a few changes that built up. I removed two scale sub-setting options, which also meant I had to decrement a few integers in my code, but the menu was a bit more elegant. "Restore Defaults" also disappeared since "Bypass" ignored the settings and Restore might get triggered by accident. I found some missing EEPROM assignments, which I rectified by changing the non-volatile settings.
The new code did not work immediately, but it stopped boot-looping. The documentation was not entirely clear about how I should handle .load() and .save() and I tried sending several. The problem was another missing step because I was supposed to call EEPROM.commit() after saving, so I never wrote any data to non-volatile memory. Once I implemented the command, I could see the restored variables after unplugging the device. Not all the variables seem to actually "stick," but calling them in a print function made it mostly functional. More work is needed, but the EEPROM is mostly solved.
The rest of the posts for this project have been arranged by date.
First time here?
Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5
Completed projects from year 6
Completed projects from year 7
Completed projects from year 8
Completed projects from year 9
Completed projects from year 10
Completed projects from year 11
Disclaimer for http://24hourengineer.blogspot.com and 24HourEngineer.com
This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.
All information on this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property, or similar, is the responsibility of those involved in the replication.
All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by Brian McEvoy, cannot be used to claim property or assets.
Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.
This blog, including pictures and text, is copyright to Brian McEvoy.
2025-03-29
The new code did not work immediately, but it stopped boot-looping. The documentation was not entirely clear about how I should handle .load() and .save() and I tried sending several. The problem was another missing step because I was supposed to call EEPROM.commit() after saving, so I never wrote any data to non-volatile memory. Once I implemented the command, I could see the restored variables after unplugging the device. Not all the variables seem to actually "stick," but calling them in a print function made it mostly functional. More work is needed, but the EEPROM is mostly solved.
 |
| Receiving signals after a reboot |
The rest of the posts for this project have been arranged by date.
First time here?
Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5
Completed projects from year 6
Completed projects from year 7
Completed projects from year 8
Completed projects from year 9
Completed projects from year 10
Completed projects from year 11
Disclaimer for http://24hourengineer.blogspot.com and 24HourEngineer.com
This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.
All information on this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property, or similar, is the responsibility of those involved in the replication.
All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by Brian McEvoy, cannot be used to claim property or assets.
Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.
This blog, including pictures and text, is copyright to Brian McEvoy.
2025-03-29
Comments
Post a Comment