RE: RPi 4B MMU seems to be enabled but throwing aarch64-default-exception error

[Alan Cudmore]

Hi Noor, Nice blog entry on the JTAG setup. I ordered the FT232H board like yours to see if I can get the same setup working. I have my Pi 4 running the bare metal OS examples, and I have built your branch, so I hope to start looking at the code. What needs to be in the MMU table? I see different entries in the Aarch64 BSPs. For example the Xilinx-versal BSP has entries for the GIC, peripherals, and memory. Can you cover RAM and I/O space on the Pi 4 with just one entry? Looking at the RT-Thread OS, they have the following Pi4/Aarch64 MMU table: https://github.com/RT-Thread/rt-thread/blob/master/bsp/raspberry-pi/raspi4-64/driver/board.c#L25   Alan From: Noor Aman Sent: Friday, September 2, 2022 2:18 PM To: Alan Cudmore Cc: Hesham Moustafa; William Moore; rtems-de...@rtems.org Subject: Re: RPi 4B MMU seems to be enabled but throwing aarch64-default-exception error   Openocd connection is on my website. Here's the link to that. https://0xnoor.hashnode.dev/setup-openocd-with-jtag-uart-on-raspberry-pi-4-using-ft232h   I pushed the code to my github repo. Be sure to checkout noor-dev branch. Here's the link for that. https://github.com/0xnoor/rtems   And yes the code looks bad as of now, I'll do optimization and everything soon.   Thanks   On Fri, 2 Sept 2022 at 23:31, Alan Cudmore <alan.cudm...@gmail.com> wrote: Hi Noor, Can you describe the setup you use for testing the BSP? I can set up my Pi 4 to try running your code as you update it. How do you setup the OCD connection?   Thanks, Alan   On Fri, Sep 2, 2022 at 11:48 AM Noor Aman <nooraman5...@gmail.com> wrote: Hey all, Raspberry Pi 4B MMU seems to be enabled, as reported by openocd but gdb is showing to run in a loop from aarch64-defaulit-exception.S file starting from code line number 143 to 220.   From what I can gather, it is being caused by the wrong MMU address.  Here's a RAM and MMU allocation sizes and base     MEMORY {   RAM_MMU  : ORIGIN = 0x0, LENGTH = (0x1000 * ${AARCH64_MMU_TRANSLATION_TABLE_PAGES})   RAM      : ORIGIN = 0x80000, LENGTH = 1024M   }   Relevant Openocd info   bcm2711.cpu0 halted in AArch64 state due to debug-request, current mode: EL1T cpsr: 0x200003c4 pc: 0x8e208 MMU: enabled, D-Cache: enabled, I-Cache: enabled Info : New GDB Connection: 1, Target bcm2711.cpu0, state: halted   Any ideas?   Thanks, Noor

_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel