Linux/TCI6630K2L: memory layout

Atmeg

Part Number: TCI6630K2L

Tool/software: Linux

I have k2l evm with 2G DDR installed. In the device tree there are:

memory {
        device_type = "memory";
        reg = <0x0 0x8000 0000 0x0 0x2000 0000>;
       };

dspmem {
        compatible = "linux,rproc-user";
        mem = <0x0c00 0000 0x0020 0000 0xa000 0000 0x2000 0000>;
        label = "dspmem";
       };

That is 512M for Linux + 512M for DSP starting with 0x8000 0000. Than at boot time u-boot patches device-tree and sets 1.5G for Linux starting with 0x8000 0000, as I understand it. Thus, I have 1.5G for Linux, that I see at /proc/meminfo.

What about the rest 512M starting from 0xC000 0000? Why 512M DSP still starting at 0xA000 0000, not 0xC000 0000?

over 8 years ago

0 Cvetolin Shulev-XID over 8 years ago

TI__Guru 65405 points

Hi Atmeg,

I've forwarded this to the SW experts. Their feedback should be posted here.

BR
Tsvetolin Shulev

0 Cesar over 8 years ago in reply to Cvetolin Shulev-XID

TI__Guru**** 151514 points

The TCI6630K2L device has some memory aliasing to support 40bit address space from ARM

thank you

Cesar

0 Atmeg over 8 years ago in reply to Cesar

Intellectual 870 points

I have in device tree after boot:

root@k2l-evm:~# hexdump -C /proc/device-tree/memory/reg
00000000 00 00 00 08 00 00 00 00 00 00 00 00 60 00 00 00 |............`...|

That is 0x8000 0000 shifted by 4 bits left (aliasing) and 0x6000 0000 (size patched by u-boot).

But I want to understand what about 512M dsp memory and its position regarding linux memory

Processors

Processors forum

Linux/TCI6630K2L: memory layout