Re: Question regarding `WATCHDOG_AUTOMONITOR_BY_CAPTURE`
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 < saramonteirosouz...@gmail.com> wrote: > 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 > pass a watchdog_upperhalf_s * pointer? I mean, from inside the lower-half > it seems that I only have access to the watchdog_lowerhalf_s * . > > Thanks in advance, > > warm regards, > > Sara Monteiro >
Question regarding `WATCHDOG_AUTOMONITOR_BY_CAPTURE`
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 pass a watchdog_upperhalf_s * pointer? I mean, from inside the lower-half it seems that I only have access to the watchdog_lowerhalf_s * . Thanks in advance, warm regards, Sara Monteiro
building nuttX with the sample Elf loader
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': errno.c:(.text+0x2c): undefined reference to `fwrite' arm-none-eabi-ld: errno.c:(.text+0x48): undefined reference to `fwrite' arm-none-eabi-ld: errno.c:(.text+0x54): undefined reference to `fopen' arm-none-eabi-ld: errno.c:(.text+0x80): undefined reference to `fprintf' arm-none-eabi-ld: errno.c:(.text+0x88): undefined reference to `exit' arm-none-eabi-ld: errno.c:(.text+0x98): undefined reference to `__errno' arm-none-eabi-ld: errno.c:(.text+0xb0): undefined reference to `fprintf' arm-none-eabi-ld: errno.c:(.text+0xc8): undefined reference to `_impure_ptr' I'm using the toolchain indicated in the howtos from https://nuttx.apache.org/docs/latest/quickstart/install.html I haven't found any howto or FAQ explaining howto build nuttX with the sample ElfLoader, so I assumed that it only needs to be selected in the menuconfig. Did I miss something? Thanks in advance Nuno
Re: Serial console strange behaviour
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 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 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 line. Other lines are shown only > if I type at least one symbol. > I tried with and without CONFIG_USART6_RXDMA - same result. > > USB CDC ACM console works OK. > > Any thoughts on what can cause such behavior? > > --- > With best regards, Oleg >
RE: Serial console strange behaviour
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 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 line. Other lines are shown only if I type at least one symbol. I tried with and without CONFIG_USART6_RXDMA - same result. USB CDC ACM console works OK. Any thoughts on what can cause such behavior? --- With best regards, Oleg
Serial console strange behaviour
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 line. Other lines are shown only if I type at least one symbol. I tried with and without CONFIG_USART6_RXDMA - same result. USB CDC ACM console works OK. Any thoughts on what can cause such behavior? --- With best regards, Oleg
