After I got Secure Boot running for NOR flash boot I'm again working on SD boot.
First of all, the SDK 2.0-1703 manual doesn't fit my platform, as it seems. Let me explain. I built images for T1024RDB using the SDK, but the files rcw.bin and u-boot-dtb.bin (required according to the manual) are not present. Then, I need input_files/uni_sign/<platform>/sdboot/input_uboot_secure, which doesn't exist for my platform (the directory input_files/uni_sign/t1_t2_t4/sdboot does not exist). Also, the file input_files/create_pbi/<platform>/input_pbi_sd_secure does not exist for the T-series platform (only for ls1). I guess that the manual has Layerscape in mind. Maybe you want to update it a little bit to help T-series users find their corresponding files.
Anyway, I managed to partly adapt the config file uni_pbi input_files/create_pbi/ls1/input_pbi_sd_secure to my needs. The uni_pbi tool now creates a PBI file which writes the BOOT1_PTR value to the address 0xee0200, which looks like the Layerscape DCFG_CCSR_SCRATCHRW1 address, which is wrong for the T-series. The address seems to be hardcoded in the uni_pbi source ("#define BOOTPTR_ADDR 0x09ee0200").
Question: Can the uni_pbi tool be used for T1024 (if yes: how?).