Skip to content
New issue

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

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

Already on GitHub? # to your account

devmem cann't write into all physical address of a new peripheral #63

Open
monireee opened this issue Mar 6, 2022 · 1 comment
Open

Comments

@monireee
Copy link

monireee commented Mar 6, 2022

I tried to write data to the physical address of the already available peripheral, Timer (base address 0x18000000), and newly added peripheral (base address 0x60000000). The read data after writing at several physical addresses for these peripherals are shared in screenshots.
For Timer: Data written into an address is read at another address as you see in the screenshot.
image

For new peripheral: Data can be written with the offset of multiple of 8, 0x60000000, 0x60000008, 0x60000010, 0x60000018. But after that, data reads as zero for the rest of the addresses.
image

Can anybody explain this data pattern that I read after writing?
Again, would you please suggest how can I write into all physical addresses while OS is running?
Thanks in advance.

yvantor pushed a commit to pulp-platform/cva6-sdk that referenced this issue Apr 10, 2024
…sync

Expose asynchronous register interface from Cheshire wrap
@wal222
Copy link

wal222 commented Jul 28, 2024

Hi, I also wanna add a peripheral to the core. Could you tell how exactly you did it? I would highly appreciate it.

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

No branches or pull requests

2 participants