Do you have enough gpio's available to dedicate two pins per switch? If
so, just tie them in pairs, program one of the pair to interrupt high,
the other low.
On 3/17/25 14:18, Matteo Golin wrote:
Hello everyone,
I have an application wherein I am using a W5500-EVB Pico as the MCU for a
netwo
Hello everyone,
I have an application wherein I am using a W5500-EVB Pico as the MCU for a
network controlled system. I need to connect
several switch inputs into this MCU. The switches are normally held high via
the RP2040's internal pullups, and pulled
low when flipped.
The problem I'm encoun
Hello all,
I fully agree with you Mark, hence my question.
Though your point would only be true if we deprecate nxstyle. Maintenance
or adding new features is still work/time spent.
It's just that, at current time I'm willing to spend my time on a new
implementation. I would argue it's the better
Hi all,
I'm a strong supporter of linting tools that can save us work during
development. In fact, I added the pre-commit-config to NuttX so I can apply
nxstyle at each commit in a "nicer" way (even though I'm sure most people are
not aware of it).
Honestly, if this was a new project, I would
A couple of things to bear in mind:
- Perfection is the enemy of good
- Would you rather maintain a tool for styling or work on Apps/OS code?
I agree that as it stands, clang-format does not always allow enforcement of
the exact style we would like but if it is nearly there is it worth looking a
Hi,
I do agree with clang format part, if we are to alter existing style it
will mean to maintain it ourselves, on some codebase that is not nuttx, I
would avoid that.
About the other part, I do not fully agree.
If we take 2019 - 2025 period, Nuttx has changed more than Python. I'm a
new contribu
The main issue I was facing with clang-format was the indentation with NuttX
BreakBeforeBraces style see
https://github.com/llvm/llvm-project/issues/44188
Regards,
Peter
-Original Message-
From: Nathan Hartman
Sent: Monday, March 17, 2025 2:39 PM
To: dev@nuttx.apache.org
Subject: Re: [
Regarding the missing features in clang format, have you considered opening
feature requests for these with the clang devs?
Regarding a nxtool with multiple subcommands for things, such as style
checking, this is an interesting idea that should be explored.
My only concern is with the addition of
Hello,
I have tried to make a clang format configuration to use, but I have the
same problem where there are a couple style items that clang format has no
options for. Things like enforcing lowercase hex or putting curly braces
indented on a separate line after static initializers.
On Mon, Mar 17
Has anyone looked at using a custom .clang-format file to see if we can get
close to the NuttX style?
I’ve used this route in a couple of projects. I did have to compromise on one
or two rules as I could not get the exact format I wanted. I thought this was
worth it as it saved me writing my
Hello Nuttx,
*--- Summary ---*
I've been in the habit of fixing small issues regarding nxstyle.
One of the last conclusions drawn was that it does not tokenize the file,
which leads to limitations in checking syntax.
Please check https://github.com/apache/nuttx/pull/15847 for further details.
I
11 matches
Mail list logo
