TDA4VM: Questions about converting to rprc files

Could you please comment on this question?
If there is anything unclear about the content, please let me know.

Hi Tatsuaki,

Sorry for delay here.

Tatsuaki Shibuya said:

・The source file has a 64-bit space section.
・On the scatter file, there is a section for Empty.

Can you show this from the snippet of the map / linker file?

Regards

Karan

Hi Karan

Thank you for the reply.
The script file where the problem occurs is described as follows
(Only relevant points are described.)

> The source file has a 64-bit space section.

ENTITY1 0x0000000088000000
{
BOOT_RO 0x0000000088000000
{
xxxx
}
BOOT_RW +0
{
xxxx
}
BOOT_SECTION +0 ALIGN 0x1000
{
xxxx
}
BOOT_STUB 0x08C0000000 ALIGN 0x1000
{
xxxx
}

At this time, the BOOT_STUB conversion is not executed.

> On the scatter file, there is a section for Empty.

BOOT_STACK +0x1000 ALIGN 0x1000 EMPTY 0x2000
{
}

At this time, the BOOT_STACK conversion is not performed.

Best Regards

Hi Karan

I supplement the above.
The following sections will not be converted.

BOOT_STUB 0x08C0000000 ALIGN 0x1000
{
        xxxx
}

All sections after this section will not be converted.
The area before this section will be converted.

Best Regards

Is there any updated information on this issue?

I have organized the content for this question.
I want to convert the linker file with the attached section information to TI RPRC image format.
However, the following problems have been encountered when performing the conversion.
・I can only convert up to [4].
・Only the sections that have PROGBITS set up are being converted.

I want a tool to convert this section information to TI format.
If you don't have a tool to convert it, could you please tell me how to convert it?
section_info.txt

Hi,

I don't think the issue with with the section marked PROGBITS or not. I was trying to get map for the elf image generated for another example for A72.

See udma_memcpy_testapp_mcu1_0_release_readelf.txt

Can you help me understand what are you trying to load at the address 0x08C0000000 ? And can you confirm the core this is intended for is A72?

We do have example linker files for A72 as well see https://git.ti.com/cgit/processor-sdk/pdk/tree/packages/ti/build/j721e/linker_a72_mpu1_0.lds 

Regards

Karan

Hi Karan

Thank you for the reply.
Can you help me understand what are you trying to load at the address 0x08C0000000 ?
→An empty area has been set. However, in our system, we have to define it.

And can you confirm the core this is intended for is A72?
→Yes. The target core is A72.

Thank you for the link file. We will check this out.

The definition of 0x08C0000000 is attached.
I want to resolve this issue by August 31.

I want a tool that can convert this link file by then.
Or can you tell me how to work around it?

Is there any updated information on this issue?

Is there any updated information on this issue?