Unify halcogen projects between VCU and BMS

[rafguevara14]

The VCU and BMS run on the same hardware design. There is no reason not to configure all hardware upfront and never worry about configuration again until a new design is made

• [x] Run 1227 code on launchpad and see if it works. Use PhantomRelease1 branch
• [ ] Test ECAP module with PWM so that merging can work (FUTURE WORK)

[rafguevara14]

1227 and 1224 microcontrollers use the same reference manual so should have the same pin configurations

[rafguevara14]

The only differences between VCU and a launchpad is dedicated hardware. The launchpad does not have the following:

• CAN transceiver

• TSAL voltage divider? (double check)

• BUZZER and Brakelight need MOSFETS for "high voltage" switching (12V)

• Launchpad is 3V3 ADC range, Pin 69 is ADRef of VCU which is 5V

• APPS/BSE is a 5V range, so the Launchpad will saturate and be inaccurate when testing these sensors. We can potentially change to 5V Launchpad user manual pg6

[ManojBR105]

The VCU and BMS run on the same hardware design. There is no reason not to configure all hardware upfront and never worry about configuration again until a new design is made

• [x] Run 1227 code on launchpad and see if it works. Use PhantomRelease1 branch
• [ ] Test ECAP module with PWM so that merging can work (FUTURE WORK)

Simulation Mode works as expected, one change that was required was to switch PC_UART to scilin port instead of sci port, as the USB to UART on launchpad is connected to scilin port

[ManojBR105]

1227 and 1224 microcontrollers use the same reference manual so should have the same pin configurations

If 1227 and 1224 are set up with the same configuration with EMAC and FlexRay modules disabled, they have similar output from HalCoGen. Except, 1227 comes with extra EMAC header files, which are not used and won't affect correctness.

[rafguevara14]

@ManojBR105 Once you finish moving this info to the google doc, we can close this issue!