Over the Air Software Update Realization within Generic Modules with Microcontrollers Using External Serial FLASH
Bibliographic record
Abstract
<div class="section abstract"><div class="htmlview paragraph">Connecting mobile communication channels to vehicles’ networks is currently attracting engineers in a wide range. Herein the desire of vehicle manufacturers to remotely execute software updates over the air (SOTA) within electronic control units (ECU) is probably the field of highest attention at the moment.</div><div class="htmlview paragraph">Today software updates are typically done at vehicle service stations and connection the vehicles electronic network via the onboard diagnosis (OBD) interface to a service computer. Herby the duration of the update is invisible to the user, as this happens during standard service appointments. With introduction of SOTA, these updates become very convenient to the customer and can lead to higher customer satisfaction levels. SOTA can be made transparent to the user however the method of implementation can affect the user experience. Currently the range of solutions for data storage to address SOTA ranges from: <ol class="list nostyle"><li class="list-item"><span class="li-label">1</span><div class="htmlview paragraph">Central Storage Approach whereby external Non-Volatile Memory (NVM) at this device and distributed via the internal car networks to the respective module to be updated.</div></li><li class="list-item"><span class="li-label">2</span><div class="htmlview paragraph">Localized storage external to the Microcontroller of the device being updated.</div></li><li class="list-item"><span class="li-label">3</span><div class="htmlview paragraph">Localized storage within the Microcontroller with an “A/B Swap” with separate Linker Scripts</div></li><li class="list-item"><span class="li-label">4</span><div class="htmlview paragraph">Localized storage internal to the Microcontroller of the device being updated supporting a so called “Ideal A/B Swap” approach.</div></li></ol></div><div class="htmlview paragraph">These solutions directly correlate with the duration of the switching time between software versions resulting in differing user experiences. In principle the closer the updated software is stored to the microcontroller, the shorter the time for the update. Additionally a solution may dictate as well new hardware capability in the microcontroller, i.e. the Ideal A/B Swap is the fastest approach and not all microcontrollers on the market today can support this method.</div><div class="htmlview paragraph">A compromise to implement a convenient SOTA user experience is to have additional external serial non-volatile memory attached to the microcontroller within an electronic control unit. The duration and handling of the software update would still allow for a high customer satisfaction.</div><div class="htmlview paragraph">The study starts with a short overview of the operation and activities for updating software within a vehicle. Next, a hardware and software architecture overview is given for the SOTA methods available. Followed by an in depth focus on the implementation method using external non-volatile memory at the microcontroller being updated. In conclusion performance analyses of the data flow for each of the solution from the central storage to the external non-volatile memory to the internal FLASH of the microcontroller. Herby the following aspects for implementation and performance measurements are considered: <ol class="list nostyle"><li class="list-item"><span class="li-label">1</span><div class="htmlview paragraph">Communication to central storage via the internal bus (CAN or CAN-FD) based on UDS</div></li><li class="list-item"><span class="li-label">2</span><div class="htmlview paragraph">Security Aspects</div><ol class="list nostyle"><li class="list-item"><span class="li-label">a</span><div class="htmlview paragraph">Central Storage to external non-volatile FLASH</div></li><li class="list-item"><span class="li-label">b</span><div class="htmlview paragraph">External non-volatile FLASH and internal FLASH</div></li><li class="list-item"><span class="li-label">c</span><div class="htmlview paragraph">Image Check before update activation</div></li></ol></li><li class="list-item"><span class="li-label">3</span><div class="htmlview paragraph">Fall back scenarios</div></li></ol></div></div>
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.001 | 0.000 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.001 | 0.001 |
| 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".