Re: Alternative Emulador to test NuttX

On Sun, May 10, 2020 at 7:06 PM Alan Carvalho de Assis wrote: > > Renode is a very interesting alternative to QEMU: > > https://interrupt.memfault.com/blog/intro-to-renode > > According with project: > > "Why not QEMU? - Readers who have experience with emulation will point > out that QEMU has exi

Re: Alternative Emulador to test NuttX

On 5/10/20, Nathan Hartman wrote: > > This is interesting! > > Maybe it could be possible to have some cooperation between the two > projects (NuttX and Renode) to benefit both somehow? > I think it could be a good idea! The default STM32F4Discovery example is with Contiki. BR, Alan

Re: Alternative Emulador to test NuttX

This is what I use to test my LiteX FPGA based RISC-V development. It works fairly well if you can represent enough of the IP which is why for the opensource RISC-V side of things it works quite well, for ARM I have seen mixed results although as you said there is a lot more emulated. They do have

Build failed in Jenkins: NuttX-Nightly-Build #122

See Changes: -- Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H27 (ubuntu) in workspace

enter/leave_critical_section() calls in the user space library

Hi all, I found a few enter/leave_critical_section() calls in libs/ directory. It is ok for flat build, but unavailable in the user library for protected/kernel build. Is it correct ? For example, libs/libc/syslog/lib_setlogmask.c calls them. In fact, using setlogmask() in protected build raises

RE: enter/leave_critical_section() calls in the user space library

I think enter/leave_critical_section() call should be replaced with semaphore/mutex/spinlock/atomic_ in most case, not only more standard but also more fast in SMP. Especially, multiple core MCU/DSP design extend from desktop to mobile and embedded now. -Original Message- From: Nakamura, Y

RE: enter/leave_critical_section() calls in the user space library

Hi all, I have tried to simply replace enter/leave_critical_section() into pthread_mutex if not flat build, and issued the PR. It seems works well in uniprocessor, but there are a few remaining enter/leave_critical_section() calls if SMP is used. Thanks, Yuuichi Nakamura > -Original Messag

Re: enter/leave_critical_section() calls in the user space library

I think enter/leave_critical_section() call should be replaced with semaphore/mutex/spinlock/atomic_ in most case, not only more standard but also more fast in SMP. Especially, multiple core MCU/DSP design extend from desktop to mobile and embedded now. I would consider just removing the ente

Re: enter/leave_critical_section() calls in the user space library

One way to make this work correctly would be to remove the logmask as a global variable and, instead, put the logic mask in the group structure or in the TCB structure.  That would make logmask thread safe (in the second case).  This would be the preferred solution. This solution would work.

Re: enter/leave_critical_section() calls in the user space library

One way to make this work correctly would be to remove the logmask as a global variable and, instead, put the logic mask in the group structure or in the TCB structure. That would make logmask thread safe (in the second case).  This would be the preferred solution. This solution would work

RE: enter/leave_critical_section() calls in the user space library

>From this link: https://linux.die.net/man/3/setlogmask logmask has per task scope not per thread scope. So we still suffer the concurrent issue if we change to group-specific logmask. -Original Message- From: Gregory Nutt Sent: Monday, May 11, 2020 10:59 AM To: dev@nuttx.apache.org Sub

Re: enter/leave_critical_section() calls in the user space library

On Sun, May 10, 2020 at 11:35 PM Xiang Xiao wrote: > From this link: > https://linux.die.net/man/3/setlogmask > logmask has per task scope not per thread scope. So we still suffer the > concurrent issue if we change to group-specific logmask. So if I understand correctly, that means that moving

Re: enter/leave_critical_section() calls in the user space library

From this link: https://linux.die.net/man/3/setlogmask logmask has per task scope not per thread scope. So we still suffer the concurrent issue if we change to group-specific logmask. The same text appears in the more authoritative Opengroup.org web page: https://pubs.opengroup.org/onlinepu

Build failed in Jenkins: NuttX-Nightly-Build #123

See Changes: -- Started by timer Started by user btashton Rebuilds build #122 Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H27 (ubuntu) in

Build failed in Jenkins: NuttX-Nightly-Build #124

See Changes: -- Started by user btashton Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H27 (ubuntu) in workspace

RE: enter/leave_critical_section() calls in the user space library

But we need to consider syslog call from interrupt context too. So I think the simple modification is: 1.Drop the critical section 2.Keep the global variable In FLAT/PROTECTED build, all user space applications have to share the same variable. -Original Message- From: Gregory Nutt Sent