From 2c3f3edf560698f7e5a458dfbf57d5b13d7d4d60 Mon Sep 17 00:00:00 2001 From: zhangxiaowei16 Date: Fri, 6 Feb 2026 09:54:17 +0800 Subject: [PATCH 1/2] Product documentation for version 5.4 --- README.md | 67 ++++-- README_zh-cn.md | 67 ++++-- en/faq/QuickStart_FAQ.md | 2 +- en/faq/devoloper_tech_faq.md | 225 ++++++++++++++++++ en/quickstart/openvela_ubuntu_quick_start.md | 1 + en/release_notes/v5.2.md | 2 +- en/release_notes/v5.4.md | 152 ++++++------ zh-cn/faq/devoloper_tech_faq.md | 4 +- .../quickstart/openvela_ubuntu_quick_start.md | 1 + zh-cn/release_notes/v5.4.md | 167 +++++++------ 10 files changed, 501 insertions(+), 187 deletions(-) create mode 100644 en/faq/devoloper_tech_faq.md diff --git a/README.md b/README.md index cff12586..5cf95f97 100644 --- a/README.md +++ b/README.md @@ -62,6 +62,50 @@ The name "Vela" is originated from the Latin term for "sail," which is also the - Please refer to the [Supported Architectures and Platforms](https://nuttx.apache.org/docs/latest/platforms/index.html) page for a complete list. - For adaptation cases regarding development boards, please refer to the [Case Documentation](./en/dev_board/Development_Board.md). +## Version Strategy + +We manage releases based on the `trunk` branch, using Tags to track release history. This ensures traceability and stability for production environments. + +### Release Tags + +Release tags are immutable markers created on the `trunk` branch. Each tag represents an officially released version of openvela. + +- **Production Environment Recommendation**: To ensure maximum system stability and security, we **strongly recommend** using the latest release tags in production environments (Production Environment), rather than using branch code directly. + +### Released Versions + +Below are the currently released stable versions and their change logs: + +- **trunk-5.4**: Please refer to the [v5.4 Release Notes](./en/release_notes/v5.4.md) for detailed changes. + +- **trunk-5.2**: Please refer to the [v5.2 Release Notes](./en/release_notes/v5.2.md) for detailed changes. + +### Version Maintenance Strategy + +openvela follows a strict version maintenance lifecycle: + +- **Patch Updates**: For critical bugs or security vulnerabilities discovered in released versions, the team issues new patch release tags (Patch Release) to provide fixes. +- **Naming Convention**: Patch versions increment based on the original version number, such as `trunk-5.2.1`. + +## Branch Strategy + +openvela adopts a dual-branch model to balance system innovation and stability. Please select the appropriate branch according to your development needs. + +### dev (Development Branch) + +- **Definition**: This is the cutting-edge development branch of openvela, aggregating the latest features and bug fixes. +- **Status**: The code updates frequently and remains in a state of continuous integration and rapid iteration. It may contain features not yet fully verified, so potential instability exists. +- **Target Audience**: + + - Developers who wish to experience new features early. + - Contributors planning to submit code or participate in core function development. + +### trunk (Stable Trunk Branch) + +- **Definition**: This is the fully tested main branch, representing the current stable state of the system. +- **Status**: Features from the `dev` branch are merged here only after they pass rigorous testing and verification. +- **Target Audience**: Most users who require high system stability, and engineers developing standard applications. + ## Quick start ### Device Development @@ -115,29 +159,6 @@ To see the full list of native apps, please visit the [Native App Examples Repos More Quick App examples are continuously being added. To see all examples, please visit the [Quick App Examples Repository](../../../packages_fe_examples). -## openvela Versioning Strategy - -- **dev (Development Branch)** - - Contains the latest features and fixes, and may be unstable. Recommended for developers who wish to experience new features or contribute. - -- **trunk (Main Stable Branch)** - - A comprehensively tested, stable version. Stable features from the `dev` branch are merged here. Recommended for most users seeking stability. - -- **Release Tags** - - Permanent tags created from the `trunk` branch, representing an official, stable release. We strongly recommend using the latest release tag in **production environments** to ensure maximum stability. - - - **List of Released Versions**: - - - `trunk-5.2`: For detailed changes in this version, please refer to its [v5.2 Release Notes](./en/release_notes/v5.2.md). - - `trunk-5.4`: For detailed changes in this version, please refer to its [v5.4 Release Notes](./en/release_notes/v5.4.md). - - - **Maintenance Policy**: - - Critical bug fixes for a released version will be delivered by releasing a new patch tag (e.g., `trunk-5.2.1`). - ## Code contribution - [Code Contribution Guide](./CONTRIBUTING.md) diff --git a/README_zh-cn.md b/README_zh-cn.md index 1f646402..45eb8a6d 100644 --- a/README_zh-cn.md +++ b/README_zh-cn.md @@ -63,6 +63,50 @@ Vela 的命名源自拉丁语中船帆的含义，也是南方星空中船帆星 - openvela 支持各种不同的架构（ARM32、ARM64、RISC-V、Xtensa、MIPS、CEVA 等）和硬件平台。请在[硬件支持](https://nuttx.apache.org/docs/latest/platforms/index.html)页面上查看完整列表。 - 关于**开发板**的适配案例，请参见[案例文档](./zh-cn/dev_board/Development_Board.md)。 +## 版本发布管理 (Version Strategy) + +我们基于 `trunk` 分支进行版本发布，通过标签（Tags）管理发布历史，确保生产环境的可追溯性与稳定性。 + +### 发布标签 (Release Tags) + +发布标签是基于 `trunk` 分支创建的不可变标记（Immutable Marker）。每个标签代表一个正式发布的 openvela 版本。 + +- **生产环境建议**：为了确保系统的最高稳定性和安全性，我们**强烈建议**在生产环境（Production Environment）中使用最新的发布标签，而非直接使用分支代码。 + +### 已发布版本列表 + +以下是当前已发布的稳定版本及其变更说明： + +- **trunk-5.4**：请查阅 [v5.4 版本发布说明](./zh-cn/release_notes/v5.4.md) 了解详细变更。 + +- **trunk-5.2**：请查阅 [v5.2 版本发布说明](./zh-cn/release_notes/v5.2.md) 了解详细变更。 + +### 版本维护策略 + +openvela 遵循严格的版本维护生命周期： + +- **补丁更新**：针对已发布版本中发现的关键缺陷（Critical Bugs）或安全漏洞，团队将发布新的补丁版本标签（Patch Release）进行修复。 +- **命名规则**：补丁版本将在原版本号基础上递增，例如 `trunk-5.2.1`。 + +## 代码分支管理 (Branch Strategy) + +openvela 采用双分支模型来平衡系统的创新性与稳定性。请根据您的开发需求选择合适的分支。 + +### dev (开发分支) + +- **定义**：这是 openvela 的前沿开发分支，汇集了最新的功能特性与缺陷修复。 +- **状态**：代码更新频率高，处于持续集成与快速迭代状态，可能包含尚未完全验证的特性，因此可能存在不稳定性。 +- **适用人群**： + + - 希望抢先体验新功能的开发者。 + - 计划向社区提交代码、参与核心功能建设的贡献者。 + +### trunk (主干稳定分支) + +- **定义**：这是经过全面测试的主干分支，代表了当前系统的稳定状态。 +- **状态**：`dev` 分支中的功能在经过严格测试验证稳定后，会被合并至此分支。 +- **适用人群**：大多数对系统稳定性有较高要求的用户，以及进行标准应用开发的工程师。 + ## 快速入门 ### 设备开发 @@ -116,29 +160,6 @@ Vela 的命名源自拉丁语中船帆的含义，也是南方星空中船帆星 快应用相关示例正在持续丰富中。查看所有示例，请访问[快应用示例仓库](../../../packages_fe_examples)。 -## openvela 版本策略 - -- **dev (开发分支)** - - 汇集了最新的功能与修复，可能不稳定。推荐给希望体验新功能或参与贡献的开发者。 - -- **trunk (主干稳定分支)** - - 经全面测试的稳定版本，`dev` 分支的稳定功能会合并于此。推荐大多数追求稳定性的用户使用。 - -- **Release Tags (版本发布标签)** - - 基于 `trunk` 分支创建的永久标记，代表一个正式、稳定的发布版本。我们强烈建议**生产环境**使用最新的发布标签以确保最高稳定性。 - - - **已发布版本列表**： - - - `trunk-5.2`：关于此版本的详细变更，请查阅其 [v5.2 版本发布说明](./zh-cn/release_notes/v5.2.md)。 - - `trunk-5.4`：关于此版本的详细变更，请查阅其 [v5.4 版本发布说明](./zh-cn/release_notes/v5.4.md)。 - - - **维护策略**： - - 针对已发布版本的关键 Bug 修复，会通过发布新的补丁版本标签来提供（例如 `trunk-5.2.1`）。 - ## 参与贡献 - [代码贡献指南](./CONTRIBUTING_zh-cn.md) diff --git a/en/faq/QuickStart_FAQ.md b/en/faq/QuickStart_FAQ.md index 9308af90..c948e1d8 100644 --- a/en/faq/QuickStart_FAQ.md +++ b/en/faq/QuickStart_FAQ.md @@ -1,6 +1,6 @@ # Quick Start FAQ -\[ English | [简体中文](./../../zh-cn/faq/QuickStart_FAQ.md) \] +[ English | [简体中文](./../../zh-cn/faq/QuickStart_FAQ.md) ] ## I. Unable to Access Remote Repository diff --git a/en/faq/devoloper_tech_faq.md b/en/faq/devoloper_tech_faq.md new file mode 100644 index 00000000..474c8f70 --- /dev/null +++ b/en/faq/devoloper_tech_faq.md @@ -0,0 +1,225 @@ +# Developer FAQ + +[ English | [简体中文](./../../zh-cn/faq/devoloper_tech_faq.md) ] + +## I. Community and General + +### 1. What should I do if I encounter technical issues or bugs? + +If it is a technical issue, please submit it on the [Issue page](../../../../docs/issues). + +- For blocking issues, after submitting the Issue, you can send the link directly to the WeChat group for a quick response. +- For non-blocking issues, the community maintenance team will reply and handle them regularly within the Issue tracker. + +### 2. Are there rewards for community contributions? + +Yes, the community has a contribution incentive mechanism. For detailed reward rules and instructions, please refer to the [Contribution Reward Instructions](../../../../docs/issues). + +### 3. When will the IDE be released? + +It is expected to be officially released in early 2026. + +### 4. Is there a difference between the Gitee and GitHub versions of the source code repository? + +There is no difference between the two. The GitHub and Gitee internal repositories utilize bidirectional real-time synchronization. You can choose either one for access based on your network conditions. + +## II. Compilation and Build + +### 5. Does openvela application development (e.g., Hello World) run in kernel mode or user mode? + +The system primarily supports three compilation modes. + +Currently, the official recommendation is to use **Flat Build**, where applications and the kernel reside in the same address space (similar to kernel mode). This provides optimal performance and is suitable for embedded small systems such as modules and smart bands. + +Additionally, Kernel Build (user mode isolation) and Product Mode are supported, but they are less commonly used in resource-constrained scenarios. + +### 6. Using the recommended Flat Build mode, will an application crash cause the entire system to crash? + +Theoretically, in Flat Build mode, since applications and the kernel share the same space, an application crash can indeed affect the system. However, openvela is developing a polymorphic isolation protection mechanism to prevent memory corruption. Although the system supports running ELF binary files, the official recommendation remains strongly in favor of using Flat Build mode for embedded scenarios. + +### 7. Does openvela support incremental compilation? Do I need to rebuild everything every time I modify the code? + +The system supports incremental compilation. + +- If you only modified `.c` or `.h` source files, you can compile incrementally, which is relatively fast. +- However, if you modified the `Kconfig` (menuconfig) configuration file (i.e., enabled or disabled certain features), it is recommended to perform a full recompilation to ensure the configuration takes effect properly. + +## III. System Architecture and Kernel + +### 8. Is the openvela protocol stack located in the module or on the AP side? + +The protocol stacks (such as TCP/IP, Bluetooth Host Stack, etc.) run on the AP (Application Processor) side. External WiFi or Bluetooth modules are typically used only as transceivers, communicating with the main controller via interfaces like HCI or SDIO, with the modules primarily running firmware internally. + +### 9. I see many functions starting with NX_ in the code (e.g., nx_read). Should I use them in my application? + +**It is not recommended.** + +Functions starting with `NX_` are typically system calls or low-level encapsulations used internally by the kernel. + +To ensure code standardization and portability (openvela has passed PNS 52 certification), please strictly use standard POSIX interfaces (such as `open`, `read`, `pthread_create`) for development. + +### 10. In isolation mode, does user memory use a physical flat model or virtual address mapping? + +The system uses a **Physical Flat Memory Model**. + +In this model, user memory is not mapped via virtual addresses through an MMU like in Linux. Instead, independent segments are partitioned within the physical flat memory. + +### 11. Do user memory segments of different processes (Tasks) have the same virtual base address? + +**No, they do not.** + +Since there is no virtual address overlapping, different processes do not share the same virtual base address (e.g., all processes starting from 0x0000). Each process possesses an independent base address in physical memory, and different tasks are distinguished by their physical address ranges. + +### 12. Does the system's isolation mechanism rely on MMU or MPU? + +System memory isolation primarily relies on the **MPU (Memory Protection Unit)**. + +This is designed to achieve secure isolation even on chips that do not possess an MMU (such as the Cortex-M series). + +### 13. How is secure isolation achieved without an MMU? + +This is achieved by defining access permission regions on physical memory via the MPU. + +The system allocates specific physical memory regions for each task and utilizes the MPU to restrict that task to accessing only its allocated region, thereby realizing secure isolation between tasks at the physical addressing level. + +### 14. In a multi-tasking environment, how are the user-mode Heap and Stack allocated? + +To align with the MPU's region protection mechanism, each task is technically required to have an independent user-mode Heap and Stack. This ensures that runtime data storage does not interfere with others and prevents out-of-bounds memory access between tasks. + +## IV. Development Environment and Tools + +### 15. Are the JLink and Trace32 debugging tools mentioned in the documentation mandatory? + +This depends on your run target. + +If debugging on real hardware, hardware debuggers like JLink or Trace32 are usually required. If you are using a Simulator (running locally on Linux) or an Emulator (QEMU/Goldfish) for development, the system comes with built-in debugging mechanisms, and you can use GDB directly without extra hardware. + +### 16. What if the simulator fails to start (missing libraries) when configuring the environment on macOS (M1/M2)? + +Currently, QEMU/Goldfish has relatively less compatibility testing on macOS, and you may encounter missing libraries or instruction set translation efficiency issues. + +At this stage, it is strongly recommended to install an **Ubuntu 22.04 Virtual Machine** on macOS for development, as this is the most fully verified and stable environment. + +### 17. What if `repo sync` has no response or fails to download in the Ubuntu VM? + +Please troubleshoot in the following order: + +- Confirm you are downloading code based on the `trunk` branch. +- Confirm the operating system version is Ubuntu 22.04. +- Check network connections and proxy settings (there may be network firewall issues). + +If the problem persists after troubleshooting, please screenshot the error message and submit an Issue in the community. + +### 18. Does openvela have a companion VS Code plugin or IDE? + +Yes, there is an official IDE customized based on VS Code that supports openvela development. + +The current version has not yet been fully released as open source. It will be synchronized with developers as soon as it is officially released. + +### 19. Why can the AI assistant (like the Doubao plugin) in the Quick App IDE only read code but not edit/automatically modify it? + +This situation is usually caused by compatibility issues resulting from the synchronization delay between the rapidly updating VS Code core version and the VS Code source version built into the IDE. + +It is recommended to report the specific plugin version and IDE version, and the development team will investigate and fix it. + +### 20. Why can't I see network interfaces when enabling network configuration under the QEMU goldfish arm64 configuration? + +This is because basic configurations like `goldfish arm64` are primarily used to verify CPU architecture and basic kernel functions, and do not enable complete network bridging or peripheral support by default. + +If you need to verify network or multimedia functions, it is recommended to use product-form configuration files, such as the complete configuration for `smart speaker` or `ARMv7a Goldfish`. + +### 21. Files created by programs running in the simulator are lost after restart. How can I achieve data persistence? + +It is recommended to use the **9PFS (9P File System)** feature. + +By directly mounting and mapping a folder from the host machine (Host PC) into the simulator, data can be written directly to the PC hard drive, achieving both persistence and convenient viewing on the PC side. + +### 22. Why do low-power devices like smart bands/watches also use QEMU Goldfish (ARM A-series) for simulation? + +This is mainly to unify the teaching platform and facilitate management; currently, the QEMU platform based on Google Goldfish is used uniformly. +The openvela operating system abstracts underlying architectural differences, so whether the bottom layer is A-series or M-series has little impact on the learning of upper-layer applications and frameworks. Support for ARM M/R series simulators will be released in the future. + +### 23. Is it possible to start driver development learning and course design before physical development boards arrive? + +**Absolutely.** + +It is recommended to prioritize using the simulator (QEMU). The driver framework is consistent across the simulator and physical boards. You can first complete theoretical learning, framework development, and core concepts like memory management based on the simulator, and then perform hardware adaptation verification once the development board arrives. + +### 24. Does Telephony (phone/communication) related business need to be verified on real devices? + +It is recommended to use the **Simulator**. + +Debugging communication business on real machines has a high threshold (requires Modem, SIM card, network access). The openvela simulator features a built-in Modem Simulator capable of fully simulating processes like making calls and sending/receiving SMS, which is sufficient to meet teaching needs. + +### 25. Can the RPK file generated by Quick App packaging run directly on openvela devices? + +Currently, it cannot. The Quick App framework engine (Runtime) is planned to be open-sourced in library form and integrated into the system around **February 2026**. At this stage, it is recommended to use the simulator for learning and development. + +## V. Hardware Adaptation and Porting + +### 26. Can openvela be ported to hardware platforms not currently officially supported (e.g., STM32)? + +**Yes.** + +openvela is fully compatible with the NuttX kernel. Theoretically, openvela can be smoothly adapted and ported to all hardware platforms supported by NuttX. + +### 27. What is the current support status for ESP32 series development boards? + +Although the bottom layer is compatible with NuttX, adaptation and testing for ESP32 are not yet fully covered, and some Demos may not run directly. If a stable development experience is required, it is currently recommended to prioritize using officially verified ARM platform development boards. + +### 28. When developing drivers or low-level code, which directory should the code be submitted to? + +Please decide based on the universality of the code: + +- General driver frameworks, scheduling code, or bug fixes are recommended to be submitted to the `nuttx` main directory (e.g., under `drivers`). +- Specific chip vendor or private board-level driver code is recommended to be stored in the `vendor` directory. + +openvela follows the Apache license, so you can freely choose whether to open source it. + +## VI. Application Framework and Multimedia + +### 29. Is the underlying engine for openvela Quick Apps Node.js or V8? + +Neither. The openvela device-side Quick App engine is based on **QuickJS**. + +### 30. What is the difference in running mechanisms between Quick Apps and Native Apps? + +- Quick Apps run in an independent container within the system, isolated from the system. A crash does not easily cause a system freeze, and they invoke underlying capabilities via JS interfaces. +- Native Apps call system APIs directly, offering higher performance but also a higher degree of coupling with the system. + +### 31. Does openvela currently support running MPlayer? + +Running MPlayer directly is currently not supported; the official team has not yet ported it. + +### 32. What multimedia development tools or frameworks are available under the current system? + +Currently available solutions include: ported FFmpeg, the system's built-in native multimedia toolkit (please refer to the [Sim Environment Audio Function Development Guide](../quickstart/emulator/sim_audio_guide.md)), and ported open-source codec libraries such as `libx264`, `openh264`, and `libopus`. + +### 33. Which common Linux multimedia tools are suitable for porting to openvela? + +Tools with a Pure Software implementation are usually easier to port. Tools that rely heavily on specific hardware drivers or hardware acceleration cannot be ported directly and must be adapted based on openvela's existing multimedia framework. + +### 34. Is there any reference case or path if third-party code needs to be ported? + +Developers are advised to directly reference the `apps/external` folder in the source directory. This directory contains a large number of ported third-party libraries and serves as the best practice for understanding the build system and porting methods. + +### 35. For developing graphical interfaces on openvela, are Qt or GTK/JDK supported? + +**Not supported and not recommended.** + +- Qt and GTK frameworks are too heavy for embedded RTOS. +- The official recommendation is to use **LVGL**, which the team has deeply optimized and integrated well with the NuttX system. + +### 36. Does openvela support IoT protocols like MQTT, CoAP, Matter? + +**Yes.** + +The system has integrated MQTT, CoAP, and Matter (partial versions). + +Relevant libraries are usually located in the `apps/netutils` or `external` directories and can be referenced directly in the source code. + +### 37. Is it necessary to deeply master kernel principles just to learn multimedia development? + +**No.** + +You only need to master basic system calls (such as threads, locks, message queues, Sockets). The learning focus should be on Pipeline design (decoding, post-processing), without needing to delve into kernel underlying implementations like scheduling algorithms. \ No newline at end of file diff --git a/en/quickstart/openvela_ubuntu_quick_start.md b/en/quickstart/openvela_ubuntu_quick_start.md index 5d7c7d59..e1562fa9 100644 --- a/en/quickstart/openvela_ubuntu_quick_start.md +++ b/en/quickstart/openvela_ubuntu_quick_start.md @@ -185,6 +185,7 @@ After the emulator starts, you will see the `goldfish-armv8a-ap>` prompt, indica - Frequently Asked Questions - [Quick Start FAQ](../faq/QuickStart_FAQ.md) + - [Developer FAQ](../faq/QuickStart_FAQ.md) - Further Reading diff --git a/en/release_notes/v5.2.md b/en/release_notes/v5.2.md index e6dabc8b..9182f830 100644 --- a/en/release_notes/v5.2.md +++ b/en/release_notes/v5.2.md @@ -1,6 +1,6 @@ # openvela trunk-5.2 -\[ English | [简体中文](../../zh-cn/release_notes/v5.2.md) \] +[ English | [简体中文](../../zh-cn/release_notes/v5.2.md) ] ## I. Quick Start diff --git a/en/release_notes/v5.4.md b/en/release_notes/v5.4.md index e7f09356..34820564 100644 --- a/en/release_notes/v5.4.md +++ b/en/release_notes/v5.4.md @@ -1,91 +1,109 @@ # openvela trunk-5.4 -\[ English | [简体中文](../../zh-cn/release_notes/v5.4.md) \] +[ English | [简体中文](../../zh-cn/release_notes/v5.4.md) ] ## I. Overview + openvela has been dedicated to introducing support for more chips, enhancing system real-time communication capabilities, and significantly improving system robustness, storage functionality, and debuggability. This release focuses on enhancements around the following core themes: + - Hardware Ecosystem Expansion: **Added support for [Infineon AURIX™ TC4](../quickstart/development_board/tc4d9_evb_guide.md), [Flagchip MCU](../quickstart/development_board/fc7300f8m_evb_guide.md), and QEMU-R52 SIL platforms**, broadening the scope of platform applicability. - System Kernel Hardening: **Achieved collaborative operation of SMP and PM, introduced MPU-based thread stack protection and RPC framework refactoring**, making the system safer and more stable. - Key Capabilities Integration: **Added SocketCAN and Ethernet protocol stacks; introduced the highly reliable NVS2 storage solution**. - Developer Experience Optimization: Provided low-overhead FDX real-time tracing tools and multiple LVGL application examples, lowering the barrier for development and debugging. ## II. Major New Features & Enhancements -### **1. Platform Support** + +### 1. Platform Support + - Added support for Infineon AURIX™ TriCore™ TC4 chips - Added support for Flagchip MCUs - Added Cortex-R52 core support under QEMU platform, supporting Vector SIL platform - Resolved compilation issues for nuttx boards, better supporting native nuttx boards platforms -### **2. Kernel & Security** -- Power Management (PM) & Symmetric Multi-Processing (SMP): - - Achieved simultaneous enablement of SMP and PM functions, and completed functional verification on the `qemu-armv8a` platform, covering basic PM functions and `ostest` base cases. + +### 2. Kernel & Security + +- Power Management (PM) & Symmetric Multi-Processing (SMP): Achieved simultaneous enablement of SMP and PM functions, and completed functional verification on the `qemu-armv8a` platform, covering basic PM functions and `ostest` base cases. + - RPC - - Framework Refactoring: Refactored the RPC framework to possess greater versatility, enabling cross-core communication capabilities for other VirtIO devices. - - Functional Enhancements for Rptun/Rpmsg: Introduced a multi-priority mechanism to meet the real-time needs of automotive scenarios, and fixed issues from functional safety code scans. + + - Framework Refactoring: Refactored the RPC framework to possess greater versatility, enabling cross-core communication capabilities for other VirtIO devices. + - Functional Enhancements for Rptun/Rpmsg: Introduced a multi-priority mechanism to meet the real-time needs of automotive scenarios, and fixed issues from functional safety code scans. + - Memory Management Enhancements: Implemented Task-independent Heap space, now supported by libraries like `libdbus`. - Binder Message Mechanism: Integrated Binder server/client fds into the `libuv` event loop, handling messages via callbacks, achieving unified management with other modules. - Added Rpmsg Battery & Gauge drivers. -- Inter-thread Isolation Protection Mechanism - The kernel now supports thread stack protection based on the hardware Memory Protection Unit (MPU). When a thread experiences a stack overflow, this mechanism triggers a hardware exception, preventing it from corrupting other threads' stack spaces or critical data. -- Code Quality: - - Completed multiple static code issue fixes, improving the overall quality of the code base. -### **3. Communication** -- Added SocketCAN and Ethernet Support - Introduced a CAN communication framework following standard Socket APIs. Users can now use standard interfaces like `socket()`, `bind()`, `send()`, `recv()` for CAN message transmission and filtering. -- WebSocket Function Enhancement - Added default certificate support for the WebSocket Feature, simplifying the secure connection establishment process. -### **4. Storage** -- Added NVS2 (Non-Volatile Storage v2) - Integrated a brand-new, highly reliable NVS2 storage solution. This storage solution is deeply optimized for embedded Flash media, supporting wear leveling, power-loss safety, and data encryption. -### **5. Debugging & Diagnostics** -- Added FDX-based Real-time Trace Function - Implemented a low-intrusion real-time tracing tool based on the FDX (Fast Debug eXchange) protocol. It can capture and export high-precision system events, such as task switching, interrupt response, semaphore operations, etc., with extremely low system overhead. -## **6. Application Examples** +- Inter-thread Isolation Protection Mechanism: The kernel now supports thread stack protection based on the hardware Memory Protection Unit (MPU). When a thread experiences a stack overflow, this mechanism triggers a hardware exception, preventing it from corrupting other threads' stack spaces or critical data. + +- Code Quality: Completed multiple static code issue fixes, improving the overall quality of the code base. + +### 3. Communication + +- Added SocketCAN and Ethernet Support: Introduced a CAN communication framework following standard Socket APIs. Users can now use standard interfaces like `socket()`, `bind()`, `send()`, `recv()` for CAN message transmission and filtering. +- WebSocket Function Enhancement: Added default certificate support for the WebSocket Feature, simplifying the secure connection establishment process. + +### 4. Storage + +Added NVS2 (Non-Volatile Storage v2): Integrated a brand-new, highly reliable NVS2 storage solution. This storage solution is deeply optimized for embedded Flash media, supporting wear leveling, power-loss safety, and data encryption. + +### 5. Debugging & Diagnostics + +Added FDX-based Real-time Trace Function: Implemented a low-intrusion real-time tracing tool based on the FDX (Fast Debug eXchange) protocol. It can capture and export high-precision system events, such as task switching, interrupt response, semaphore operations, etc., with extremely low system overhead. + +## 6. Application Examples + - Added [Breakout Game](./../../../../../packages_demos/blob/trunk-5.4/breakout/Readme.md): A touchscreen breakout game developed based on openvela and LVGL, which has implemented basic game logic, added image assets, and implemented impact sound effects. - Added [Virtual Pet](./../../../../../packages_demos/blob/trunk-5.4/pet/README.md) application: An interactive demo program based on the LVGL graphics library, simulating the process of raising a digital pet. Users can care for the virtual pet through operations like feeding, giving water, exercise, and rest to improve its mood and level. - [Snake Game](./../../../../../packages_demos/blob/trunk-5.4/snake_game/Readme.md): An automatic Snake game implemented using the LVGL graphics library. -- [Electronic Wooden Fish](./../../../../../packages_demos/blob/trunk-5.4//wooden_fish/README_zh-cn.md): Based on the openvela `nxaudio` service and the upper-layer LVGL UI framework, implementing a complete interaction link containing responsive layout and secure resource management, realizing an application showcase with smooth animation effects, secure resource management, and a good user experience. -## **7. Development Tools** -- Ubuntu Environment VS Code Plugin Support - Support installing openvela VS Code plugin in Ubuntu environment, achieving full-process support from project creation, compilation and building, system debugging to application development, significantly improving development efficiency. ([openvela VS Code Plugin Usage Guide](../quickstart/vscode_plugin_usage.md)) -## **8. Emulator Runtime Parameter Extensions** -- `emulator.sh` adds `-keep` parameter support - - If `emulator.sh` supports multi-instance configuration, you can access an instance with a specified name via the `-keep` parameter (creating it if it doesn't exist), and relevant contexts will not be deleted when that instance exits. - ```plaintext - # Usage - cp cmake_out/vela_goldfish-arm64-v8a-ap/nuttx* cmake_out/vela_goldfish-arm64-v8a-ap/vela_* cmake_out/vela_goldfish-arm64-v8a-ap/advancedFeatures.ini nuttx/ - - ./emulator.sh vela -keep -no-window - - # Test example: create a test file in /data directory and write content - nsh> echo test > /data/test - nsh> echo "openvvela qemu keep test" >> /data/test - nsh> quit - - # Exit emulator and re-enter, the previously written content is still preserved - ./emulator.sh vela -keep -no-window - nsh> cat /data/test - test - openvela qemu keep test - ``` +- [Electronic Wooden Fish](./../../../../../packages_demos/blob/trunk-5.4/wooden_fish/README_zh-cn.md): Based on the openvela `nxaudio` service and the upper-layer LVGL UI framework, implementing a complete interaction link containing responsive layout and secure resource management, realizing an application showcase with smooth animation effects, secure resource management, and a good user experience. + +## 7. Development + +Ubuntu Environment VS Code Plugin Support: Support installing openvela VS Code plugin in Ubuntu environment, achieving full-process support from project creation, compilation and building, system debugging to application development, significantly improving development efficiency. ([openvela VS Code Plugin Usage Guide](../quickstart/vscode_plugin_usage.md)) + +## 8. Emulator Runtime Parameter Extensions + +- `emulator.sh` adds `-keep` parameter support: + + If `emulator.sh` supports multi-instance configuration, you can access an instance with a specified name via the `-keep` parameter (creating it if it doesn't exist), and relevant contexts will not be deleted when that instance exits. + + ```bash + # Usage + cp cmake_out/vela_goldfish-arm64-v8a-ap/nuttx* cmake_out/vela_goldfish-arm64-v8a-ap/vela_* cmake_out/vela_goldfish-arm64-v8a-ap/advancedFeatures.ini nuttx/ + + ./emulator.sh vela -keep -no-window + + # Test example: create a test file in /data directory and write content + nsh> echo test > /data/test + nsh> echo "openvvela qemu keep test" >> /data/test + nsh> quit + + # Exit emulator and re-enter, the previously written content is still preserved + ./emulator.sh vela -keep -no-window + nsh> cat /data/test + test + openvela qemu keep test + ``` - `emulator.sh` adds support for using Hostfs function, default support using 9pfs, effect as follows: - ```Shell - goldfish-armv8a-ap> df -h - Filesystem Size Used Available Mounted on - binfs 0B 0B 0B /bin - fatfs 255M 78M 177M /data - romfs 1152B 1152B 0B /etc - hostfs 0B 0B 0B /host - procfs 0B 0B 0B /proc - v9fs 878G 626G 252G /share - romfs 512B 512B 0B /system - tmpfs 6K 1K 5K /tmp - ``` - - Usage: - ```plaintext - # Usage - cp cmake_out/vela_goldfish-arm64-v8a-ap/nuttx* cmake_out/vela_goldfish-arm64-v8a-ap/vela_* cmake_out/vela_goldfish-arm64-v8a-ap/advancedFeatures.ini nuttx/ - - ./emulator.sh vela - ``` + + ```bash + goldfish-armv8a-ap> df -h + Filesystem Size Used Available Mounted on + binfs 0B 0B 0B /bin + fatfs 255M 78M 177M /data + romfs 1152B 1152B 0B /etc + hostfs 0B 0B 0B /host + procfs 0B 0B 0B /proc + v9fs 878G 626G 252G /share + romfs 512B 512B 0B /system + tmpfs 6K 1K 5K /tmp + ``` + + Usage: + + ```bash + # Usage + cp cmake_out/vela_goldfish-arm64-v8a-ap/nuttx* cmake_out/vela_goldfish-arm64-v8a-ap/vela_* cmake_out/vela_goldfish-arm64-v8a-ap/advancedFeatures.ini nuttx/ + + ./emulator.sh vela + ``` diff --git a/zh-cn/faq/devoloper_tech_faq.md b/zh-cn/faq/devoloper_tech_faq.md index 3665bdfc..692b1543 100644 --- a/zh-cn/faq/devoloper_tech_faq.md +++ b/zh-cn/faq/devoloper_tech_faq.md @@ -1,4 +1,6 @@ -# openvela 开发者常见问题解答 (FAQ) +# 开发者常见问题解答 + +[ [English](./../../en/faq/devoloper_tech_faq.md) | 简体中文 ] ### 一、社区与通用 diff --git a/zh-cn/quickstart/openvela_ubuntu_quick_start.md b/zh-cn/quickstart/openvela_ubuntu_quick_start.md index 08c3094c..7b3d91a0 100644 --- a/zh-cn/quickstart/openvela_ubuntu_quick_start.md +++ b/zh-cn/quickstart/openvela_ubuntu_quick_start.md @@ -185,6 +185,7 @@ sudo mv repo /usr/local/bin - 常见问题 - [快速入门常见问题](../faq/QuickStart_FAQ.md) + - [开发者常见问题解答](../faq/devoloper_tech_faq.md) - 进一步阅读 diff --git a/zh-cn/release_notes/v5.4.md b/zh-cn/release_notes/v5.4.md index 050cd94b..3fa0778e 100644 --- a/zh-cn/release_notes/v5.4.md +++ b/zh-cn/release_notes/v5.4.md @@ -1,91 +1,116 @@ # openvela trunk-5.4 -\[ [English](../../en/release_notes/v5.4.md) | 简体中文 \] +[ [English](../../en/release_notes/v5.4.md) | 简体中文 ] ## 一、概览 + openvela 一直致力于引入更多的芯片的支持、增强系统的实时通信能力，并大幅提升了系统的健壮性、存储功能和可调试性。本次发布围绕以下核心主题进行了增强： -- 硬件生态扩展：**新增对**[**英飞凌 AURIX™ TC4**](../quickstart/development_board/tc4d9_evb_guide.md)**、**[**旗芯微 MCU**](../quickstart/development_board/fc7300f8m_evb_guide.md)** 及 QEMU-R52 SIL 平台的支持**，拓宽了平台适用范围。 + +- 硬件生态扩展：**新增对**[**英飞凌 AURIX™ TC4**](../quickstart/development_board/tc4d9_evb_guide.md)**、**[**旗芯微 MCU**](../quickstart/development_board/fc7300f8m_evb_guide.md)** 及 QEMU-R52 SIL 平台的支持，拓宽了平台适用范围。 - 系统内核加固：**实现了 SMP 与 PM 的协同工作，引入了基于 MPU 的线程栈保护和 RPC 框架重构**，系统更安全、更稳定。 - 关键能力集成：**新增了 SocketCAN 和以太网协议栈；引入了高可靠性的 NVS2 存储方案**。 - 开发者体验优化：提供了低开销的 FDX 实时追踪工具和多个 LVGL 应用范例，降低了开发和调试门槛。 ## 二、主要新增功能与增强 -### **1、平台支持 (Platform Support)** + +### 1、平台支持 (Platform Support) + - 新增对英飞凌 AURIX™ TriCore™ TC4 芯片的支持 - 新增对旗芯微（Flagchip）MCU 的支持 - QEMU 平台下新增 Cortex-R52 核支持，支持 Vector SIL 平台 - 解决 nuttx boards 的编译问题，更好得支持原生 nuttx boards 平台 -### **2、内核与安全 (Kernel & Security)** -- 电源管理 (PM) & 对称多处理 (SMP): - - 实现了 SMP 和 PM 功能的同时开启，并在 `qemu-armv8a` 平台上完成功能验证，覆盖了 PM 基础功能和 `ostest` 的基础用例。 -- RPC - - 框架重构: 重构了 RPC 框架，使其具备更强的通用性，能够为其他 VirtIO 设备提供跨核通信能力。 - - 对 Rptun/Rpmsg 进行了功能增强，引入多优先级机制以满足汽车场景的实时性需求，并修复了功能安全相关的代码扫描问题。 + +### 2、内核与安全 (Kernel & Security) + +- 电源管理 (PM) & 对称多处理 (SMP)：实现了 SMP 和 PM 功能的同时开启，并在 `qemu-armv8a` 平台上完成功能验证，覆盖了 PM 基础功能和 `ostest` 的基础用例。 + +- RPC + + - 框架重构: 重构了 RPC 框架，使其具备更强的通用性，能够为其他 VirtIO 设备提供跨核通信能力。 + - 对 Rptun/Rpmsg 进行了功能增强，引入多优先级机制以满足汽车场景的实时性需求，并修复了功能安全相关的代码扫描问题。 + - 内存管理增强: 实现了 Task 独立的 Heap 空间，`libdbus` 等库已支持。 + - Binder 消息机制: 将 Binder 的 server/client fd 集成到 `libuv` 事件循环中，通过回调进行消息处理，实现了与其他模块的统一管理。 + - 新增 Rpmsg Battery & Gauge 驱动。 -- 线程间隔离保护机制 - 内核现已支持基于硬件内存保护单元 (MPU) 的线程栈保护功能。当一个线程发生栈溢出时，该机制会触发硬件异常，阻止其破坏其他线程的栈空间或关键数据。 -- 代码质量: - - 完成了多项静态代码问题的修复，提升了代码库的整体质量。 -### **3、通信 (Communication)** -- 新增 SocketCAN 、以太网支持 - 引入了遵循标准 Socket API 的 CAN 通信框架。用户现在可以使用 `socket()`, `bind()`, `send()`, `recv()` 等标准接口进行 CAN 报文的收发和过滤。 -- WebSocket 功能增强 - 为 WebSocket Feature 新增了默认证书支持，简化了安全连接的建立流程。 -### **4、存储 (Storage)** -- 新增 NVS2 (Non-Volatile Storage v2) - 集成了一个全新的、全新高可靠性的 NVS2 存储方案。该存储方案针对嵌入式 Flash 介质进行了深度优化，支持磨损均衡、掉电安全和数据加密。 -### **5、调试与诊断 (Debugging & Diagnostics)** -- 新增基于 FDX 的实时性 Trace 功能 - 实现了一种基于 FDX (Fast Debug eXchange) 协议的低侵入式实时追踪工具。它能够以极低的系统开销，捕获并导出高精度的系统事件，如任务切换、中断响应、信号量操作等。 -## **6、应用示例** + +- 线程间隔离保护机制：内核现已支持基于硬件内存保护单元 (MPU) 的线程栈保护功能。当一个线程发生栈溢出时，该机制会触发硬件异常，阻止其破坏其他线程的栈空间或关键数据。 + +- 代码质量：完成了多项静态代码问题的修复，提升了代码库的整体质量。 + +### 3、通信 (Communication) + +- 新增 SocketCAN、以太网支持：引入了遵循标准 Socket API 的 CAN 通信框架。用户现在可以使用 `socket()`, `bind()`, `send()`, `recv()` 等标准接口进行 CAN 报文的收发和过滤。 + +- WebSocket 功能增强：为 WebSocket Feature 新增了默认证书支持，简化了安全连接的建立流程。 + +### 4、存储 (Storage) + +新增 NVS2 (Non-Volatile Storage v2)：集成了一个全新的、全新高可靠性的 NVS2 存储方案。该存储方案针对嵌入式 Flash 介质进行了深度优化，支持磨损均衡、掉电安全和数据加密。 + +### 5、调试与诊断 (Debugging & Diagnostics) + +新增基于 FDX 的实时性 Trace 功能：实现了一种基于 FDX (Fast Debug eXchange) 协议的低侵入式实时追踪工具。它能够以极低的系统开销，捕获并导出高精度的系统事件，如任务切换、中断响应、信号量操作等。 + +## 6、应用示例 + - 新增[打砖块游戏](./../../../../../packages_demos/blob/trunk-5.4/breakout/Readme.md)：基于 openvela 和 LVGL 开发的触屏打砖块游戏，已实现了基本游戏逻辑，增加了图片素材并实现了打击音效。 + - 新增[虚拟宠物](./../../../../../packages_demos/blob/trunk-5.4/pet/README.md)应用：一个基于LVGL图形库的交互式演示程序，模拟了一个数字宠物的饲养过程。用户可以通过喂食、饮水、运动和休息等操作来照顾虚拟宠物，提升其心情和等级。 -- [贪吃蛇游戏](./../../../../../packages_demos/blob/trunk-5.4/snake_game/Readme.md)：一个使用 LVGL 图形库实现的自动贪吃蛇游戏 -- [电子木鱼](./../../../../../packages_demos/blob/trunk-5.4/wooden_fish/README_zh-cn.md)：基于 openvela `nxaudio` 服务与上层 LVGL UI 框架，并实现了包含响应式布局和安全资源管理的完整交互链路，实现了一个动画效果流畅、资源安全管理、良好用户体验的一个应用展示 -## **7、开发工具** -- Ubuntu 环境 VS Code 插件支持 -支持在 Ubuntu 环境下安装 openvela VS Code 插件，实现了从项目创建、编译构建、系统调试到应用开发的全流程支持，显著提升开发效率。（[openvela VS Code 插件使用指南](../quickstart/vscode_plugin_usage.md)） -## **8、模拟器运行时参数扩展** + +- [贪吃蛇游戏](./../../../../../packages_demos/blob/trunk-5.4/snake_game/Readme.md)：一个使用 LVGL 图形库实现的自动贪吃蛇游戏。 + +- [电子木鱼](./../../../../../packages_demos/blob/trunk-5.4/wooden_fish/README_zh-cn.md)：基于 openvela `nxaudio` 服务与上层 LVGL UI 框架，并实现了包含响应式布局和安全资源管理的完整交互链路，实现了一个动画效果流畅、资源安全管理、良好用户体验的一个应用展示。 + +## 7、开发工具 + +Ubuntu 环境 VS Code 插件支持：支持在 Ubuntu 环境下安装 openvela VS Code 插件，实现了从项目创建、编译构建、系统调试到应用开发的全流程支持，显著提升开发效率。（[openvela VS Code 插件使用指南](../quickstart/vscode_plugin_usage.md)） + +## 8、模拟器运行时参数扩展 + - emulator.sh 新增 -keep 参数支持 - - 如果 emulator.sh 支持多实例配置时，可以通过 `-keep` 参数接入指定的名称的实例（如果不存在则创建），并且在该实例退出时不会删除相关上下文 - ```Shell - # 使用方法 - cp cmake_out/vela_goldfish-arm64-v8a-ap/nuttx* cmake_out/vela_goldfish-arm64-v8a-ap/vela_* cmake_out/vela_goldfish-arm64-v8a-ap/advancedFeatures.ini nuttx/ - - ./emulator.sh vela -keep -no-window - - # 测试举例，在/data目录创建 test 文件并写入内容 - nsh> echo test > /data/test - nsh> echo "openvvela qemu keep test" >> /data/test - nsh> quit - - # 模拟器退出重新进入，上一次写入的内容仍然被保留 - ./emulator.sh vela -keep -no-window - nsh> cat /data/test - test - openvela qemu keep test - ``` - -- emulator.sh 新增支持使用 Hostfs 功能，默认支持使用9pfs，效果如下： - ```Shell - goldfish-armv8a-ap> df -h - Filesystem Size Used Available Mounted on - binfs 0B 0B 0B /bin - fatfs 255M 78M 177M /data - romfs 1152B 1152B 0B /etc - hostfs 0B 0B 0B /host - procfs 0B 0B 0B /proc - v9fs 878G 626G 252G /share - romfs 512B 512B 0B /system - tmpfs 6K 1K 5K /tmp - ``` - - 用法： - ```Shell - # 使用方法 - cp cmake_out/vela_goldfish-arm64-v8a-ap/nuttx* cmake_out/vela_goldfish-arm64-v8a-ap/vela_* cmake_out/vela_goldfish-arm64-v8a-ap/advancedFeatures.ini nuttx/ - - ./emulator.sh vela - ``` + + 如果 emulator.sh 支持多实例配置时，可以通过 `-keep` 参数接入指定的名称的实例（如果不存在则创建），并且在该实例退出时不会删除相关上下文 + + ```bash + # 使用方法 + cp cmake_out/vela_goldfish-arm64-v8a-ap/nuttx* cmake_out/vela_goldfish-arm64-v8a-ap/vela_* cmake_out/vela_goldfish-arm64-v8a-ap/advancedFeatures.ini nuttx/ + + ./emulator.sh vela -keep -no-window + + # 测试举例，在/data目录创建 test 文件并写入内容 + nsh> echo test > /data/test + nsh> echo "openvvela qemu keep test" >> /data/test + nsh> quit + + # 模拟器退出重新进入，上一次写入的内容仍然被保留 + ./emulator.sh vela -keep -no-window + nsh> cat /data/test + test + openvela qemu keep test + ``` + +- emulator.sh 新增支持使用 Hostfs 功能，默认支持使用 9pfs，效果如下： + + ```bash + goldfish-armv8a-ap> df -h + Filesystem Size Used Available Mounted on + binfs 0B 0B 0B /bin + fatfs 255M 78M 177M /data + romfs 1152B 1152B 0B /etc + hostfs 0B 0B 0B /host + procfs 0B 0B 0B /proc + v9fs 878G 626G 252G /share + romfs 512B 512B 0B /system + tmpfs 6K 1K 5K /tmp + ``` + + 用法： + + ```bash + # 使用方法 + cp cmake_out/vela_goldfish-arm64-v8a-ap/nuttx* cmake_out/vela_goldfish-arm64-v8a-ap/vela_* cmake_out/vela_goldfish-arm64-v8a-ap/advancedFeatures.ini nuttx/ + + ./emulator.sh vela + ``` From 81a67239ee52587d0cecdcbbb72a22c1e4e00fcb Mon Sep 17 00:00:00 2001 From: zhangxiaowei16 Date: Fri, 6 Feb 2026 10:37:39 +0800 Subject: [PATCH 2/2] Add openvela Highlights --- README.md | 6 ++++++ README_zh-cn.md | 6 ++++++ en/release_notes/v5.4.md | 10 +++++----- zh-cn/release_notes/v5.4.md | 10 +++++----- 4 files changed, 22 insertions(+), 10 deletions(-) diff --git a/README.md b/README.md index 5cf95f97..b3b9b7ab 100644 --- a/README.md +++ b/README.md @@ -62,6 +62,12 @@ The name "Vela" is originated from the Latin term for "sail," which is also the - Please refer to the [Supported Architectures and Platforms](https://nuttx.apache.org/docs/latest/platforms/index.html) page for a complete list. - For adaptation cases regarding development boards, please refer to the [Case Documentation](./en/dev_board/Development_Board.md). +## What's New + +- **Significant Hardware Ecosystem Expansion**: Added support for **Infineon AURIX™ TC4**, **Flagchip MCU**, and the **QEMU-R52 SIL** platform. (View [TC4 Guide](./en/quickstart/development_board/tc4d9_evb_guide.md) / [Flagchip Guide](./en/quickstart/development_board/fc7300f8m_evb_guide.md)) + +- **Enhanced Ubuntu Development Experience**: The OpenVela VS Code plugin now **fully supports the Ubuntu environment**. Linux developers can enjoy a seamless, end-to-end workflow—from project creation and build to system debugging—significantly boosting development efficiency. Get started: [VS Code Plugin Guide](./en/quickstart/vscode_plugin_usage.md). + ## Version Strategy We manage releases based on the `trunk` branch, using Tags to track release history. This ensures traceability and stability for production environments. diff --git a/README_zh-cn.md b/README_zh-cn.md index 45eb8a6d..ae402eb5 100644 --- a/README_zh-cn.md +++ b/README_zh-cn.md @@ -63,6 +63,12 @@ Vela 的命名源自拉丁语中船帆的含义，也是南方星空中船帆星 - openvela 支持各种不同的架构（ARM32、ARM64、RISC-V、Xtensa、MIPS、CEVA 等）和硬件平台。请在[硬件支持](https://nuttx.apache.org/docs/latest/platforms/index.html)页面上查看完整列表。 - 关于**开发板**的适配案例，请参见[案例文档](./zh-cn/dev_board/Development_Board.md)。 +## 最新动态 + +- 硬件生态大幅扩展：新增对 **英飞凌 AURIX™ TC4**、**旗芯微 (Flagchip) MCU** 以及 **QEMU-R52 SIL** 平台的适配支持。（查看 [TC4 指南](./zh-cn/quickstart/development_board/tc4d9_evb_guide.md) / [旗芯微指南](./zh-cn/quickstart/development_board/fc7300f8m_evb_guide.md)） + +- Ubuntu 开发体验升级：openvela VS Code 插件现已**完美支持 Ubuntu 环境**。Linux 开发者现在也可以享受从项目创建、编译构建到系统调试的一站式流畅体验，开发效率显著提升。即刻体验：[VS Code 插件使用指南](./zh-cn/quickstart/vscode_plugin_usage.md)。 + ## 版本发布管理 (Version Strategy) 我们基于 `trunk` 分支进行版本发布，通过标签（Tags）管理发布历史，确保生产环境的可追溯性与稳定性。 diff --git a/en/release_notes/v5.4.md b/en/release_notes/v5.4.md index 34820564..829a734c 100644 --- a/en/release_notes/v5.4.md +++ b/en/release_notes/v5.4.md @@ -6,17 +6,17 @@ openvela has been dedicated to introducing support for more chips, enhancing system real-time communication capabilities, and significantly improving system robustness, storage functionality, and debuggability. This release focuses on enhancements around the following core themes: -- Hardware Ecosystem Expansion: **Added support for [Infineon AURIX™ TC4](../quickstart/development_board/tc4d9_evb_guide.md), [Flagchip MCU](../quickstart/development_board/fc7300f8m_evb_guide.md), and QEMU-R52 SIL platforms**, broadening the scope of platform applicability. -- System Kernel Hardening: **Achieved collaborative operation of SMP and PM, introduced MPU-based thread stack protection and RPC framework refactoring**, making the system safer and more stable. -- Key Capabilities Integration: **Added SocketCAN and Ethernet protocol stacks; introduced the highly reliable NVS2 storage solution**. +- Hardware Ecosystem Expansion: Added support for [Infineon AURIX™ TC4](../quickstart/development_board/tc4d9_evb_guide.md), [Flagchip MCU](../quickstart/development_board/fc7300f8m_evb_guide.md), and QEMU-R52 SIL platforms**, broadening the scope of platform applicability. +- System Kernel Hardening: Achieved collaborative operation of SMP and PM, introduced MPU-based thread stack protection and RPC framework refactoring**, making the system safer and more stable. +- Key Capabilities Integration: Added SocketCAN and Ethernet protocol stacks; introduced the highly reliable NVS2 storage solution**. - Developer Experience Optimization: Provided low-overhead FDX real-time tracing tools and multiple LVGL application examples, lowering the barrier for development and debugging. ## II. Major New Features & Enhancements ### 1. Platform Support -- Added support for Infineon AURIX™ TriCore™ TC4 chips -- Added support for Flagchip MCUs +- Added support for Infineon AURIX™ TriCore™ TC4 chips +- Added support for Flagchip MCUs - Added Cortex-R52 core support under QEMU platform, supporting Vector SIL platform - Resolved compilation issues for nuttx boards, better supporting native nuttx boards platforms diff --git a/zh-cn/release_notes/v5.4.md b/zh-cn/release_notes/v5.4.md index 3fa0778e..794697b1 100644 --- a/zh-cn/release_notes/v5.4.md +++ b/zh-cn/release_notes/v5.4.md @@ -6,17 +6,17 @@ openvela 一直致力于引入更多的芯片的支持、增强系统的实时通信能力，并大幅提升了系统的健壮性、存储功能和可调试性。本次发布围绕以下核心主题进行了增强： -- 硬件生态扩展：**新增对**[**英飞凌 AURIX™ TC4**](../quickstart/development_board/tc4d9_evb_guide.md)**、**[**旗芯微 MCU**](../quickstart/development_board/fc7300f8m_evb_guide.md)** 及 QEMU-R52 SIL 平台的支持，拓宽了平台适用范围。 -- 系统内核加固：**实现了 SMP 与 PM 的协同工作，引入了基于 MPU 的线程栈保护和 RPC 框架重构**，系统更安全、更稳定。 -- 关键能力集成：**新增了 SocketCAN 和以太网协议栈；引入了高可靠性的 NVS2 存储方案**。 +- 硬件生态扩展：新增对[英飞凌 AURIX™ TC4](../quickstart/development_board/tc4d9_evb_guide.md)、[旗芯微 MCU](../quickstart/development_board/fc7300f8m_evb_guide.md) 及 QEMU-R52 SIL 平台的支持，拓宽了平台适用范围。 +- 系统内核加固：实现了 SMP 与 PM 的协同工作，引入了基于 MPU 的线程栈保护和 RPC 框架重构，系统更安全、更稳定。 +- 关键能力集成：新增了 SocketCAN 和以太网协议栈；引入了高可靠性的 NVS2 存储方案。 - 开发者体验优化：提供了低开销的 FDX 实时追踪工具和多个 LVGL 应用范例，降低了开发和调试门槛。 ## 二、主要新增功能与增强 ### 1、平台支持 (Platform Support) -- 新增对英飞凌 AURIX™ TriCore™ TC4 芯片的支持 -- 新增对旗芯微（Flagchip）MCU 的支持 +- 新增对英飞凌 AURIX™ TriCore™ TC4 芯片的支持 +- 新增对旗芯微（Flagchip）MCU 的支持 - QEMU 平台下新增 Cortex-R52 核支持，支持 Vector SIL 平台 - 解决 nuttx boards 的编译问题，更好得支持原生 nuttx boards 平台