Hi Boyan,
That's true, but it must not have came up this far with the existing platforms tftf supports. I don't see why it can't it be done, so if you have an idea for an implementation me or someone else on the team would
be happy to review it.
To handle custom invalid entry addresses, we have updated a template change on one of our platforms to use the PLAT_INVALID_ADDR macro instead of the default 0x0. This change is part of the TFTF test for validating invalid entry addresses in the CPU hot plug scenario. A custom address can be provided either through the header (defaulting to the invalid address) or via the platform makefile to specify a custom valid or invalid address. Please review this idea and let us know your thoughts.
Please find the attached patch for the same.
Patches are pushed to gerrit, please review the changes.
https://review.trustedfirmware.org/c/TF-A/tf-a-tests/+/35311/1 https://review.trustedfirmware.org/c/TF-A/tf-a-tests/+/35310/1
Regards, Maheedhar.