1.11.0 - 2025-12-31:

- docs: README: add compile error faq.
- docs: ad notice about openocd updates.'
- docs: update user guide for hpm6360evk and hpm5301evklite.
- openocd: fix buffer size calculation for snprintf null terminator
- start_gui: add openocd path hint if hpm_sdk_base changed.
- start_gui: fix bug
- start_gui: update programing flash command and bugfix in start_gui.
- update FTDI_InstallDriver.exe to improve stability

- Notice:
  - openocd: due updating to recent code base of riscv-openocd (https://github.com/riscv-collab/riscv-openocd),
  it only works with the openocd cfg files included in hpm_sdk v1.11.0.

Signed-off-by: Ryan QIAN <jianghao.qian@hpmicro.com>

Author: jhqian

CHANGELOG.md

@@ -1,5 +1,19 @@
 # Change Log 
 
+## [1.11.0] - 2025-12-31:
+- docs: README: add compile error faq.
+- docs: ad notice about openocd updates.'
+- docs: update user guide for hpm6360evk and hpm5301evklite.
+- openocd: fix buffer size calculation for snprintf null terminator
+- start_gui: add openocd path hint if hpm_sdk_base changed.
+- start_gui: fix bug
+- start_gui: update programing flash command and bugfix in start_gui.
+- update FTDI_InstallDriver.exe to improve stability
+
+### Notice:
+  - openocd: due updating to recent code base of riscv-openocd (https://github.com/riscv-collab/riscv-openocd),
+  it only works with the openocd cfg files included in hpm_sdk v1.11.0. 
+
 ## [1.10.0] - 2025-06-30:
 - start_gui: add quick start menu
 - start_gui: change the gcc compile button text to compile.

README.md

@@ -62,4 +62,7 @@ The menu bar supports setting both English and Chinese languages and provides ac
   The warning occurs because the path to the current build project's output directory is too long. This may result in some generated obj files having paths that exceed the maximum length supported by the compiler, potentially causing compilation failures. You can address this issue by making the following adjustments:
   - To minimize the absolute path length for hpm_sdk, place the SDK_ENV directory as close to the root of the drive as possible, such as "D:\sdk_env". This reduces the number of directory levels in the absolute path for sdk_env, thereby shortening the entire path length for hpm_sdk.
   - Alternatively, you can shorten the final output directory path length. For example, in start_gui, reduce the "Build Path" to minimize the number of directory levels in the absolute path. Ensuring a shorter path length can help guarantee that the project builds successfully.
-  
+### During compilation, the SAMPLE prompt "fatal error: xxxx: No such file or directory"
+  - When a compilation error indicates that a file or directory cannot be found, first check whether the file path is correct and whether the file exists.
+  - Next, verify that the file path is correctly specified in CMakeLists.txt, as an incorrect path may cause the file to be missing.
+  - Then, ensure that the file path length complies with the Windows file path length limit. The file may fail to be read if the directory path exceeds Windows' path length limitation. If the file path that caused the compilation failure is too long, try shortening the directory hierarchy of SDK_ENV to keep the path as concise as possible. After that, recheck whether the compilation can proceed successfully.

README_zh.md

@@ -61,4 +61,8 @@
 ### 使用 CMAKE 构建项目时提示 “The object file directory xxx has xxx characters. The maximum full path to an object file is 250 characters..The build may not work correctly.” 警告
   该警告是由于当前构建项目的生成目录路径过长，有可能会使编译时生成的某些 obj 文件路径超过编译器支持的最大长度导致编译失败，可以做如下调整：
   - 将 SDK_ENV 放置到尽量靠近驱动器根目录位置如 “D:\sdk_env” ，缩短绝对路径下 sdk_env 的目录层级，这样可以缩短整个 hpm_sdk 的绝对路径长度；
-  - 或者缩短最终生成目录路径长度，如 start_gui 中缩短 “Build Path” 路径，尽量减少该路径层级（绝对路径长度）可确保项目正常生成；
+  - 或者缩短最终生成目录路径长度，如 start_gui 中缩短 “Build Path” 路径，尽量减少该路径层级（绝对路径长度）可确保项目正常生成；
+### 编译过程中 SAMPLE 提示 “fatal error: xxxx: No such file or directory”
+  - 当编译提示找不到文件或目录时，需要首先检查该文件路径是否正确，检查该文件是否存在；
+  - 其次需要确认该文件路径在 CMakeLists.txt 中是否被正确添加，路径错误有可能导致文件找不到；
+  - 然后需要确认该文件路径长度是否符合 Windows 文件路径长度限制，有可能因为文件目录超过了 Windows 文件路径长度限制，导致无法正常读取到该文件。如果编译失败的文件路径过长，可以先缩短 SDK_ENV 的目录层级，确保编译失败的文件目录层级尽量短，然后再确认是否能编译通过。