You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
The text was updated successfully, but these errors were encountered:
yvantor
pushed a commit
to pulp-platform/cva6-sdk
that referenced
this issue
Apr 10, 2024
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.
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.
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.
The text was updated successfully, but these errors were encountered: