On 3/10/2023 4:55 AM, Sebastien Lorquet wrote:
Well, there it is
https://github.com/apache/nuttx-apps/issues/1653
Note that I dont get this behaviour with readline.
We can continue to discuss this in the issue.
Sebastien
There are bandaid fixes going in that try to recover from the primary
they can't hand carry any significant amount of boards. This probably
5-6 freight boxes of boards. I will not be giving or sending anyone
individual boards. Take all or none.
On 3/10/2023 6:54 AM, Alan C. Assis wrote:
Hi Tomek,
That is a good idea too!
Greg, my uncle and my cousin will be
How do you plan to handle incoming vt100 escape sequences. I see you
kludged around one, but there are hundreds. TheY are used in BAS,
pdcurses and other apps extensively.
You are ruining that critical vt100 capability and breaking a lot of
things
Has anyone done any serious CLE editing
I'm guessing it is around 5-6 freight boxes of hardware, perhaps more.
It is not really possible to hand carry any meaningful part of that.
On 3/10/2023 6:54 AM, Alan C. Assis wrote:
Hi Tomek,
That is a good idea too!
Greg, my uncle and my cousin will be in Costa Rica in the following weeks.
If CONFIG_SERIAL_TERMIOS is not selected then non-consoles will do
nothing. In order to restore legacy behavior you would have to do this:
+#ifdef CONFIG_SERIAL_TERMIOS
if (
-#ifdef CONFIG_SERIAL_TERMIOS
dev->tc_iflag & ECHO
-#else - dev->isconsole -
First of all, people never respect pull request formats if this is not
enforced. So enforcement is required as well.
No member of the PMC has authority over any other. An Apache project is
ultra democratic bordering on anarchistic. Each member is basically a
"sovereign citizen."
So we c
Sometime ago I was talking with Brennan about listing the board that I
have here and he surprised me showing this board listing spreadsheet
on google docs. Maybe we can organize a listing to see who has board
X, Y, or Z and to make it possible to test NuttX on all possible
boards.
I have almos
At some point NuttX will grow too large for deep embedded platforms.
My concern exactly. Yes, POSIX compliance is super important because it
provides portability: I regularly write a program and run it on PC and
embedded with almost no changes. This is one of the big selling points of
NuttX f
You are right about posix compliance, this is a valuable goal, but at
the same time it raises the hard remark:
At some point NuttX will grow too large for deep embedded platforms.
That may or may not be true. Certainly NuttX has outgrown most old
architectures with 16-bit address space lim
architecture support, increased code size, forced redesigns, etc. So I
think it is pretty hard to come with a truly convincing argument why we
should support a clearly non-compliant behavior (or lack or behavior).
On 3/8/2023 2:35 PM, Nathan Hartman wrote:
On Wed, Mar 8, 2023 at 3:20 PM Gregory Nutt
POSIX defines the TERMIOS options and, I suspect that those TERMIOS
options are required, not optional (need to check that). If that is
true, then there should be no CONFIG_SERIAL_TERMIOS option; it should
always be enabled.
On 3/8/2023 2:15 PM, Nathan Hartman wrote:
On Wed, Mar 8, 2023 at 2:
I imagine that this is occurring because readline also echos the input:
https://github.com/apache/nuttx-apps/blob/master/system/readline/readline_common.c#L644
The low-level serial driver should not echo just because /isconsole /is
true. Console echo is always handled by the application.
Hi,
I think that some key information is missing like what is the NuttX version
used. Is it mainline or some release or custom.
Best regards,
Petro
It would be helpful to understand where and why the crash occurs too.
You can get that information by analyzing the stack. See
https://cwik
I imagine that this is occurring because readline also echos the input:
https://github.com/apache/nuttx-apps/blob/master/system/readline/readline_common.c#L644
The low-level serial driver should not echo just because /isconsole /is
true. Console echo is always handled by the application. I
I think that there are two different kinds of discussion that we need to
have and these are probably best done in different forums.
/*Black Box*/
By black box I mean the externally observed behavior and characteristics
of the OS: Interfaces, performance, driver facilities, build changes
etc.
On 3/8/2023 9:17 AM, Gregory Nutt wrote:
``There's a saying here that "if it didn't happen on list, it didn't
happen." '' (yes, probably from someone that develops or sales a
mailing list software) Hehehe
No. That is official ASF policy summarized as a m
``There's a saying here that "if it didn't happen on list, it didn't
happen." '' (yes, probably from someone that develops or sales a
mailing list software) Hehehe
No. That is official ASF policy summarized as a motto:
https://community.apache.org/newbiefaq.html#NewbieFAQ-IsthereaCodeofCond
Agreed!
The dev list is the only official way to communicate with all users of
NuttX. I would think ALL important discussions need to occur there.
Github is for developers; dev is for everyone.
On 3/7/2023 11:43 AM, Nathan Hartman wrote:
On Tue, Mar 7, 2023 at 12:27 PM Alan C. Assis wrote:
I imagine that this is occurring because readline also echos the input:
https://github.com/apache/nuttx-apps/blob/master/system/readline/readline_common.c#L644
The low-level serial driver should not echo just because /isconsole /is
true. Console echo is always handled by the application. I wo
It is likely that the issue with the SIGNAL number was introduced by
commit e6227e19433c4999d500437d0a8a5c05f476ceb1
Author: chenrun1
Date: Wed Feb 1 17:17:43 2023 +0800
include/signal.h:Expanding SIGNAL to be consistent with Linux
There is nothing inherently wrong with the
Put a breakpoint on up_assert.
You can also then set the PC and SP to the saved value to see the
context of the assertion.
On 3/6/2023 1:01 PM, Tim Hardisty wrote:
Am I being dumb again? With CONFIG_DEBUG_ASSERTIONS set, the system doesn't
halt with a DEBUGASSERT (in a driver), and ends up i
Interesting:
https://news.slashdot.org/story/23/02/26/1950212/who-writes-linux-and-open-source-software
I've often complained on list about the near disappearance of individual
contributors to the OS. It was created by individual contributors and
most of the early, critical designs came fro
On 3/3/2023 12:56 PM, Gregory Nutt wrote:
On 3/3/2023 12:36 PM, Nathan Hartman wrote:
On Fri, Mar 3, 2023 at 1:07 PM Tim Hardisty wrote:
The bug I thought I had in a driver I'm developing (well, one of
them!) appears to be related to file closing.
- I have a related example-type ap
On 3/3/2023 12:36 PM, Nathan Hartman wrote:
On Fri, Mar 3, 2023 at 1:07 PM Tim Hardisty wrote:
The bug I thought I had in a driver I'm developing (well, one of them!) appears
to be related to file closing.
- I have a related example-type app I'm using to exercise and check the driver. It open
If the cost isn't affordable and the company doesn't want to public all
source code, he can try this approach:
1. Enable userfs to move yaffs from kernel to userspace
2. Build yaffs as wasm module and run it in:
https://github.com/apache/nuttx-apps/tree/master/interpreters/wamr
Th
Why not redirect them to https://nuttx.apache.org and crowdfund the bills ? :-)
Anyone who wants to pay for the domains is welcome to do that. I am
finished paying.
Maybe LittleFS or SmartFS could be extended to handle NAND.
I believe that LittleFS has been used with NAND with a NAND FLASH
translation layer. I am not sure of the state of that work, but I know
that people have tried it. Google "LittleFS on NAND flash" and see the
hits.
If a NAND fla
I have two pre-Apache NuttX domains that are parked and one of them
expires soon. /I will not be renewing them/ so if someone has a
legitimate use for these domains, I will transfer them to you. These
are available:
* /nuttx.com/ will expire April 2, 2023. This would would be a good
plac
> >..l. I could not find where
> > select() or poll() are implemented in the nuttx repository. Is there
> some
> > kind of magic going on with that?
> >
> >
> They hare here:
> https://github.com/apache/nuttx/blob/master/fs/vfs/fs_select.c
> https://github.com/apache/nuttx/blob/master/fs/vfs/fs_p
mber is hardcode to 256:
> https://github.com/apache/nuttx/blob/master/include/sys/select.h#L38-L91
> it's better to define FD_SETSIZE to OPEN_MAX.
>
>
> On Sun, Feb 19, 2023 at 9:53 AM Gregory Nutt wrote:
>
> > That is okay. My answer is possibly wrong anyway. OPEN_MAX
gt;
> best regards,
> KIKUCHI Takeyoshi
>
>
> On 2023/02/19 9:20, Gregory Nutt wrote:
> > The maximum number of file descriptors is a constant value provided by
> > the preprocessor definition OPEN_MAX.
> >
> > On 2/16/2023 5:44 PM, KIKUCHI Takeyoshi wrote:
>
The maximum number of file descriptors is a constant value provided by
the preprocessor definition OPEN_MAX.
On 2/16/2023 5:44 PM, KIKUCHI Takeyoshi wrote:
currently porting the Nim language to NuttX.
(It has been merged into the Nim devel branch)
When using select/epoll, it is necessary to de
Other POSIX-based systems use getrlimit(RLIMIT_NOFILE) to derive
maxDescriptor.
ulimit(4, nn) should also work but is old and obsolete (/like me ;)/ ).
https://man7.org/linux/man-pages/man3/ulimit.3.html
In terms of "POSIX compliant", the same system calls could be used for
a clean impleme
In NuttX, the current number of file descriptions is held in the
fl_rows field of struct filelist. Access to that field is provided
only through the /proc file file system.
Hmm.. the test is
if (row * CONFIG_NFILE_DESCRIPTORS_PER_BLOCK > OPEN_MAX)
{
return -EMFILE;
}
So th
Since the available memory capacity varies from device to device,
Is there any way to find the best value for each build config?
The maximum number of file descriptors for a task is OPEN_MAX which is
determined by CONFIG_LIBC_OPEN_MAX. The actual number may vary from
task to task.
In Lin
On 2/10/2023 3:19 PM, Nathan Hartman wrote:
You know what, I think that might be it. I think I did notice that CLE was
enabled and didn't think about it. Let me look into it...
Even if that is the case, it is still and error if the escape sequence
from the host appears on the NSH console. It
#x27;, (v), ';', (h), 'R'}
/* Response: cursor is at v,h */
I don't know why this is showing up on the NSH console. It should be
invisible. That is a bug.
On 2/10/2023 2:42 PM, Gregory Nutt wrote:
On 2/10/2023 2:24 PM, Nathan Hartman wrote:
I think so. I'm
On 2/10/2023 2:24 PM, Nathan Hartman wrote:
I think so. I'm using Konsole and I'm pretty sure this worked before.
What's surprising is that the board boots fine, finds its IP address
through DHCP, prints the NSH title and prompt... only then does it get
messed up. ...
That is the point in time
Looks like a terminal control sequence. Most of the VT100 commands
begin with every prompt like "nsh> " is followed by a VT100 clear to end of line
command.
Do you have VT100 support enabled in your terminal?
On 2/10/2023 10:54 AM, Nathan Hartman wrote:
I have a board configured with NSH_TEL
On 1/28/2023 7:15 AM, Max Kriegleder wrote:
I am using the tickless OS setting with 1 USEC_PER_TICK and ultimately
I want to control a stepper motor where I need to delay toggling of
pins for very short and accurate amounts of time to achieve a certain
movement profile of the motor - just for i
On 1/27/2023 12:15 PM, Nathan Hartman wrote:
Is there a global structure where you retain state information where it
would be appropriate to save the most refent known state in a volatile
variable?
Good, modular design would discourage the use of global variables in
such a way.
Typically, if you want to pass a small amount of information from an
interrupt handler to a task, you would use a normal IPC like sigqueue()
(https://pubs.opengroup.org/onlinepubs/7908799/xsh/sigqueue.html) which
allows to send a type union sigval to the task.
The task would have to catch the
On 1/26/2023 1:52 PM, Gregory Nutt wrote:
Perhaps you need a driver on Windows? It appears so from a quick
Google where I find articles like:
https://learn.microsoft.com/en-us/windows-hardware/drivers/network/overview-of-remote-ndis--rndis-
https://supportcommunity.zebra.com/s/article
pings without problem. But
this may
be more relevant once I can get the NuttX ping to Windows available.
Linux not even seeing my board with RNDIS, but think I found that
when I last tried this, years ago.
On 25/01/2023, 19:11, "Gregory Nutt" mailto:spudan...@gmail.com>
<mailto:s
The windows firewall usually blocks pings (at least incoming pings).
May sure that you configure the firewall to permit this operation.
On 1/25/2023 1:01 PM, Tim Hardisty wrote:
Hi all,
I'm trying to get RNDIS working. It nearly does - Windows sees the "gadget" and
it has the right IP addres
An embarrassingly large number of typos:
On 1/19/2023 2:19 PM, Gregory Nutt wrote:
Should be pretty easy. I think that you just need to add a HID report
descriptor to the USB keyboard driver.
https://wiki.osdev.org/USB_Human_Interface_Devices#Protocol. Shouldn't
really require any
On 1/19/2023 2:13 PM, Tim Hardisty wrote:
Ultimately I need to make sure it works with most/any USB-C keyboard that
customers might choose to plugin (or, at least, a style/type of keyboard that
is widely available), but it’s not a priority right now.
Should be pretty easy. I think that you j
On 1/19/2023 1:12 PM, Alan C. Assis wrote:
I think the currently NuttX USB Keyboard driver needs to be extended
to support more keyboards. Do do that someone need to inspect the USB
communication and figure out what is going on.
Unless someone has extended the driver, the USB keyboard driver on
> But nuttx doesn't support task sesion/group yet, so the simple
solution is extend kill command instead.
Wouldn't you have to introduce a non-standard interface behavior to
that? I would think you would want to avoid that.
> In fact, I was citing threads, but all children were tasks created
If you kill a process in Linux. All of its child processes should continue
to run as orphan processes. This is the Linux compatible behavior for the
case that Alan presented.
On Sun, Jan 15, 2023 at 10:31 PM Gregory Nutt wrote:
> That wouldn’t be consistent with how Linux works, would
d tasks.
We can extend kill to support -P flag like pkill:
https://linux.die.net/man/1/pkill
-P ppid,...
Only match processes whose parent process ID is listed.
On Mon, Jan 16, 2023 at 10:14 AM Gregory Nutt wrote:
> he
>
> > Ooops. No, you a re asking about tasks, not thre
he
> Ooops. No, you a re asking about tasks, not threads. That is easier.
> The answer is no: One task exiting has not effect at all any other tasks.
>
The question is confusing because it asks about killing other threads (aka
pthreads) when the main (task) exits. But the example shows only t
NuttX
On Sun, Jan 15, 2023 at 7:59 PM Gregory Nutt wrote:
> Xaio Xiang problem will know the current behavior better then me, But I
> think you need: only pthread support. See use of HAVE_GROUP_MEMERS in
> sched/task/exit.c. see include/nuttx/sched.h for definition of
> HAVE_G
Xaio Xiang problem will know the current behavior better then me, But I
think you need: only pthread support. See use of HAVE_GROUP_MEMERS in
sched/task/exit.c. see include/nuttx/sched.h for definition of
HAVE_GROUP_MEMBERS. (seems to depend only on phtreads).
On Sun, Jan 15, 2023 at 5:25 PM A
Look at the hidden file .version. You will need to modify that file as
you see fit. It is not controlled under GIT (but is provided with each
new release package).
On 1/3/2023 2:38 AM, Jernej Turnsek wrote:
Hi All,
when building the latest NuttX OS from git, I am having problems with
.vers
How would you handle the numerous color resolutions (mono, greyscale,
various 8, 16, 24,32 color formats)? How would you handle different color
representations (RGB multiplexed, CMYK multiplexed, planar colors, etc.).
Rotations? Interleaved pixels? If it does not work with all video
hardware, it
POSIX does not support this capability with any uniform, standard
interfaces.
NuttX, however, does permit you to create and use as many separate heaps
as you would like to. See interfaces in include/nuttx/mm/mm.h
For an example, look at the standard malloc/free implementation:
mm/umm_heap/
I think that I can't use a shared memory with my embedded system
(nucleo-144), because I can't see the CONFIG_BUILD_KERNEL=y in my
.config file.
You can use "shared memory" in other build modes too. The APIs to
management shared memory don't exist in other build modes because they
are use
Do you have the compiler option -mlong-calls selected? That is necessary
in order to call from the FLASH address space (at 0xxx ) to the SRAM
address space (2xxx ).
On 12/8/2022 5:55 AM, David Sidrane wrote:
Is the NVIC_VTABLE repointed to the RAM vectors?
The RAM functions are like .bss: There is a storage area of code that
that is copied into RAM only power up. But the symbols associated with
the RAMFUNCs are defined by the linker script to be the ad
+1 Let's do it!
On 11/22/2022 7:30 AM, Nathan Hartman wrote:
After hearing back from Infra about the repository naming convention,
all the recent feedback has been to stay with the default and just
remove "incubator-" from our repo names, giving:
https://github.com/apache/nuttx
https://github.c
On 11/20/2022 1:18 PM, Tim Hardisty wrote:
Might I humbly suggest that "if it isn't broken, don't fix it"?
Just stick with the names already in use (minus the incubator, as will happen anyway).
Just tried searching the Apache website for "RTOS" and NuttX is top of the
list; searching the Apach
On 11/20/2022 6:21 AM, Nathan Hartman wrote:
...
Are we ready to call a [VOTE] thread or does anyone have more
input/arguments/suggestions?
...
Good job, Nathan. I think you have summarized the options and issues well.
Could we simplify the options before a vote be discussing the
possibiliti
On 11/19/2022 9:02 AM, Tomek CEDRO wrote:
On Sat, Nov 19, 2022 at 3:53 PM Thiago Costa de Paiva wrote:
From these, the valid argument is that it would be non-standard (not a top
level name) related to Appache rules, which I think is indeed not acceptable.
It would not imply any source code or
On 11/19/2022 8:31 AM, Tomek CEDRO wrote:
As we have this honor and pleasure to talk directly with the NuttX
RTOS author.. maybe really we should listen to Gregory Nutt himself as
the most experienced person in the room? There was a discussion in
this area and the choice is strongly reasoned not
> I am not attached to the name itself, I was just trying to solve the
problem with special characters. Would the following work?
>
> nuttx/core
> nuttx/apps
Again, We need to verify, but I do not think that the Apache github
repository
supports directories like nuttx/ with repositories under the
On 11/19/2022 8:12 AM, Gregory Nutt wrote:
We need to verify, but I do not think that the Apache github
repository supports directories
Technically, NuttX is NOT a kernel in most build modes. A kernel is a
very specific architectural implementation involving protected
resources: https
y tentative idea!
BR,
---Original---
From: "Gregory Nutt"
it. I
was VERY strongly opposed to the idea then and I still am.
- apps is NOT part of NuttX. It is an achitecturally unrelated,
mish mash
or useful applications for NuttX, but it is not NuttX.
- I consists of mostly 3rd
> Isn't it possible to merge the nuttx and apps into only one
repository？e.g:
> |-rtos
> |-apps
We discussed this option a couple of years ago and decided against it. I
was VERY strongly opposed to the idea then and I still am.
- apps is NOT part of NuttX. It is an achitecturally unrelated, mi
The advantage of nuttx?kernel et nuttx?apps that both repository are together
in listing or folders. You can replace ‘?’ by as you want.
I don't see any other examples of folders. We would have to ask, I suppose.
PS: Pierre-Noel: Good to see your name in print. It has been awhile.
Isn’t nuttx supposed to be the Apache RTOS?
rtos/nuttx
rtos/apps
?
The are other Apache RTOSs, or at OSs. There is, at least,
https://mynewt.apache.org/
MyNewt uses several repositories, one for each major subsystem. Their
naming uses hyphens: mynewt-core, mynewt-newt, mynewt-nimble,
why can’t we just have :
nuttx, apps
as it has been for a long time (before Apache) …
Ultimately, the repository names would appear here:
https://github.com/orgs/apache/repositories
nuttx/ would probably be fine, but apps/ probably would not be
appropriate at that level.
I see all the other two-word Apache repositories use hyphens not underscores,
and on GitHub they are URLs which as has been pointed out should ideally be
hyphenated?
To me the underscore looks wrong...but, in the grand scheme of things, it's
just a name and, like Sebastien, I will not lose
But NuttX has more features than traditional RTOS(e.g. FreeRTOS). Actually,
Xiaomi uses it in the IoT space which has less real time requirements.
Other similar OS(e.g. Zephyr) doesn't append rtos suffix.
So, I prefer keep nuttx and nuttx-apps.
I just endorsed nuttx_rtos and nuttx_apps, but X
+1 for nuttx_rtos and nuttx_apps
On 11/18/2022 8:39 AM, Tomek CEDRO wrote:
nuttx_rtos and nuttx_apps :-)
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
On Sat, Nov 12, 2022 at 9:28 AM Gregory Nutt wrote:
> There was also IAR/uVision IDE support in the repository for STM32. All
> of the IAR/uVision helper tools are still present (I think), but the IAR
> board support was removed
> https://bitbucket.org/patacongo/o
On 11/12/2022 9:05 AM, Brennan Ashton wrote:
I can probably help revive my past effort to run some native builds in CI
to at least prevent it from getting fully broken. One of the blockers last
time, was just how slow it was and the limited number of Windows workers.
Did we ever really have a n
+1: Apache NuttX is ready to graduate to TLP
Gregory Nutt
On 10/21/2022 6:46 AM, Nathan Hartman wrote:
Dear Apache NuttX Community,
Following the [DISCUSS] thread which has gone 72 hours without any
further issues raised [1]:
This is a call to VOTE on Graduation of Apache NuttX from the
>
> But the simplest thing that comes to mind is just to kill the NSH task,
> run modbus, and restart NSH when you are finished with modbus.
>
Maybe even simpler: Run the modbus task at a higher priority than NSH.
Then all of the serial into should go to Modbus and not to NSH
I suppose there are lots of ways to do that by closing and redirecting
NSH's standard I/O.
But the simplest thing that comes to mind is just to kill the NSH task, run
modbus, and restart NSH when you are finished with modbus.
On Thu, Oct 20, 2022 at 6:05 PM Daniel Pereira Carvalho
wrote:
> Hi g
> If external is historic, what is the preferred way to include a custom
out-of-tree (i.e. non-public) App in a build, in a way that won't get
trashed if a distclean or Nuttx upgrade merge is done?
Distclean will not affect any untracked files/directories/symbolic links.
If an untracked director
Did you check the "external" directory or are you looking for something
else?
Basically the external directory allows you to symlink an out of tree
repository (or repositories) that should contain, at least, the minimal
build glues (Makefile and Make.defs). The build system should pick up the
On 10/11/2022 3:14 AM, Tomek CEDRO wrote:
On Tue, Oct 11, 2022 at 12:49 AM Gregory Nutt wrote:
Several years ago Mike Smith did a 68000 port of NuttX. I’m not sure if he
completed it or not, but the port never came upstream. Mike is no longer
involved with NuttX and probably not contactable
Several years ago Mike Smith did a 68000 port of NuttX. I’m not sure if he
completed it or not, but the port never came upstream. Mike is no longer
involved with NuttX and probably not contactable. If anyone out there in
PX4 land knows where Mike kept his code, that might be helpful.
A port t
I am not a attorney, but I seem to recall that a legal reference
reference to a copyright or a trademark require the © and small tm
superscript .
This -- plus the names that Brennan mentions -- are some of the reasons
why unicode really needs to be permitted within comments. None of these
sh
nxstyle should only complain if this is a source or build file, right?
And only if if the unicode is outside of a comment. Unicode characters
are useful in .txtf, .md, a probably other file typles and also in code
comments.
There are flags in nxstyle that tells if you the type of file (by
e
com/apache/incubator-nuttx/blob/master/libs/libnx/nxmu/nxmu_sendserver.c>
function
using the queues, from there it shouldn't be difficult to do a networked
implementation.
On Tue, Oct 4, 2022 at 12:47 PM Gregory Nutt wrote:
Yes, NX is a server within the OS. The server side is in direct
other frameworks like ImGUI too since I have some
experience with it
On Tue, Oct 4, 2022 at 12:13 PM Gregory Nutt wrote:
NxWidgets is a drawing tool in C++ that supports graphics objects. It
integrates naturally with NX.
NX is the graphics server that supports multi-threaded 3D windowed
displays (
NxWidgets is a drawing tool in C++ that supports graphics objects. It
integrates naturally with NX.
NX is the graphics server that supports multi-threaded 3D windowed
displays (3D in the since that X/Y windows exists in a Z plane). NX is
the embedded, moral equivalent of X in Linux. It is N
More screenshots here:
https://cwiki.apache.org/confluence/display/NUTTX/NuttX+Presentations
https://cwiki.apache.org/confluence/display/NUTTX/Graphics
NxWidgets is a port of Whoopsi which was a Nintendo DS GUI framework. I
don't think that the original is still supported. It contains many,
I wonder if this is some interaction between the USB console and
NxTerm? Both are rather special cases. Have you tried NxTerm with a
serial console. There are quite a few examples that worked in the past:
$ find boards -name defconfig | xargs grep CONFIG_NXTERM=y
boards/arm/lpc17xx_40xx/open
This does not seem like a technical issue but rather awkward
usage/naming that is prone to misuse.
Yes, free() should be called to release the memory allocated by strdup.
But applications cannot use the kernel heap and, for reasons of
protection, the kernel should not store anything in the use
> The only clue I have is that g_inode_sem.holder is set to -1, which
intuitively seems wrong to me, but this is way beyond me at this time of my
NuttX journey!
The value -1 is not an error. It means that one thread is waiting to
take a count from the semaphore. The value of the semaphore was 0
I did the D3 and D4 ports years ago and I am not aware of any other use of
those boards. DMA was partially functional then, but was not well tested
and was still buggy. There were problems documented in
https://github.com/apache/incubator-nuttx/blob/master/boards/arm/sama5/sama5d4-ek/README.txt
Might be a corrupted address; 0x7278 is ASCII "rx". Could be stack
overflow corrupting the address.
On Tue, Sep 6, 2022 at 5:37 PM Nathan Hartman
wrote:
> On Tue, Sep 6, 2022 at 6:35 PM Victor Benso wrote:
> > Besides all the SMP related issues that most likely I failed to figure
> out,
> > I
No, that logic is not limiting the number of socket families, it is simply
picking a valid socket family to access socket IOCTLs. See line 78 in that
same file:
/* The address family that we used to create the socket really does not
* matter. It should, however, be valid in the current configurat
> There used to be one defining inline to be nothing for ZDS-II . It would
> > only be necessary to restore it for ZDS-II. This does not fix the
> function
> > duplication of static inline functions in header files, however.
>
> Is the duplication really a problem, though?
>
> After all, the whole
Since SDCC supports Zilog chipset very well, why not switch from ZDS-II to
> SDCC?
>
SDCC supports z80 and z180 but none of the other ZiLOG chipsets. ez80 has
an unverified GCC port but ZDS-II is the only compiler option for the
remaining parts.
See http://sdcc.sourceforge.net/
> > compiler.h
Yes. 2.95
> > Classic Z80 is probably not viable due to the 64Kb address limitation but
> > is still relevant for Z80 derived parts with MMUs such as Z180 and the ZX
> > Spectrum Next or with wider address buses such as the eZ80. z8 was never
> > well tested. But eZ80 and ZNEO have been importa
> Just FYI, based on what Byron points out with regard to the Zilog
families needing C89 (and possibly other archs that weren't mentioned), I
would probably vote -1 unless...
There have been several other cases over the years where there were ports
to classic architectures no longer supported by c
301 - 400 of 1020 matches
Mail list logo
