• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 692 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

GLSDK memory layout

yangwoo Lee
Intellectual 910 points
Other Parts Discussed in Thread: DRA742

Hello.

Im finding information about memory layout of GLSDK(physical memory map).

Is there any document of memroy layout of GLSDK linux? Now, I only know that kernel image start at 0x82000000 from uenv.txt

If there is no document for memory layout, please share old one of other process.

  • 0
    TI__Guru** 116100 points

    Hi,
    You can't find physical RAM memory map since Linux is using virtual address mapping.
    You can find the physical layout of flash devices from DTB file.

  • 0
    TI__Mastermind 29520 points

    Hello Yangwoo,

    You can find the information about GLSDK memory layout you can find in GLSDK datasheet:

    Below table lists the size and memory of areas that are set aside from the Linux memory map for use by remotecores. This information is taken from $GLSDK/board-support/linux/arch/arm/boot/dts/dra7-evm.dts.

    RemotecoreStart AddressCarveout size(MB)
    IPU2 0x95800000 56
    DSP1 0x99000000 64
    IPU1 0x9d000000 32
    DSP2 0x9f000000 8

    {
    model = "TI DRA742";
    compatible = "ti,dra7-evm", "ti,dra742", "ti,dra74", "ti,dra7";

    memory {
    device_type = "memory";
    reg = <0x80000000 0x60000000>; /* 1536 MB */
    };

    reserved_mem: reserved-memory {
    #address-cells = <1>;
    #size-cells = <1>;
    ranges;

    ipu2_cma_pool: ipu2_cma@95800000 {
    compatible = "shared-dma-pool";
    reg = <0x95800000 0x3800000>;
    reusable;
    status = "okay";
    };

    dsp1_cma_pool: dsp1_cma@99000000 {
    compatible = "shared-dma-pool";
    reg = <0x99000000 0x4000000>;
    reusable;
    status = "okay";
    };

    ipu1_cma_pool: ipu1_cma@9d000000 {
    compatible = "shared-dma-pool";
    reg = <0x9d000000 0x2000000>;
    reusable;
    status = "okay";
    };

    dsp2_cma_pool: dsp2_cma@9f000000 {
    compatible = "shared-dma-pool";
    reg = <0x9f000000 0x800000>;
    reusable;
    status = "okay";
    };
    };

    Best regards,

    Yanko

  • 0 in reply to Yanko Todorov-XID
    Intellectual 910 points

    Thank you for your answer.

    Actually, Im trying to boot linux core1 in jacinto6.

    I want know why GLSDK define kernel load addreass at 0x82000000 and fdt at 0x88000000.

    If I understand this memory map(before kernel boot) I can proceed next OS load address.

    As I know, All target board s/w is designed with memory map

    - flash memory map

    - image load memory map(u-boot, kernel, others...)