ot image
> creation/signing tool. This I think I can do by reference to
> existing NuttX board code. Fingers crossed.
>
> Once I am happy, I will try and find time to see if I can "back port" it
> to the in-tree SAMA5D2 reference boards (that I have a couple of) in the
Hello Tim,
Some time ago I was adding MCUboot support for SAMv7 family that should be
pretty similar to your system. If you can give some more description of
your use case: RAM and ROM config, does it have internal flash or external,
where the program is executed from, etc. maybe I will be able to
ut what difference has caused the issue though, as my
> linker script is almost identical to the other arm64 implementations
> outside of requiring a different load address. It seems to not be an issue
> with the `lowputc` functions either, as printing is working with static
>
Hi,
Based on what you describe it seems like a stack configuration issue. About
"but the
`uint8_t i` variable I use as a counter in my for-loop is working just
fine" -- I think that the compiler just optimizes out loop variable and
does not use stack for it. There are a few things here to try here
Hi,
This comes more to the edge of coding language paradigms, personal
preferences and readability.
For enable in Rust everything that you define is "const" and if you want to
modify it you should explicitly specify it. On another hand in C everything
you define is modifiable unless you specify "c
Hi,
I do not fully understand if you are looking from Application or Kernel
perspective?
Also I do not know if the CAN driver is capable of providing you with
information when the message is actually transmitted on the bus. I mean
that for example CAN peripheral may have multiple TX buffers and yo
ealised it was
> going to be *pip3*
>
> I used:
>
>
>
>
> *brew install pythonpython3 -m ensurepip --upgradepip3 install kconfiglib*
> But I'll see if I can reconfirm the exact requirements and create a PR.
>
>
> On Wed, 18 Oct 2023 at 16:03, Petro Kara
I think the latest code rely on kconfiglib, so theoretically things should
work without kconfig-frontends. But I haven't tested case when
kconfig-frontends is not installed (current I have installed both).
Best regards,
Petro
On Wed, Oct 18, 2023, 1:35 AM Christian Catchpole
wrote:
> Thanks I'l
I think there was an option to specify custom drivers relative to board
level. This should remain third party as long as you go with
"CONFIG_ARCH_BOARD_CUSTOM"
BOARD_DRIVERS_DIR ?= $(wildcard $(BOARD_DIR)$(DELIM)..$(DELIM)drivers)
Personally I never used it that way, but do not see anything that
I think ESP32 also has IDLE cycles configuration for UART, so adding it as
serial generic config makes sense to me.
пн, 9 жовт. 2023 р. о 12:51 David Sidrane пише:
> What about adding it per [LP]U[S]ART in the Kconfig here
> https://github.com/apache/nuttx/tree/master/drivers/serial
>
> Then any
ed via menuconfig it will work.
чт, 21 вер. 2023 р. о 15:44 Gustavo Soares
пише:
> So setting a value for the IP address in Kconfig and assigning it to
> address.sin_addr.s_addr should solve the problem?
>
> De: Petro Karashchenko
> Enviado: quinta-feir
t; the incoming requests so you can take a better look. How should I make the
> API call to get the device IP?
> --
> *De:* Petro Karashchenko
> *Enviado:* quinta-feira, 21 de setembro de 2023 09:00
> *Para:* dev@nuttx.apache.org
> *Assunto:* Re: diff
;
>
> Hi, Petro!
>
> I use this struct:
>
> [image: image.png]
>
> and this where I use the inet_ntoa:
>
> [image: image.png]
> --
> *De:* Petro Karashchenko
> *Enviado:* quinta-feira, 21 de setembro de 2023 08:16
> *Para
Hi,
"INADDR_ANY" definitely does not match "listens to the defined IP"
statement. I do not understand exactly what you are trying to do, but it
would be good to know what is the output of "ifconfig" running from NSH.
If you do not want to share code details, maybe you can check how your
applicatio
Hi,
I think that FAT32 is not a fail-safe file system by its nature. There may
be data losses (file table corruption) in case of power loss during file
write (file table update) or maybe in some other cases when file system
access is interrupted.
I think HCC had some product called SafeFAT that wa
with this chip
> the more I'm wondering if I'm going to have to move to using master.
> I've been trying to avoid not using an actual release version of NuttX.
>
> -m
>
> On 9/18/2023 3:08 PM, Petro Karashchenko wrote:
> > Hello Mike,
> >
> > Which
Hello Mike,
Usually most of the "/dev/XXX" devices are registered at board level (in
xxx_bringup() call
https://github.com/apache/nuttx/blob/master/boards/xtensa/esp32s3/esp32s3-devkit/src/esp32s3_bringup.c
).
Enabling peripherals does not always lead to registration of "/dev/XXX"
node as drivers
Hello Mike,
Which version of nuttx code are you using? Recently I was dealing with
UART1/2 on ESP32S3 and managed those to be working in
https://github.com/apache/nuttx/pull/10467
There were few issues including some clocking configuration problem as well
as wrong pin functions used for UART1.
At
Since C++ most likely will never be used in the kernel I see that
compatibility border should stay in the "include" folder in nuttx repo. The
nuttx-apps headers should be C++ compatible as we can mix things at
application level.
Hi,
What kind of RISC-V toolchain are you using? I recall that the RISC-V
toolchain provided by Ubuntu is built without libm support. Also I noticed
that you have "CFLAGS += -lm " in Make.defs and with CONFIG_LIBM=y that
should be removed I think as you try to rebuild math from NuttX sources.
Ple
You can try searching for "CONFIG_NSH_ROMFSETC" and
"CONFIG_NSH_CUSTOMROMFS" options in the code tree.
I see that currently ESP32-C3 and SIM use it. Also I used the same with
custom board and it works pretty well.
нд, 10 вер. 2023 р. о 00:35 Gustavo Soares
пише:
> Do you have any example of how
Hello NuttX developers,
Recently I fixed a latency issue related to Ethernet transmission with
SAMv7. Now I'm moving forward and meeting the next issue:
I'm having a nuttx based board installed in the industrial Ethernet network
environment. By "industrial Ethernet network environment" I mean that
its when I was debugging the
> issue with MQTT, see attached image.
>
> I saved all the wireshark dumps, I can share it with you case you want
> to compare.
>
> BR,
>
> Alan
>
> On 9/7/23, Petro Karashchenko wrote:
> > Hi,
> >
> > I got back to investigati
Hi,
The ESP32-S3 BLE support was added in
https://github.com/apache/nuttx/pull/10200 so seems that was done after
12.2.1 was released.
Best regards,
Petro
ср, 6 вер. 2023 р. о 23:28 Mike Moretti пише:
> Hi,
>
> After all the troubles I had with BLE+WiFi on the esp32, I found out
> that we are
I rethink my question again and this depends on HW configuration also, so
can't be handled at driver level generically.
сб, 2 вер. 2023 р. о 18:31 Petro Karashchenko
пише:
> Hello Alan,
>
> Thank you. I will try to port SW RS485 to ESP32-S3, but from my experience
> in the
r by RS485 driver.
>
> It is possible to use the internal IP RS485 from ESP32 or ESP32-S3,
> you just need to look how it is done in the ESP-IDF and replicate it.
>
> But the SW RS485 works fine and it is easier to implement.
>
> BR,
>
> Alan
>
> On 9/2/23, Petro Karash
Hi,
I'm currently trying to enable RS485 support for ESP32-S3. I see that there
is some support of RS485 mode in ESP32 and it seems to be straight forward
to port it to ESP32-S3 however I see that currently ESP32-S3 lowputc has
next lines
modifyreg32(UART_RS485_CONF_REG(priv->id), UART_RS485_EN_M
The delayed ACK option is selected. I will try to deselect it and make end
to end testing before going further with investigation.
Thank you very much for the hint.
пт, 1 вер. 2023 р. о 01:04 Gregory Nutt пише:
>
> On 8/31/2023 3:39 PM, Petro Karashchenko wrote:
> > Hello,
> >
Hi,
I have a question about is it possible to have multiple CAN frame producers
(threads) and one CAN frame reader using SocketCAN interface? With a
traditional CAN driver it is even possible to have multiple CAN frames
consumers, but still I do not need that.
I'm asking because I'm not sure if i
Hello,
I'm having an issue with a network based application on NuttX.
I have a HTTP server that is built with the help of the "netlib_server"
interface. When I'm trying to access my server with curl multiple times in
a row I see that there is a gap close to 500ms on the PC side when
accessing the
Hello Mark,
I think that the best would be to use not GPIO interface, but NuttX buttons
interface. You can try to search for the "btn_lower_initialize" call in the
code tree. I definitely tested that some time ago with same70-qmtech board.
You can also search for the "examples/buttons" applicatio
https://github.com/apache/nuttx/issues/9670
On Thu, Jul 6, 2023, 2:29 PM Mark Stevens
wrote:
> So had a play with 12.2 and came across an error when building.
>
> make -j V=2 generates the following expanded output for the error:
>
> grep -v "CONFIG_BASE_DEFCONFIG"
> "/Users/markstevens/GitHub/N
an errors with vars, I
> believe.
>
> On 05/07/2023 19:24, Petro Karashchenko wrote:
>
> Just to clarify, when you run lvgldemo from nsh, do you also pass "widgets"
> as argument, right?
>
> On Wed, Jul 5, 2023, 8:54 PM Tim Hardisty t...@hardisty.co.uk> wrote:
>
ED_HPWORK=y
> CONFIG_SCHED_HPWORKPRIORITY=192
> CONFIG_SCHED_HPWORKSTACKSIZE=2048
> CONFIG_SCHED_WAITPID=y
> CONFIG_SENDFILE_BUFSIZE=256
> CONFIG_SENSORS=y
> CONFIG_SENSORS_MAX31855=y
> CONFIG_SERIAL_TERMIOS=y
> CONFIG_SIG_DEFAULT=y
> CONFIG_SPI_DELAY_CONTROL=y
>
Maybe you can share the defconfig for faulty case, so that can be inspected?
On Wed, Jul 5, 2023, 8:29 PM Tim Hardisty wrote:
> Yes - both that and the lvgldemo stack size (up to 65535 each).
>
> On 05/07/2023 18:21, Xiang Xiao wrote:
>
> Do you try CONFIG_INIT_STACKSIZE instead?
>
> On Thu, Jul
Hi,
The de-init part is a bit tricky here. I think that u-boot enables clocking
for various parts of the SoC and mux pins used in bootloader, so if I
recall correctly the clocks are not shutted down and pins are not
de-muxed to reset value state when the OS is booted. The best would be if
the OS (
Hi,
Could you please add some more information about the configuration like
"CONFIG_STM32F7_DMACAPABLE", "CONFIG_SPI_TRIGGER",
"CONFIG_STM32F7_SPIx_DMA_BUFFER" and "CONFIG_STM32F7_SPI_DMATHRESHOLD".
Also the D-cache configuration like "CONFIG_ARMV7M_DCACHE_WRITETHROUGH".
I do not see obvious issu
The sendfile() description across the OSes is not the same. The FreeBSD
version https://man.freebsd.org/cgi/man.cgi?sendfile(2) for example has
words "The nbytes argument specifies how many bytes of the file should be
sent, with 0 having the special meaning of send until the end of file has been
re
The nuttx file is actually an ELF file, but without .elf extension.
BR,
Petro
On Sun, Jun 11, 2023, 10:39 AM Mark Stevens wrote:
> I think the missing piece of information is that the nuttx file contains
> the debug symbols.
>
> Thanks for your time and help.
>
> Regards,
> Mark
> _
Kudos and looking forward to seeing pictures and videos!
Thank you!
пт, 26 трав. 2023 р. о 20:54 Tim Hardisty пише:
> I have been tinkering with a blog/AboutMe thingy, also using it as a way
> to learn markdown. Although I've not updated it for a short while, I
> decided to add it to my GitHub
I think you can try to compare versus SAMv7 SPI+DMA driver that is working
well and see if there are obvious differences.
BR,
Petro
On Wed, May 17, 2023, 9:18 PM Simon Filgis
wrote:
> D-Cache flush?
>
> --
> Ingenieurbüro-Filgis
> USt-IdNr.: DE305343278
> --
> sent by mobile phone
>
> Tim Hardi
How do you measure the wait period? Are you togging a pin or used MCU free
running HW timer?
Best regards,
Petro
On Wed, May 17, 2023, 5:43 PM Jukka Laitinen wrote:
>
> On 17.5.2023 16.38, Gregory Nutt wrote:
> > On 5/17/2023 7:21 AM, Gregory Nutt wrote:
> >> On 5/17/2023 4:21 AM, Jukka Laitine
Hello Krasimir,
One of the contributors brought
https://lists.apache.org/thread/y7zrsbf2k86n1qbjlt67hlcj10smjdfw into the
discussion.
Could you please take a look and reply if you agree?
Best regards,
Petro
On Wed, Apr 26, 2023, 10:26 AM Petro Karashchenko <
petro.karashche...@gmail.com>
Hi,
Some time ago I tried to fix this with
https://github.com/apache/nuttx/pull/6376 but it ended-up nowhere as I
didn't find time for a proper solution.
Best regards,
Petro
ср, 26 квіт. 2023 р. о 12:50 Ville JUven пише:
> Hi,
>
> I'm in the process of trying to fix this issue:
> https://githu
l the system has booted.
>*/
>
> up_rtc_initialize();
> .
>
> Best regards
>
> -Original Message-
> From: Petro Karashchenko
> Sent: Wednesday, April 26, 2023 10:02 AM
> To: dev@nuttx.apache.org
> Subject: Re: external rtc small fix
>
> Hi,
>
&
Hi,
Which version are you using? In the latest master I see:
#if defined(CONFIG_RTC)
/* Initialize the internal RTC hardware. Initialization of external RTC
* must be deferred until the system has booted.
*/
up_rtc_initialize();
#if !defined(CONFIG_RTC_EXTERNAL)
/* Initialize the ti
HCI device and temporarily
> provide it largely isolated control over it (you cannot scan from the host
> anymore for example).
> There is a good description of this feature in the patch that introduced
> it. https://marc.info/?l=linux-bluetooth&m=137757846631034&w=2
>
> On Tue,
Is this going to work on OSX? Or Linux only is verified?
вт, 25 квіт. 2023 р. о 19:45 Brennan Ashton
пише:
> On Tue, Apr 25, 2023, 5:41 PM Brennan Ashton
> wrote:
>
> >
> > On Tue, Apr 25, 2023, 5:36 PM Petro Karashchenko <
> > petro.karashche...@gmail.com> wro
Hello,
I'm starting to experiment with NuttX BLE support. I have a device that I
can successfully pair with my phone and I would like to try pairing it with
the NuttX based device. I chose ESP32 for my experiments. For now I enabled
(and fixed) esp32-devkitc:ble configuration, but that is basicall
but might be over the top? USB host/device works and you
> can do OTG/DRP on a custom board and it should be more than capable of
> doing CDC-ACM I would have thought?
>
> From: Petro Karashchenko
> Reply to: "dev@nuttx.apache.org"
> Date: Thursday, 20 April 2023 at 14:25
Hello,
I'm looking for an MCU or better a development board that has WiFi, BT and
USB host capabilities. Can anybody give me advice for that? I need to
connect a CDC ACM device to that USB, so maybe there are some alternatives
that can be used (there is a device that exposes its functionality via
Apr 15, 2023 at 5:07 AM Petro Karashchenko <
> petro.karashche...@gmail.com> wrote:
>
> > Hello team,
> >
> > I want to ask a question regarding running the ostest with priority
> > inheritance on the sim target. The priority inheritance test uses a
> special
&
Hello team,
I want to ask a question regarding running the ostest with priority
inheritance on the sim target. The priority inheritance test uses a special
routine for "hog_cpu" on the sim target by calling "up_idle()". I
understand that it is due to the simulator not having any mechanism to do
as
I agree with Greg!
If we can have stable operation of priority inheritance with semaphores
then we can build mutex as a macro based wrapper (mostly as it is now).
One thing that I can think of is adding a "mutex" attribute to a semaphore
and creating a separate task list for faster scheduling, bu
Just posted a comment in GitHub, but duplicating it here for visibility.
The change might not be needed with
https://github.com/apache/nuttx/pull/8951 as it removes access to pid hash
table during sem_post()
Best regards,
Petro
On Wed, Apr 5, 2023, 12:53 AM Gregory Nutt wrote:
>
> On 4/4/2023 3
I drafted some optimization in https://github.com/apache/nuttx/pull/8951
I would appreciate some support with that if possible as these days I'm a
bit overloaded.
Best regards,
Petro
сб, 1 квіт. 2023 р. о 23:35 David S. Alessio
пише:
>
>
> > On Apr 1, 2023, at 12:54 PM, David S. Alessio
> wrot
Xiang Xiao, is that still true for the latest code in master branch?
And by "system will
crash if the priority inheritance enabled semaphore is waited or posted
from different threads" do you mean at the point of sem_post/sem_wait or
some system instability in general?
Best regards,
Petro
On Fri
Hello Greg,
I already wrote that my example is more theoretical and may be a "bad
design", but it illustrates the issue in the current code.
Please understand me right, I'm not against having priority inheritance
available for semaphores. I just want to have things well defined and
possibly prohib
Even more. In my previous example if semaphore is posted from the interrupt
we do not know which of TaskA or TaskB is no longer a "holder l" of a
semaphore.
Best regards,
Petro
On Fri, Mar 31, 2023, 5:39 PM Petro Karashchenko <
petro.karashche...@gmail.com> wrote:
> Sorry
Sorry for been not clear. Here is a better description:
2 DMA channels accountable by a counting semaphore.
The semaphore is posted by DMA completion interrupt.
TaskA with priority 10 allocates DMA0 channel and starts DMA activity.
TaskB with priority 20 allocates DMA1 channel and starts DMA activi
I still see more questions than answers. As semaphores can be posted from
the interrupt level. Let's take next example:
The counting semaphore manages DMA channels.
Task allocates a DMA channels and takes counting semaphore (becomes a
holder), but posting a semaphore is done from DMA completion can
Yes and No. For counting semaphores we have multiple holders for example
with priorities 10, 50 and 90. Now a task with priority 100 comes and wants
to take a semaphore. Priority which of the holders should be increased? The
lowest or the highest holder? With a real-time point of view it should be
Hello,
Migration to nxmutex is quite a big effort and unfortunately recently I
didn't have much time to deep dive into this. In general I support an
initiative and do not see a use case for priority inheritance for regular
semaphores, so I think we should clean-up priority inheritance code for the
Hi,
Recently during the review I have found that most of the linker script
files in the code tree have CONSTRUCTORS placed in the .data section. On
the other hand the linker script files that use .ctors and .dtors sections
place those in the .text or .rodata segment.
Does anybody know anything ab
I've counted 28 signals specified in
https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/signal.h.html and
2 (SIGUSR1 and SIGUSR2) are already reserved for application needs. So 31 -
(28 - 2) == 5. One signal value is "reserved" for SIGWORK, so it makes 4
signal values that can be used by app
>
> So can we just get rid of the configurations and just make the signal
> numbers fixed (and equal to the fixed numbers assigned by Linux)?
>
> That would make your job easier and, I think, clean up some useless
> stuff in the OS.
>
> Greg
>
> On 3/21/2023 12:18 PM, Petr
Hello team,
Recently I've been looking into signal implementation and particularly into
strsignal() API. As a result I've drafted
https://github.com/apache/nuttx/pull/8867 that intends to optimize the
implementation, but during CI I found out that some configurations have
different signal numbers
t; board profile).
> >
> > Try this sequence:
> > make distclean
> > ./tools/configure.sh esp32-devkitc:wapi
> >
> > Then example the webserver example.
> >
> > BR,
> >
> > Alan
> >
> > On 3/17/23, Gustavo Soares wrote:
> &g
Hi,
Seems like I will be able to attend. I'm arriving today, so have some spare
day tomorrow just in case someone wants to get some beers together before
the event.
Best regards,
Petro
On Sun, Mar 12, 2023, 5:26 PM Alin Jerpelea wrote:
> hi
> I will be there and I hope to meet some of our awes
On the libm: some time ago I tried to install the RISCV toolchain on Ubuntu
with apt and the installed toolchain was built without libm :)
In other words, running compiler + arch flags with "--print-file-name=libm.a"
option gave me an empty output (also "find gcc_folder -name libm.a" gave me
an em
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
On Wed, Mar 8, 2023, 7:24 PM Xiang Xiao wrote:
> On Thu, Mar 9, 2023 at 12:57 AM Simon Filgis <
> si...@ingenieurbuero-filgis.de>
> wrote:
>
> > D
Hi,
I agree with Nathan. The "V=0" -- seems to be an explicit option for "no
verbose" compilation (in other worlds should suppress all the outputs
except errors I hope).
Best regards,
Petro
вт, 7 бер. 2023 р. о 15:59 Nathan Hartman пише:
> On Tue, Mar 7, 2023 at 8:12 AM Sebastien Lorquet
> wr
Hello Simon,
Maybe adding "apt-get install -y xxd" -- I mean adding xxd separately
instead of vim-common and let package manager to resolve dependencies is a
better approach?
Best regards,
Petro
пт, 24 лют. 2023 р. о 10:46 Simon Filgis
пише:
> Hi Alan,
>
> many thanks:
>
> xxd -i romfs.img | s
to drain the instruction
pipeline before jumping to relocated code and that will require making sure
that start-up is done in position independent code and just to the
relocated code will not use relative offset jumps.
Best regards,
Petro
пт, 9 груд. 2022 р. о 12:18 Petro Karashchenko
пише
Hi,
Finally I was able to take a look here. The case is that armv7-m (and some
other ARM versions) do not use arm_head.S and __start entry points are
implemented in C code and CONFIG_BOOT_COPYTORAM option is not implemented,
so code is always executed from internal flash. So when you are trying to
Hello James,
I've been working with SAMe70 based device and can try to take a look at a
case that you are talking about.
Do you have any specific config that I can start from?
In general I expect that if you fully relocate your program to SRAM you
should be capable of reprogramming a full flash,
+1
вт, 22 лист. 2022 р. о 16:35 Gregory Nutt пише:
> +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
Hi,
My two cents are that I think we should not rock the boat and just remove
"incubator-" prefix from current repos that results in:
nuttx
nuttx-apps
Best regards,
Petro
сб, 19 лист. 2022 р. о 17:03 Tomek CEDRO пише:
> On Sat, Nov 19, 2022 at 3:53 PM Thiago Costa de Paiva wrote:
> > From the
ous updates are a good thing most times.
>
> David
>
>
> -Original Message-
> From: Petro Karashchenko
> Sent: Friday, November 11, 2022 6:50 PM
> To: dev@nuttx.apache.org
> Subject: PWM fast stop operation
>
> Hello team,
>
> Recently I had a project wh
Hello team,
Recently I had a project where I had to control a motor using PWM. In
general things worked pretty well, but I've met an issue when I need to
stop PWM as soon as possible. My custom board is based on SAMv7 and uses
the standard NuttX PWM driver. The issue with the SAMv7 PWM peripheral
I see that those comments are there starting from the initial commit. Maybe
f...@feedforward.com.cn can update those comments to something readable
(added to recipients list)?
Best regards,
Petro
пн, 10 жовт. 2022 р. о 19:05 Fotis Panagiotopoulos
пише:
> I used the following two commands to che
Hello,
Does anybody have experience with exposing functionality of NuttX based
device via REST API?
Also maybe someone did integration with SCPI?
I'm looking for some lightweight implementations for both REST API and SCPI
and would appreciate for any references that I can explore. Maybe there ar
de Assis
wrote:
> ACK
>
> Strange, the previous email went only to you!
>
> On 8/11/22, Alin Jerpelea wrote:
> > @Alan Carvalho de Assis please confirm that works
> > after revert
> >
> > On Thu, 11 Aug 2022, 20:22 Petro Karashchenko,
> >
>
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
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
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
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?
>
>
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
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
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>
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
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
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
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
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 р
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,
>
>
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
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
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:
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
1 - 100 of 185 matches
Mail list logo
