Hi Edison,
OK. So, according to https://review.trustedfirmware.org/c/trusted-firmware-m/+/463/ the armclang IPC was added only to one platform (target/mps2/an521/armclang/mps2_an521_s.sct).
What about Musca A and Musca B?
Thanks,
Andrej
-----Original Message-----
From: Edison Ai (Arm Technology China) <Edison.Ai(a)arm.com>
Sent: Tuesday, March 19, 2019 9:52 AM
To: Andrej Butok <andrey.butok(a)nxp.com>
Cc: nd <nd(a)arm.com>
Subject: RE: IPC and clang
Hi Andrej,
You can see the log history of master branch: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.trust…p;reserved=0.
All the IPC patches had been existed in master branch.
You can use the master branch now, all the IPC functions had been ready for GCC and ARMCLANG.
Thanks,
Edison
-----Original Message-----
From: Andrej Butok <andrey.butok(a)nxp.com>
Sent: Tuesday, March 19, 2019 4:43 PM
To: Edison Ai (Arm Technology China) <Edison.Ai(a)arm.com>
Cc: nd <nd(a)arm.com>
Subject: RE: IPC and clang
Hi Edison,
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.trust… master head the latest commit is still 4-day old (4 days Core: Retrieve extra parameter from correct positionHEADmaster Summer Qin).
Should I wait some time till it will be propagated to the public git?
Thanks,
Andrej
-----Original Message-----
From: Edison Ai (Arm Technology China) <Edison.Ai(a)arm.com>
Sent: Tuesday, March 19, 2019 9:26 AM
To: Andrej Butok <andrey.butok(a)nxp.com>
Cc: nd <nd(a)arm.com>
Subject: RE: IPC and clang
Hi Andrej,
You are welcome.
Now, the "feature-ipc" branch had been merge into the master branch with the merge patch mentioned below. So all the patches in "feature-ipc" branch had been merge into master too. You can find the related IPC patch in the log history of master branch.
The IPC can works rightly in GCC and ARMCLANG on master branch.
Thanks,
Edison
-----Original Message-----
From: Andrej Butok <andrey.butok(a)nxp.com>
Sent: Tuesday, March 19, 2019 4:10 PM
To: Edison Ai (Arm Technology China) <Edison.Ai(a)arm.com>
Cc: nd <nd(a)arm.com>
Subject: RE: IPC and clang
Thanks Adison,
Yes, we are using the master branch.
When are you planning to merge the mentioned fix to the mainline?
Thanks,
Andrej
-----Original Message-----
From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Edison Ai (Arm Technology China) via TF-M
Sent: Tuesday, March 19, 2019 9:00 AM
To: tf-m(a)lists.trustedfirmware.org
Cc: nd <nd(a)arm.com>
Subject: Re: [TF-M] IPC and clang
Hi Andrej,
I think you mention the "Merge remote-tracking branch 'feature-ipc' into 'master" patch: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.tr…p;reserved=0.
This is a merge patch to fix the merge conflicts. The original patch to support to change the linker file is here: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.tr…p;reserved=0. You can see both the linker files for GCC and ARMCLANG are changed.
IPC had been developed and tested on both the GCC and ARMLANG already.
Thanks for your question.
Edison
-----Original Message-----
From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Andrej Butok via TF-M
Sent: Tuesday, March 19, 2019 3:35 PM
To: tf-m(a)lists.trustedfirmware.org
Subject: [TF-M] IPC and clang
Hello,
I have noticed, that with adding the IPC feature to master branch, it were updated GCC linker files (#ifdef TFM_PSA_API sections), but ARMCLANG linker files are without any change.
Does it mean that IPC was developed and tested only using GCC? Is there a plan to updated the armclang linker files?
Thanks,
Andrej Butok
--
TF-M mailing list
TF-M(a)lists.trustedfirmware.org
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.tru…
--
TF-M mailing list
TF-M(a)lists.trustedfirmware.org
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.tru…
Hi Andrej,
I think you mention the "Merge remote-tracking branch 'feature-ipc' into 'master" patch: https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/677/-1..2.
This is a merge patch to fix the merge conflicts. The original patch to support to change the linker file is here: https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/463/. You can see both the linker files for GCC and ARMCLANG are changed.
IPC had been developed and tested on both the GCC and ARMLANG already.
Thanks for your question.
Edison
-----Original Message-----
From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Andrej Butok via TF-M
Sent: Tuesday, March 19, 2019 3:35 PM
To: tf-m(a)lists.trustedfirmware.org
Subject: [TF-M] IPC and clang
Hello,
I have noticed, that with adding the IPC feature to master branch, it were updated GCC linker files (#ifdef TFM_PSA_API sections), but ARMCLANG linker files are without any change.
Does it mean that IPC was developed and tested only using GCC? Is there a plan to updated the armclang linker files?
Thanks,
Andrej Butok
--
TF-M mailing list
TF-M(a)lists.trustedfirmware.org
https://lists.trustedfirmware.org/mailman/listinfo/tf-m
Hello,
I have noticed, that with adding the IPC feature to master branch, it were updated GCC linker files (#ifdef TFM_PSA_API sections), but ARMCLANG linker files are without any change.
Does it mean that IPC was developed and tested only using GCC? Is there a plan to updated the armclang linker files?
Thanks,
Andrej Butok
On Thu, Mar 14, 2019 at 06:51:04PM +0000, Christopher Brand via TF-M wrote:
>I've posted a design document for bootloader changes to support twin
>cpu at
>https://developer.trustedfirmware.org/w/tf_m/design/twin-cpu/bootloader/
There are efforts underway to get the TF-M changes to the bootloader
contributed back to the upstream MCUboot project.
We should be trying to make sure that we continue this effort, as well
as to make sure that any efforts to extend the bootloader are done
upstream, and not in the TF-M-specific branch.
Are you expecting to be running the non-secure CPU before the secure
CPU has finished verifying the images?
David
Hi,
I've posted a design document for bootloader changes to support twin cpu at https://developer.trustedfirmware.org/w/tf_m/design/twin-cpu/bootloader/
Comments appreciated!
Thanks,
Chris
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.
Hi,
I will update the wait object from 'event' to 'condition'. This is mainly for fixing the issue:
https://developer.trustedfirmware.org/T273
'event' is actually a depth 1 semaphore, which is not good enough for signals synching case.
Involve a simpler sync object 'condition' for signals (and client ACKs):
https://review.trustedfirmware.org/c/trusted-firmware-m/+/712
Please help to check if you are interested in it.
Thanks
-Ken
Hi Alan,
Expected to be merged before end of Mar 13th if there is no more raised concern ;)
-Ken
> -----Original Message-----
> From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of DeMars,
> Alan via TF-M
> Sent: Tuesday, March 12, 2019 11:27 AM
> To: tf-m(a)lists.trustedfirmware.org
> Subject: Re: [TF-M] [EXTERNAL] Branches merging from 'feature-ipc' to 'master'
> is happening
>
> Yay! When?
>
> > On Mar 11, 2019, at 6:57 PM, Ken Liu (Arm Technology China) via TF-M <tf-
> m(a)lists.trustedfirmware.org> wrote:
> >
> > Hi TF-M Subscribers,
> > The branch 'feature-ipc' is going to be merged into 'master', and here is the
> patch:
> > https://review.trustedfirmware.org/c/trusted-firmware-m/+/677
> >
> > After the merging, the IPC feature will be available in the 'master' branch,
> future updates on the IPC part will happen in 'master' branch, too.
> > For those patches pushed towards 'feature-ipc' will be reviewed and we
> suggest push new patchset to 'master' branch.
> >
> > Please reply to this thread without hesitation if there are any questions.
> >
> > Thanks.
> >
> > -Ken
> > --
> > TF-M mailing list
> > TF-M(a)lists.trustedfirmware.org
> > https://lists.trustedfirmware.org/mailman/listinfo/tf-m
> --
> TF-M mailing list
> TF-M(a)lists.trustedfirmware.org
> https://lists.trustedfirmware.org/mailman/listinfo/tf-m
Yay! When?
> On Mar 11, 2019, at 6:57 PM, Ken Liu (Arm Technology China) via TF-M <tf-m(a)lists.trustedfirmware.org> wrote:
>
> Hi TF-M Subscribers,
> The branch 'feature-ipc' is going to be merged into 'master', and here is the patch:
> https://review.trustedfirmware.org/c/trusted-firmware-m/+/677
>
> After the merging, the IPC feature will be available in the 'master' branch, future updates on the IPC part will happen in 'master' branch, too.
> For those patches pushed towards 'feature-ipc' will be reviewed and we suggest push new patchset to 'master' branch.
>
> Please reply to this thread without hesitation if there are any questions.
>
> Thanks.
>
> -Ken
> --
> TF-M mailing list
> TF-M(a)lists.trustedfirmware.org
> https://lists.trustedfirmware.org/mailman/listinfo/tf-m