Hi Robin, Did you test previous release versions? It could be useful to know in which version the issue was introduced.
After that we could use git bisect to pinpoint the commit that introduced this issues. Best Regards, Alan On Mon, May 13, 2024 at 5:41 PM Robin Randhawa <robin.randh...@gmail.com> wrote: > Hi. > > I find that: > > $ ./tools/configure.sh lm3s6965-ek:qemu-flat > $ make > $ qemu-system-arm -M lm3s6965evb -net nic,model=stellaris -net > user,hostfwd=tcp:127.0.0.1:10023-10.0.2.15:23,hostfwd=tcp:127.0.0.1:10021- > 10.0.2.15:21 -kernel nuttx -nographic > > .. gets me to a nice NSH prompt with ping working. > > However, the following: > > $ ./tools/configure.sh lm3s6965-ek:qemu-protected > $ make > $ qemu-system-arm -M lm3s6965evb -net nic,model=stellaris -net > user,hostfwd=tcp:127.0.0.1:10023-10.0.2.15:23,hostfwd=tcp:127.0.0.1:10021- > 10.0.2.15:21 -kernel nuttx -nographic > > .. gets me: > > ==== > > Timer with period zero, disabling > ABCEF > > ==== > > .. with no other output. > > Adding qemu logging after disabling translation block chaining using: > > $ qemu-system-arm -M lm3s6965evb -net nic,model=stellaris -net > user,hostfwd=tcp:127.0.0.1:10023-10.0.2.15:23,hostfwd=tcp:127.0.0.1:10021- > 10.0.2.15:21 -kernel nuttx -nographic -d nochain,in_asm -D /tmp/qemu.log > > .. and processing the log like so gives me (with apologies for the > verbosity): > > $ cat /tmp/qemu.log | grep ^IN | awk '!seen[$0]++' | nl > 1 IN: __start > 2 IN: tiva_clock_configure > 3 IN: tiva_clock_reconfigure > 4 IN: tiva_lowsetup > 5 IN: modifyreg32 > 6 IN: tiva_configgpio > 7 IN: tiva_gpiobaseaddress > 8 IN: tiva_gpiofunc > 9 IN: tiva_gpiowrite > 10 IN: arm_lowputc > 11 IN: memset > 12 IN: memcpy > 13 IN: tiva_userspace > 14 IN: tiva_mpuinitialize > 15 IN: mpu_configure_region > 16 IN: mpu_allocregion > 17 IN: mpu_log2regionceil > 18 IN: mpu_subregion > 19 IN: mpu_control > 20 IN: tiva_boardinitialize > 21 IN: lm_ssidev_initialize > 22 IN: board_autoled_initialize > 23 IN: nx_start > 24 IN: strlcpy > 25 IN: up_allocate_heap > 26 IN: mpu_log2regionfloor > 27 IN: board_autoled_on > 28 IN: tiva_mpu_uheap > 29 IN: umm_initialize > 30 IN: mm_initialize > 31 IN: nxmutex_init > 32 IN: nxsem_init > 33 IN: nxsem_set_protocol > 34 IN: mm_addregion > 35 IN: mm_lock > 36 IN: nxsched_gettid > 37 IN: nxmutex_lock > 38 IN: nxsem_wait > 39 IN: nxsched_remove_readytorun > 40 IN: nxsched_add_prioritized > 41 IN: up_switch_context > 42 IN: exception_common > 43 IN: arm_doirq > 44 IN: arm_ack_irq > 45 IN: irq_dispatch > 46 IN: irq_unexpected_isr > 47 IN: syslog > 48 IN: vsyslog > 49 IN: nx_vsyslog > 50 IN: lib_syslograwstream_open > 51 IN: lib_vsprintf_internal > 52 IN: vsprintf_internal.constprop.0 > 53 IN: strnlen > 54 IN: syslograwstream_puts > 55 IN: syslog_write > 56 IN: syslograwstream_putc > 57 IN: syslog_putc > 58 IN: __ultoa_invert > 59 IN: __aeabi_uldivmod > 60 IN: __udivmoddi4 > 61 IN: __assert > 62 IN: _assert > 63 IN: up_saveusercontext > 64 IN: panic_notifier_call_chain > 65 IN: syslog_flush > 66 IN: uname > 67 IN: gethostname > 68 IN: snprintf > 69 IN: lib_memoutstream > 70 IN: lib_vsprintf > 71 IN: memoutstream_puts > 72 IN: memoutstream_putc > 73 IN: up_dump_register > 74 IN: up_getusrsp > 75 IN: up_check_tcbstack > 76 IN: arm_stack_check > 77 IN: stack_dump > 78 IN: nxsched_foreach > 79 IN: sched_lock > 80 IN: sched_unlock > 81 IN: reboot_notifier_call_chain > 82 IN: up_mdelay > 83 IN: board_autoled_off > > I assume this is unexpected ? If not, I'd appreciate any insights. > > Thanks, > Robin >
