Looking for NuttX dev opportunities

to me in DM if you know such companies. Best regards, Petro Karashchenko

FS automount: callback when FS is mounted

Hello, I have a question regarding FS automount functionality. Is there a way to get a callback when file system is mounted and ready to be accessed? Or the only way is to implement a polling loop like: while ( access( "/mnt/sdcard0", F_OK ) != 0 ) {   sleep(1); } Best regards, Petro

Re: FS automount: callback when FS is mounted

Hi Greg, Yeah, I used a wrong term when was asking about "callback". Actually I need asynchronous notification, so I can pend a task on some primitive like a semaphore. Thank you for replying with an example. I will examine it. Best regards, Petro On Wed, Dec 1, 2021, 8:43 PM Gregory Nutt wro

Re: FS automount: callback when FS is mounted

Yes. Thank you for pointing me out this. I was looking into SIGEV_THREAD with a callback posting a semaphore, but sigtimedwait() seems to be exactly what I'm looking for. Best regards, Petro On Thu, Dec 2, 2021, 12:20 AM Gregory Nutt wrote: > > Yeah, I used a wrong term when was asking about "

Re: FS automount: callback when FS is mounted

But ai think that the approach with a signal will require turning automount into a complete file based driver with open/close/ioctl support. What do you think? Best regards, Petro On Thu, Dec 2, 2021, 12:37 AM Petro Karashchenko < petro.karashche...@gmail.com> wrote: > Yes. Than

blockmtd device on top of /dev/null

Hello, Is it possible to create a "fake" MTD device on top /dev/null? In theory I think that should be possible. Does anyone see any drawbacks with such approach? Best regards, Petro

Re: blockmtd device on top of /dev/null

oblem, you can try RAMMTD: https://github.com/apache/incubator-nuttx/blob/master/drivers/mtd/rammtd.c On Thu, Dec 2, 2021 at 7:06 AM Petro Karashchenko < petro.karashche...@gmail.com> wrote: Hello, Is it possible to create a "fake" MTD device on top /dev/null? In theory I

Re: Change default behavior of semaphores?

Hi team, Sorry I probably missed some part of discussion. So it was decided to keep priority inheritance ON for counting semaphores by default if the feature is enabled? And we are modifying all the POSIX by adding explicit setting to SEM_PRIO_NONE? I truly believe that priority inheritance on co

Re: Change default behavior of semaphores?

default value of the attribute shall be PTHREAD_PRIO_NONE. So it is reasonable to change default behavior for semaphores in order to restore POSIX compliance for pthread mutexes as well. Best regards, Petro On Wed, Jan 5, 2022, 8:17 PM Petro Karashchenko < petro.karashche...@gmail.com> wrote:

Re: Change default behavior of semaphores?

Hi, Yes, POSIX does not support priority inheritance on counting semaphores, but priority inheritance things seems to be already broken for a long time. I mean the changes like https://github.com/apache/incubator-nuttx/pull/5170 just highlight the top of an iceberg. For the POSIX compliance of pt

pthread mutex default protocol POSIX compliance

Hello team, I've started initial activity on restoring POSIX compliance for pthread mutex default protocol in https://github.com/apache/incubator-nuttx/pull/5180 Will appreciate if you can give me feedback with the estimated impact of this change so I can work on modifying code based on pthread m

Move to C99 for common code

Hello team, Recently I mr. @Xiang Xiao had a discussion in one of the PR's related to C89 code compliance. Particularly related to initializing a structure by field names (designated initializers). Mr. @Xiang Xiao pointed out that "for the common code it is better to avoid C99 only features". I

Re: Move to C99 for common code

2022 at 6:29 AM Petro Karashchenko < > petro.karashche...@gmail.com> wrote: > >> Hello team, >> >> Recently I mr. @Xiang Xiao had a discussion >> in one of the PR's related to C89 code compliance. Particularly related to >> initializing a structure by f

Re: Move to C99 for common code

In addition I just checked latest GCC with HC12 support is 3.0.4 version. It have C99 integrated. Will check with AVR32, but will probably need some help with others. Best regards, Petro On Sat, Jan 8, 2022, 7:15 AM Petro Karashchenko < petro.karashche...@gmail.com> wrote: > Hi, >

Re: Move to C99 for common code

imply undefined. > > I have built ez80 using the ZiLOG tools fairly recently, but none of the > others. It worked fine. > > On Fri, Jan 7, 2022 at 11:15 PM Petro Karashchenko < > petro.karashche...@gmail.com> wrote: > > > Hi, > > > > What about inline fu

Re: Move to C99 for common code

There used to be a > > >> small > > >> but important group of retro computer folk using NuttX; this > eliminates > > >> support for them. There is language in the INVIOLABLES that is there > > >> specifically to protect them from actions like

Re: Move to C99 for common code

In general yes, but my main point was that I saw designated initializer list heavily used in drivers code that is intended to be common. Also there are some C99 features like inline functions in common code. So we need to make an effort and clean-up common code to get back C89 compatibility. Best

Re: Move to C99 for common code

Following the discussion related to the "inline" keyword usage in common code. I have done draft changes in https://github.com/apache/incubator-nuttx/pull/5201 with an approach that possibly can be used to get rid of "inline" in common code. But I'm not even sure if this is needed to anyone, since

Qencoder position value range

Hi, I've been working to add SAMv7 Qencoder interface and see that Qencoder driver expects QEIOC_POSITION to be int32_t value. The issue is that SAMv7 has 16 bit timer counter interface and the SW extension to 32 bits (by adding adding or subtracting UINT16_MAX+1 when counter matches 0x) does

Re: Qencoder position value range

I will appreciate if you can share your code so I can take it as a reference. Best regards, Petro On Thu, Jan 13, 2022, 4:26 PM Nathan Hartman wrote: > On Thu, Jan 13, 2022 at 8:19 AM Petro Karashchenko < > petro.karashche...@gmail.com> wrote: > > > Hi, > > > >

Re: Qencoder position value range

Ok. So I will leave 0 ... UINT16_MAX to be returned by the driver and will handle rollover on the application side. Thanks! Petro On Thu, Jan 13, 2022, 5:15 PM Nathan Hartman wrote: > On Thu, Jan 13, 2022 at 9:50 AM Petro Karashchenko > wrote: > > > > Thank you. I would ap

Redirect syslog to file

Hi, Is it possible to redirect syslog into a file (maybe even have it both on UART and a file)? Also a question is there utility like logrotate or any other so that maximum size for logs can be set and possibly compression when one log file is closed and new one is open? Best regards, Petro

Re: rp2040: composite-cdcecm: hardfault due to alignment issue in driver/usbdev/usbdev.c

Hi, I examined the proposed fix and the root cause of the issue. I found out that all network related types definitions are missing the "packed" attribute hence the crash on certain platforms may happen. Actually we should have begin_packed_struct struct eth_hdr_s { uint8_t dest[6]; /* Ethernet

Re: FS automount: callback when FS is mounted

Hello Gregory, I made some progress with this activity. Will appreciate your review https://github.com/apache/incubator-nuttx/pull/5345 Best regards, Petro чт, 2 груд. 2021 р. о 01:42 Gregory Nutt пише: > > > But ai think that the approach with a signal will require turning > automount > > into

is CODE keyword still used?

Hello team, Recently I noticed that some structures in common code use CODE keyword for pointers to functions and some do not, so I have the question: is CODE keyword still supported? Here are few examples: struct automount_lower_s { ... CODE int (*attach)(FAR const struct automount_lower_s *low

Re: is CODE keyword still used?

is: Should we add CODE to function pointers in common code? Best regards, Petro ср, 26 січ. 2022 р. о 15:21 Alan Carvalho de Assis пише: > > Hi Petro, > > It is used by Z80, Z180 and Z16/ZNEO, see include/nuttx/compiler.h for > reference. > > BR, > > Alan > > On 1

Re: is CODE keyword still used?

ok in the FS code. > > BR, > > Alan > > On 1/26/22, Petro Karashchenko wrote: > > Hello Alan, > > > > Yeah, I see that. But since CODE is missing for the most of the > > pointers to functions in common code I just wonder how that platform > > works.

Re: is CODE keyword still used?

emove it. There is no benefit to remonving it and > there is most certainly a downside. > > On Wed, Jan 26, 2022 at 7:06 AM Petro Karashchenko < > petro.karashche...@gmail.com> wrote: > > > Hello team, > > > > Recently I noticed that some structures in common code u

register_driver with 0000 mode

Hello team, Recently I have noticed that there are many places in code where register_driver() is called with non-zero mode with file operation structures that have neither read nor write APIs implemented. For example "ret = register_driver(path, &opamp_fops, 0444, dev);" while opamp_fops has only

Re: register_driver with 0000 mode

ster/include/uapi/asm-generic/ioctl.h#L85-L91 > and let's VFS layer do the check for each driver. > > On Fri, Jan 28, 2022 at 5:14 PM Petro Karashchenko < > petro.karashche...@gmail.com> wrote: > > > Hello team, > > > > Recently I have noticed that there a

Re: register_driver with 0000 mode

access mode, but I > passed 0 to the access mode flag of open() and it was accepted, but > when the file has permission it returns -EPERM: "Failed to open > file: error -1" > > BR, > > Alan > > On 1/28/22, Petro Karashchenko wrote: > > Hello, > > &

Re: [DISCUSS] Default state of NDEBUG

I'm not sure that I'm fully following the discussion (I will read the PR comments to get the full context), but my vote is for: 1. There should be a separate way to build kernel and app with assert() enabled. 2. The assert() should be disabled by default. So the default build is a release build. 3.

Re: [DISCUSS] Default state of NDEBUG

d requires it to expand to a void expression (a minor conformance > issue, most real programs won't notice the difference). > > -Juha > > From: Petro Karashchenko > Sent: Wednesday, February 16, 2022 10:31 PM > To: dev@nuttx.apache.org > Su

Re: [DISCUSS]: Self merge and Single company/organization merge gating

Hello, Regarding PRs megre by the author: I think that if the changes are relatively simple (again that is very subjective, but I hope that people with merge rights have more or less the same common sense of it) and there is an approval from outside of the company/organization then the author can

Re: [DISCUSS]: Self merge and Single company/organization merge gating

tside of the company/organization then the author > > can do the merge. For complex changes the person outside the > > organization should perform the merge even if there are more than 1 > > approval from inside the company/organization. > > I agree. > > David > >

Re: [DISCUSS]: Self merge and Single company/organization merge gating

in > > > On Fri, Feb 18, 2022 at 8:52 AM Petro Karashchenko < > petro.karashche...@gmail.com> wrote: > > > Hi, > > > > I agree that auto-merge should not be used. > > > > But I disagree that "as it is now since almost all patches follow the &

echo "X" > /dev/gpio lead to 3 writes instead of 1

Hello team, Recently I've been working with a dev gpio interface (IO expander case) and noticed that in NSH use case use echo to change the state of GPIO output pin the actual GPIO write is executed 3 times. The first one when the data are actually written, then when flush happens and the third ti

[Russia attacked Ukraine]

Hi, I know that this channel is not intended for things that I will write, but I still will send this E-mail. For people that do not know: yesterday at 5AM Russia started massive invasion and attacked Ukraine. The fightings are all over the central, eastern, north and south. The bombs are explodi

NuttX and C++ libraries: boost / ASIO / std::chrono

Hello team, I would like to ask who has used C++ libraries with NuttX. For example if I have a C++ application that is based on boost and std::chrono then what should be a good way of starting it with NuttX? Best regards, Petro

Re: Error when building custom board

Hi, Do you want to use board common code? There where some code tree restructurings to eliminate code duplication. There is an option to enable/disable common code in menu config. Please try to use it and feedback if it helps you. Best regards, Petro On Thu, Mar 3, 2022, 12:06 AM Daniel Pereira

Re: Error when building custom board

р. о 07:40 Jukka Laitinen пише: > > HI, > > Not sure what is the correct way to fix this, but I reverted: > > " > > commit f77956a227f1db6ecb44eda3814e7b02aa2187a6 > Author: Petro Karashchenko > Date: Wed Jan 19 11:16:11 2022 +0200 > > tools: add option

Re: Error when building custom board

rms/nuttx/Nuttx/nuttx. > > > > I didn't yet start looking into it in detail, what goes wrong, just > > bisected the nuttx and reverted the commit which broke it for me. I need > > to look back later to see how to change the off-tree board config to get > > it back onlin

Re: Error when building custom board

aching that Make rule, BOARD_COMMON_DIR will have > a value, whether there is a common directory or not. > > On Thu, Mar 3, 2022 at 11:09 AM Petro Karashchenko > wrote: > > > > Hello Abdelatif, > > > > "Which is forcing a common di

Re: Error when building custom board

f "BOARD_COMMON_DIR" exists or not. > > > > Unix.mk includes $(TOPDIR)/Make.defs which in its turn includes > > tools/Config.mk so reaching that Make rule, BOARD_COMMON_DIR will have > > a value, whether there is a common directory or not. > > > > On Thu, Mar 3

Re: Error when building custom board

't yet start looking into it in detail, what goes wrong, just > bisected the nuttx and reverted the commit which broke it for me. I need > to look back later to see how to change the off-tree board config to get > it back online. > > Just noticed that the error is somewhat similar, a

Re: Error when building custom board

mon folder. It could be that they have an old board > where the common folder structure didn't exist at the time and they > don't want to change their structure. > > > Or maybe I'm missing the exact use case. > > Daniel's use case is the following: Use a custo

Re: Error when building custom board

ser. As it was before. > If we want to keep the option to share it for both in-tree and > out-of-tree boards, then there has to be an _option_. Not > unconditionally forced. > One solution is to introduce a new CONFIG_ that defaults to false. > > > > > On Thu, Mar 3, 2022 at 1

Re: Error when building custom board

ate options but > used consistently across all boards and defaulting all to 'n'. > If this keeps the original behavior and as a bonus also removes those > weird steps where we have to rename makefiles, then this is the best > of both worlds. > > On Thu, Mar 3, 2022 at 2:01

Re: Error when building custom board

t; > > > > > > > One version, where it fails is available publicly in > > > > > > > > https://github.com/tiiuae/px4-firmware/ (nuttx is included as a > > > > submodule) > > > > > > > > Building "make ssrc_icic

Re: SPI problem

Hello Roberto, It would be good if you can dump assembly that is generated. What I see is that "int spi_register(FAR struct spi_dev_s *spi, int bus)", so I'm assuming that R0 should be "spi" and R1 should be "bus", but in your dump "R0: 0001 R1: 2004e840" those seems to be inverted (0001 s

Re: SPI problem

etro нд, 6 бер. 2022 р. о 13:40 Petro Karashchenko пише: > Hello Roberto, > > It would be good if you can dump assembly that is generated. What I see is > that "int spi_register(FAR struct spi_dev_s *spi, int bus)", so I'm > assuming that R0 should be "s

Re: SPI problem

s Petro > > I've modified the nucleo-144/src/stm32_spi.c file by simply adding: > > struct spi_dev_s *g_spiX; > > and by adding > > spi_register(g_spiX, X); > > in the > > where X is the spi device number (in my example spi2) > > in the shell the /dev/sp

Re: SPI problem

vtype=0x23 and spitool->csn=0 should give 0x23 as return > value and not 0x17... > > Best regards > > Roberto > > > On 3/7/22 16:22, Petro Karashchenko wrote: > > Hello Roberto, > > I think that the problem is in the line's: "stm32_gpiowrite(g

Re: Error when building custom board

roduce the issue :) > > > > > > > > > Jukka Laitinen kirjoitti torstai 3. maaliskuuta 2022: > > > > Hi, sorry about that; you can just remove that submodule, it is not > > > > needed to re-produce the issue. > > > > > > >

Re: Error when building custom board

st leave the > CONFIG_BOARD_CUSTOM_ARCH_BOARD_COMMON undefined. > > Thanks, > > Jukka > > On 9.3.2022 19.22, Petro Karashchenko wrote: > > Hello Jukka, > > > > I was able to localize the root cause of the issue. I've created > > https://github.com/apache/incubator-nut

Re: Error when building custom board

such file or directory > make[3]: *** No rule to make target 'board/Make.defs'. Stop. > > Should I add some new CONFIGs? Sorry but I don't have much time today to > debug this further > > -Jukka > > > On 10.3.2022 21.00, Petro Karashchenko wrote: > >

Re: Error when building custom board

leads to a situation that leads to a need to make a distclean each time the ARCH_BOARD_COMMON is changed. Best regards, Petro Best regards, Petro пт, 11 бер. 2022 р. о 11:33 Petro Karashchenko пише: > > Hello Jukka, > > I'm still in the middle of building a docker image

Re: Error when building custom board

introduce without modification of PX4 > build system is https://github.com/apache/incubator-nuttx/pull/5715 > > I do not like it a bit because this leads to a situation that leads to > a need to make a distclean each time the ARCH_BOARD_COMMON is changed. > > Best regards, > Pet

Re: Error when building custom board

; > > > Finally I was able to reproduce the situation that you are talking > > about. The case is that in PX4 environment the path to the board files > > is hardcoded to $(BOARD_DIR)/src unconditionally, but actually it > > depends on BOARD_COMMON_DIR value: > > ifne

Re: Error when building custom board

le or directory > make[3]: *** No rule to make target 'board/Make.defs'. Stop. > > Should I add some new CONFIGs? Sorry but I don't have much time today to > debug this further > > -Jukka > > > On 10.3.2022 21.00, Petro Karashchenko wrote: > > Hello

Re: NuttX github code review practices

Hi, As I'm the person who usually generates a lot of "style related" comments I want to reply as well. Since GitHub does not have a "severity" option for the option it is not too convenient to distinguish between "optional" with "must have" comments. So usually I use the "Comment" button instead

What is the purpose of FTPD_ACCOUNTFLAG_SYSTEM?

Hi team, Recently I've been working with FTP server example and explored the code for FTPD as well. I have a question related to account flags. In "apps/examples/ftpd/ftpd_main.c" I see the line: { FTPD_ACCOUNTFLAG_SYSTEM, "root", "abc123", NULL }, and message: (account->flags & FTPD_ACCO

mktime() does not "normalize" struct tm argument

Hello team, Recently I've been reviewing "strftime()" implementation from "libs/libc/time/lib_strftime.c" and found interesting lines: /* %s: The number of seconds since the Epoch, that is, * since 1970-01-01 00:00:00 UTC. * Hmmm... mktime argume is not 'const'.

FAR usage education

Hi, I want to improve my knowledge about FAR usage in NuttX code. I've already read some initial information related to "Far memory" and "3-byte pointers to access extended memory spaces", but still lacking a practical experience with a real compiler and device use case. My main question is about

Re: FAR usage education

Thank you Gregory for your reply. I will definitely examine all the links that you provided. I'm familiar with ARM address access limitations and also with more exotic ARC architecture where I first met .sdata and .sbss sections usage for data that are located near GP. But as you already pointed ou

Re: register_driver with 0000 mode

oper permissions and open files with correct flags. So if the driver does not have neither read nor write handlers the "" mode should be used and "0" should be used during opening of a file. Or we need to remove "inode_checkflags()". Best regards, Petro пт, 28 січ. 202

Re: register_driver with 0000 mode

" > > The man pages uses "MUST", the OpenGroups uses "SHALL", but according > to RFC2119 they are equivalents: > > https://www.ietf.org/rfc/rfc2119.txt > > BR, > > Alan > > On 4/1/22, Petro Karashchenko wrote: > > Hi, >

Re: register_driver with 0000 mode

ag check. > > BR, > > Alan > > On 4/1/22, Xiang Xiao wrote: > > It's better to check ioctl callback too since ioctl means the driver has > > the compatibility of read(i)and write(o). > > > > On Fri, Apr 1, 2022 at 9:15 PM Petro Karashchenko < > >

Re: register_driver with 0000 mode

Ok. I will update the code example and come back later with some answers. On Fri, Apr 1, 2022, 5:32 PM Xiang Xiao wrote: > We need to try some ioctl with read/write some driver(e.g. serial driver > baud) internal state. > > > On Fri, Apr 1, 2022 at 10:05 PM Pet

Re: register_driver with 0000 mode

gt; > So, in fact on Linux/Mac when we are opening a file with oflag 0 we > are opening it for reading only. > > On NuttX the value 0 is not defined, O_RDONLY is 1: > > #define O_RDONLY(1 << 0) > > BR, > > Alan > > On 4/1/22, Petro Karashchenko wrote

Re: register_driver with 0000 mode

ks because of it: > > > > > > #define O_RDONLY > > > > > > So, in fact on Linux/Mac when we are opening a file with oflag 0 we > > > are opening it for reading only. > > > > > > On NuttX the value 0 is not defi

Re: register_driver with 0000 mode

Hello Gregory, Do you recommend not to allow registration of a driver that does not have read method and make a requirement for the driver to provide at least dummy read? Best regards, Petro On Fri, Apr 1, 2022, 9:48 PM Gregory Nutt wrote: > > > One option, conforming standard, would be that y

Re: register_driver with 0000 mode

inter is initialized. Then you don't need to provide the dummy > implementation in every driver. > > Petro Karashchenko kirjoitti lauantai 2. huhtikuuta 2022: > > Hello Gregory, > > > > Do you recommend not to allow registration of a driver that does not h

Re: register_driver with 0000 mode

Hi, Here are a few examples of "broken" drivers: - opamp_fops - lcddev_fops - g_pca9635pw_fileops - g_foc_fops - notectl_fops - powerled_fops - g_rptun_devops - g_video_fops The list is not complete. But since the "register_driver()" does not return an error if both fops read and write po

Re: register_driver with 0000 mode

For what I see in Linux headers #define O_ACCMODE 0003 #define O_RDONLY #define O_WRONLY 0001 #define O_RDWR 0002 So 3 seems to be a reserved value and because O_RDONLY in Linux is defined to 0 the 3 value from Linux is similar to 0 value in NuttX. Regarding "Yes, for examp

Websockets with NuttX

Hello team, Has anybody used websockets with NuttX? If yes, then which libraries have you used? Maybe there are some examples? Thank you in advance for replies Best regards, Petro

[LEGAL] Update of include/nuttx/wireless/ieee80211/ieee80211.h

Hello, We are having a PR https://github.com/apache/incubator-nuttx/pull/5755 that is intended to update "include/nuttx/wireless/ieee80211/ieee80211.h" header in NuttX code tree. the changes are the sync with https://github.com/torvalds/linux/blob/master/include/linux/ieee80211.h verison that is

Re: Websockets with NuttX

> 发件人 > > > style="text-decoration:none;color:#0886e8;" href="mailto: > petro.karashche...@gmail.com">Petro > Karashchenko<petro.karashche...@gmail.com> >

Re: [LEGAL] Update of include/nuttx/wireless/ieee80211/ieee80211.h

The PR contains the implementation of inline functions. Are those handled in the same way as symbols definitions? Best regards, Petro ср, 13 квіт. 2022 р. о 16:10 Alan Carvalho de Assis пише: > Simple header files, for example only symbols definitions are not > considered derivative work, more

SocketCAN and CAN char diver merge

Hello, Recently I've been working on LIN bus support with SAME70 based device. In general the integration was done smoothly and I would like to contribute my work to the community. The LIN is pretty similar to CAN and in Linux is abstracted as a SocketCAN device. During my integration I chose a mo

Re: SocketCAN and CAN char diver merge

The main reason why I'm raising this topic is that I think that the CAN lower part should be a standard way the upper layer talks to CAN HW and the upper half should perform the translation to a char or netdev interface. Now that is not true. Basically I'm looking into the minimal set of functions

Re: SocketCAN and CAN char diver merge

How does Linux deal with the CAN low level interface? My bet would be > through a raw socket. Commonality with Linux in at least naming would be a > good thing too. > > > > > On Mon, Apr 25, 2022 at 3:49 PM Petro Karashchenko < > petro.karashche...@gmail.com> wrote:

Re: Still problems with network on stm32f7 nucleo-144 board

Hi, I think that it is expected. In case of "NETDEV_LATEINIT" the " arm_netinitialize" is not called and you need to add explicit " stm32_ethinitialize(0);" somewhere in "*board_app_initialize()*" and wrap it with "defined(CONFIG_NETDEV_LATEINIT)". Best regards, Petro пт, 29 квіт. 2022 р. о 10:3

Anyone using SAMv7 PWM?

Hello, Recently I've tried to use PWM on SAMe70 based board. I tried to execute PWM example from apps. The PWM on SAMv7 seems to be not functional, at least I observe only that pin goes high when PWM start is executed and the goes to low when PWM stop is executed. Is anyone using PWM with SAMv7 b

Re: Anyone using SAMv7 PWM?

ude/board.h#L345> > > > > > > > I will double check tomorrow if the configuration does not work for you. > > > > > Best regards, > Michal Lenc > > -- Původní e-mail -- > Od: Petro Karashchenko > Komu: dev@nuttx.apache.org > Datum:

Re: Anyone using SAMv7 PWM?

Hi, I was able to resolve the issue. Will push patch soon. Best regards, Petro ср, 18 трав. 2022 р. о 16:24 Michal Lenc пише: > Hello > > > > CONFIG_EXAMPLES_PWM=y > > > CONFIG_PWM=y > > > CONFIG_SAMV7_PWM0=y > > CONFIG_SAMV7_PWM0_CH2=y > > > > > I used your configuration options and there ind

Re: Anyone using SAMv7 PWM?

Hello Michal, Please participate in the review of https://github.com/apache/incubator-nuttx/pull/6298 I would appreciate it if you can try if changes work for you. Looking forward receiving feedback from you. Best regards, Petro ср, 18 трав. 2022 р. о 16:33 Petro Karashchenko < petro.karash

Re: Anyone using SAMv7 PWM?

annels will lead to an update of HW channels 5 and 6. Is my understanding correct? Maybe somebody can point me to the description of PWM multi-channel mode? Best regards, Petro чт, 19 трав. 2022 р. о 01:56 Petro Karashchenko < petro.karashche...@gmail.com> пише: > Hello Michal, > >

Re: Network debug info level breaks nx_start -> group_setupidlefiles

Hi, Most probably we need to trace when network init is done. Usually in the early stages the "# define showprogress(c) arm_lowputc(c)" and "arm_lowputs" is used to trace the init process, so maybe you can instrument the code to find out what is going on. Best regards, Petro чт, 19 трав. 2022 р

POSIX: ECANCELED returned by sem_wait

Hi, I have a question about sem_wait. Current implementation in NuttX can return failure and set errno to ECANCELED in case if the semaphore wait is done while code is inside the cancelation point. However I do not see ECANCELED in the POSIX description of sem_wait. Can anyone bring some more ligh

Re: POSIX: ECANCELED returned by sem_wait

Hi, This question arises during the review of one PRs. Indeed, it seems that ECANCELED should never be returned to the app because leave_cancellation_point() should terminate the task; however there are quite a few places in code that check ECANCELED returned by semaphore. Those are: - mm_takesema

Re: POSIX: ECANCELED returned by sem_wait

l be canceled. > > There is some relevant discussion here: > https://cwiki.apache.org/confluence/display/NUTTX/Cancellation+Points > > > > On Thu, May 26, 2022 at 8:16 AM Petro Karashchenko < > petro.karashche...@gmail.com> wrote: > > > Hi, > > > > This question ari

Re: POSIX: ECANCELED returned by sem_wait

ed by sem_wait and _SEM_WAIT() will be called again endlessly because cancelation nesting counted will just increment and decrement. Best regards, Petro пт, 27 трав. 2022 р. о 16:23 Gregory Nutt пише: > On 5/27/2022 12:52 AM, Petro Karashchenko wrote: > > Hi, > > > > Ok. That

Re: POSIX: ECANCELED returned by sem_wait

function nxsem_wait(). This is a new internal OS interface. It is functionally equivalent to sem_wait() except that (1) it is not a cancellation point, and (2) it does not set the per-thread errno value on return. пт, 27 трав. 2022 р. о 16:57 Petro Karashchenko < petro.karashche...@gmail.com>

Re: POSIX: ECANCELED returned by sem_wait

Ok. Let's fill the issue and clean-up sem_wait as well as I met that code in sem_wait only, so other places should never return ECANCELED. пт, 27 трав. 2022 р. о 17:07 Gregory Nutt пише: > > > Yes and no. I've posted a code from sem_wait that checks if a > cancellation > > is pending but cannot

[NuttX] CONFIG_NET_TCP_WRITE_BUFFERS=y deadlock issue

Hello team, Recently I've been using NuttX on a SAMv7 based board with Ethernet. I've tried to use the FTP server for remote access to the SD card. During implementation I faced https://github.com/apache/incubator-nuttx/issues/5973 and did some further analysis. When CONFIG_NET_TCP_WRITE_BUFFERS

Re: [NuttX] CONFIG_NET_TCP_WRITE_BUFFERS=y deadlock issue

IOB_THROTTLE=8, so 8 IOB buffers are still available) and the > device > > wants to send the FTP response message. > > Do you refer to an actual FTP response here, or to a TCP level response? > Is the problem caused by the TCP ACK's on the received packets? > >

Re: Potential UDP packets loss, how to debug?

Hello Oleg, Can you try to test with "CONFIG_NET_UDP_WRITE_BUFFERS=y" vs "CONFIG_NET_UDP_WRITE_BUFFERS=n"? The transfer will definitely impact the speed, but at least we can have a idea if buffer allocation impacts the upload process or not. Best regards, Petro чт, 4 серп. 2022 р. о 15:51 Alan C

Re: Potential UDP packets loss, how to debug?

Hi, Yes, the packet lost on UDP is a normal situation, but... If the board is directly connected to the PC, then from my experience the probability to lose a UDP packet in the wire is pretty low. So only loss may be done in the stack and statistics should identify this easily. Best regards, Petro

Re: [VOTE] Apache NuttX 10.4.0 (incubating) RC0 release

Hello Alan, Seems that the root cause is my change https://github.com/apache/incubator-nuttx-apps/pull/1097 I think that all previously generated passwords need to be re-generated. Best regards, Petro On Thu, Aug 11, 2022, 8:49 PM Alan Carvalho de Assis wrote: > Alin, > > I want to redraw my

  1   2   >