Hi Nick

First, i share that i'm reviewing TF-M v2.3.0 with tag https://review.trustedfirmware.org/plugins/gitiles/TF-M/trusted-firmware-m/+/refs/tags/TF-Mv2.3.0 

In the shared commit, platform/ext/target/arm/rse/neoverse_rd/rdv3/bl2/boot_hal_bl2.c call atu_rse_drv_init() in boot_platform_post_init() like below.

int32_t boot_platform_post_init(void)

{

    int32_t result;

    enum atu_error_t atu_err;

    result = rse_sam_init(RSE_SAM_INIT_SETUP_FULL);

    if (result != 0) {

        return result;

    }

    atu_err = atu_rse_drv_init(&ATU_DEV_S, ATU_DOMAIN_ROOT, atu_regions_static, atu_stat_count);

    if (atu_err != ATU_ERR_NONE) {

            return result;

    }

But, atu_rse_drv_init don't be called in platform/ext/target/arm/rse/neoverse_rd/rdv3r1/bl2/boot_hal_bl2.c anywhere.

So, i tried to find ATU setting to other sources in RDV3R1 platform, i couldn't find ATU setting to load post image.

Is there any codes setting ATU for each processor region that image will be loaded?

Best Regards

RH Kim

----- 원본 메시지 -----
보낸 사람: Nicola Mazzucato <Nicola.Mazzucato@arm.com>
받는 사람: tf-m@lists.trustedfirmware.org <tf-m@lists.trustedfirmware.org>,김륜현 <winxp4333@adtek.co.kr>
날짜: 2026-05-13 17:01:37
제목: Re: [TF-M] no ATU setting in RDV3r1 with TF-M v2.3.0

Thanks RH Kim,

The commit you shared did not remove any ATU initialisations from what I see.

To understand better, are you working on a branch or old commit where you see atu_rse_drv_init for RDV3R1? If so, can you please share?

I'm also not very familiar with that platform so it's likely I'm missing something, though it seems that the platform_post_init sequence is different from RDV3.

Thanks

Best regards,

Nick

---

From: 김륜현 via TF-M <tf-m@lists.trustedfirmware.org>
Sent: 13 May 2026 03:16
To: tf-m@lists.trustedfirmware.org <tf-m@lists.trustedfirmware.org>
Subject: [TF-M] no ATU setting in RDV3r1 with TF-M v2.3.0

 

Dear all, i'm developing the RSE firmware based on rdv3r1.

I'm reviewing TF-M v2.3.0 was recently released for checking difference our project codes.

Among many differences, i discovered missing ATU settings to load post processor images.

In the similar platform rdv3, it calls atu_rse_drv_init() at boot_platform_post_init(). 

But rdv3r1 doesn't call atu_rse_drv_init() also i can't found ATU settings to load post images in BL2.

Is there any intentions?

Or was it just missing while integrating by this commit https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/39562?

Please check it 

Best Regards

RH Kim