GUIDINGLI opened a new pull request, #13985:
URL: https://github.com/apache/nuttx/pull/13985

   ## Summary
   
   arch/arm64: Add the interface for icache and dcache.
   arch/arm64: Fixed arm64_cache_get_info obtaining cache.
   arm64_checkstack: fix crash, optimize the stack color, sync with arm
   arm64: fix backtrace failed
   arm64-r/mpu: add TBI setting to r82 when use SW_TAG
   
   @pussuw 
   Removed un-used function arm64_exception_context_save(), how do you think ?
   
   I have tried with/without this PR:
   Documentation/platforms/arm64/qemu/boards/qemu-armv8a/README.txt
   ```
   151   3.5 Single Core /w kernel mode (GICv3)
   152    Configuring NuttX and compile:
   153    $ ./tools/configure.sh -l qemu-armv8a:knsh
   154    $ make
   155    Running with qemu
   156    $ qemu-system-aarch64 -semihosting -cpu cortex-a53 -nographic \
   157      -machine virt,virtualization=on,gic-version=3 \
   158      -net none -chardev stdio,id=con,mux=on -serial chardev:con \
   159      -mon chardev=con,mode=readline -kernel ./nuttx
   
   this will crash:
   dump_assert_info: Current Version: NuttX  10.4.0 90836e5db1 Oct  9 2024 
17:15:15 arm64
   dump_assert_info: Assertion failed : at file: init/nx_bringup.c:381 task: 
Idle_Task process: Kernel 0x40286394
   up_dump_register: stack = 0x402b90c0
   up_dump_register: x0:   0x402b90c0          x1:   0x0
   up_dump_register: x2:   0x0                 x3:   0x0
   up_dump_register: x4:   0xcd0               x5:   0x402bfff0
   up_dump_register: x6:   0x402be108          x7:   0x7f7f7f7f7f7f7f7f
   
   ```
   
   Seems we should put a APPs into the romfs bin ?
   
   ## Impact
   
   arm64
   
   ## Testing
   
   xiaomi armv8r board & qemu
   
   qemu-armv8a:nsh
   qemu-armv8a:nsh_smp
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to