Re: Version when building the latest NuttX

2023-01-03 Thread Jernej Turnsek
Hi, I have done the prune and prune-tags option again and now it seems to work ok. The .version file gets the proper version, although git describe command still gives me 8.2 version. On Tue, Jan 3, 2023 at 2:50 PM Gregory Nutt wrote: > Look at the hidden file .version. You will need to modify

Re: Version when building the latest NuttX

2023-01-03 Thread Jernej Turnsek
Hi, the .version file is overridden when make command is executed. If I change it manually, it gets overridden. On Tue, Jan 3, 2023 at 2:50 PM Gregory Nutt wrote: > Look at the hidden file .version. You will need to modify that file as > you see fit. It is not controlled under GIT (but is pro

Re: d_len/d_buf arbitration for s32k1xx_flexcan

2023-01-03 Thread Xiang Xiao
Sorry, "you must do..." may confuse you. What I mean is the CAN driver. On Wed, Jan 4, 2023 at 2:30 AM Carlos Sanchez wrote: > Hi Xiang, > > Please note what I describe is not caused by my code using multiple > threads, but is happening on Nuttx upstream. My code is single threaded, > but s32k

Re: d_len/d_buf arbitration for s32k1xx_flexcan

2023-01-03 Thread Carlos Sanchez
Hi Xiang, Please note what I describe is not caused by my code using multiple threads, but is happening on Nuttx upstream. My code is single threaded, but s32k1xx_flexcan driver (and several other Socket CAN drivers as they all seem to be derived from the same code base) does some things on the th

Re: d_len/d_buf arbitration for s32k1xx_flexcan

2023-01-03 Thread Xiang Xiao
Since tx/rx share the same d_len/d_buf, you must do send/recv in one and only thread(either by system work thread or driver dedicated thread) to avoid the race condition you describe below. On Wed, Jan 4, 2023 at 1:45 AM Carlos Sanchez wrote: > Hi all, > > I am observing an extrange behavior: un

d_len/d_buf arbitration for s32k1xx_flexcan

2023-01-03 Thread Carlos Sanchez
Hi all, I am observing an extrange behavior: under heavy-error CAN TX scenario (no acks so TX fails always), usually after the second call to write() my writes fail. This is expected as s32k1xx_flexcan has two TX mailboxes and from my understanding of the code there is no other buffering (on this

Re: Syslog file max Size wrap issue

2023-01-03 Thread Xiang Xiao
On Tue, Jan 3, 2023 at 8:51 PM Simon Filgis wrote: > Hi Alan, > > Thanks for your email. > > I had a closer look and I think I do not think of a bug anymore. > > Filesize is only checked once, while initializing the syslog file channel > with syslog_file_channel() at board level. In other words,

Re: Version when building the latest NuttX

2023-01-03 Thread Gregory Nutt
Look at the hidden file .version.  You will need to modify that file as you see fit.  It is not controlled under GIT (but is provided with each new  release package). On 1/3/2023 2:38 AM, Jernej Turnsek wrote: Hi All, when building the latest NuttX OS from git, I am having problems with .vers

Re: Syslog file max Size wrap issue

2023-01-03 Thread Simon Filgis
Hi Alan, Thanks for your email. I had a closer look and I think I do not think of a bug anymore. Filesize is only checked once, while initializing the syslog file channel with syslog_file_channel() at board level. In other words, rotation does only happen on reboot. A "life-rotate" mechanism wo

Version when building the latest NuttX

2023-01-03 Thread Jernej Turnsek
Hi All, when building the latest NuttX OS from git, I am having problems with .version file, where wrong version is used. Running the git describe, I get nuttx-8.2-12100-g56c6943311, although I have the latest code. I have updated the local repo from upstream with --prune and --prune- tags option