Resources tabs

With an editable analog resource selected, click the Edit Route command to enable edit mode. If multiple routes are selected, a pull-down menu displays to select the route to edit. You cannot edit multiple routes at the same time.

In edit mode, the net tree shows only the applicable route entries, and you cannot select resources using the tree. However, the lock/unlock check boxes remain enabled for use. The inactive switches change color to indicate they can be selected to use for the route being edited.

Route changes are live with updates applied automatically as you make changes. Selecting a switch adds it to the current route in a locked state and the route tree is updated to reflect the modifications.

If a change results in an error, a message displays. The routes are automatically rolled back to the previous state, so you will lose at most the last invalid change.

The toolbar shows the Finish edit command to return the editor to selection mode.

To edit allocations, double-click an allocated row to open Edit Memory Region dialog.

To add an allocation, double-click an unallocated row to open the Add New Memory Region dialog.

Once the dialog is open, enter values:

1. As needed, type the name of the Region id.
2. Select a Domain from the pull-down menu.
3. Enter the Offset and Size.

The Size entry allows for hex or decimal entry. It also accepts specifying units, which will always be converted to bytes. Units are case insensitive and can be entered as follows:

• bytes or b = byte
• kb or k = kilobyte (1 KB = 1,024 Bytes)
• mb or m = megabyte (1 MB = 1024KB = 1,048,576 Bytes)
• gb or g = gigabyte (1 GB = 1024MB = 1,048,576 KB = 1,073,741,824 Bytes)
• tb or t = terabyte (1 TB = 1024 GB = 1,048,576 MB = 8,388,608 KB = 1,099,511,627,776 Bytes)
• pb or p = petabyte (1 PB = 1024 TB = 1,048,576 GB = 1,073,741,824 MB = 1,099,511,627,776 KB = 1,125,899,906,842,624 Bytes)
• eb or e = exabyte (1 EB = 1024 PB = 1,048,576 TB = 1,073,741,824 GB = 1,099,511,627,776 MB = 1,125,899,906,842,624 KB = 1,152,921,504,606,846,976 Bytes)
• zb or z = zettabyte (1 ZB = 1024 EB = 1,048,576 PB = 1,073,741,824 TB = 1,099,511,627,776 GB = 1,125,899,906,842,624 MB = 1,152,921,504,606,846,976 KB = 1,180,591,620,717,411,303,424 Bytes)
• yb or y = yottabyte (1 YB = 1024 ZB = 1,048,576 EB = 1,073,741,824 PB = 1,099,511,627,776 TB = 1,125,899,906,842,624 GB = 1,152,921,504,606,846,976 MB = 1,180,591,620,717,411,303,424 KB = 1,208,925,819,614,629,174,706,176 Bytes)

If there are obvious errors, the dialog will not allow you to click OK. There may also be an error message.

You can also open the dialog using the drop-down button at the beginning of a row or right-clicking on a row. Unallocated regions will start with an Add region option while allocated regions will have the Edit region option. Both options launch the same edit dialog.

If you prefer, use the keyboard shortcuts defined on the menus.

On the context menu, there are various options to move regions, as well as cut, copy, and paste regions.

When moving a region, there are two options: After existing regions and Specify offset.

When you select Specify offset, this dialog displays to enter the offset.

Code that doesn't have an explicit section name goes in .text (or .text.function_name when using -ffunction-sections). Search for .text in the linker script or search the .map file for the function name.

For each project in an application, “make build” will display a summary of the output sections:

Memory region             Used Size  Region Size  %age Used
 m55_data_INTERNAL:         3796 B        256 KB      1.45%
 m55_code_INTERNAL:        12024 B        256 KB      4.59%
        user_nvm_C:            0 GB        32 KB      0.00%
           m55_nvm:        24900 B       2816 KB      0.86%
       m55_trailer:            0 GB       256 KB      0.00%
m55_code_secondary:            0 GB       256 KB      0.00%
m55_data_secondary:         2800 KB      2800 KB    100.00%
    m33_m55_shared:          256 KB       256 KB    100.00%

           gfx_mem:            0 GB      1808 KB      0.00%

          m33_data:            0 GB       256 KB      0.00%

m33s_allocatable_shared:       0 GB         4 KB      0.00%

m33_allocatable_shared:        0 GB         4 KB      0.00%

m55_allocatable_shared:     1088 B          4 KB     26.56%

The “.map” file generated by the linker contains details about which input sections the linker placed into each output section. To find the memory region corresponding to each output section, search for the memory region that contains the section's address.

.appText_1      0x60580400     0x1f70
...
.text.main     0x6058094c       0x14 build/APP_KIT_PSE84_EVAL/Debug/main.o
               0x6058094c                main
.text.Cy_PDL_Init
               0x60580960        0xc build/APP_KIT_PSE84_EVAL/.../cy_device.o
               0x60580960                Cy_PDL_Init

• .appText_1 is the output section name. It is followed by the output section start address (0x60580400) and the output section total size (0x1f70).
• .text.main is the input section name. It is followed by its address (0x6058094c) and size (0x14).

Initialized data in volatile memory also consumes space in a non-volatile memory.

.data           0x20000000       0x24 load address 0x60582658

The .data section consumes 0x24 bytes at both its writable address 0x20000000 and its non-volatile address 0x60582658.

1. In the memory tab, add a new region named “CUSTOM_CODE” in a non-volatile memory such as RRAM.
2. In the linker script, add a section for the region:

   GNU ld or LLVM lld

   a.	.custom_code :
   {
       *(.custom_code*)
   } >CUSTOM_CODE
   

   armlink

   LOAD_CUSTOM_CODE CYMEM_CM55_0_CUSTOM_CODE_START CYMEM_CM55_0_CUSTOM_CODE_SIZE
   {
       EXEC_CUSTOM_CODE +0
       {
           *(.custom_code*)
       }
   }
   

   ilinkarm

   place in CUSTOM_CODE { section .custom_code* }

3. In the source code, assign the variable to the section (GCC, armclang, or iccarm)

   __attribute__((section ".custom_code"))
   void custom_code_function1(void);
   

Variables and functions may be assigned to a section using the section attribute. The linker script must assign the section to an output section.

__attribute__((section ".custom_data"))
uint32_t data_buffer[DATA_BUFFER_COUNT];

__attribute__((section ".custom_code"))
void custom_code_function1(void);

GNU ld or LLVM lld

.custom_code :
{
    main.o(.text* .rodata*)
} >CUSTOM_CODE
.custom_data :
{
    main.o(.data*)
    main.o(.bss*)
} >CUSTOM_DATA AT>CUSTOM_CODE

armlink

LOAD_CUSTOM_CODE CYMEM_CM55_0_CUSTOM_CODE_START CYMEM_CM55_0_CUSTOM_CODE_SIZE
{
    EXEC_CUSTOM_CODE +0
    {
        main.o(+RO)
    }
    EXEC_CUSTOM_DATA CYMEM_CM55_0_CUSTOM_DATA_START CYMEM_CM55_0_CUSTOM_DATA_SIZE
    {
        main.o(+RW,+ZI)
    }
}

ilinkarm

place in CUSTOM_CODE { ro object main.o }
place in CUSTOM_DATA { rw object main.o }

The linker script example assigns all of the code and data from object files matching mtb_hal_*.o to the .custom_code and .custom_data sections respectively. If the middleware’s object files cannot be described in a single pattern, it may be necessary to use multiple patterns.

GNU ld or LLVM lld

.custom_code :
{
    mtb_hal_*.o(.text* .rodata*)
} >CUSTOM_CODE
.custom_data :
{
    mtb_hal_*.o(.data*)
    mtb_hal_*.o(.bss*)
} >CUSTOM_DATA AT>CUSTOM_CODE

armlink

LOAD_CUSTOM_CODE CYMEM_CM55_0_CUSTOM_CODE_START CYMEM_CM55_0_CUSTOM_CODE_SIZE
{
    EXEC_CUSTOM_CODE +0
    {
        mtb_hal_*.o(+RO)
    }
    EXEC_CUSTOM_DATA CYMEM_CM55_0_CUSTOM_DATA_START CYMEM_CM55_0_CUSTOM_DATA_SIZE
    {
        mtb_hal_*.o(+RW,+ZI)
    }
}

ilinkarm

place in CUSTOM_CODE { ro object mtb_hal_*.o }
place in CUSTOM_DATA { rw object mtb_hal_*.o }

This is highly dependent on the needs of the customer’s application. Solutions may include:

• Resizing existing regions
  • Double-click on the region to open the Edit dialog.
  • Update the Size. If the region needs to be moved, also update the Offset.
• Moving existing regions to another memory
• Updating linker scripts to place code or data in different regions