Over the Air Software Update Realization within Generic Modules with Microcontrollers Using External Serial FLASH
Notice bibliographique
Résumé
<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>
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Comment cette classification a été obtenuedéplier
Prédiction distillée sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Apprise à partir de 10 348 étiquettes directes de Codex et de 10 348 étiquettes directes de Gemma. Le mode candidate est l'union des têtes enseignantes seuillées; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont ni des étiquettes humaines ni des étiquettes directes de modèles de pointe.
Scores Codex et Gemma par catégorie
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,001 | 0,000 |
| Méta-épidémiologie (sens strict) | 0,001 | 0,001 |
| Méta-épidémiologie (sens large) | 0,001 | 0,000 |
| Bibliométrie | 0,000 | 0,000 |
| Études des sciences et des technologies | 0,001 | 0,001 |
| Communication savante | 0,001 | 0,001 |
| Science ouverte | 0,001 | 0,000 |
| Intégrité de la recherche | 0,001 | 0,001 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,000 | 0,000 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découleClassification
machine, non validéePrédiction automatique; un appel candidat d’une seule tête enseignante, pas un consensus.
Le détail, modèle par modèle et score par score, se trouve en fin de page sous « Comment cette classification a été obtenue ».