-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Description
- Update AM263px to AM263Px (both filenames & inside the files)
- Evaluate replacing memory section nomenclature like PRU0_DMEM0 / TX_PRU0_DMEM1 to something else
For the memory section nomenclature renames, how do we want to think about it?
It is currently intended to tell the reader which perspective they are viewing (e.g., ICSSG slice 1 perspective of memory is:
- PRU1_DMEM_1 (PRU1 allocation of DMEM1)
- RTU1_DMEM_1 (RTU1 allocation of DMEM1)
- TX_PRU1_DMEM_1 (TX_PRU1 allocation of DMEM1)
- PRU1_DMEM_0 (slice 1 view of PRU0's allocation of DMEM0)
- RTU1_DMEM_0 (slice 1 view of RTU0's allocation of DMEM0)
- TX_PRU1_DMEM_0 (slice 1 view of TX_PRU0's allocation of DMEM0)
But I see now how that could be confusing. If we really wanted to give per-slice views, it would make more sense to say SLICEx_[CORE-USING-ALLOCATION]_[MEMORY-REGION] to make it consistent.
PROPOSAL 1: switch to format [CORE-USING-ALLOCATION]_[MEMORY-REGION]
In this case, the labels would be the same in all linker.cmd files, and the memory offsets to the DMEM regions would be different. Default would be
- PRU0_DMEM_0
- RTU0_DMEM_0
- TX_PRU0_DMEM_0
- PRU1_DMEM_1
- RTU1_DMEM_1
- TX_PRU1_DMEM_1
Metadata
Metadata
Assignees
Labels
No labels