Re: Question regarding `WATCHDOG_AUTOMONITOR_BY_CAPTURE`

2020-11-11 Thread Xiang Xiao
watchdog_register return watchdog_upperhalf_s * pointer, so lowerhalf could save the return value some place. Here is an example: https://github.com/FishsemiCode/nuttx/blob/song-u1/drivers/timers/dw_wdt.c#L350 On Thu, Nov 12, 2020 at 4:59 AM Sara da Cunha Monteiro de Souza <

Question regarding `WATCHDOG_AUTOMONITOR_BY_CAPTURE`

2020-11-11 Thread Sara da Cunha Monteiro de Souza
Dear Greg, I've been exploring the AUTOMONITOR feature and I had an issue. It seems the watchdog_automonitor_capture callback expects to receive a watchdog_upperhalf_s * pointer, but since the registration and call of this callback happen from inside the lower-half, how would we be supposed to

building nuttX with the sample Elf loader

2020-11-11 Thread nuno felicio
Hi! I'm trying to build nuttX with the ElfLoader sample, I already tried master from the git repo and the 9.1.0. And both fail the same way. LD: errno.o arm-none-eabi-ld: warning: cannot find entry symbol _start; defaulting to 8000 arm-none-eabi-ld: errno.o: in function `main':

Re: Serial console strange behaviour

2020-11-11 Thread Oleg Evseev
No, it is the same board and config that worked before with NuttX 8.2 without such issues. Only several modifications same as was done for fmu-v5 to work with 10.0.0. Serial consoles on PX4 boards work ok, no such issues, right? ср, 11 нояб. 2020 г. в 14:14, David Sidrane : > Are you running any

RE: Serial console strange behaviour

2020-11-11 Thread David Sidrane
Are you running any PX4IO drivers or RC input? -Original Message- From: Oleg Evseev [mailto:ev.m...@gmail.com] Sent: Wednesday, November 11, 2020 3:09 AM To: dev@nuttx.apache.org Subject: Serial console strange behaviour Hi, Custom board stm32f7, PX4 based project - moved from NuttX

Serial console strange behaviour

2020-11-11 Thread Oleg Evseev
Hi, Custom board stm32f7, PX4 based project - moved from NuttX 8.2 to 10.0.0. If serial dev console (CONFIG_USART6_SERIAL_CONSOLE=y) is used, it works: prints all corresponding output on boot, but then "nsh> " is shown only when I start typing in putty. "ls" command shows only the first output