RE: Arm Kinetis: set_errno in nx_start with CONFIG_TLS_ALIGNED not set
> From: Gregory Nutt [mailto:spudan...@gmail.com] > I just configured a new computer and I am having problems with MSYS2. I > can't even create the "symbolic" links needed at start up. I am not > sure why. Probably some priveleges issues. I activate Windows 10 Developer Mode, and create an environment variable named "MSYS" with value "winsymlinks:nativestrict". That's it. > But I did verify the build on Cygwin and it was about the same as > always. About 7 minutes using configuration stm32f4discovery with > realtime virus checking off. [That is disappointing to me because I > just built hot new Rizen 5 PC and expected better]. It's more than half an hour here with an (older) I7-3770. I will have a look today. Johannes
Re: FAR for pointer to pointer
On Tue, May 26, 2020 at 8:05 PM Alan Carvalho de Assis wrote: > > man strtoul my question was about FAR. strtoul is just an example. > > On 5/25/20, Takashi Yamamoto wrote: > > hi, > > > > our strtoul prototype is: > > > > unsigned long strtoul(FAR const char *nptr, FAR char **endptr, int > > base); > > > > why shouldn't they be like, say, "FAR char * FAR * endptr"? > >
Showing all registered IRQs in /proc/irqs interface
I was trying to debug something today where I was dynamically registering some IRQs and I was trying to figure out what was wrong because they did not show up in /prov/irqs. This seems to be the expected behavior, but I am not sure why we would not want to show all the registered IRQs just because they have not yet been triggered. The /proc interface is more likely to be used for capturing diagnostic information I would be in favor of dropping this restriction --Brennan
Re: Arm Kinetis: set_errno in nx_start with CONFIG_TLS_ALIGNED not set
I'm currently updating MSYS2, and will then repeat the build. Then I'll test on another computer. And when it's happening there as well, I'll try to narrow down the reason. I just configured a new computer and I am having problems with MSYS2. I can't even create the "symbolic" links needed at start up. I am not sure why. Probably some priveleges issues. But I did verify the build on Cygwin and it was about the same as always. About 7 minutes using configuration stm32f4discovery with realtime virus checking off. [That is disappointing to me because I just built hot new Rizen 5 PC and expected better]. Windows WSL is only a little faster. If fast build turn-around time is what you need, you can't beat Linux. I am seeing build times in the 30 second range there. I used to get about 10-15 seconds in the past, I think the ARM Embedded Toolchain is a lot slower these days. I have heard people in the past who got the build time down to 7 seconds in the past. For me, I can live with 7 minutes for the convenience of using my Windows desktop.
RE: Arm Kinetis: set_errno in nx_start with CONFIG_TLS_ALIGNED not set
> -Original Message- > From: Gregory Nutt [mailto:spudan...@gmail.com] > Sent: Tuesday, May 26, 2020 4:20 PM > To: dev@nuttx.apache.org > Subject: Re: Arm Kinetis: set_errno in nx_start with CONFIG_TLS_ALIGNED > not set > > > Today I had time to return to nuttx and rebased to master. > > But after doing a distclean and configuration, the build process on MSYS2 is > extremely slow. It takes hours for a build with "make -j8 V=1". > > I already had my company admin disable antivirus. Had there been a > change in the process? > > I use both MSYS2 and Cygwin (really both Cygwin) and have not noticed > any slowdown using Cygwin ... still minutes, certainly not hours. I > haven't used MSYS2 in some time. > > Perhaps you could do a git bisect and see if there is some particular > commit that introduced the MSYS2 problem > I'm currently updating MSYS2, and will then repeat the build. Then I'll test on another computer. And when it's happening there as well, I'll try to narrow down the reason.
RE: Arm Kinetis: set_errno in nx_start with CONFIG_TLS_ALIGNED not set
Thanks a lot for the fixes. Yes I know that I won't have stdio in this configuration. I followed the README of stm32f429i-disco concerning CDC/ACM console, and it's for testing/playing anyway. Today I had time to return to nuttx and rebased to master. But after doing a distclean and configuration, the build process on MSYS2 is extremely slow. It takes hours for a build with "make -j8 V=1". I already had my company admin disable antivirus. Had there been a change in the process? Regards, Johannes > -Original Message- > From: Gregory Nutt [mailto:spudan...@gmail.com] > Sent: Saturday, May 23, 2020 5:02 PM > To: dev@nuttx.apache.org > Subject: Re: Arm Kinetis: set_errno in nx_start with CONFIG_TLS_ALIGNED > not set > > > > PR #1105 should eliminate the primary cause of the error: fs_fdopen() > > will not longer set the errno variable. The secondary error, the > > uninitialized stack description, is still a problem. > Since the errno value was only set before fs_fdopen() failed, this means > that you system will still not work. It should not crash but it should > not work either. Now the fs_fdopen() calls will silently and > mysteriously fail, perhaps with the only symptom being no standard I/O > in the started tasks.
Re: FAR for pointer to pointer
man strtoul On 5/25/20, Takashi Yamamoto wrote: > hi, > > our strtoul prototype is: > > unsigned long strtoul(FAR const char *nptr, FAR char **endptr, int > base); > > why shouldn't they be like, say, "FAR char * FAR * endptr"? >
