Hi Antonio,

And welcome to the TF-M community.  To get a better understanding of your issue it I would like to ask from some further details, such as the HEAD of the TF-M which you are trying to build, as well as the HEAD of the test branche.

There has been a large overhaul of several components on the TF-M project, including the build system, so it would be good to have a common point of reference /

By examples, do you refer to the official user guide?
https://ci.trustedfirmware.org/view/TF-M/job/tf-m-build-docs-nightly/lastStableBuild/artifact/trusted-firmware-m/build/install/doc/user_guide/html/docs/getting_started/tfm_user_guide.html

For Musca_A you only need the hex file to flash it, which is generated using the srec_cat command mentioned above which utilises the platform specific offsets and merges the signed secure and non-secure binaries with the bootloader.

If you are facing any issues flashing the HEX file, make sure that you have an up-to date daplink firmware.

https://community.arm.com/developer/tools-software/oss-platforms/w/docs/554/musca-a-firmware-update-qspi-boot-recovery

If your output folder contains the HEX file, you can try flashing it by dragging and dropping, and see if it runs the regression tests.


Regards,
Minos Galanakis


From: TF-M <tf-m-bounces@lists.trustedfirmware.org> on behalf of Antonio Ken IANNILLO via TF-M <tf-m@lists.trustedfirmware.org>
Sent: 05 October 2020 14:06
To: tf-m@lists.trustedfirmware.org <tf-m@lists.trustedfirmware.org>
Subject: [TF-M] Running Tests on Musca-A
 

Dear all,

I’m a researcher exploring TF-M.

I have a Musca-A board, and I was able to build it with tests.

Now, it seems that the examples running the tests [1] are outdated: I simply do not have the same files.

My understanding is that I should merge two files (secure and non-secure) but it is not clear which ones and how the offset are computed.

Can somebody help me on this?

 

The output files in the /bin folder are: bl2, tfm_ns, and tfm_s in .axf, .bin, .elf, .hex, .map; tfm_s_ns.bin; and tfm_s_ns_signed.bin.

 

Best,

 

[1] https://ci.trustedfirmware.org/view/TF-M/job/tf-m-build-docs-nightly/lastStableBuild/artifact/trusted-firmware-m/build/install/doc/user_guide/html/docs/getting_started/tfm_user_guide.html#example-application-with-bl2-bootloader

 

-- 

Antonio Ken Iannillo, PhD

Research ScientistSEDAN group

SnT – Interdisciplinary Centre for Security, Reliability and Trust

UNIVERSITÉ DU LUXEMBOURG

 

CAMPUS KIRCHBERG
29, avenue John F. Kennedy 
L-1855 Luxembourg Kirchberg
T +352 46 66 44 9660 |
antonioken.iannillo@uni.lu 

 

Join the conversation

News | Twitter | Linkedin

www.uni.lu/snt

 

 

 https://akiannillo.github.io/

 

P Please consider the environment before printing this e-mail