{"id":22241,"date":"2025-12-02T16:22:25","date_gmt":"2025-12-02T14:22:25","guid":{"rendered":"https:\/\/www.btc-embedded.com\/?p=22241"},"modified":"2025-12-02T16:36:17","modified_gmt":"2025-12-02T14:36:17","slug":"developing-algorithms-for-sdvs","status":"publish","type":"post","link":"https:\/\/www.btc-embedded.com\/zh-hans\/developing-algorithms-for-sdvs\/","title":{"rendered":"Developing Algorithms for SDVs: Models or Handwritten Code?"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The rise of Software Defined Vehicles (SDVs) is a massive transformation in automotive industry. Unlike traditional vehicles, SDVs rely on software to deliver advanced features such as over-the-air updated, connectivity, autonomous driving etc. Two dominant approaches stand out: MBD and Handwritten C-code<\/a>. So, which approach is the best for SDVs? In this article, we\u2019ll explore history, pros and cons of both approaches.<\/p>

Software-Defined Vehicles (SDVs) trends are rising in the automotive industry. With features like ADAS, autonomous driving and over-the-air updates, software complexity is increasing day-by-day. Once critical question a developer might ask: What is the best approach to develop such a complex algorithm for SDV? Using Model-Based Development (MBD) or Handwritten C code.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

A Brief History: From Machine Code to MBD<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The question of using MBD or C-Code often comes up in SDV discussions. The answer is in the level of abstraction.<\/p>\n

In early days, engineer wrote raw machine code in strings of 1s and 0s, executed directly by the CPU to control simple hardware like 8-bit microcontrollers. This was however extremely difficult and required deep technical expertise.<\/p>\n

Assembly language was the next level of abstraction, first appeared in the 1950s and 60s. In this way, human-readable mnemonics took the place of binary instructions. For example, early washing machine controller used assembly language to manage timers and valves.<\/p>\n

As systems became more complex day by day, the next level of abstraction is this handwritten C code. It appeared in the 1980s and 90s giving the engineers the feasibility to create structured C-code using variables and functions. Compilers are used to convert or translate the sea code into assembly language. Automotive Engineers use C code for ABS controllers to ensure real-time performance.<\/p>\n

Finally, the 2000s brought Model-Based Development, where engineers could design algorithms graphically and simulate behavior. Auto-code generators are used to translate the Model into C-Code.<\/p>\n

With each high level of abstraction, specialized programming knowledge becomes less crucial, and Engineers gain flexibility to focus on system behavior and design quality rather than syntax and low-level details.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"SDV\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Why Model-Based Development in SDV?<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Model-Based Development uses graphical models to design and simulate algorithms before generation production code automatically. This approach is ideal for high level logic and complex algorithms.<\/p>

\u00a0<\/p>