You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nuttx.apache.org by "yf13 (via GitHub)" <gi...@apache.org> on 2024/08/10 01:58:08 UTC

Re: [I] [BUG] Running lm3s6965-ek:qemu-protected with gdb-multiarch is crashing [nuttx]

yf13 commented on issue #12872:
URL: https://github.com/apache/nuttx/issues/12872#issuecomment-2278936876

   @acassis this is my first taste of `qemu-system-arm` with a NuttX arm port. Here I followed your QEMU launching method and got that error directly:
   
   ```shell
   $ qemu-system-arm -M lm3s6965evb -net user,hostfwd=tcp:127.0.0.1:10023-10.0.2.15:23 -net nic,model=stellaris -nographic -kernel nuttx
   Timer with period zero, disabling
   ABCDEF
   qemu: fatal: Lockup: can't escalate 3 to HardFault (current priority -1)
   
   ```
   
   I am wondering how `nuttx_user.elf` get loaded to QEMU? Protected build has two ELFs and for riscv we use "-device loader,file=xxx" to load the other ELF. But when I added that option I got:
   
   ```shell
   $ qemu-system-arm -M lm3s6965evb -net user,hostfwd=tcp:127.0.0.1:10023-10.0.2.15:23 -net nic,model=stellaris -nographic -kernel nuttx -device loader,file=nuttx_user.elf
   qemu-system-arm: Some ROM regions are overlapping
   ...
   The following two regions overlap (in the cpu-memory-0 address space):
     nuttx ELF program header segment 2 (addresses 0x000000000001e048 - 0x0000000000021984)
     nuttx_user.elf ELF program header segment 1 (addresses 0x0000000000020000 - 0x00000000000400e8)
   ```
   


-- 
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: commits-unsubscribe@nuttx.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org