Page MenuHomePhabricator
Create Task
Maniphest T617

Secure image (tfm_s.hex) output directory is not constant
Open, NormalPublic
Actions

Description

When compile with the configuration (ConfigXXX.cmake) that has CORE_TEST enabled.
The output directory of secure image (tfm_s.hex) would be changed to unit_test (secure_fw/CMakeLists.txt).
e.g.: <build>/unit_test/tfm_s.*

This behaviour causing problem in build procedure (and CI). Extra scripts is needed to find where the image is, to sign/flash it. And there is no clue (as CORE_TEST is a internal variable in each configuration file that could be enabled/disabled) for the script to know ahead where the output image would be.

Which also introduce hidden problem to engineer in developing stage, that s/he could not make incremental build, but having to clean & rebuild everything to make sure not to get the wrong image (generated from previous build), if s/he is modifying something that might change output directory.

Trace the commit, found that it was firstly introduced in

30fa9871a8 Build: Cmake build system

I didn't find the reason, or related info, that why it has to be put in different directory (unit_test).
If possible, please keep the output directory fixed (e.g.: SPE: secure_fw/; NSPE: app/) to make life easier.
(I like to have computer to help human to solve problem, not to generate problem :) )

Event Timeline

AlamyLiu triaged this task as Normal priority.Dec 13 2019, 2:09 AM
AlamyLiu created this task.
• broderickson added a subscriber: • broderickson.Mar 12 2025, 8:39 PM

The issue of the secure image (tfm_s.hex) output directory not being constant can create inconsistencies in build processes, making it harder to locate and manage files efficiently. This unpredictability can lead to errors, especially in automated workflows that rely on a fixed directory structure. Similarly, just like how Download Snaptroid APK Free ensures a consistent and reliable platform for accessing media content, having a stable output directory for tfm_s.hex is crucial for seamless development and deployment processes. Standardizing the directory path would improve workflow efficiency and reduce unnecessary troubleshooting.

• tiedemannsonb49 added a subscriber: • tiedemannsonb49.Mon, Mar 24, 11:25 AM

The secure image (tfm_s.hex) output directory is not constant, which can lead to inconsistencies in file management and deployment. Ensuring a fixed output path helps streamline workflows and prevents errors. Just like avoiding risks with fake PhonePe apps, maintaining a structured and reliable system is essential for security and efficiency. Standardizing directories can improve automation and reduce potential issues in the development process. 🚀