Re: STM32F4 SPI DMA buffer size issue

e most 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 [ma

Re: STM32F4 SPI DMA buffer size issue

> Hi 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

Re: STM32F4 SPI DMA buffer size issue

t; > Have you scoped the 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 >

STM32F4 SPI DMA buffer size issue

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

Re: Serial console strange behaviour

lease (you 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

Re: Serial console strange behaviour

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 based

Serial console strange behaviour

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 li

Re: SD FAT32: Write failed with err 28 (no space left on device)

dware 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 boa

SD FAT32: Write failed with err 28 (no space left on device)

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 lot

Re: Telnet: up arrow key in putty returns ^[[A

You are right! Great thanks! сб, 22 авг. 2020 г. в 02:59, Abdelatif Guettouche < abdelatif.guettou...@gmail.com>: > You must be missing CONFIG_TELNET_CHARACTER_MODE > > On Sun, Aug 16, 2020 at 3:32 PM Oleg Evseev wrote: > > > > Hi Alan, > > > > I can open

Re: Telnet: up arrow key in putty returns ^[[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

Telnet: up arrow key in putty returns ^[[A

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

Re: stm32f7 CONFIG_RAM understanding

-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 hea

Re: stm32f7 CONFIG_RAM understanding

> > 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 > *Su

Re: stm32f7 CONFIG_RAM understanding

onfig 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&P from > the F4, that should be removed. > > > > *From:* Oleg Evseev [mailto:ev.m...@g

Re: stm32f7 CONFIG_RAM understanding

: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

stm32f7 CONFIG_RAM understanding

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

Re: stm32f7 CAN driver

://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

Re: stm32f7 CAN driver

020 г. в 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 sc

stm32f7 CAN driver

Hi all, Did anybody use the NuttX CAN driver with stm32f7 mcu? Does it work ok? --- With regards, Oleg.

Re: How to debug DEBUGASSERT in shed?

made the PR 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/s

Re: How to debug DEBUGASSERT in shed?

there. > > 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 > > >

Re: How to debug DEBUGASSERT in shed?

. 2020 г. в 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_hold

CAN driver and critical section use

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) in

Re: How to debug DEBUGASSERT in shed?

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 > messag

How to debug DEBUGASSERT in shed?

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(&CANmodule->f

Re: Get size of block character device file with stat()

> 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 #1118

Re: Get size of block character device file with stat()

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 > s

Get size of block character device file with stat()

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 ro

Re: [PATCH] apps, system/cu fix and additional option

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, &

Re: [PATCH] apps, system/cu fix and additional option

ncubator-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 w

[PATCH] apps, system/cu fix and additional option

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 serial devices with binary protocol -- Best Regards, Oleg

Re: Usrsocktest app example fails

ry corrruption(maybe the > stack 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 sever

Re: Usrsocktest app example fails

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, > >

Re: Usrsocktest app example fails

Hi Masayuki, Thanks for the work! Looking forward to new PRs. пт, 21 февр. 2020 г. в 08:42, Ishikawa, Masayuki (SHES) < masayuki.ishik...@sony.com>: > Hi, Oleg, > > > > Though I am not an author of the code, > > I found a couple of bugs both usrsocktest and nuttx. > > I will send PRs later. > >

Re: Usrsocktest app example fails

onnect. */ ret = connect(test_sd[tidx], (FAR const struct sockaddr *)&addr, sizeof(addr)); -> usrsock_connect: /* Wait for completion of request (or signal). */ ret = net_lockedwait(&state.recvsem); чт, 20 февр. 2020 г. в 13:19, Oleg Evseev : > Hi all,

Usrsocktest app example fails

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 *)&remoteaddr, &addrlen); fills sin_zero in remoteaddr with some notzero values. [image: и

Re: Can't make work shared file for CAN

Hi Gregory, I found the problem. Made an issue: https://github.com/apache/incubator-nuttx/issues/111 чт, 16 янв. 2020 г. в 00:31, Gregory Nutt : > > > But file_read on file pointer doesn't work in the same way as read on > file > > descriptor, even if it is in the same thread - right after file_

Re: Can't make work shared file for CAN

you use the 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(&CANmodule->fi

Can't make work shared file for CAN

mmediately. Doing file_detach() 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