Local Access Windows (LAWs), memory overlap

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Local Access Windows (LAWs), memory overlap

2,153 Views
marklv
Contributor I

About LAW understanding : about the B4860 , just e.g B4860QDS;

Local Access Windows (LAWs):

in the B4860_QDS_Init.tcl file have set the Local Access Window Registers (as below have defined the phy address 0x000000, size 2Gbytes target to DDR)

and in the  dpaa_demo.c of CW_SC_3900FP_v10.8.3\SC\StarCore_Support\SmartDSP\demos

add the LAW setting the phy address 0x20000000 target  to  QMAN

my query or confusing is  the LAW 10 setting (0x0000000~0x7fffffff target to DDR)   memory overlapped with  QMAN software port  LAW setting the phy address 0x20000000 target  to  QMAN.

memory overlapped  between LAW , is it ok? and can explain detail why it can work ? there is not descript memory overlapped situation of LAW  in the reference manual of B4860.


 ## LAW10 to DDRC2
 # LAWBARH
 mem [CCSR_ADDR 0x000CA0] = 0x00000000
 # LAWBARL
 mem [CCSR_ADDR 0x000CA4] = 0x00000000
 # LAWAR
 mem [CCSR_ADDR 0x000CA8] = 0x8110001E

0 Kudos
Reply
3 Replies

867 Views
jons_william
Contributor I

 

Thanks for sharing the [RTD200P04 MCAL] S32M244 PWM PDB ADC MCAL demo—really helpful for developers working with embedded systems. For those handling compliance or security logging alongside hardware interfaces, reviewing Missouri offense records could offer useful insights for managing real-world data inputs. Always good to bridge technical applications with broader contextual awareness.

0 Kudos
Reply

2,083 Views
ufedor
NXP Employee
NXP Employee

Please refer to the B4860 QorIQ Qonverge Multicore Baseband Processor Reference Manual, 2.3.1 Precedence of Local Access Windows.

2,084 Views
marklv
Contributor I

thx

0 Kudos
Reply