masayuki2009 commented on PR #13022:
URL: https://github.com/apache/nuttx/pull/13022#issuecomment-2305867808

   @tmedicci 
   Thanks for confirming. Could you tell me what version of the toolchain are 
you using now?
   I'm using the following version.
   
   ```
   $ xtensa-esp32-elf-gcc --version
   xtensa-esp32-elf-gcc (crosstool-NG esp-12.2.0_20230208) 12.2.0
   Copyright (C) 2022 Free Software Foundation, Inc.
   This is free software; see the source for copying conditions.  There is NO
   warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
   ```
   
   Also, could you try the NuttX with QEMU?
   I got the following log with QEMU.
   
   ```
   $ 
/home/ishikawa/opensource/QEMU/qemu-esp-develop-8.2.0-20240122/build/qemu-system-xtensa
 -nographic -M esp32 -smp 2 -drive 
file=/home/ishikawa/qemu_efuse.bin,if=none,forma
   ==1601971==WARNING: ASan doesn't fully support makecontext/swapcontext 
functions and may produce false positives in some cases!
   Adding SPI flash device
   ets Jul 29 2019 12:21:46
   
   rst:0x1 (POWERON_RESET),boot:0x12 (SPI_FAST_FLASH_BOOT)
   configsip: 0, SPIWP:0xee
   clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
   mode:DIO, clock div:2
   load:0x3ffb2090,len:1484
   ho 0 tail 12 room 4
   load:0x40080000,len:21372
   entry 0x40082648
   *** Booting NuttX ***
   dram: lma 0x00001020 vma 0x3ffb2090 len 0x5cc    (1484)
   iram: lma 0x000015f4 vma 0x40080000 len 0x537c   (21372)
   padd: lma 0x00006988 vma 0x00000000 len 0x9670   (38512)
   imap: lma 0x00010000 vma 0x40100000 len 0x26258  (156248)
   padd: lma 0x00036260 vma 0x00000000 len 0x9db8   (40376)
   dmap: lma 0x00040020 vma 0x3f400020 len 0x29554  (169300)
   total segments stored 6
   
   NuttShell (NSH) NuttX-12.6.0-RC1
   nsh>  
   nsh> uname -a
   NuttX 12.6.0-RC1 fe642f1cfd Aug 23 2024 07:37:44 xtensa esp32-devkitc
   nsh> ps 
     PID GROUP PRI POLICY   TYPE    NPX STATE    EVENT     SIGMASK           
STACK   USED  FILLED COMMAND
       0     0   0 FIFO     Kthread   - Ready              0000000000000000 
003040 000824  27.1%  Idle_Task
       1     0 224 RR       Kthread   - Waiting  Semaphore 0000000000000000 
001960 000392  20.0%  hpwork 0x3ffb17e4 0x3ffb17f8
       2     0 100 RR       Kthread   - Waiting  Semaphore 0000000000000000 
001960 000392  20.0%  lpwork 0x3ffb17bc 0x3ffb17d0
       3     3 100 RR       Task      - Running            0000000000000000 
003008 002176  72.3%  nsh_main
   nsh> elf
   Initial memory usage: 13272
   Registering romdisk at /dev/ram0
   
   Memory Usage after romdisk_register:
     Before:    13272 After:    13328 Change:       56
   Mounting ROMFS filesystem at target=/mnt/romfs with source=/dev/ram0
   
   Memory Usage after mount:
     Before:    13328 After:    13888 Change:      560
   
   ****************************************************************************
   * Executing errno
   ****************************************************************************
   
   
   Memory Usage after exec:
     Before:    13888 After:    17056 Change:     3168
   Wait a bit for test completion
   Hello, World on stdout
   Hello, World on stderr
   We failed to open "aflav-sautga-ay!" errno is 0
   xtensa_user_panic: User Exception: EXCCAUSE=001c task: errno
   _assert: Current Version: NuttX  12.6.0-RC1 fe642f1cfd Aug 23 2024 07:37:44 
xtensa
   _assert: Assertion failed user panic: at file: :0 task: errno process: errno 
0x40085538
   up_dump_register:    PC: 4000c780    PS: 00060430
   up_dump_register:    A0: 800593a4    A1: 3ffe2b50    A2: 00000000    A3: 
40059320
   up_dump_register:    A4: 000000d8    A5: 3ffe2b50    A6: 00000008    A7: 
00000000
   up_dump_register:    A8: 80104ea1    A9: 3ffe2b20   A10: 00000000   A11: 
3ffe2b40
   up_dump_register:   A12: 3ffe2008   A13: 3ffe2b50   A14: 00000008   A15: 
3ffe1e40
   up_dump_register:   SAR: 00000004 CAUSE: 0000001c VADDR: 000000e0
   up_dump_register:  LBEG: 4000c28c  LEND: 4000c296  LCNT: 00000000
   
   ```


-- 
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