lupyuen/nuttx-ox64
1
0
Fork 0
mirror of https://github.com/lupyuen/nuttx-ox64.git synced 2025-01-12 20:58:31 +08:00
Code Issues Projects Releases Packages Wiki Activity Actions

Add article

Browse source
This commit is contained in:
Lee Lup Yuen 2023-11-19 07:46:41 +08:00
parent f4af13ce86
commit 6948da9d6b
1 changed files with 10 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
README.md
View file

@ -4,6 +4,8 @@
Read the articles...
- ["RISC-V Ox64 BL808 SBC: Sv39 Memory Management Unit"](https://lupyuen.github.io/articles/mmu)
- ["RISC-V Ox64 BL808 SBC: Starting Apache NuttX RTOS"](https://lupyuen.github.io/articles/ox2)
- ["RISC-V Ox64 BL808 SBC: Booting Linux and (maybe) Apache NuttX RTOS"](https://lupyuen.github.io/articles/ox64)
@ -1914,6 +1916,10 @@ Now we fix the Memory Map...
# NuttX Memory Map for Ox64 BL808
Read the article...
- ["RISC-V Ox64 BL808 SBC: Sv39 Memory Management Unit"](https://lupyuen.github.io/articles/mmu)
To fix the NuttX Memory Map for Ox64, let's trace the MMU Page Table Entries. From the [MMU Log](https://gist.github.com/lupyuen/22712d6a2c3a7eb2da1f3cd5c2f4f6cf)...
## Map the I/O Region (Level 1)
@ -2156,6 +2162,10 @@ lnvaddr=0x5061b000 is User L3 Page Table for Heap
# Fix the NuttX Memory Map for PLIC
Read the article...
- ["RISC-V Ox64 BL808 SBC: Sv39 Memory Management Unit"](https://lupyuen.github.io/articles/mmu)
_Can we add L1 for 0xE000 0000 to access PLIC?_
[Nope it fails](https://gist.github.com/lupyuen/73906723edf5f1611c7829779b18668a). Because 0xE000 0000 is not aligned to 0x4000 0000 for L1.