The ticket I created last month for Calendar on the website.
Can document a go or no-go decision here.

Hi,
Please use personal email and git configs/identity to push the patch to trustedfirmware.org. Few developers from the tf-a community have done this. Here is a link to contribution guidelines:

Thanks for your reply. It is difficult to submit code to community or Gerrit using company's account and system. So, I wonder whether it's permitted to upload by providing modifications or “git send-email” with patches.

The whole problem has boiled down to a flash write issue and it has been worked around by c32710c7fc8514dd0d072a01549e23a94278ee17.

Verified with https://github.com/zephyrproject-rtos/zephyr/pull/30226

This issue is now fixed and can be closed

Hi Li,

Hi,
Yeah, looks like such a large system with numerous clusters will run into an issue with the current limitation of "lock_index" being "unsigned char". Please go ahead and submit a patch for review:

Yes, The power domain topology of the system can be described as 8 sockets, each socket with 10 clusters and each cluster with 8 cores. We just consider a system like this might face the constraint mentioned above, and we must modify the declaration of lock_index to solve this problem. Feature, more and more interconnected system, with numerous cpus, might face the same problem.

Hi,
The struct "non_cpu_pwr_domain_node" represents a non-leaf power domain in an SoC such as a logical cluster. As you mentioned, the lock_index declaration with "unsigned char" limits such non-cpu power domains to 64. I believe it doesn't restrict the number of CPUs in a system to be <= 64. Do you currently face an issue with PSCI implementation due to the above constraint? Can you advise what is the power domain topology of your system? I think the lock_index can be expanded using "unsigned int" if needed.

Patch fixed and merged

Fixed by merge of https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/6604

Closed the previous issue https://developer.trustedfirmware.org/T845 as duplicate

Internal ref : https://jira.arm.com/browse/IOTPSW-3471

Change has been merged: https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/commit/?id=8c2f524067093681896cd69474813488ac59e022

Thanks, everybody.

Related gerrit review: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/6655

Linaro ticket from Kyle: https://projects.linaro.org/browse/WEBDEV-1051

https://production-trustedfirmware-org-300.ghactions.linaro.org/meetings/

Discussed with @kylekirkby and he has deployed a mockup for me.

It is not a requirement for test data to persist across reboots, and there is no impact on release code, so this would be a nice-to-have improvement to the tests rather than an issue that needs fixing with any priority.

Tested changes on LPC55S69, both patches seem good here.

Related code reviews:

• https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5534
• https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/6517

Cleaning the flash properly seems to solve the issue. Closing this bug as resolved. The SST hardening will taken up as a backlog item.

The latest FVP claims to have resolved this problem. This needs to be re-tested on latest AN521 FVP.