Hi Raymond,

 

Here is the proposed fix:
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/6028

 

Could you verify on your board? Pls use at build -DCMAKE_BUILD_TYPE=Debug for full logging in bootloader.

 

Tamas

 

From: TF-M <tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Tamas Ban via TF-M
Sent: 01 October 2020 10:37
To: Raymond Ngun <Raymond.Ngun@cypress.com>; tf-m@lists.trustedfirmware.org
Cc: nd <nd@arm.com>
Subject: Re: [TF-M] Musca-B1 and new build system

 

Hi Raymond,

 

Thanks for reporting the issue! 

 

The observed behaviour has two reason:
- In the new build system the default CMAKE_BUILD_TYPE=Release. In this case the logging is disabled in MCUboot to get smaller binary.  You can set manualy to Debug in the command line to enable logging from bootloader

 

Tamas

 

From: TF-M <tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Raymond Ngun via TF-M
Sent: 30 September 2020 17:44
To: David Hu via TF-M <tf-m@lists.trustedfirmware.org>
Subject: [TF-M] Musca-B1 and new build system

 

Hi all,

 

I am attempting to build Musca-B1 with the latest in master but I’m not able to get it to run (nothing shows on the UART). At a minimum, the User Guide is out of date in terms of how the final hex is created. So, I have a couple questions.

 

  1. Is the latest tested with Musca-B1?
  2. Can I obtain some updated information on how to build and create an image for Musca-B1?

 

Thank you,


Ray


This message and any attachments may contain confidential information from Cypress or its subsidiaries. If it has been received in error, please advise the sender and immediately delete this message.