t welcome,
>
> Did you adjust the size of the board dma allocator?
>
>
> https://github.com/PX4/PX4-Autopilot/blob/1dd6b6a5058199ea6bbf1e2321010abe88a656ee/platforms/nuttx/src/px4/common/board_dma_alloc.c#L57
> ?
>
> -----Original Message-
> From: Oleg Evseev [mailto:
Oleg,
>
> See inline [DBS]
>
> David
> -Original Message-
> From: Oleg Evseev [mailto:ev.m...@gmail.com]
> Sent: Tuesday, November 24, 2020 9:46 AM
> To: dev@nuttx.apache.org
> Subject: Re: STM32F4 SPI DMA buffer size issue
>
> > Have you scoped the interface?
he interface?
>
> For gins and giggles try reducing the SPI clock drive strength. Step it
> down
> and retest.
>
> David
>
> -----Original Message-
> From: Oleg Evseev [mailto:ev.m...@gmail.com]
> Sent: Tuesday, November 24, 2020 4:57 AM
> To: dev@nuttx.apache.org
Hi all,
STM32f405rg custom board - MTD on SPI1 and SD card on SPI2.
MTD on SPI1 works without DMA and with if defined CONFIG_STM32_SPI1_DMA=y
but if also
CONFIG_STM32_SPI1_DMA_BUFFER=1024
is set, partitions get created, there are mtdblockX in /dev, geometry can
be read correctly, but reading or
will need this patch to not get a hadrfault
https://github.com/apache/incubator-nuttx/pull/2209)?
ср, 11 нояб. 2020 г. в 14:18, Oleg Evseev :
> No, it is the same board and config that worked before with NuttX 8.2
> without such issues. Only several modifications same as was done for
any PX4IO drivers or RC input?
>
> -Original Message-
> From: Oleg Evseev [mailto:ev.m...@gmail.com]
> Sent: Wednesday, November 11, 2020 3:09 AM
> To: dev@nuttx.apache.org
> Subject: Serial console strange behaviour
>
> Hi,
>
> Custom board stm32f7, PX4 bas
Hi,
Custom board stm32f7, PX4 based project - moved from NuttX 8.2 to 10.0.0.
If serial dev console (CONFIG_USART6_SERIAL_CONSOLE=y) is used, it works:
prints all corresponding output on boot, but then
"nsh> " is shown only when I start typing in putty.
"ls" command shows only the first output
read using dma (CONFIG_STM32F7_DMACAPABLE=y,
CONFIG_STM32F7_SDMMC_DMA=y).
MCU is stm32f767
It doesn't happen every time, but quite rare. Any thoughts where should I
look further?
пн, 7 сент. 2020 г. в 10:49, Oleg Evseev :
> Hi all,
>
> I'm working with stm32f7 custom board and px4
Hi all,
I'm working with stm32f7 custom board and px4 firmware, but my concerns are
with the NuttX FAT32 driver. I have an issue. PX4 logger module writes high
rate data to SD card successfully awhile, until at some point write func
return error 28 (“No space left on device”) while there is a
BTW, could you please open an issue for it?
>
> https://github.com/apache/incubator-nuttx/issues
>
> BR,
>
> Alan
>
> On 8/16/20, Oleg Evseev wrote:
> > Hi all,
> >
> > Up arrow key in Putty returns ^[[A instead of choosing last command when
> >
Hi all,
Up arrow key in Putty returns ^[[A instead of choosing last command when
connected to NuttX 8.2 via Telnet, while everything is ok when connected to
serial console.
I've already tried different keyboard configurations ("linux", Xterm and so
on) in putty as suggested in internet - nothing
-microprocessors/stm32f746ng.html
>
> Best regards,
> Gustavo.
>
> On Tue, Aug 4, 2020 at 5:04 PM Oleg Evseev wrote:
>
>> Hi David,
>>
>> As I see they are used to define:
>> CONFIG_RAM_END (CONFIG_RAM_START+CONFIG_RAM_SIZE)
>> which in turn is used in
>
> I deleted them and it px4_fmuv5 still builds. I will clean that up when I
> get past the upgrade.
>
>
>
> David
>
>
>
>
>
> *From:* Oleg Evseev [mailto:ev.m...@gmail.com]
> *Sent:* Tuesday, August 04, 2020 1:04 PM
> *To:* dev@nuttx.apache.org
>
and ask this question (of course it may not be related to my issue).
вт, 4 авг. 2020 г. в 22:49, David Sidrane :
> Both are not used in the source. I would assume it is a legacy C from
> the F4, that should be removed.
>
>
>
> *From:* Oleg Evseev [mailto:ev.m...@gmail.com]
:27, Gregory Nutt :
> External SRAM?
>
> On 8/4/2020 1:08 PM, Oleg Evseev wrote:
>
> Hi,
>
> I wonder why stm32f7 boards has such RAM parameters in defconfigs:
> CONFIG_RAM_SIZE=245760
> CONFIG_RAM_START=0x2001
>
> Where do these numbers come from w
Hi,
I wonder why stm32f7 boards has such RAM parameters in defconfigs:
CONFIG_RAM_SIZE=245760
CONFIG_RAM_START=0x2001
Where do these numbers come from while memory map is this?
[image: изображение.png]
---
With regards,
Oleg
://github.com/PX4/libuavcan/blob/52e7ce09907bcec8a0b93e7a15d5fbd121c686dc/libuavcan_drivers/stm32/driver/src/uc_stm32_can.cpp#L195
ср, 22 июл. 2020 г. в 11:29, Oleg Evseev :
> Hi Ben,
>
> Yes, I mean native internal stm32f7 CAN controller RX, TX connected to CAN
> phy chip (SN65HVD230 in our case
. в 10:54, Disruptive Solutions <
disruptivesolution...@gmail.com>:
> Oleg do you mean the SPI version (mcp) or native with a say tja1050? The
> SPI version I use on different platforms. The stm32f7 I have to try
> though...
>
> Ben
>
> Op di 21 jul. 2020 23:06 schreef
Hi all,
Did anybody use the NuttX CAN driver with stm32f7 mcu? Does it work ok?
---
With regards, Oleg.
R 1370 <https://github.com/apache/incubator-nuttx/pull/1370>.
пт, 3 июл. 2020 г. в 16:26, Oleg Evseev :
> Hi, Alan.
>
> Thanks for the feedback.
>
> Found out that I'm still get DEBUGASSERT(pholder != NULL) in function
> nxsem_allocholder in file semaphore/sem_holder.c aft
.
>
> BR,
>
> Alan
>
> On 7/3/20, Oleg Evseev wrote:
> > Regarding to can driver, from some moment I started getting
> > DEBUGASSERT(sem->semcount > in sem_post.c. Found the bug
> > https://github.com/apache/incubator-nuttx/issues/1354
> >
> &g
0 г. в 20:16, Oleg Evseev :
> Find out that this happens while in poll.
>
> вт, 30 июн. 2020 г. в 15:45, Oleg Evseev :
>
>> Hi all,
>>
>> I wonder how can I debug
>> DEBUGASSERT(pholder != NULL) in function nxsem_allocholder in file
>> semaphore/sem_holder
Hi all,
I wonder if it is right to call nxsem_wait while in critical section?
Regardless of the answer I also wonder why can_read() and can_write()
enter_critical_section before accessing the received FIFO, but can_poll
doesn't?
Can this be related to getting into DEBUGASSERT(pholder != NULL)
Find out that this happens while in poll.
вт, 30 июн. 2020 г. в 15:45, Oleg Evseev :
> Hi all,
>
> I wonder how can I debug
> DEBUGASSERT(pholder != NULL) in function nxsem_allocholder in file
> semaphore/sem_holder.c that happens after some time reading a lot of
> mes
Hi all,
I wonder how can I debug
DEBUGASSERT(pholder != NULL) in function nxsem_allocholder in file
semaphore/sem_holder.c that happens after some time reading a lot of
messages from can bus in can_reciever task?
Task looks like this (CAN dev is opened as shared file with
file_open(>file,
> The bch driver supports an IOCTL called BIOC_GEOMETRY that will return
the geometry of the underlying block device.
Yes, I understand. But user application handle all files the same way using
path and
int stat(FAR const char *path, FAR struct stat *buf) function.
I've made a pull request
25 мая 2020 г. в 15:03, Oleg Evseev :
> Hi,
>
> I wonder how to get size of character device that referenced mtd partition
> block device? As I see bchlib_setup in drivers/bch/bchlib_setup.c fills
> block geometry info to bchlib_s structure (number of sectors and sector
>
Hi,
I wonder how to get size of character device that referenced mtd partition
block device? As I see bchlib_setup in drivers/bch/bchlib_setup.c fills
block geometry info to bchlib_s structure (number of sectors and sector
size) that then stored as i_private to inode.
This inode is part of the
eview process smother.
> If you can use Github, please for future contributions submit PRs at
> https://github.com/apache/incubator-nuttx and
> https://github.com/apache/incubator-nuttx-apps
>
> Thanks.
>
> On Fri, Mar 13, 2020 at 9:41 PM Oleg Evseev wrote:
> >
> > Hi,
&
/incubator-nuttx-apps
>
> On Fri, Mar 13, 2020 at 3:26 PM Oleg Evseev wrote:
> >
> > 1) system/cu: fix wrongly swapped parity options
> > 2) system/cu: add option -f to loop forever
> > endless mode: pass all characters and ignore escape sequence, handy to
> interact with s
ck too small) which platform you are running.
>
> On Sat, Feb 22, 2020 at 6:52 PM Oleg Evseev wrote:
> >
> > Hi Xiang,
> >
> > I can check it only on Monday, thanks!
> >
> > But, by the way, in commits you mentioned several errors in usrsocktest
>
fail is very minor:
> 1.Set the different errno
> 2.Foget to check NULL pointer
> 3.Don't zero the sockaddr padding bytes
> ,usrsock work well very even without these patch.
>
> On Fri, Feb 21, 2020 at 4:17 PM Oleg Evseev wrote:
> >
> > Hi Masayuki,
> >
>
onnect. */
ret = connect(test_sd[tidx], (FAR const struct sockaddr *),
sizeof(addr));
-> usrsock_connect:
/* Wait for completion of request (or signal). */
ret = net_lockedwait();
чт, 20 февр. 2020 г. в 13:19, Oleg Evseev :
> Hi all,
>
> Trying to run
Hi all,
Trying to run usrsocktest example from app:
[image: изображение.png]
1) first two failed test in NoBlockRecv and BlockRecv fail because
ret = recvfrom(sd, data, datalen, 0, (FAR struct sockaddr
*), );
fills sin_zero in remoteaddr with some notzero values.
[image: изображение.png]
2)
e CAN app
> from examples?
>
> Verstuurd vanaf mijn iPhone
>
> > Op 15 jan. 2020 om 22:02 heeft Oleg Evseev het
> volgende geschreven:
> >
> > Hi!
> >
> > When I use usual file descriptor for can device:
> > file_open(>file, "/dev/can0",
() as describe in
https://www.nuttx.org/doku.php?id=wiki:nxinternal:detachedfds leads to the
same result.
Any thoughts?
Thanks.
--
With regards,
Oleg Evseev
36 matches
Mail list logo
