Hi Kevin,

Thank you for the feedback and bringing debugging topic up.

You are right, this part is missed and would be useful. We will consider it in our planning for User Experience improvements.

Independent from that, let me encourage everyone here having TF-M debug experience to share it with community, contributing to TF-M.

Thanks and best regards,

Anton

From: Kevin Townsend <kevin.townsend@linaro.org>
Sent: 28 February 2020 09:46
To: Anton Komlev <Anton.Komlev@arm.com>
Cc: tf-m@lists.trustedfirmware.org; nd <nd@arm.com>
Subject: Re: [TF-M] Call for a feedback on TF-M adaptation experience

Hi Anton,

One particular difficulty I've encountered working with TF-M for the Zephyr certification demo app, and with the LPC55S69 port to upstream TF-M is the debugging experience with GDB and the dual execution environments. GDB can be quite powerful if you are familiar with it, but there is a definite learning curve, and the S and NS separation and the dual binary images (three with BL2) adds an additional degree of complexity. 

I think having a dedicated debugging tutorial around GDB would be very useful to people adopting TF-M and perhaps new to GDB, just to show how some basic debugging might happen, how to debug across the NS/S boundary, etc.

For example, the '--tui' option for GDB may not be very well known, and it may be useful to highlight (see screenshots at the bottom of this issue: https://github.com/microbuilder/trusted-firmware-m/issues/1)

Practical, step-by-step debugging documentation just seems like a good investment to help flatten this inevitable learning curve developing real-world solutions with TF-M?

Best regards,

Kevin

On Thu, 27 Feb 2020 at 13:13, Anton Komlev via TF-M <tf-m@lists.trustedfirmware.org> wrote:

A kind reminder.
Your feedback is valuable all the time with no deadline defined.

From: TF-M <tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Anton Komlev via TF-M
Sent: 07 February 2020 13:13
To: tf-m@lists.trustedfirmware.org
Cc: nd <nd@arm.com>
Subject: [TF-M] Call for a feedback on TF-M adaptation experience

Dear All,

As I mentioned on yesterday’s call, there is a concern on user experience related to TF-M use.

To In order to understand and potentially improve it I am looking for a voice of partners who adopted TF-M project.

Please share your experience and thoughts on parts which are good or might be done better to simplify TF-M integration with your project.

You feedback will be very appreciated in any form – as a response to this mail or as a direct mail to me (anton.komlev@arm.com) if it’s more comfortable for you.

Thank you in advance,

Anton

--
TF-M mailing list
TF-M@lists.trustedfirmware.org
https://lists.trustedfirmware.org/mailman/listinfo/tf-m