Process documentation has been merged (https://git.trustedfirmware.org/trusted-firmware-m.git/commit/?id=5c87323db941c3470eb4d4998981ced8b33cf84c) and process is in place.
Fri, Aug 23
CMake Error in cmake/FindSphinx.cmake: A logical block opening on line 84 is not closed.
Newer versions of sphinx seem to print the version as:
$ sphinx-build.exe --version sphinx-build 2.1.2
I think the ) character is making the reqexp on this line https://git.trustedfirmware.org/trusted-firmware-m.git/tree/cmake/FindSphinx.cmake#n85 fail to match.
Can you please check if changing line 85 like this helps?: if(_SPHINX_VERSION MATCHES ".*sphinx-build[^0-9.]*([0-9.]+).*")
The same issue seems to affect mbedcrypto and this commit has the fix: https://github.com/ARMmbed/mbed-crypto/pull/118/commits/7346b312e12a54d77608fc6bb8aa3c55cf046d90
In TF-M build instructions (https://git.trustedfirmware.org/trusted-firmware-m.git/about/docs/user_guides/tfm_build_instruction.rst ) the following dependencies are defined:
- mbedtls v2.7.9
- mbedcrypto v1.1.0
@jainvikas8: Thank you for volunteering! Please create a patch to fix the documentation.
I'm happy to create a patch set for it.
That's a valid point, the documentation needs to be fixed.
The documentation https://git.trustedfirmware.org/trusted-firmware-m.git/tree/docs/user_guides/tfm_sw_requirement.rst defines exporting PLANTUML_JAR_PATH including the double quotes. The issue is valid and the documentation needs fixing.
Based on my investigations this is not a bug and no fix is needed.
It is wrong to set PLANTUML_JAR_PATH as export PLANTUML_JAR_PATH="~/plantuml/plantuml.jar" and instead export PLANTUML_JAR_PATH=~/plantuml/plantuml.jar shall be used (Note: quotation marks removed).
patch had been merged.
Thu, Aug 22
Wed, Aug 21
Tue, Aug 20
Changes to build environment after rebasing/merging
- master branch switches to use mbed-crypto *1.1.0* since https://review.trustedfirmware.org/c/trusted-firmware-m/+/1562. After rebasing/merging, mbed-crypto should be updated to 1.1.0 from 1.0.0.
- CMSIS 5.5
- master branch changes to use CMSIS 5.5 since https://review.trustedfirmware.org/c/trusted-firmware-m/+/1421.
- TF-M can co-work with both 5.2 and 5.5. But after the CMSIS is updated to 5.5, it is required to manually to fetch the CMSIS RTOS v2 binaries via git-lfs
Mon, Aug 19
The conflicts include but not limited to the following list
Sat, Aug 17
Fri, Aug 16
Thu, Aug 15
Wed, Aug 14
Tue, Aug 13
Mon, Aug 12
Fri, Aug 9
Thu, Aug 8
I saw your previous discussion, more comprehensive than I considered, I look forward to the addition of this feature in MCUBoot。
Wed, Aug 7
Tue, Aug 6
Currently, these are the patches:
Propose a patch https://review.trustedfirmware.org/c/trusted-firmware-m/+/1718 to split memory check process from other common secure APIs. Thus single Armv8-M and multi-core scenario can implement own process.
Keep this task open since more alignments would come in Q4.
Mon, Aug 5
Fri, Aug 2
Patch for this task: https://review.trustedfirmware.org/c/trusted-firmware-m/+/1704
Add the initialisation of the MPC interrupt driver on Musca_A platform.
Perform manual tests of ConfigRegression and ConfigRegressionIPC on Musca_A2 platform.
The patch passes internal CI tests.
Changes for this issue:
Patches for additionnal refactoring:
Hi @qixiang , the problem is right about memory, I don't think we have enough space to support debug options for crypto on both platforms.
If you agree, can we close it as "won't fix". Thanks.
Thu, Aug 1
patch 1: merge IPC model partition data into library model partition data.
patch 2: use the merged library model partition data struct as the common one, and replace the old IPC partition data.
patch 3: merge tfm_spm.c into spm_api_ipc.c and remove old files.
patch 4: separate library model SPM code from spm_api.c and create a new file 'spm_api_func.c' for library model.
Patch for master branch updated: