Hello
That fflush is for fgets
Yes, with a stdout flush, message prints but the question remains about why
is it needed and how can I get input echo
Thanks
Grr
El lun, 25 ene 2021 a las 13:30, Ken Pettit () escribió:
> Hey Grr,
>
> You need the fflush(stdout) call to be *after* the printf("\n
On Fri, Jan 22, 2021 at 3:16 AM wrote:
>
> Hi Nathan,
>
> Count me in
>
> Regards
> Alin
On Sat, Jan 23, 2021 at 7:51 AM Xiang Xiao wrote:
> Nathan, thanks for raising the proposal.
> We want to join the license clearing effort and will resolve some
> engineer resource for it in this year.
Than
Grr,
Yeah, in Nuttx, fgets, fgetc, etc. don't echo. Even in Linux, the echo
is actually a function of the terminal, not the running program and
'fgets'.
In Nuittx, use the readline routine instead. But keep in mind that
readline is only *inspired* by GNU readline and has different calling
Grr,
Slightly revised version to remove trailing '\n', just for completenes. :)
my_get_command(struct spitest_s *spitest)
{
charinput[80];
ssize_t len = 0;
while (len == 0)
{
printf("\nEnter Command:");
fflush(stdout);
len = readline(input, sizeof(input), stdin, st
On 2021-01-26 16:16, Ken Pettit wrote:
Grr,
Yeah, in Nuttx, fgets, fgetc, etc. don't echo. Even in Linux, the echo
is actually a function of the terminal, not the running program and
'fgets'.
It is actually not a function of the terminal, but the terminal (serial)
device driver.
Johnny
Ken:
Thanks a lot for your code. I will try it
I was researching that echo thing and yes, that's a terminal device driver
thing. More exactly, c_lflag of termios struct. Problem is I haven't found
yet where that is set in the serial terminal setup sequence
El mar, 26 ene 2021 a las 11:28, Johnny
Hi,
working with nimBLE I found that I had an issue when scheduling a callback to
be made from within the signal handler for a timer, which was set with
SIGEV_THREAD. The issue was that I was pushing to a POSIX queue from within the
handler, and it was failing with BADFD. From debugging I realiz
Yes, you are right. Perhaps this could be added to
https://github.com/apache/incubator-nuttx/issues/1352
That is a different issue description but might still be a good location
because both issues have the same solution. The solution to both issues
is to enhance the OS by adding a new OS fa
Thanks, I'll add a comment on that issue for reference.
On Tue, Jan 26, 2021, at 20:12, Gregory Nutt wrote:
> Yes, you are right. Perhaps this could be added to
> https://github.com/apache/incubator-nuttx/issues/1352
>
> That is a different issue description but might still be a good location
