Source Review and Known Issues
This page records items found during a static review of SDK v1.0.10 that may affect builds or usage. Unless explicitly marked as verified on hardware, findings are based on source inspection and have not necessarily been reproduced on a device.
| Item | Source location | Confirmed finding | Impact and action |
|---|---|---|---|
app install_to_userdata packaging path | project/build.sh, __PACKAGE_USERDATA() | The app-directory check uses userdata_app, but the copy command still reads from the media path. Confirmed in source. | Files expected in the userdata image may not be copied from the app output directory. If this feature is needed, inspect the final image or device contents; alternatively, create/copy the files during startup. |
rkflash.sh update branch | project/rkflash.sh | The corresponding branch is commented out. Confirmed in source. | Do not assume ./rkflash.sh update performs an update. Use a supported command from Flashing and Boot. |
Env image in rkflash.sh all | project/rkflash.sh | The all branch does not include env.img. Confirmed in source. | After changing the partition table or boot environment, verify separately that the env image was flashed and took effect. |
Case of the save archive directory | project/build.sh, build_save(); root quick_start_cn.md | build_save() converts the Image/... path to uppercase; the actual directory is IMAGE/.... The quick-start guide also uses IMAGE/. Confirmed in source. | Look for the directory name generated by the current script. The Wiki's earlier reference to Image/ was incorrect. |
SDK Version in sdkinfo | project/build.sh, build_get_sdk_version() | The version comes from .repo/manifest.xml. This source snapshot has no .repo/, so the build may write NONE. Confirmed in source. | Check /etc/ota_version, the BoardConfig name, and the build archive together. Do not identify the release from the SDK Version field in sdkinfo alone. |
| RTC comment vs. UTC option | project/cfg/BoardConfig_Recamera2/overlay-buildroot-hwclock/etc/init.d/S20hwclock | The script comment and hwclock --utc appear to specify different time conventions. Confirmed in source; timezone behavior needs hardware verification. | Before changing time handling, verify the timezone, RTC convention, and actual time after reboot. |
Default cross target for recamera_services | project/app/recamera_services/Makefile | The default target appears to be armv7; whether the top-level build overrides it needs to be checked against the build entry point. Static finding; final binary not yet verified. | After a manual build, run file on the output and confirm that it targets aarch64. |
| Release Notes filename and auto-discovery | project/cfg/BoardConfig_Recamera2/ and build_info() in project/build.sh | The current Release Notes filename does not match the naming pattern searched by the script; the document is also brief. Confirmed in source. | Before release, manually confirm that the archive contains the correct change log. Do not rely on automatic promotion. |
recamera_onvif and recamera_utils READMEs | Respective application directories | The README files are generic templates and do not describe this project's build or usage. Confirmed by reading the files. | To understand component behavior, inspect the Makefile, source, and callers. Do not treat the template README as project documentation. |
How to Interpret These Findings
- Confirmed in source: the implementation or configuration is directly visible in the cited source; it may not yet have been exercised on a device.
- Needs hardware verification: the result depends on hardware, firmware, runtime configuration, or build outputs and must be reproduced on the relevant device.
- Paths and behavior refer to the v1.0.10 source snapshot covered by this Wiki. Recheck them after an SDK upgrade; do not treat these findings as guarantees across versions.
- Fix these issues in the SDK source and rebuild as needed. This page records current behavior and impact; it does not apply fixes.
Tech Support & Product Discussion
Thank you for choosing our products! We are here to provide you with different support to ensure that your experience with our products is as smooth as possible. We offer several communication channels to cater to different preferences and needs.