Pete:

Perhaps I don't understand the question. However, setup() calls this code, which is at line 14 in EEPROMNew.cpp:

void ReadUserSettings()
{
? int val;
? EEPROM.get(0, val);????? // Read first byte of EEPROM memory
//val = 0;???????????????? // Uncomment this line forces a rewrite of EEPROM. Comment out line 23 to display
??????????????????????????????????????????????????????????? // is not changed.
?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? ?
? if (val != EEPROMINITVALUE) {???????????????????????????? // Already set or not?
??? GlobalDefaultEEPROMValues();??????????????????????????? // No, so set some common values
??? WriteEEPROMSettings(EEPROMDEFAULTOFFSET);?????????????? // Write default values to default block
??? WriteEEPROMSettings(EEPROMUSEROFFSET);????????????????? // Also assume defaults for user first time through
??? InitDisplayCalibration();?????????????????????????????? // Now have them calibrate display
? }
? ReadEEPROMSettings(EEPROMUSEROFFSET);
}

The second lines causes a read of the first EEPROM byte and save that value in val. If val is not equal to EEPROMINITVALUE, which is 150, then the code sets a bunch of default values for variables. (If you uncomment the line immediately below the EEPROM.get() call, it will force the if statement block to execute.) The second statement in the if block writes those default values to one segment of EEPROM reserved for default values. I did this so you can always return to a default set of values. (This is what the Restore button you see in the lower right of the main program screen does when you press it.) Those same set of values are then also written into the EEPROM segment set aside for your own custom settings for those variables. As a result, EEPROM maintains a default set of values and a separate set that is whatever you have made them.

The last function call in the if statement block (i.e., InitDisplayCalibration()) is the routine that allows you to calibrate your display. If you place this statement:

MyDelay(10000UL);

immediately before InitDisplayCalibration(), you will have 10 seconds to turn off your rig. (Note: there is a standard Delay() function provided by the standard library, but it is a "blocking" function. That is, it blocks any interrupts that might occur while processing its delay. I wrote MyDelay() as a replacement because it does not block interrupts. So, if you plan to do any code that needs a program delay, you most likely will want to use MyDelay() instead of the stock Delay().)

Anyway, I'm not sure I answered your question, but perhaps this info will help you do what you need to do.

Jack, W8TEE

On Saturday, January 26, 2019, 6:42:18 PM EST, PeteWK8S via Groups.Io <pmeier@...> wrote:

Ok I've built my JackAl in such a way I cannot program the Teensy with it in place. Not enough room to plug a cable in. So I have to program it out of the JackAL board. I'm working out a workaround. However, in the meantime, how do delay the Touch calibration routine so that is doesn't execute upon completion of the load ? ?Insert a long enough DELAY so I have time to turn off the Teensy before it the routine executes?

Pete WK8S

Pete:

Perhaps I don't understand the question. However, setup() calls this code, which is at line 14 in EEPROMNew.cpp:

void ReadUserSettings()
{
? int val;
? EEPROM.get(0, val);????? // Read first byte of EEPROM memory
//val = 0;???????????????? // Uncomment this line forces a rewrite of EEPROM. Comment out line 23 to display
??????????????????????????????????????????????????????????? // is not changed.
?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? ?
? if (val != EEPROMINITVALUE) {???????????????????????????? // Already set or not?
??? GlobalDefaultEEPROMValues();??????????????????????????? // No, so set some common values
??? WriteEEPROMSettings(EEPROMDEFAULTOFFSET);?????????????? // Write default values to default block
??? WriteEEPROMSettings(EEPROMUSEROFFSET);????????????????? // Also assume defaults for user first time through
??? InitDisplayCalibration();?????????????????????????????? // Now have them calibrate display
? }
? ReadEEPROMSettings(EEPROMUSEROFFSET);
}

The second lines causes a read of the first EEPROM byte and save that value in val. If val is not equal to EEPROMINITVALUE, which is 150, then the code sets a bunch of default values for variables. (If you uncomment the line immediately below the EEPROM.get() call, it will force the if statement block to execute.) The second statement in the if block writes those default values to one segment of EEPROM reserved for default values. I did this so you can always return to a default set of values. (This is what the Restore button you see in the lower right of the main program screen does when you press it.) Those same set of values are then also written into the EEPROM segment set aside for your own custom settings for those variables. As a result, EEPROM maintains a default set of values and a separate set that is whatever you have made them.

The last function call in the if statement block (i.e., InitDisplayCalibration()) is the routine that allows you to calibrate your display. If you place this statement:

MyDelay(10000UL);

immediately before InitDisplayCalibration(), you will have 10 seconds to turn off your rig. (Note: there is a standard Delay() function provided by the standard library, but it is a "blocking" function. That is, it blocks any interrupts that might occur while processing its delay. I wrote MyDelay() as a replacement because it does not block interrupts. So, if you plan to do any code that needs a program delay, you most likely will want to use MyDelay() instead of the stock Delay().)

Anyway, I'm not sure I answered your question, but perhaps this info will help you do what you need to do.

Jack, W8TEE

On Saturday, January 26, 2019, 6:42:18 PM EST, PeteWK8S via Groups.Io <pmeier@...> wrote:

Ok I've built my JackAl in such a way I cannot program the Teensy with it in place. Not enough room to plug a cable in. So I have to program it out of the JackAL board. I'm working out a workaround. However, in the meantime, how do delay the Touch calibration routine so that is doesn't execute upon completion of the load ? ?Insert a long enough DELAY so I have time to turn off the Teensy before it the routine executes?

Pete WK8S