Re: Same70 adc

Very nice Simon! It's a relief to hear that! Welcome aboard! BR, Alan On 8/3/21, Simon Filgis wrote: > Hi Alan, > > that is what I started today. It turns out to be a good exercise. > > Nuttx is fun :) > > Regards, > > Simon > > -- > > Alan Carvalho de Assis schrieb am Di., 3. Aug. 2021, >

Re: Same70 adc

Hi Alan, that is what I started today. It turns out to be a good exercise. Nuttx is fun :) Regards, Simon -- Alan Carvalho de Assis schrieb am Di., 3. Aug. 2021, 17:27: > Hi Simon, > > I didn't look the SAME70 datasheet/reference manual, but probably the > ADC is similar to SAMA5, normally

Re: esp32-wrover-kit:lvgl lvgldemo not working properly

Hi Murat, All you need to do is to define: CONFIG_INPUT_TOUCHSCREEN (and enable your touchscreen driver) and CONFIG_EXAMPLES_LVGLDEMO_CALIBRATE Your touchscreen device needs to be at /dev/input0 Look at apps/examples/lvgldemo, it is very straightforward. If your touchscreen is not

Re: esp32-wrover-kit:lvgl lvgldemo not working properly

Hi @Barbiani, I got a 3.2" resistive touch panel from Buydisplay, however I would like to use it with ADS7843e controller using nuttx/drivers/input/ads7843e.c instead of connecting it direct to ESP32 ADC inputs as you did, however I'm not experienced enough in lvgl so I don't know how to make

Re: Same70 adc

Hi Simon, I didn't look the SAME70 datasheet/reference manual, but probably the ADC is similar to SAMA5, normally the manufacturer reuse their IP around many chips families. Please use the arch/arm/src/sama5/sam_adc.c as reference to implement the same70 ADC driver. BR, Alan On 8/3/21, Simon

Re: Introduction + incoming RISC-V port(s)

Hi Robert, We all here appreciate your effort to make it happen, but I think you also started things very badly. No matter what was your previous culture, we never arrive at someone home and start talking bad things about their furniture and/or their children. We all here was very patience to

Same70 adc

Dear all, has anybody implemented adc for same70? That would be nice! Regards, Simon

Re: ./tools/configure.sh | find -L | to follow symlinks

Better! Thank you! On Tue, Aug 3, 2021 at 10:20 AM Abdelatif Guettouche < abdelatif.guettou...@gmail.com> wrote: > > Regarding my advice from a few minutes ago. Somebody in > > > https://github.com/apache/incubator-nuttx/issues/2206#issuecomment-721138548 > > complains that > > the process is

Re: ./tools/configure.sh | find -L | to follow symlinks

> Regarding my advice from a few minutes ago. Somebody in > https://github.com/apache/incubator-nuttx/issues/2206#issuecomment-721138548 > complains that > the process is not working. That's only when the board is part of a group that has the "common" directory and the common directory isn't

Re: ./tools/configure.sh | find -L | to follow symlinks

Regarding my advice from a few minutes ago. Somebody in https://github.com/apache/incubator-nuttx/issues/2206#issuecomment-721138548 complains that the process is not working. Just to be sure I will test it today and maybe finish that documentation. If I won't, still just try what is described

Re: ./tools/configure.sh | find -L | to follow symlinks

What's the reason for symlinking the custom board to the in-tree boards/ folder? The configuration script accepts a relative path to a custom location. On Tue, Aug 3, 2021 at 9:56 AM Simon Filgis wrote: > > Dear all, > > I have my own board assembled with Atmel SAME70 and I would like to work

Re: ./tools/configure.sh | find -L | to follow symlinks

In general, you probably don't want to change files in the OS repository just to attach your board. I was supposed to document how to do this correctly, more than a half year ago. I didn't, but what you need is described in this issue

./tools/configure.sh | find -L | to follow symlinks

Dear all, I have my own board assembled with Atmel SAME70 and I would like to work on the board files "outside" the nuttix structure in a separate folder (custom_board). Now I symlinked my custom_board folder into nuttx: cd ../nuttx/boards/arm/samv7 > ln -s ../../../../custom_board/ custom_board

Re: Introduction + incoming RISC-V port(s)

This iteration of BeagleV hardware is canceled . Given the friction of landing PR#3965, I'm just going to abandon it and mark that CL closed and will be unsubscribing from the lists. There's probably nothing worth heroic efforts to preserve; only a few of those 108 commits