Re: Problems and a bug in samd2l2 ADC code

On Fri, Oct 30, 2020 at 12:26:33PM +0100, Bernd Walter wrote: > On Thu, Oct 29, 2020 at 07:39:16PM -0300, Alan Carvalho de Assis wrote: > > Ok, now I understood the issue you found > > > > Yes, arch/arm/include/samd2l2/sam_adc.h is wrong. > > > > I think this file shouldn't exit, it doesn't exist

Re: Problems and a bug in samd2l2 ADC code

Hi Bernd, On 11/2/20, Bernd Walter wrote: sic > > Well, thiss is all weird. > My Chip is a SAMD21E17A, so it has only 16k RAM. > I had been using in in another project with my own IO code and NXFFS on > an SPI flash (W25), but had to reduce stack sizes to have enough RAM > for the NXFFS. Well, 1

Re: LVGL moving to Kconfig, how we could integrated better with them

Hi Gábor, On 11/2/20, Gábor Kiss-Vámosi wrote: sic > > Why is it not an issue with other projects you use in NuttX? Have we missed > something? > This is the first time we need to integrate with an external library that uses Kconfig and have more configuration options. All other libraryies/appli

Re: LVGL moving to Kconfig, how we could integrated better with them

whoa, I did so many mistakes (it happens everything I don't sleep well) Let's see it: On 11/2/20, Alan Carvalho de Assis wrote: > Hi Gábor, > > On 11/2/20, Gábor Kiss-Vámosi wrote: > sic >> >> Why is it not an issue with other projects you use in NuttX? Have we >> missed >> something? >> > This

Re: LVGL moving to Kconfig, how we could integrated better with them

On Mon, Nov 2, 2020, at 09:51, Gábor Kiss-Vámosi wrote: > Hi, > >> BTW, is LVGL going to provide a script to convert the Kconfig to a >> lv_config.h of some sort? If that's the case we'll only have to call >> the script after we download the tarball. > > Yes, We have lv_conf_internal.h >

Re: LVGL moving to Kconfig, how we could integrated better with them

Hi Gabor, we just recently added a __NuttX__ macro as part of our base compilation flags, so I guess it should be: #ifdef __NuttX__ #include #endif What do others think? BTW, are you thinking of a single root Kconfig or a series of nested Kconfigs? The latter would be a bit more difficult to

Re: LVGL moving to Kconfig, how we could integrated better with them

I see, thanks for the explanation. I understand that we can consider each project to be configured separately, > but IMHO it would be great if we could just > use your Kconfig files as part of Kconfig system (having the Kconfig files > downloaded previously, as I suggested). If your internal heade

Re: LVGL moving to Kconfig, how we could integrated better with them

Hi, BTW, is LVGL going to provide a script to convert the Kconfig to a > lv_config.h of some sort? If that's the case we'll only have to call > the script after we download the tarball. Yes, We have lv_conf_internal.h that tr