Build failed in Jenkins: NuttX-Nightly-Build #100

[Apache Jenkins Server]

See 

Changes:


--
[...truncated 292.71 KB...]

Configuration/Tool: sim/sixlowpan

  Cleaning...
  Configuring...
  Copy files
  Select CONFIG_HOST_LINUX=y
  Refreshing...
  Building NuttX...


Skipping: sim/cxxtest

Configuration/Tool: sim/nettest

  Cleaning...
  Configuring...
  Copy files
  Select CONFIG_HOST_LINUX=y
  Refreshing...
  Building NuttX...


Skipping: sim/nxwm

Configuration/Tool: sim/ipforward

  Cleaning...
  Configuring...
  Copy files
  Select CONFIG_HOST_LINUX=y
  Refreshing...
  Building NuttX...


Configuration/Tool: sim/nx

  Cleaning...
  Configuring...
  Copy files
  Select CONFIG_HOST_LINUX=y
  Refreshing...
  Building NuttX...


Configuration/Tool: sim/ostest

  Cleaning...
  Configuring...
  Copy files
  Select CONFIG_HOST_LINUX=y
  Refreshing...
  Building NuttX...


Configuration/Tool: sim/mount

  Cleaning...
  Configuring...
  Copy files
  Select CONFIG_HOST_LINUX=y
  Refreshing...
  Building NuttX...


Configuration/Tool: sim/module

  Cleaning...
  Configuring...
  Copy files
  Select CONFIG_HOST_LINUX=y
  Refreshing...
  Building NuttX...


Configuration/Tool: sim/minibasic

  Cleaning...
  Configuring...
  Copy files
  Select CONFIG_HOST_LINUX=y
  Refreshing...
  Building NuttX...


Configuration/Tool: sim/tcpblaster

  Cleaning...
  Configuring...
  Copy files
  Select CONFIG_HOST_LINUX=y
  Refreshing...
  Building NuttX...


Configuration/Tool: sim/touchscreen

  Cleaning...
  Configuring...
  Copy files
  Select CONFIG_HOST_LINUX=y
  Refreshing...
  Building NuttX...


Configuration/Tool: sim/bas

  Cleaning...
  Configuring...
  Copy files
  Select CONFIG_HOST_LINUX=y
  Refreshing...
  Building NuttX...


Configuration/Tool: sim/mtdpart

  Cleaning...
  Configuring...
  Copy files
  Select 

Re: Adding support for STM32G474RET6

[Nathan Hartman]

I've begun work on supporting the STM32G474RET6, and also the
B-G474E-DPOW1 Discovery board.

So far I don't have much to show, but hopefully there will be much
more in the coming days. What I have so far is in my fork, in a branch
called stm32g474:

https://github.com/hartmannathan/incubator-nuttx/tree/stm32g474

I'll be back with news and updates, and probably lots more questions!!!

Cheers,
Nathan

Re: The new Apache NuttX Logo

[Gregory Nutt]

I think if everybody send it as SVG we couldn't have any issue. And
because SVG is a common standard all good graphic design software
supports it.
That is unnecessary.  SVG will only be required for the single graphic 
that is selected for the logo.  It is not needed for any of the others.

porting imxrt/cxd5602 SD Card driver to sama5 - questions

[Adam Feuer]

Hi,

I'm trying to port the imxrt SD Card driver (imxrt_usdhc.c) to the
sama5d27. Both chips appear to use similar Cadence IP blocks... the
registers appear to be almost identical. I know the SDMMC peripheral and
the SD Card both work since I can boot from it using U-Boot on the
SAMA5D2-XULT board.

I have the driver compiling and I can get SDMMC peripheral reset and the
clock started and stabilized. (I think.) However, I can't seem to receive
command responses from the SD Card... I just receive timeouts.
See below for some debug logging. Source code is here on this branch
.
Here's the sam_sdmmc.c driver file, which corresponds to the imxrt_usdhc.c
file.

Does anyone have any tips about how to debug this driver? Did anyone do a
port of this driver? If so how did you debug it or get it working? I know
the Sony cxd5602 and imxrt family both use this driver.

cheers
adam
-- 
Adam Feuer 

[0.00] sam_rng_initialize: Initializing TRNG hardware
[3.45] nsh_main: custinfo: Entry
[3.45] nsh_main: mcinfo: Entry
[3.46] nsh_initialize: Entry
[3.46] nsh_initialize: about to mount romfs
[3.47] board_app_initialize: custinfo: Here 0.1
[3.47] board_app_initialize: mcinfo: Here 0.2
[3.48] sam_sdmmc_initialize: Entry.
[3.48] sam_sdmmc_sdio_initialize: sdio init
[3.49] sam_reset: Reset complete
[3.49] sam_clock: DISABLED, SYSCTRL: 
[3.50] sam_reset: SYSCTL:  PRSSTAT: 01ff IRQSTATEN:
117f01ff
[3.50] sam_dumpsample: SDMMC Registers: After reset
[3.51] sam_dumpsample:DSADDR[]: 040e
[3.52] sam_dumpsample:   BLKATTR[0004]: 0010040e
[3.52] sam_dumpsample:CMDARG[0008]: 0020040e
[3.53] sam_dumpsample:XFERTY[000c]: 00300416
[3.53] sam_dumpsample:   CMDRSP0[0010]: 00400416
[3.54] sam_dumpsample:   CMDRSP1[0014]: 00500416
[3.55] sam_dumpsample:   CMDRSP2[0018]: 00600416
[3.55] sam_dumpsample:   CMDRSP3[001c]: 00700416
[3.56] sam_dumpsample:   PRSSTAT[0024]: 
[3.56] sam_dumpsample:PROCTL[0028]: 
[3.57] sam_dumpsample:SYSCTL[002c]: 
[3.58] sam_dumpsample:   IRQSTAT[0030]: 
[3.58] sam_dumpsample: IRQSTATEN[0034]: 
[3.59] sam_dumpsample:  IRQSIGEN[0038]: 
[3.59] sam_dumpsample:   AC12ERR[003c]: 
[3.60] sam_dumpsample:  HTCAPBLT[0040]: 
[3.60] sam_dumpsample:   WML[0044]: 
[3.61] sam_dumpsample:ADMAES[0054]: 
[3.62] sam_dumpsample:   ADSADDR[0058]: 
[3.62] sam_dumpsample:VENDOR[00c0]: 
[3.63] sam_dumpsample:   MMCBOOT[00c4]: 
[3.63] sam_sdmmc_sdio_initialize: sdio init complete
[3.64] mmcsd_slotinitialize: minor: 0
[3.64] mmcsd_slotinitialize: in mmcd_slotinitnitialize
[3.65] mmcsd_slotinitialize: about to mmcd_hwinitialize
[3.66] mmcsd_hwinitialize: in mmcsd_hwinitialize
[3.66] mmcsd_hwinitialize: DMA supported: 0
[3.67] mmcsd_hwinitialize: Attached MMC/SD interrupts
[3.67] sam_registercallback: Register 0x2007374c(0x200ad880)
[3.68] sam_status: cdstatus=01
[3.68] mmcsd_probe: type: 0 probed: 0
[3.69] sam_status: cdstatus=01
[3.69] mmcsd_removed: type: 0 present: 1
[3.70] sam_clock: DISABLED, SYSCTRL: 
[3.70] sam_status: cdstatus=01
[3.71] sam_status: cdstatus=01
[3.71] sam_clock: IDMODE
[3.73] sam_clock: Waiting for SDMMC clock to stablize.
[3.73] sam_clock: SYSCTRL: 8003
[3.74] mmcsd_cardidentify: About to mmcsd_sendcmdpoll 1...
[3.74] sam_sendcmd: in sendcmd[3.75] sam_sendcmd: cmd:
 arg:  regval:  mcrval: 8000
[3.75] sam_sendcmd: sendcmd complete.
[3.86] sam_waitresponse: ERROR: Timeout cmd:  IRQSTAT:

[3.86] mmcsd_sendcmdpoll: ERROR: Wait for response to cmd: 
failed: -116
[3.87] mmcsd_cardidentify: About to mmcsd_sendcmdpoll 2...
[3.88] sam_sendcmd: in sendcmd[3.88] sam_sendcmd: cmd:
 arg:  regval:  mcrval: 8000
[3.99] sam_sendcmd: ERROR: Timeout (waiting CIHB) cmd: 
PRSSTAT: 01ff0001

Re: The new Apache NuttX Logo

[Alan Carvalho de Assis]

Thank you for this information Justin.

I think if everybody send it as SVG we couldn't have any issue. And
because SVG is a common standard all good graphic design software
supports it.

On 4/18/20, Justin Mclean  wrote:
> HI,
>
> https://apache.org/logos/ prefers svg, eps, ai or pdf. If you submit
> something else they will likely vectorise it for you and make them the right
> size. Central services can also help if it needed.
>
> Thanks,
> Justin

Re: The new Apache NuttX Logo

[Nathan Hartman]

On Sat, Apr 18, 2020 at 4:30 PM David Alessio 
wrote:

> I feel strongly about this.  "NuttX" preserves the origin of NuttX and the
> name of Mr. Gregory Nutt.  I think we need a logo that respects both.


I also feel strongly about keeping NuttX capitalized like this.

Having said so, I don't think the logo should include too much text because
that makes it hard to shrink down to very small sizes, in contexts where
that becomes necessary (e.g., website icon), and causes a need to have
alternate logos for those situations.

I think it's a good idea for a logo to fit within a square, with the
important part fitting within a circle, because icons are square and
because many social media sites etc automatically crop your logo to a
circle.

I'd like to work on a couple of logo ideas that are floating around in my
mind, so I hope there isn't any terrible rush to select a logo... let us
know if there's a timeframe in mind.

Thanks
Nathan

Re: The new Apache NuttX Logo

[Justin Mclean]

HI,

https://apache.org/logos/ prefers svg, eps, ai or pdf. If you submit something 
else they will likely vectorise it for you and make them the right size. 
Central services can also help if it needed.

Thanks,
Justin

Re: The new Apache NuttX Logo

[Alan Carvalho de Assis]

Hi Brennan,

Yes, I was planing to ask Xiang and Alin to submit those logos again as SVG.

Alin and Xiang, please resend those logos as SVG format (sorry I don't
have Corel, Ilustrator or other).

BR,

Alan

On 4/18/20, Brennan Ashton  wrote:
> Alan thanks for putting them up. Can we make sure we have vector files for
> all of them we will need this in the future. I assume the ones from Hans we
> do but I am not sure about the others.
>
> --Brennan
>
> On Sat, Apr 18, 2020, 12:47 AM Alan Carvalho de Assis 
> wrote:
>
>> Good point David!
>>
>> I got all logos from PDF and put it publicly visible:
>>
>> https://cwiki.apache.org/confluence/display/NUTTX/New+Apache+Nuttx+Logo
>>
>> None of those logo respect the original N and X and lowercase utt of
>> NuttX.
>>
>> I think Mr. Greg never enforced it too much, although he almost always
>> wrote NuttX.
>>
>> I recall Mr. Wolfgang Denx in the U-Boot mailing list always to scold
>> on people who misspelling it as uboot, u-boot, uBoot, etc.
>>
>> So I always called "NuttX as NuttX" and as you can see even in the URL
>> of NuttX Channel it is present:
>>
>> https://www.youtube.com/c/NuttXChannel
>>
>> BR,
>>
>> Alan
>>
>> On 4/14/20, David Alessio  wrote:
>> > I don’t wish to offend anyone but I object to all options on the basis
>> that
>> > “NuttX” should be spelled with capital ‘N’ and ‘X’, lowercase “utt”.
>> >
>> > Regards,
>> > -david
>> >
>> > Sent from my iPhone
>> >
>> >> On Apr 13, 2020, at 7:42 PM, Xiang Xiao 
>> >> wrote:
>> >>
>> >> The new logo could be viewed online here:
>> >> https://cwiki.apache.org/confluence/display/NUTTX/New+Apache+Nuttx+Logo
>> >> Please give your feedback and suggestoion.
>> >>
>> >> Thanks
>> >>
>> >> Xiang
>> >>
>> >>> On Tue, Apr 14, 2020 at 5:54 AM Justin Mclean <
>> jus...@classsoftware.com>
>> >>> wrote:
>> >>>
>> >>> Hi,
>> >>>
>> >>> It would be easy to put the image on your wiki / confluence.
>> >>>
>> >>> Justin
>> >
>>
>

Re: The new Apache NuttX Logo

[Brennan Ashton]

Alan thanks for putting them up. Can we make sure we have vector files for
all of them we will need this in the future. I assume the ones from Hans we
do but I am not sure about the others.

--Brennan

On Sat, Apr 18, 2020, 12:47 AM Alan Carvalho de Assis 
wrote:

> Good point David!
>
> I got all logos from PDF and put it publicly visible:
>
> https://cwiki.apache.org/confluence/display/NUTTX/New+Apache+Nuttx+Logo
>
> None of those logo respect the original N and X and lowercase utt of NuttX.
>
> I think Mr. Greg never enforced it too much, although he almost always
> wrote NuttX.
>
> I recall Mr. Wolfgang Denx in the U-Boot mailing list always to scold
> on people who misspelling it as uboot, u-boot, uBoot, etc.
>
> So I always called "NuttX as NuttX" and as you can see even in the URL
> of NuttX Channel it is present:
>
> https://www.youtube.com/c/NuttXChannel
>
> BR,
>
> Alan
>
> On 4/14/20, David Alessio  wrote:
> > I don’t wish to offend anyone but I object to all options on the basis
> that
> > “NuttX” should be spelled with capital ‘N’ and ‘X’, lowercase “utt”.
> >
> > Regards,
> > -david
> >
> > Sent from my iPhone
> >
> >> On Apr 13, 2020, at 7:42 PM, Xiang Xiao 
> >> wrote:
> >>
> >> The new logo could be viewed online here:
> >> https://cwiki.apache.org/confluence/display/NUTTX/New+Apache+Nuttx+Logo
> >> Please give your feedback and suggestoion.
> >>
> >> Thanks
> >>
> >> Xiang
> >>
> >>> On Tue, Apr 14, 2020 at 5:54 AM Justin Mclean <
> jus...@classsoftware.com>
> >>> wrote:
> >>>
> >>> Hi,
> >>>
> >>> It would be easy to put the image on your wiki / confluence.
> >>>
> >>> Justin
> >
>

RE: The new Apache NuttX Logo

[David Sidrane]

+1

-Original Message-
From: David Alessio [mailto:david.s.ales...@gmail.com]
Sent: Saturday, April 18, 2020 1:30 PM
To: dev@nuttx.apache.org
Cc: palomino...@gmail.com; 李骁; nand...@xiaomi.com; Hans
Subject: Re: The new Apache NuttX Logo

I feel strongly about this.  "NuttX" preserves the origin of NuttX and the
name of Mr. Gregory Nutt.  I think we need a logo that respects both.

On Sat, Apr 18, 2020 at 12:47 AM Alan Carvalho de Assis 
wrote:

> Good point David!
>
> I got all logos from PDF and put it publicly visible:
>
> https://cwiki.apache.org/confluence/display/NUTTX/New+Apache+Nuttx+Logo
>
> None of those logo respect the original N and X and lowercase utt of
> NuttX.
>
> I think Mr. Greg never enforced it too much, although he almost always
> wrote NuttX.
>
> I recall Mr. Wolfgang Denx in the U-Boot mailing list always to scold
> on people who misspelling it as uboot, u-boot, uBoot, etc.
>
> So I always called "NuttX as NuttX" and as you can see even in the URL
> of NuttX Channel it is present:
>
> https://www.youtube.com/c/NuttXChannel
>
> BR,
>
> Alan
>
> On 4/14/20, David Alessio  wrote:
> > I don’t wish to offend anyone but I object to all options on the basis
> that
> > “NuttX” should be spelled with capital ‘N’ and ‘X’, lowercase “utt”.
> >
> > Regards,
> > -david
> >
> > Sent from my iPhone
> >
> >> On Apr 13, 2020, at 7:42 PM, Xiang Xiao 
> >> wrote:
> >>
> >> The new logo could be viewed online here:
> >> https://cwiki.apache.org/confluence/display/NUTTX/New+Apache+Nuttx+Logo
> >> Please give your feedback and suggestoion.
> >>
> >> Thanks
> >>
> >> Xiang
> >>
> >>> On Tue, Apr 14, 2020 at 5:54 AM Justin Mclean <
> jus...@classsoftware.com>
> >>> wrote:
> >>>
> >>> Hi,
> >>>
> >>> It would be easy to put the image on your wiki / confluence.
> >>>
> >>> Justin
> >
>

Re: The new Apache NuttX Logo

[David Alessio]

I feel strongly about this.  "NuttX" preserves the origin of NuttX and the
name of Mr. Gregory Nutt.  I think we need a logo that respects both.

On Sat, Apr 18, 2020 at 12:47 AM Alan Carvalho de Assis 
wrote:

> Good point David!
>
> I got all logos from PDF and put it publicly visible:
>
> https://cwiki.apache.org/confluence/display/NUTTX/New+Apache+Nuttx+Logo
>
> None of those logo respect the original N and X and lowercase utt of NuttX.
>
> I think Mr. Greg never enforced it too much, although he almost always
> wrote NuttX.
>
> I recall Mr. Wolfgang Denx in the U-Boot mailing list always to scold
> on people who misspelling it as uboot, u-boot, uBoot, etc.
>
> So I always called "NuttX as NuttX" and as you can see even in the URL
> of NuttX Channel it is present:
>
> https://www.youtube.com/c/NuttXChannel
>
> BR,
>
> Alan
>
> On 4/14/20, David Alessio  wrote:
> > I don’t wish to offend anyone but I object to all options on the basis
> that
> > “NuttX” should be spelled with capital ‘N’ and ‘X’, lowercase “utt”.
> >
> > Regards,
> > -david
> >
> > Sent from my iPhone
> >
> >> On Apr 13, 2020, at 7:42 PM, Xiang Xiao 
> >> wrote:
> >>
> >> The new logo could be viewed online here:
> >> https://cwiki.apache.org/confluence/display/NUTTX/New+Apache+Nuttx+Logo
> >> Please give your feedback and suggestoion.
> >>
> >> Thanks
> >>
> >> Xiang
> >>
> >>> On Tue, Apr 14, 2020 at 5:54 AM Justin Mclean <
> jus...@classsoftware.com>
> >>> wrote:
> >>>
> >>> Hi,
> >>>
> >>> It would be easy to put the image on your wiki / confluence.
> >>>
> >>> Justin
> >
>

Re: Start of the NuttX 9.0 release cycle

[Gregory Nutt]

The final tag should have a format similar to the old one: nuttx-9.0.0
(or nuttx-9.0.0-rc1 for an RC)
The version.sh script needs the "-" to parse the tag.


It would seem that if we wanted to make an April 30 release, we should 
create the tarball now and ask for beta testers.  Or do you have some 
other plan to qualify the release.


Can the nightly build be directed to build the releasse branch?

Re: Start of the NuttX 9.0 release cycle

[Abdelatif Guettouche]

The final tag should have a format similar to the old one: nuttx-9.0.0
(or nuttx-9.0.0-rc1 for an RC)
The version.sh script needs the "-" to parse the tag.

On Sat, Apr 18, 2020 at 7:52 PM Brennan Ashton
 wrote:
>
> Looks good. I'll update my PR now that we have the updated format. I assume
> we will apply a tag for the RC and release so we will want to consume that
> correctly. I can do that today.
>
> Happy to upload the signed files to staging when we agree we are all ready
> to go.
>
> --Brennan
>
> On Sat, Apr 18, 2020, 11:04 AM Abdelatif Guettouche <
> abdelatif.guettou...@gmail.com> wrote:
>
> > > The patch, however, could be an option.  Some files will need to adapt
> > > to that though, not only the version.sh script.
> >
> > I submitted a PR for that. Please take a look.
> > (https://github.com/apache/incubator-nuttx/pull/827)
> >
> > I backported some trivial changes and bugfixes from master to the
> > release branch.  I guess once the release notes and this PR (if it
> > gets merged) are backported we can go ahead and create the tarballs
> > then call for a vote.
> >
> > Brennan, I understand that you have a script to upload the tarballs to
> > where they should be.  Can you do that once we get everything in
> > place?  They need to be signed as well.
> >
> >
> > On Thu, Apr 16, 2020 at 2:10 AM Abdelatif Guettouche
> >  wrote:
> > >
> > > I don't think we need to expose the RC, it's not the one that's going
> > > to be released.
> > > The patch, however, could be an option.  Some files will need to adapt
> > > to that though, not only the version.sh script.
> > >
> > >
> > > On Wed, Apr 15, 2020 at 5:33 PM Brennan Ashton
> > >  wrote:
> > > >
> > > > On Wed, Apr 15, 2020, 9:29 AM Abdelatif Guettouche <
> > > > abdelatif.guettou...@gmail.com> wrote:
> > > >
> > > > > > We should probably figure out how this patch would be represented
> > in code
> > > > > > and if we want to have 9.0.0-RC1 or whatever supported.
> > > > > What do you mean in code?
> > > > > A release will go through possibly multiple release candidates all
> > > > > tagged as 9.0.0-rcX, the final tag will be the same as the last
> > > > > accepted RC without the -rc suffix.
> > > > > Patches will have to go through the same process. With the voting in
> > > > > the incubator general list, etc.
> > > > >
> > > >
> > > > There is a version file that is generated but it only exposes major,
> > minor,
> > > > and build hash as defines for code to use. Do we need to extend the
> > code to
> > > > support a patch version? And should the RC be exposed to the code as
> > well
> > > > somehow (probably less important).
> > > >
> > > > >
> >

Re: Start of the NuttX 9.0 release cycle

[Brennan Ashton]

Looks good. I'll update my PR now that we have the updated format. I assume
we will apply a tag for the RC and release so we will want to consume that
correctly. I can do that today.

Happy to upload the signed files to staging when we agree we are all ready
to go.

--Brennan

On Sat, Apr 18, 2020, 11:04 AM Abdelatif Guettouche <
abdelatif.guettou...@gmail.com> wrote:

> > The patch, however, could be an option.  Some files will need to adapt
> > to that though, not only the version.sh script.
>
> I submitted a PR for that. Please take a look.
> (https://github.com/apache/incubator-nuttx/pull/827)
>
> I backported some trivial changes and bugfixes from master to the
> release branch.  I guess once the release notes and this PR (if it
> gets merged) are backported we can go ahead and create the tarballs
> then call for a vote.
>
> Brennan, I understand that you have a script to upload the tarballs to
> where they should be.  Can you do that once we get everything in
> place?  They need to be signed as well.
>
>
> On Thu, Apr 16, 2020 at 2:10 AM Abdelatif Guettouche
>  wrote:
> >
> > I don't think we need to expose the RC, it's not the one that's going
> > to be released.
> > The patch, however, could be an option.  Some files will need to adapt
> > to that though, not only the version.sh script.
> >
> >
> > On Wed, Apr 15, 2020 at 5:33 PM Brennan Ashton
> >  wrote:
> > >
> > > On Wed, Apr 15, 2020, 9:29 AM Abdelatif Guettouche <
> > > abdelatif.guettou...@gmail.com> wrote:
> > >
> > > > > We should probably figure out how this patch would be represented
> in code
> > > > > and if we want to have 9.0.0-RC1 or whatever supported.
> > > > What do you mean in code?
> > > > A release will go through possibly multiple release candidates all
> > > > tagged as 9.0.0-rcX, the final tag will be the same as the last
> > > > accepted RC without the -rc suffix.
> > > > Patches will have to go through the same process. With the voting in
> > > > the incubator general list, etc.
> > > >
> > >
> > > There is a version file that is generated but it only exposes major,
> minor,
> > > and build hash as defines for code to use. Do we need to extend the
> code to
> > > support a patch version? And should the RC be exposed to the code as
> well
> > > somehow (probably less important).
> > >
> > > >
>

Re: Start of the NuttX 9.0 release cycle

[Abdelatif Guettouche]

> The patch, however, could be an option.  Some files will need to adapt
> to that though, not only the version.sh script.

I submitted a PR for that. Please take a look.
(https://github.com/apache/incubator-nuttx/pull/827)

I backported some trivial changes and bugfixes from master to the
release branch.  I guess once the release notes and this PR (if it
gets merged) are backported we can go ahead and create the tarballs
then call for a vote.

Brennan, I understand that you have a script to upload the tarballs to
where they should be.  Can you do that once we get everything in
place?  They need to be signed as well.


On Thu, Apr 16, 2020 at 2:10 AM Abdelatif Guettouche
 wrote:
>
> I don't think we need to expose the RC, it's not the one that's going
> to be released.
> The patch, however, could be an option.  Some files will need to adapt
> to that though, not only the version.sh script.
>
>
> On Wed, Apr 15, 2020 at 5:33 PM Brennan Ashton
>  wrote:
> >
> > On Wed, Apr 15, 2020, 9:29 AM Abdelatif Guettouche <
> > abdelatif.guettou...@gmail.com> wrote:
> >
> > > > We should probably figure out how this patch would be represented in 
> > > > code
> > > > and if we want to have 9.0.0-RC1 or whatever supported.
> > > What do you mean in code?
> > > A release will go through possibly multiple release candidates all
> > > tagged as 9.0.0-rcX, the final tag will be the same as the last
> > > accepted RC without the -rc suffix.
> > > Patches will have to go through the same process. With the voting in
> > > the incubator general list, etc.
> > >
> >
> > There is a version file that is generated but it only exposes major, minor,
> > and build hash as defines for code to use. Do we need to extend the code to
> > support a patch version? And should the RC be exposed to the code as well
> > somehow (probably less important).
> >
> > >

pulse counter using timer with external clock source

[Matias N.]

Hi,
with spare time in my hands due to quarantine I'm picking up a low-power 
project using STM32L4, prototyping over Nucleo L476RG board. I'm using LPTIM 
timers, one as PWM (I implemented that in the past) and would like to use the 
other as pulse-counter by configuring the timer as external clock source, which 
would count pulses from the given pin.

>From the user-side, I could expose this via the qencoder driver (in this case, 
>pulses would only go up), although maybe eventually the "qencoder" could be 
>generalized to "pulse counter". Now, I could have a lower-half driver that 
>calls into stm32l4_lptim_* functions to initialize timer in pulse-counter mode 
>and allow to retrieve/reset counter. By looking at stm32l4_lptim.h/c I would 
>need to extend stm32l4_lptim_setmode to include a new "pulse counter" mode 
>flag which would just enable the timer (no single/continuous setting). Then I 
>would need to add a function to allow setting counter mode (external 
>clock/source, external clock+internal source, internal clock+source) and when 
>to count (rising, falling, both edges). Also, I would expose the counter via a 
>getcounter function.

Would this be the correct way to expose the pulse-counter functionality of 
LPTIM? I think it is most similar to how the common TIM functionality is 
exposed in stm32l4_tim.h/c.

Thanks,
Matias

Re: The new Apache NuttX Logo

[Alan Carvalho de Assis]

Good point David!

I got all logos from PDF and put it publicly visible:

https://cwiki.apache.org/confluence/display/NUTTX/New+Apache+Nuttx+Logo

None of those logo respect the original N and X and lowercase utt of NuttX.

I think Mr. Greg never enforced it too much, although he almost always
wrote NuttX.

I recall Mr. Wolfgang Denx in the U-Boot mailing list always to scold
on people who misspelling it as uboot, u-boot, uBoot, etc.

So I always called "NuttX as NuttX" and as you can see even in the URL
of NuttX Channel it is present:

https://www.youtube.com/c/NuttXChannel

BR,

Alan

On 4/14/20, David Alessio  wrote:
> I don’t wish to offend anyone but I object to all options on the basis that
> “NuttX” should be spelled with capital ‘N’ and ‘X’, lowercase “utt”.
>
> Regards,
> -david
>
> Sent from my iPhone
>
>> On Apr 13, 2020, at 7:42 PM, Xiang Xiao 
>> wrote:
>>
>> The new logo could be viewed online here:
>> https://cwiki.apache.org/confluence/display/NUTTX/New+Apache+Nuttx+Logo
>> Please give your feedback and suggestoion.
>>
>> Thanks
>>
>> Xiang
>>
>>> On Tue, Apr 14, 2020 at 5:54 AM Justin Mclean 
>>> wrote:
>>>
>>> Hi,
>>>
>>> It would be easy to put the image on your wiki / confluence.
>>>
>>> Justin
>