Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 170 views

    Davinci Configures Vlinkgen - Programmer Sought PDF

    Uploaded by

    Chittaranjan Baral
    The document discusses the steps to configure Vlinkgen memory regions in Davinci. It explains that memory regions are first divided into address segments that cannot exceed hardware limits or overlap. These segments are then divided into region blocks corresponding to physical addresses. Variables are assigned to sections mapped to these regions. Logical variable groups then define the relationship between sections and regions, and specify initialization information like core ID. Custom sections and regions can also be defined to remap standard names to a custom memory map.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Davinci Configures Vlinkgen - Programmer Sought PDF

    Uploaded by

    Chittaranjan Baral
    170 views4 pages
    The document discusses the steps to configure Vlinkgen memory regions in Davinci. It explains that memory regions are first divided into address segments that cannot exceed hardware limits or overlap. These segments are then divided into region blocks corresponding to physical addresses. Variables are assigned to sections mapped to these regions. Logical variable groups then define the relationship between sections and regions, and specify initialization information like core ID. Custom sections and regions can also be defined to remap standard names to a custom memory map.

    Original Title

    Davinci configures Vlinkgen - Programmer Sought.pdf

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document discusses the steps to configure Vlinkgen memory regions in Davinci. It explains that memory regions are first divided into address segments that cannot exceed hardware limits or overlap. These segments are then divided into region blocks corresponding to physical addresses. Variables are assigned to sections mapped to these regions. Logical variable groups then define the relationship between sections and regions, and specify initialization information like core ID. Custom sections and regions can also be defined to remap standard names to a custom memory map.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    170 views4 pages

    Davinci Configures Vlinkgen - Programmer Sought PDF

    Uploaded by

    Chittaranjan Baral
    The document discusses the steps to configure Vlinkgen memory regions in Davinci. It explains that memory regions are first divided into address segments that cannot exceed hardware limits or overlap. These segments are then divided into region blocks corresponding to physical addresses. Variables are assigned to sections mapped to these regions. Logical variable groups then define the relationship between sections and regions, and specify initialization information like core ID. Custom sections and regions can also be defined to remap standard names to a custom memory map.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    You are on page 1of 4

    5/12/23, 3:23 PM Davinci configures Vlinkgen - Programmer Sought

    Davinci Configure Vlinkgen


    where is the way
    Automotive electronics MCU software engineer

    4 people liked this article

    The following figure is very clear, and the configuration interface mainly cares about these
    few:

    Memmory regions->Memory Region Blocks->Var Groups

    The order of configuration:

    vLinkGenMemoryRegions:

    https://zhuanlan.zhihu.com/p/490101517 1/4
    5/12/23, 3:23 PM Davinci configures Vlinkgen - Programmer Sought

    This is mainly responsible for dividing the address segment. Generally, the Da Vinci
    package bought by vector has an initial division, and then add some Regions definitions
    according to your own needs. The configuration must meet several conditions:

    1. The definition of these address segments cannot exceed the address range of the
    hardware.
    2. These address segments do not leak or overlap
    . 3. These address segments should preferably be aligned such as 64byte or 1k.

    Here you need to configure the address regions of ram, dataflash, eeprom, and codeflash.
    Each hardware attribute can be divided into multiple regions.

    Each regions can be divided into multiple regionblocks,

    regions

    regions block

    In the actual physical address corresponding to each regionblock,

    https://zhuanlan.zhihu.com/p/490101517 2/4
    5/12/23, 3:23 PM Davinci configures Vlinkgen - Programmer Sought

    vLinkGenLinkerVarSections:

    All section names are defined in sections, here is just a section name, you need to use
    these section names to circle your memory in configuration or c files, this name actually
    corresponds to #pragam in your program. . . . , and specify the byte length of the
    alignment.

    Here only the segment name of ram, code, dataflash, are listed. . . all mean the same
    thing

    vLinkGenLogicalVarGroups:

    This defines the relationship between vLinkGenLinkerVarSections and


    vLinkGenMemoryRegions of ram, and defines the core ID of ram initialization,
    initialization sequence, initialization stage and other information. For example, the
    following figure,

    Specify which A_Regionblock address segment A_ramgroup belongs to, and specify the
    initialization related information of this ramgroup.

    vLinkGenLogicalUserGroups:

    It mainly defines some custom sections, and the corresponding regions also need to be
    defined in vLinkGenMemoryRegions

    https://zhuanlan.zhihu.com/p/490101517 3/4
    5/12/23, 3:23 PM Davinci configures Vlinkgen - Programmer Sought

    There are also ConstGroups. . . are the same

    To sum up, it is generally necessary to remap the segment names in the memmap.h file
    released by vector to ensure that all macro definitions in all BSW, SWC, and RTC are
    mapped to the custom memmap_userdef.h, and all macros in memmap_userdef.h The
    definition is mapped to the segment name you define, so that you can complete the
    memory division you want.

    https://zhuanlan.zhihu.com/p/490101517 4/4

    You might also like