CYTFM_064B0S2_4343W: Fails to complete post build operation

[hugueskamba]

Description of defect

The post build operation does not complete.

Target(s) affected by this defect ?

CYTFM_064B0S2_4343W

Toolchain(s) (name and version) displaying this defect ?

ARM, GCC_ARM

What version of Mbed-os are you using (tag or sha) ?

mbed-os-6.8.0

What version(s) of tools are you using. List all that apply (E.g. mbed-cli)

$ mbed-tools --version
7.1.0

How is this defect reproduced ?

Attempt to build mbed-os-example-blinky run the following command:
rm -rf cmake_build/ && mbedtools compile -t gcc_ARM -m CYTFM_064B0S2_4343W

Outcome:

...
Total Static RAM memory (data + bss): 11236(+11236) bytes
Total Flash memory (text + data): 51732(+51732) bytes

[338/338] Generating mbed-os-example-blinky.bin
FAILED: mbed-os/targets/TARGET_Cypress/TARGET_PSOC6/TARGET_CYTFM_064B0S2_4343W/mbed-os-example-blinky.bin 
cd /path/to/mbed-os-example-blinky/cmake_build/CYTFM_064B0S2_4343W/develop/GCC_ARM/mbed-os/targets/TARGET_Cypress/TARGET_PSOC6/TARGET_CYTFM_064B0S2_4343W && /usr/local/Frameworks/Python.framework/Versions/3.9/bin/python3.9 /path/to/mbed-os-example-blinky/mbed-os/targets/TARGET_Cypress/scripts/PSOC6.py sign --build-dir /path/to/mbed-os-example-blinky/cmake_build/CYTFM_064B0S2_4343W/develop/GCC_ARM --m0hex-filename tfm_s.hex --target-name CYTFM_064B0S2_4343W --policy-file-name policy_multi_CM0_CM4_tfm.json --boot-scheme multi_image --cm0-img-id 1 --cm4-img-id 16 --elf /path/to/mbed-os-example-blinky/cmake_build/CYTFM_064B0S2_4343W/develop/GCC_ARM/mbed-os-example-blinky.elf --m4hex /path/to/mbed-os-example-blinky/cmake_build/CYTFM_064B0S2_4343W/develop/GCC_ARM/mbed-os-example-blinky.hex --m0hex /path/to/mbed-os-example-blinky/mbed-os/targets/TARGET_Cypress/TARGET_PSOC6/TARGET_CYTFM_064B0S2_4343W/COMPONENT_TFM_S_FW/tfm_s.hex
2021-02-22 13:43:16,055 : C : ERROR : Cannot find image with id 1 and type 'BOOT' in the policy file. Check the log for details
2021-02-22 13:43:16,055 : C : ERROR : Image with ID 1 not found in '/path/to/mbed-os-example-blinky/mbed-os/targets/TARGET_Cypress/TARGET_PSOC6/TARGET_CYTFM_064B0S2_4343W/policy/policy_multi_CM0_CM4_tfm.json'. Check the log for details
Traceback (most recent call last):
  File "/path/to/mbed-os-example-blinky/mbed-os/targets/TARGET_Cypress/scripts/PSOC6.py", line 393, in <module>
    args.func(args)
  File "/path/to/mbed-os-example-blinky/mbed-os/targets/TARGET_Cypress/scripts/PSOC6.py", line 316, in sign_action
    sign_hex(
  File "/path/to/mbed-os-example-blinky/mbed-os/targets/TARGET_Cypress/scripts/PSOC6.py", line 229, in sign_hex
    sign_application(notification.debug, tools, m0hex, image_id=cm0_img_id)
  File "/path/to/mbed-os-example-blinky/mbed-os/targets/TARGET_Cypress/scripts/PSOC6.py", line 254, in sign_application
    + str(image_id) + " is " + hex(address) + ", " + hex(size))
TypeError: 'NoneType' object cannot be interpreted as an integer
ninja: build stopped: subcommand failed.
ERROR: CMake invocation failed!

More information may be available by using the command line option '-v'.

[0xc0170]

Which object is NoneType ? @ARMmbed/team-cypress can you review the post build hook?

[ciarmcom]

@hugueskamba thank you for raising this issue.Please take a look at the following comments:

Could you add some more detail to the description? A good description should be at least 25 words.

NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'. This indicates to us that at least all the fields have been considered.
Please update the issue header with the missing information, the issue will not be mirrored to our internal defect tracking system or investigated until this has been fully resolved.

[ifyall]

@0xc0170, can you assign this item to me? My team owns Mbed OS integrations going forward. Thank you.

I have filed an internal ticket on this for our tracking purposes.

[ifyall]

@hugueskamba,

Where is the policy_multi_CM0_CM4_tfm.json file that the build is complaining about? It doesn't seem to be in mbed-os but I don't see your reproduction steps documenting creation/management of it.

Thank you,

Ian

[RaymondNgun]

cysecuretools -t cy8kit-064b0s2-4343w init creates the policy file. Have a look at.

https://os.mbed.com/platforms/CY8CKIT-064B0S2-4343W/#building-the-mbed-os-blinky-application

EDIT: Sorry, I take that back. This is TF-M and that file is here - https://github.com/ARMmbed/mbed-os/tree/master/targets/TARGET_Cypress/TARGET_PSOC6/TARGET_CYTFM_064B0S2_4343W/policy

[hugueskamba]

@hugueskamba,

Where is the policy_multi_CM0_CM4_tfm.json file that the build is complaining about? It doesn't seem to be in mbed-os but I don't see your reproduction steps documenting creation/management of it.

Thank you,

Ian

The policy file is in Mbed OS. Here: https://github.com/ARMmbed/mbed-os/blob/master/targets/TARGET_Cypress/TARGET_PSOC6/TARGET_CYTFM_064B0S2_4343W/policy/policy_multi_CM0_CM4_tfm.json
Attempting to build as specified will show the same error.