Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to find the NSEC_DDR_0_BASE and NSEC_DDR_0_SIZE needed by dynamic memory sharing for a given platform? #6742

Closed
ZhanYF opened this issue Mar 7, 2024 · 3 comments
Labels

Comments

@ZhanYF
Copy link

ZhanYF commented Mar 7, 2024

Hi,

To enable dynamic memory sharing for optee os, I believe that NSEC_DDR_0_BASE and NSEC_DDR_0_SIZE need to be declared, but I don't know how to find the address base and have doubts on which format should the size be declared in.

For my rk3399 system with 4GB of memory I'm using register_ddr(0x00000000, 0xF6000000); now, it appears to work, but I doubt this is the correct values. Unfortunately rk3399's device tree source does not contain the base address, nor can I find this information from SoC's datasheet.

Any ideas on how can I find and validate the memory base and size? is this totally board-dependent?

Copy link

github-actions bot commented Apr 7, 2024

This issue has been marked as a stale issue because it has been open (more than) 30 days with no activity. Remove the stale label or add a comment, otherwise this issue will automatically be closed in 5 days. Note, that you can always re-open a closed issue at any time.

@github-actions github-actions bot added the Stale label Apr 7, 2024
@jenswi-linaro
Copy link
Contributor

I have a Rock4A+ that I've started to play with for testing purposes.
I can't find the memory node in the DTB supposedly used by the kernel.
I'll let you know if I find out anything more.

@github-actions github-actions bot removed the Stale label Apr 9, 2024
Copy link

github-actions bot commented May 9, 2024

This issue has been marked as a stale issue because it has been open (more than) 30 days with no activity. Remove the stale label or add a comment, otherwise this issue will automatically be closed in 5 days. Note, that you can always re-open a closed issue at any time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants