Hi all, we're trying to pull in some code written for Teensy 3.2 to 4.0. Honestly I'm not sure if it's going to work given the time I have.
Question 1: I looked around a bit, but wondering if anyone was maintaining a list of the areas most likely to have issues / failures when porting.
Question 2: I have one case specifically (see code below). This is a function which stores data in the EEPROM that's accessible later. I'm aware there's a lot of updates to the EEPROM library, which I can dig into also if needed.
Can anyone provide some guidance on updating this function, or use of EEPROM library generally, from 3.2 to 4.0?
Question 1: I looked around a bit, but wondering if anyone was maintaining a list of the areas most likely to have issues / failures when porting.
Question 2: I have one case specifically (see code below). This is a function which stores data in the EEPROM that's accessible later. I'm aware there's a lot of updates to the EEPROM library, which I can dig into also if needed.
Code:
// use this to store values to eeprom
#define store(location, value) { typeof(value) f = value; if (eeprom->location != f) eeprom->location = f; while (!(FTFL_FCNFG & FTFL_FCNFG_EEERDY)) {} }
//Example uses:
// store some info
store(shutdownTime, shutdownTemp);
// recall that info
eeprom->shutdownTime
Can anyone provide some guidance on updating this function, or use of EEPROM library generally, from 3.2 to 4.0?