Difference between revisions of "PF EEPROM"
From DIDEAS Wiki
m |
m |
||
| Line 8: | Line 8: | ||
* if FEATURE_USE_IMU is set, then after MC is boot (immediately before RUN_TIME), the dataport_select is set to two, and the IMU communications is enabled. | * if FEATURE_USE_IMU is set, then after MC is boot (immediately before RUN_TIME), the dataport_select is set to two, and the IMU communications is enabled. | ||
| − | =Goals= | + | =Problems / Goals= |
* need to be able to cleanly specify to boot too. | * need to be able to cleanly specify to boot too. | ||
| + | * what if a 'needed' table isn't loaded - eg calibration table. | ||
| + | ** possibly this type of error should limit the maximum level of boot capability. eg no calb table, then at most we remain in a mode that will allow for calibration | ||
Revision as of 00:14, 29 June 2009
- PF Top Nav;
- PFCMD : SC; MC; PFCMD_PY; Pf_calb_table_py; Virtual spring test; PF1_Code_History; PF EEPROM
EEPROM init table
- The defaults 'feature bits' set in statemachine.h are basically ignored (6-28-09). Although loaded in sm_init.c, they're overwritten in demux_sm - where it reads the the EEPROM init table.
- if FEATURE_MC_CURRENT_UPDATES is NOT SET, then demux_sm skips the states that boot MC through mode 2
- if FEATURE_USE_IMU is set, then after MC is boot (immediately before RUN_TIME), the dataport_select is set to two, and the IMU communications is enabled.
Problems / Goals
- need to be able to cleanly specify to boot too.
- what if a 'needed' table isn't loaded - eg calibration table.
- possibly this type of error should limit the maximum level of boot capability. eg no calb table, then at most we remain in a mode that will allow for calibration
