But using tmux, I am able to get pdcurses displays like this (it
actually has color):
File Debug Help
┌───Watch───┐
┌─┐│ │
│ ││ │
│ . *
││
Hey Johnny,
It has been a while since I ran the pdcurses with minicom, but my
recollection is that something sets attributes of the entire display to
blink all the time. Plus when drawing window borders using the VT100 /
ANSI line drawing character, you end up with a bunch of funky characters
On Fri, Jan 22, 2021, 3:54 PM Matias N. wrote:
>
> > Is there any easy way to get all of the register definition header files
> > in place (with Apache 2 headers)?
>
> If there's an SVD file somewhere, you can use this:
>
> https://gitlab.com/nuttx_projects/svdgen
>
> I've used it many times and
On 2021-01-22 23:43, Gregory Nutt wrote:
Now examples compile and work although in flashing mode with minicom in
VT102 mode
If you start mincom with -t vt100 it should force VT100 vs VT102 mode.
But I thought that VT102 was mostly compatible?
The VT102 is a superset of the VT100. There are
> Is there any easy way to get all of the register definition header files
> in place (with Apache 2 headers)?
If there's an SVD file somewhere, you can use this:
https://gitlab.com/nuttx_projects/svdgen
I've used it many times and requires minimal tweaking afterwards.
Best,
Matias
Hey Greg,
I actully tried ALL of the emulation modes offered by minicom and each
one behaved the same.
I found that using Linux 'screen' or 'tmux' works, but neither of those
deal with the /dev/tty device "disappearing" suddenly.
Ken
On 1/22/21 2:43 PM, Gregory Nutt wrote:
Now examples
Now examples compile and work although in flashing mode with minicom in
VT102 mode
If you start mincom with -t vt100 it should force VT100 vs VT102 mode.
But I thought that VT102 was mostly compatible?
The Raspberry Foundation created their own microcontroller based on
ARM Cortex M0+ with 1MB Flash and 256KB RAM.
I wonder how the performance is with two cores running from QSPI with no
instruction cache?
There is no data cache either. This could be an issue for SMP, at least
if the same
Yeah, I have never found a way to use pdcurses with minicom ... it
always has flashing characters like you stated.
Ken
On 1/22/21 2:10 PM, Grr wrote:
It also needs CONFIG_PDCURSES_MULTITHREAD or there's no PDC_ctx_free()
definition
Now examples compile and work although in flashing mode with
It also needs CONFIG_PDCURSES_MULTITHREAD or there's no PDC_ctx_free()
definition
Now examples compile and work although in flashing mode with minicom in
VT102 mode
I'll fix that later
Thanks again
Grr
El vie, 22 ene 2021 a las 14:35, Ken Pettit () escribió:
> Looks like changing nuttx/pdcdi
Looks like changing nuttx/pdcdisp.c:840 from "sp" to just "s" was the
only compile error. Though going through the exercise made me remember
that you also need to select:
Application Configuration --> Graphics Support --> pdcurses --> Input
Devices --> Terminal Input
Otherwise you don't ha
Sure, no problem!
Looking at the code, someone along the way changed the first calling
parameter in that function from "FAR SCREEN *sp" to "FAR SCREEN *s". In
my older copy of the NuttX code, the first parameter is "FAR SCREEN *sp".
Since I know the code pretty well, I can pull down the Apac
Thank you for your response
I searched menuconfig according to your instructions and found it.
Compilation crashed with
nuttx/pdcdisp.c:840:19: error: 'sp' undeclared (first use in this
function); did you mean 's'?
but it's a matter of debugging it. Maybe a lacking option, I'll research it
Than
Grr,
Actually, pdcurses has a mode that will work over serial using
System->Termcurses. This is a terminal based extension to pdcurses that
I added a few years back. It supports VT-100 / ANSI escape codes. I
haven't tested it in the Apache NuttX framework to validate it still
works though.
Hello all
Is there a way to have formatted text output over serial? I want to create
some testing utility that runs from nsh and has some screen organization to
ease use
I tested pdcurses examples but they seem to depend on fb (haven't analyzed
code) and all exited or crashed with "initscr(): Una
I didn't mean ESP8266 as RCP but as a NCP. That's why I talked about WiFi
El vie, 22 ene 2021 a las 5:35, Max Kriegleder ()
escribió:
> Just to clarify, I don't think the ESP8266 would work as it is not a
> IEEE 802.15.4 radio - see also this thread
> https://github.com/openthread/ot-esp32/issues
Just to clarify, I don't think the ESP8266 would work as it is not a
IEEE 802.15.4 radio - see also this thread
https://github.com/openthread/ot-esp32/issues/17
I was also thinking that it should be possible to somehow build on top
of Spinel something like USRSOCK to have a IEEE 802.15.4 radio
Hi Nathan,
Count me in
Regards
Alin
-Original Message-
From: Nathan Hartman
Sent: den 21 januari 2021 19:22
To: dev@nuttx.apache.org
Subject: NuttX: big accomplishment and next steps
Hi folks,
Last year we received 50 ICLAs and 7 SGAs. That is a big accomplishment and
should cover
18 matches
Mail list logo
