still the cost of remix 66-2-2-2

This commit is contained in:
rusefi 2020-04-19 18:58:22 -04:00
parent c14dce1dad
commit ca19d2fb44
3 changed files with 6 additions and 3 deletions

View File

@ -598,7 +598,7 @@ typedef enum __attribute__ ((__packed__)) {
typedef enum {
VVS_OOPS = 2,
Force_4_bytes_size_mass_storage = ENUM_32_BITS,
Force_4_bytes_size_can_vss_nbc_e = ENUM_32_BITS,
} can_vss_nbc_e;
typedef enum {

View File

@ -17,6 +17,9 @@
* Looks like 252 is explained by 60 tooth * 2 (number of fronts) * 2 (number of crank rotations within engine cycle)
*/
#ifndef PWM_PHASE_MAX_COUNT
// as of April 2020, trigger which requires most array length is REMIX_66_2_2_2
// we can probably reduce RAM usage if we have more custom logic of triggers with large number of tooth while
// pretty easy logic. like we do not need to REALLY have an array to remember the shape of evenly spaces 360 or 60/2 trigger :)
#define PWM_PHASE_MAX_COUNT 280
#endif /* PWM_PHASE_MAX_COUNT */
#define PWM_PHASE_MAX_WAVE_PER_PWM 3

View File

@ -695,10 +695,10 @@ void initEngineContoller(Logging *sharedLogger DECLARE_ENGINE_PARAMETER_SUFFIX)
// help to notice when RAM usage goes up - if a code change adds to RAM usage these variables would fail
// linking process which is the way to raise the alarm
#ifndef RAM_UNUSED_SIZE
#define RAM_UNUSED_SIZE 13500
#define RAM_UNUSED_SIZE 12900
#endif
#ifndef CCM_UNUSED_SIZE
#define CCM_UNUSED_SIZE 3600
#define CCM_UNUSED_SIZE 3000
#endif
static char UNUSED_RAM_SIZE[RAM_UNUSED_SIZE];
static char UNUSED_CCM_SIZE[CCM_UNUSED_SIZE] CCM_OPTIONAL;