E-VCU Software Toolbox for ARM Cortex-R4 Processor based Electric Vehicle Control
Bibliographic record
Abstract
Electric Vehicles (EVs) are essential for addressing climate change but developing a safe and reliable EV presents sig-nificant challenges. Compliance with functional safety standards, such as IEC 61508 and ISO 26262, is vital for EV manufacturers. However, the traditional approach of writing functional safety-compliant C code for Electric Vehicle Control Unit's (E-VCU) is complex, time-consuming, and prone to errors. Companies who provide selective hardware with model-based design support with specific software environment such as dSPACE, VECTOR, Speed Goat and NI, are increasingly preferred by the industry to address these issues. As such, we propose a MATLAB/Simulink toolbox that allows users to do development on the TMS570LS31x microcontroller through Simulink interface to address the same issues. Our toolbox streamlines the design process by allowing for easy and efficient development of software models without re-quiring extensive hard coding. Additionally, the selected software environment provides tools to verify and validate the functional safety compliance of the Simulink models, ensuring the resulting product meets automotive grade safety-critical standards. We test our library using a novel TMS570LS31x-based E-VCU on a test bench and a real electric car. The system's functionality is monitored using our data logger blocks and Graphical User Interface (GUI) application in real-time.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one teacher head, not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".