ch trouble to
> (re)create.
>
> Once (if) I am sure it is not as simple as a config error I will raise is
> as an issue but, for now, I'm inclined to think it's down to me.
>
> If I get nowhere tomorrow morning, I'll email you my config: a second
> opinion wo
; can never be as clear cut as it being a bug to report!
>
> If you happen to have a config that works for this it would be useful for
> sure, but I will plug away at it more tomorrow as the syslog port not
> behaving is probably a big clue.
>
> Regards,
>
> Tim.
> On 16/08/
y is expecting there to be a serial
> console). It's in lowput.c and I've fixed that by comparing to samv7 and,
> for now, disabling debug assertions.
>
> --
> Stopped that email draft at this point and switched tack as I'd found I
> could get it t
feature.
>
> So, start looking what the boards from other arch enable to get USB
> CDC/ACM working as console.
> And because there is no usbnsh board config for this chip, maybe it
> needs more investigation.
>
> I'm CC Adam, maybe he already tested it on Jupiter Nano board.
>
> BR,
>
> Alan
>
--
Adam Feuer
esting the creation of NuttX Channel at Hackster.io
> >> platform.
> >>
> >> As NuttX is part of Apache Software Foundation I'm CC our team members
> >> (PMC and Committers) asking for their agreement.
> >>
> >> Please respond to ALL with +1 or ACK.
> >>
> >> BR,
> >>
> >> Alan
> >
> >
> >
> > --
> > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> >
>
--
Adam Feuer
Alin,
Thanks, I would love your help on the next release, I'm looking forward to
working together.
cheers
adam
On Wed, Sep 23, 2020 at 11:15 PM Jerpelea, Alin
wrote:
> HI Brennan,
>
> The release schedule looks god.
>
> @Adam Feuer
> I want to help you on the next rele
be the release manager again for this one. But it would be great
> if someone else jumps in for the release after and I will try to
> document things a bit more to make the process easier. We will need
> to have more than one release manage to graduate, there are other
> projects that have run into this.
>
> --Brennan
>
--
Adam Feuer
before proceeding?
>
> Cheers,
> Nathan
>
--
Adam Feuer
gt; can
> > port the exfat-linux project:
> >
> > https://github.com/arter97/exfat-linux
>
>
> I do not think we will go that path right now, but it would be nice to
> have the support of course so you could throw pretty much any SD-card into
> the game without thinking about such compatibility issues. Something for
> the long TODO-in-the-future list!
>
> //Pelle
>
--
Adam Feuer
a5d27-giantboard-support/boards/arm/sama5/giant-board
I'll try to get this to be more reliable and then do a PR.
-adam
On Thu, Aug 20, 2020 at 4:01 PM Adam Feuer wrote:
> Matias,
>
> Thanks for the help. It was an incorrect master clock setting for the
> board. I updated the Giant Boa
interesting, but off topic, ESP32 Altair Emulator:
> > >
> https://hackaday.com/2020/08/20/esp32-altair-emulator-gets-split-personality/
> > >
> > >
> >
>
--
Adam Feuer
at 10:41 PM Adam Feuer wrote:
> Matias,
>
> Thanks, I have a logic analyzer and will try that when I pick it up again.
> The weird thing about this is that I can use U-Boot on the serial console
> on the Giant Board – it knows how to use the UART correctly. But NuttX
> doesn'
out real debugging it will be painful to use.
>
> Best,
> Matias
>
--
Adam Feuer
ree. If you have any ideas I'd like to know them. I'm stuck.
-adam
On Wed, Aug 19, 2020 at 10:55 AM Adam Feuer wrote:
> Greg,
>
> That keyboard/screen combo looks pretty cool. I'll see if I can come up
> with a use for it. :)
>
> -adam
>
> On Wed, Aug 19, 2020
Greg,
That keyboard/screen combo looks pretty cool. I'll see if I can come up
with a use for it. :)
-adam
On Wed, Aug 19, 2020 at 10:52 AM Adam Feuer wrote:
> Greg, Matias,
>
> Yes, I'm still working on NuttX for Giant Board, and the ACME RoadRunner
> <https://www.
ts/arturo182/keyboard-featherwing-qwerty-keyboard-26-lcd/
> >
> > There is a "Solder Party" channel forum on discord.com. Groguard
> > discusses using the Giant Boards with the keyboard FeatherWing there.
> >
> > That could be a lot of fun. I am considering one myself, but I have no
> > feather boards to drive it.
> >
> >
>
--
Adam Feuer
Thanks for catching that Abdelatif.
I moved the NuttX project board here:
https://github.com/apache/incubator-nuttx/projects/2
We can delete it if we don't like it.
-adam
On Wed, Aug 12, 2020 at 11:43 AM Adam Feuer wrote:
> On Wed, Aug 12, 2020 at 11:40 AM Abdelatif Gu
On Wed, Aug 12, 2020 at 11:40 AM Abdelatif Guettouche <
abdelatif.guettou...@gmail.com> wrote:
> Was it intentional to create it in Apache's and not here:
> https://github.com/apache/incubator-nuttx/projects?
Oops. No. :) I'll move it or recreate it there.
-adam
gt; prioritize it, connecting it with releases and the things people have
> > > energy working on and collaborating together on?
> > >
> > > If what you want to put here doesn't fit on the page, make a child
> page. :)
> > We probably should also include all Github Issues that are listed as
> > enhancements.
>
--
Adam Feuer
On Wed, Aug 12, 2020 at 11:04 AM Gregory Nutt wrote:
> We probably should also include all Github Issues that are listed as
> enhancements.
>
If we use a Github Project Board like Brennan suggested this would be
pretty easy to link them there.
-adam
--
Adam Feuer
ennan Ashton
wrote:
> On Wed, Aug 12, 2020, 10:40 AM Adam Feuer wrote:
>
> > Folks,
> >
> > I made a wiki page with the raw list of things that people are asking for
> > in this thread:
> >
> > https://cwiki.apache.org/confluence/display/NUTTX/Roadmap
>
&
the important directions that operating system
> >> > > > > will
> >> > > take.
> >> > > > >
> >> > > > > For me, the important thing is to stay relevant and contemporary
> >> and
> >> > > > > not get lost in some aging niche architecture or toolset. I
> >> > > > > think
> >> > > > > that the best way to predict where NuttX needs to be is to look
> >> > > > > at
> >> the
> >> > > > > SoCs in use just above the upper end of the NuttX market. I
> >> > > > > think
> >> > > > > over time, those features will trickle down into embedded
> systems
> >> > > > > (albeit with some twists and modifications for the embedded
> >> market).
> >> > > > > The Cortex-M7 introduces I-Cache and L1 D-Cache, for example. A
> >> few
> >> > > > > years ago, those were higher end features not available on MCUs.
> >> > > > >
> >> > > > > I think that SMP and AMP are key technologies to get us a leg up
> >> > > > > on
> >> > > > > future mutli-core MCUs. KERNEL mode places us in a position to
> >> > > > > support MCUs with MMUs. A proper TrustZone model for all ARM
> >> parts is
> >> > > > > needed too (the multi-core TrustZone model is pretty well in
> >> > > > > place,
> >> > > > > but what do we do with TrustZone on a single CPU?).
> >> > > > >
> >> > > > > Security, especially IoT security is very important. Some
> >> > > > > security
> >> > > > > topics are addressed by PROTECTED mode. So although PROTECTED
> >> > > > > and
> >> > > > > KERNEL build modes are not commonly used, I believe that they
> >> > > > > are
> >> > > > > important parts of the roadmap.
> >> > > > >
> >> > > > > Other thoughts? We should collaborate and define a meaningful
> >> > > > > roadmap that will keep the OS healthy well into the future. We
> >> should
> >> > > > > publish that roadmap somewhere so that anyone can see where we
> >> > > > > are
> >> > > > > going and can offer insights for other directions.
> >> > > > >
> >> > > > >
> >> > > > >
> >> > >
> >> > >
> >> >
> >>
> >
>
--
Adam Feuer
TX/License+Clearing
We'll report back when we have some more information.
-adam
On Tue, Jul 28, 2020 at 5:38 PM Adam Feuer wrote:
> A focused effort to do the IP clearing sounds good. If we can get funding
> to do it quicker, that would be great too. It's a good idea.
>
> I di
es/LICENSE-2.0
>
> Unless required by applicable law or agreed to in writing, software
> distributed under the License is distributed on an "AS IS" BASIS,
> WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> See the License for the specific language governing permissions and
> limitations under the License.
>
> Thanks,
> Justin
--
Adam Feuer
ed. I think it is
> good for NuttX to make things clear from start.
>
> Just my 2 cents.
>
> BR,
>
> Alan
>
> On 8/1/20, Adam Feuer wrote:
> > Thanks Xiang.
> >
> > Does anyone else have feedback or improvement ideas?
> >
> > cheers
> >
and deploy itself. The nuttx repo can still do the
> build for
> > checking on PRs but it would not make the deploy.
> > >
> > > What do you think? It would be nice to receive confirmation that this
> is also pleasing by other users before continuing with the
> effort.
> > Also, in that case we can clean up these changes and start a PR on the
> main repo and start trying the final CI approach. After
> that we
> > could finalize migration of the most important parts of the previous
> docs (mainly the HTMLs).
> > >
> > > Best,
> > > Matias
>
>
--
Adam Feuer
for the A-to-B comparison. If we detect a size increase, then bloaty
> > should tell use why.
>
>
> It will do both so might as well just save the output of it. Basically on
> the CI job on merge into master we would generate the size/bloaty report
> and save these artifacts next to the build (we do this for the source
> bundle already)
>
> Then when the PR runs it would fetch this data from the master build and
> pass it to bloaty to run the comparison report for the given build and
> report it in the comments or something.
>
--
Adam Feuer
gt; >>
> >> We do have to make this happen and I don't blame anyone on the PPMC for
> >> not wanting to take this on. It would cost you the next year of your
> >> life .. full time. I wouldn't make that commitment and I would not
> >> expect any other individual to do so either.
> >>
> >> We some need a plan. With no plan, the project will not graduate. Even
> >> with a plan in hand, I would not expect graduation to be possible within
> >> the next year or more.
> >>
> >> Greg
> >>
> >>
> >>
>
--
Adam Feuer
ctly prohibited. If you have received this message in error, please
> notify the sender immediately by telephone at 407-679-9716, and delete this
> message and all copies and backups thereof. Thank you
>
--
Adam Feuer
is
> active when CONFIG_DEBUG_SYMBOLS is also active.
> So, I guess CONFIG_DEBUG_SYMBOLS is our general "debug" macro?
>
> My application will most probably need to know whether this is a debug
> build or not.
>
>
>
> Στις Σάβ, 25 Ιουλ 2020 στις 7:44 π.μ., ο/η Ada
On Fri, Jul 24, 2020, at 17:32, Nathan Hartman wrote:
> > On Fri, Jul 24, 2020 at 3:49 PM Adam Feuer wrote:
> > >
> > > On Fri, Jul 24, 2020 at 12:40 PM Gregory Nutt
> wrote:
> > >
> > > > a dumb script like that one Abdelatif demonstrated
> > &g
On Fri, Jul 24, 2020 at 12:40 PM Gregory Nutt wrote:
> a dumb script like that one Abdelatif demonstrated
> will multiple calls to kconfig-tweak can be used to turn on all of the
> configuration options that you need.
>
Cool!
-adam
--
Adam Feuer
uilds have assertions enabled, optimizations disabled, various
> > > checks enabled etc etc, while release builds the do the opposite.
> > >
> > > How is this best to be handled by NuttX? Should I have various
> > > configuration files to load each time, or is there a better way?
> >
> >
> > I keep two config files, one for debug, one for release. Very similar
> > except for the kinds of debugging options you mentioned.
> >
> > Nathan
> >
>
--
Adam Feuer
k we could use this issue
>
> https://github.com/apache/incubator-nuttx/issues/128
>
> To track the progress. First I think we should have a full image about the
> current status, and then we split the work into several pieces and try to
> finish them one by one.
>
> Than
nse headers before the next release, but I still want to know
> that, do we have a plan on it?
>
> Thanks.
>
--
Adam Feuer
, this allows to have something to show when by put a bit of
> content there for demonstration purposes.
> >
> > Will let you know when I get something to show.
> >
> > Best,
> > Matias
> >
> > On Tue, Jul 21, 2020, at 15:02, Adam Feuer wrote:
> &
Brennan,
Cool, that's awesome. I didn't know that discussion was going on in the PR.
:)
-adam
On Tue, Jul 21, 2020 at 10:55 AM Brennan Ashton
wrote:
> On Tue, Jul 21, 2020, 10:51 AM Adam Feuer wrote:
>
> > Matias, Maciej,
> >
> > Ok, I looked into doing a Sp
s
> in.
>
The current docs are pure HTML and text, so I don't think there are any
fonts in there.
-adam
--
Adam Feuer
: Longevity of the documents. If someone has a
> copy of the tarball and no Internet, they have the docs. I suppose this
> might be less of a concern today than it was in the past, but I think
> there's some legitimacy to it still.
>
> Nathan
>
--
Adam Feuer
thedocs.io/en/stable/
> >
> > For (1) I can start by porting the main README and maybe then we could
> distribute the task for all other READMEs.
> > Regarding (2), this repository would follow versioning of NuttX as well
> as mater. On the website one can choose which version of
> the
> > documentation to display.
> >
> > Best,
> > Matias
>
>
--
Adam Feuer
RST. However, Zephyr
went with "everything the same" and just uses RST (Zephyr supported boards
<https://docs.zephyrproject.org/latest/boards/index.html>; example board
Nitrogen
<https://docs.zephyrproject.org/latest/boards/arm/96b_nitrogen/doc/index.html>;
example board nitrogen RST on github
<https://github.com/zephyrproject-rtos/zephyr/blob/master/boards/arm/96b_nitrogen/doc/index.rst>
).
-adam
--
Adam Feuer
O) and either
> Markdown, RST,
> > > > or anything else for the eventual doc-repo. These are independent
> choices,
> > > > one does not have to affect the other. In fact, maybe RST is better
> for the
> > > > doc-repo, since it supports richer syntax more apropriate for
> building
> > > > documentation.
> > > >
> > > > Best,
> > > > Matias
> > >
>
--
Adam Feuer
uble_t is defined in include/sys/types.h, but we
> >> found that this definition may different from the toolchain's one, so
> this
> >> patch move the definition into include/nuttx/lib/math.h. Both case work
> >> correctly(no mismatch) until your case:
> >> 1.double_t come from include/nuttx/lib/math.h when we enable NuttX's
> libm
> >> 2.double_t come from toolchain's math.h when we enable toolchain's libm
> >>
> >> > One possible fix (currently using) is to typedef it inside compiler.h
> >> (for the AVR compiler), however, I don't know if this would be
> >> > correct since I see no other typedefs inside that file.
> >> >
> >>
> >> Another place is arch/avr/include/types.h, all arch specific types
> >> definition come from here.
> >>
> >> > Regards
> >>
> >>
>
--
Adam Feuer
gt;
> That said, I can help in both efforts, this is something I've been meaning
> to work on for sometime and there was simply no infrastructure available at
> the moment (that is why I worked on the NuttX GitBook but such effort is
> definitely not for just one person).
>
hedocs could possibly do it already, not sure.
> >
> > One of the reasons I really like the Zephyr docs is because of this, you
> > can see how they present their supported boards there:
> > https://docs.zephyrproject.org/latest/boards/index.html
> > Even further, each board description has a nice picture, specification
> > list, etc. I thank that would be really useful and easy to do (the
> picture
> > could be stored in some stable location and the README simply link to
> it).
> >
> > Best,
> > Matias
>
--
Adam Feuer
Both are SAMA5D27 boards I would like
to use in some projects.
-adam
On Thu, Jul 2, 2020 at 10:17 PM Adam Feuer wrote:
> Hi,
>
> I pushed a cleaned-up working SAMA5 SDMMC driver to this branch:
>
>
> https://github.com/starcat-io/incubator-nuttx/tree/feature/sama5d27-sdmmc-support
The driver wasn't handling SDMA Boundary Pause interrupts, so I had
to add handling code for it.
Just writing this here in case it helps anyone looking for how this was
solved.
I'm back on track.
-adam
On Wed, Jul 8, 2020 at 2:22 PM Adam Feuer wrote:
> The kmm_malloc() also
DINT being fired when I dump the SDMMC registers, but that
interrupt is not enabled for some reason... I'm trying to track it down now.
-adam
On Tue, Jul 7, 2020 at 9:09 PM Adam Feuer wrote:
> Greg,
>
> Thanks. I'll change the call to kmm_malloc() or kmm_memalign() and see if
> Other dependencies from Debian packages:
> > * binutils-dev 2.31.1-16
> > * bison 2:3.3.2.dfsg-1
> > * flex 2.6.4-6.2
> > * gperf 3.1-1
> > * libelf-dev 0.176-1.1
> > * libgmp-dev 2:6.1.2+dfsg-4
> > * libisl-dev 0.20-2
> > * libmpc-dev 1.1.0-1
> > * libmpfr-dev 4.0.2-1
> > * libncurses5-dev 6.1+20181013-2+deb10u2
> > * libusb-1.0-0-dev 2:1.0.22-2
> > * libusb-dev 2:0.1.12-32
> > * texinfo 6.5.0.dfsg.1-4+b1
> >
> > Thanks to everyone for making this release (candidate) possible!
> >
> > Cheers,
> > Nathan
> >
>
--
Adam Feuer
not work in all configurations.Instead include
> nuttx/kmalloc,h and call kmm_malloc(). If you want aligned memory, call
> kmm_memalgn().Sent from Samsung tablet.
> Original message From: Adam Feuer
> Date: 7/7/20 9:40 PM (GMT-06:00) To: dev@nuttx.apache.org Subject:
> driver q
I'd like to
take this otherwise useless code out, or at least know why I need it.
Link to the specific line of code in sam_sdmmc.c
<https://github.com/starcat-io/incubator-nuttx/blob/feature/sama5d27-sdmmc-support/arch/arm/src/sama5/sam_sdmmc.c#L3737>
cheers
adam
--
Adam Feuer
Hi,
I added a sim:nsh build to the new checkrelease.sh script, the PR is here:
https://github.com/apache/incubator-nuttx/pull/1382
If you're interested, you can try this out on the new 9.1.0-RC2 candidate
when it comes out.
cheers
adam
--
Adam Feuer
Hartman
> wrote:
> > Summary:
> > +1 to release
> >
> > Development system: Linux
> >
> > Verified:
> > * Signatures (note GPG reports the key is expired)
>
> Correction, follow-up: I re-imported the key. GPG no longer reports
> the key as expired. My vote remains +1.
>
> Cheers,
> Nathan
>
--
Adam Feuer
e size of the
> > developer base.
> >
>
> Exactly! A project with a broad audience will get more
> contributors/developers.
>
> BR,
>
> Alan
>
--
Adam Feuer
that public interface provided that we
> do not re-distribute the copyrighted XML files. Justin certainly will
> have a different opinion.
>
> Greg
>
>
>
>
--
Adam Feuer
STM, but here we
> are...
>
> https://raw.githubusercontent.com/posborne/cmsis-svd/master/data/STMicro/License.html
>
> TI is another example with further restrictions.
>
> https://github.com/posborne/cmsis-svd/blob/master/data/TexasInstruments/TM4C123GH6ZRB.svd
>
> --Brennan
&g
gt; NRF51_RADIO_TASKS_STOP_OFFSET)
> > #define NRF51_RADIO_TASKS_DISABLE (NRF51_RADIO_BASE +
> > NRF51_RADIO_TASKS_DISABLE_OFFSET)
> > #define NRF51_RADIO_TASKS_RSSISTART (NRF51_RADIO_BASE +
> > NRF51_RADIO_TASKS_RSSISTART_OFFSET)
> > #define NRF51_RADIO_TASKS_RSSISTOP (NRF51_RADIO_BASE +
> > NRF51_RADIO_TASKS_RSSISTOP_OFFSET)
> > ... etc
> >
> > Best,
> > Matias
>
--
Adam Feuer
t; NRF51_RADIO_TASKS_STOP_OFFSET)
> #define NRF51_RADIO_TASKS_DISABLE (NRF51_RADIO_BASE +
> NRF51_RADIO_TASKS_DISABLE_OFFSET)
> #define NRF51_RADIO_TASKS_RSSISTART (NRF51_RADIO_BASE +
> NRF51_RADIO_TASKS_RSSISTART_OFFSET)
> #define NRF51_RADIO_TASKS_RSSISTOP (NRF51_RADIO_BASE +
> NRF51_RADIO_TASKS_RSSISTOP_OFFSET)
> ... etc
>
> Best,
> Matias
--
Adam Feuer
g, and get a PR submitted for review.
cheers
adam
On Wed, Jun 17, 2020 at 9:19 PM Adam Feuer wrote:
> Thanks Nathan. It's been interesting learning how to port and debug NuttX
> drivers. Hopefully I will be able to write something about it when I get
> the code accepted.
>
>
512 and GPG signatures, and checks
required files.
You still need to manually configure, build, and install the release.
https://github.com/apache/incubator-nuttx/pull/1349
-adam
--
Adam Feuer
p;r=9PLdMPCoy-UxqQeL_7fkXjdHjEO-awBtN4-Wr8MqKGE&m=wCjDPfVu4jsGF5DRTbrxss5BggITyWdmP3EyHlWz9GA&s=g0xT5Mh8tFdW2MrZsQqjGDm15xIH7hxFJuVD1BZXQjg&e=
> > [5]
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.apache.org_confluence_display_NUTTX_Validating-2Ba-2Bstaged-2BRelease&d=DwIBaQ&c=fP4tf--1dS0biCFlB0saz0I0kjO5v7-GLPtvShAo4cc&r=9PLdMPCoy-UxqQeL_7fkXjdHjEO-awBtN4-Wr8MqKGE&m=wCjDPfVu4jsGF5DRTbrxss5BggITyWdmP3EyHlWz9GA&s=VeCYBTgAJpnIOqLZJYfNtIinMUYYiApT3UWeP91kuxs&e=
> >
>
--
Adam Feuer
t; >
> https://lists.apache.org/x/thread.html/rbb1f85b5f2dba9ee221548fcc5f99d49ef55522c487b99c1549c3a52@%3Cdev.nuttx.apache.org%3E
> >
>
>
> Yes, more time for testing sounds good to me.
>
> Thanks,
> Nathan
>
--
Adam Feuer
Greg,
Thank you! That is exactly what I was looking for!
-adam
On Fri, Jun 26, 2020 at 3:02 PM Gregory Nutt wrote:
> On 6/26/2020 3:43 PM, Adam Feuer wrote:
> > Hi,
> >
> > There used to be a web page that listed NuttX supported boards– but I
> can't
> >
Hi,
There used to be a web page that listed NuttX supported boards– but I can't
find it on the new nuttx.apache.org website. Does anyone know where that
page is?
cheers
adam
--
Adam Feuer
On Sun, Jun 21, 2020 at 2:23 PM Matias N. wrote:
> I have the serial console enabled, but this is very early in the boot.
>
> On Sun, Jun 21, 2020, at 18:02, Adam Feuer wrote:
> > (printf debugging only works if you can get far enough through the boot
> > sequence to initia
(printf debugging only works if you can get far enough through the boot
sequence to initialize a serial console. But that can happen pretty early.)
On Sun, Jun 21, 2020 at 2:01 PM Adam Feuer wrote:
> Do you have a serial console available? If so, you could use printf
> debugging
pressing the reset button. It only boots normally if I
> start debugging with OCD, which issues the reset from there. Since with the
> debugger it boots normally this is impossible to debug.
> Any similar experience?
>
> Best,
> Matias
--
Adam Feuer
ort porting efforts, but let's see first if
> I can receive it via a freight-forwarder service.
>
> Erdem
>
--
Adam Feuer
x27;t have to write it from
scratch. Takeyoshi suggested doing the port and he was right about it.
-adam
On Wed, Jun 17, 2020 at 5:46 PM Nathan Hartman
wrote:
> On Wed, Jun 17, 2020 at 5:49 PM Adam Feuer wrote:
>
> > SDMMC write is working now too. So the driver can do the following
t somewhat cleaned up.
-adam
On Mon, Jun 15, 2020 at 9:14 PM Adam Feuer wrote:
> SDMMC DMA read is working now too. I'll work on DMA write next.
>
> -adam
>
> On Fri, Jun 12, 2020 at 2:45 PM Adam Feuer wrote:
>
>> I got the SDMMC write to work as well. This is in no
SDMMC DMA read is working now too. I'll work on DMA write next.
-adam
On Fri, Jun 12, 2020 at 2:45 PM Adam Feuer wrote:
> I got the SDMMC write to work as well. This is in non-DMA mode. I'm going
> to work on the DMA mode next.
>
> -adam
> --
> Adam Feuer
>
--
Adam Feuer
I got the SDMMC write to work as well. This is in non-DMA mode. I'm going
to work on the DMA mode next.
-adam
--
Adam Feuer
or your help.
>
> Greg
>
> --
> You received this message because you are subscribed to the Google Groups
> "NuttX" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to nuttx+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/nuttx/e997fdca-9bec-f93b-70a4-3ea9804e4b45%40gmail.com
> .
>
--
Adam Feuer
ck that I
> did a long time ago here too:
> https://github.com/gregory-nutt/nuttx_ieee80211
>
>
>
--
Adam Feuer
>
That would be awesome. I will get clarification on that if I get some
replies to my other email to the mentors about the BSD driver layer.
-adam
--
Adam Feuer
arty code– it's BSD licensed, my understanding is that it can be brought
> in. Is that wrong?
>
> I see this in all of the files I looked at:
>
> // SPDX-License-Identifier: GPL-2.0
>
>
--
Adam Feuer
gt; that BSD licensed code may be included in an Apache project.
>
> But, unfortunately, that driver on github is GPL.
>
--
Adam Feuer
ss is as good as mine how and open source project is supposed to
> use fully compatible code. I wish I knew and I wish I could help people
> who want to make contributions. But I don't.
>
>
>
--
Adam Feuer
t case scenario, if I can create a compatibility layer, then we could
> use a variety of FreeBSD wifi drivers.
>
> There is a RTL8187 Wifi USB driver for NuttX that you can look at here
> attached. This was ported from Linux years ago and is GPL so you can't
> bring it into NuttX, but you can look at it. It is kind of useless with no
> ieee802.11 SoftMAC stack anyway.
>
>
>
--
Adam Feuer
p.com/DevelopmentTools/ProductDetails/PartNO/DM320117
> https://www.microchip.com/wwwproducts/en/ATWILC3000
>
> https://www.mouser.com/development-tools-center/embedded-processor-development-kits/development-boards-kits-arm/microchip-atsama5d27wlsom1-eval-kit/n-cxd2tZ34u2t9
>
> On
n Mon, May 4, 2020 at 3:29 PM Adam Feuer wrote:
> Takeyoshi,
>
> Hi, I've been working on the SDMMC driver off and on. I still haven't got
> it working, but I am making some progress. Here's a log of register reads
> and writes captured from U-Boot on the SAMA5D27:
&
ds the issues will enough and did, in fact, do a real review.
>
> I have always tried to help contributors by meeting them half way. In
> the past, only I ran nxstyle and only I fixed the style errors on
> submitted code. That was a courtesy and an act that showed my thanks
> for the contributions (I still force push nxstyle fixes to contributors
> branches on occasion). Let's go that extra mile rather than be some
> kind of an oppressive organization that berates and hassles contributors
> who are just trying to do the right thing.
>
> We don't all have to be assholes.
>
> Greg
>
>
>
--
Adam Feuer
CUSS] thread to talk about
> requirements for commit messages and PR descriptions?
>
> Nathan
>
--
Adam Feuer
elease notes for the 9.1
> ahead of time.
>
> On Wed, Jun 3, 2020 at 4:58 PM Adam Feuer wrote:
> >
> > Brennan,
> >
> > What, in your opinion, needs to be done to improve the onboarding
> process?
> >
> > And what would you like to see happen to imp
py to share more on the steps of the actual release process
> outside of the release notes and branching (thank you Abdelatif that was a
> lot of work) if someone wants to take that on, or I can offer to do that
> portion again. I am happy to do it. It's a lot of little steps but none of
> them are that complicated.
>
> --Brennan
>
> >
>
--
Adam Feuer
can get signals
on the SDMMC bus. If you have more ideas, I would love to hear them.
cheers
adam
On Mon, Apr 13, 2020 at 5:38 PM Adam Feuer wrote:
> Takeyoshi,
>
> I finally got the new sama5 sam_sdmmc.c driver to compile. I haven't
> tested it yet, so I don't know if it a
Hash for the release incubating-nuttx tag:
> > 725bdfb0e8c704823669d20931fd0a824c462212
> > Hash for the release incubating-nuttx-apps tag:
> > 9d4872780f095d7af7414501ccf34ea23d4d565b
> >
> > [1] https://dist.apache.org/repos/dist/dev/incubator/nuttx/9.0.0-RC1/
> > [2]
> >
> https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-9.0.0-RC1/ReleaseNotes
> > [3] https://nuttx-companion.readthedocs.io/en/latest/
> > [4] https://www.apache.org/dev/release.html#approving-a-release
> > [5]
> >
> https://cwiki.apache.org/confluence/display/NUTTX/Validating+a+staged+Release
> >
>
--
Adam Feuer
he 9.0.0-RC1 release
> tonight if there are no objections.
>
> --Brennan
>
--
Adam Feuer
e, so they match up together and people can see the exact
docs for the version they're using. I'm happy to talk more about making
this happen.
cheers
adam
On Sun, Apr 26, 2020 at 2:57 PM Brennan Ashton
wrote:
> On Sun, Apr 26, 2020 at 12:20 PM Adam Feuer wrote:
>
> > Re: qui
Windows, and choose a
> board for each of those that demonstrates some customization or something
> instructive?
>
> Just thinking out loud here
>
> Nathan
>
--
Adam Feuer
esh.
>
> https://nuttx-companion.readthedocs.io/en/latest/
>
> --Brennan
>
--
Adam Feuer
On Mon, Apr 20, 2020 at 10:55 AM Gregory Nutt wrote:
> I think we owe Abdelatif thanks. What has happened could not have
> happened without his contribution.
>
Thank you Abdelatif! :)
-adam
--
Adam Feuer
t 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]
Takeyoshi,
I finally got the new sama5 sam_sdmmc.c driver to compile. I haven't tested
it yet, so I don't know if it actually works... I pushed the code to the
branch, I am attaching the config I used.
-adam
On Thu, Apr 2, 2020 at 3:23 PM Adam Feuer wrote:
> Takeyoshi,
>
>
t; sama5d3x-ek/src/sam_hsmci.c: sdio_mediachange(state->hsmci, cd);
> sama5d3x-ek/src/sam_hsmci.c: sdio_mediachange(state->hsmci, state->cd);
> sama5d3-xplained/src/sam_hsmci.c: sdio_mediachange(state->hsmci, cd);
> sama5d3-xplained/src/sam_hsmci.c: sdio_mediachange(state->hsmci,
> state->cd);
> sama5d4-ek/src/sam_hsmci.c: sdio_mediachange(state->hsmci, cd);
> sama5d4-ek/src/sam_hsmci.c: sdio_mediachange(state->hsmci, state->cd);
>
>
>
--
Adam Feuer
vements and
> bugfixes from 8.2 to 9.0.
>
> BR,
>
> Alan
>
> On 4/10/20, Adam Feuer wrote:
> > Ok thanks Alan. I'm sorry I wasn't clear about what we had done.
> >
> > -adam
> >
> > On Fri, Apr 10, 2020 at 11:27 AM Alan Carvalho de Assis
use I thought you,
> Nathan and Abdelatif did it.
>
> I can do it for the improvements from nuttx-8.2 until Nov. 23 2019, no
> problem.
>
> BR,
>
> Alan
>
> On 4/10/20, Adam Feuer wrote:
> > Alan,
> >
> > Next we need to check for features/improvem
P.S. I think this would have to be done for both nuttx and nuttx-apps.
On Fri, Apr 10, 2020 at 10:43 AM Adam Feuer wrote:
> Alan,
>
> Next we need to check for features/improvements and bugfixes between 23
> December 2019 (1st PR in github.com/apache/incubator-nuttx) and the 16
>
push to the
> > release branch.
> > Do we download them, sign and then upload the signatures?
> > We need at least one way to check the downloads before signing, like
> > by creating the hashes with the tarballs.
> >
> >
> > On Fri, Apr 10, 2020 at 4:41
Xiang,
Ok, thanks. It's great that this doesn't block the release!
-adam
On Thu, Apr 9, 2020 at 7:49 PM Xiang Xiao wrote:
> This build error happen for several special config only, and already exist
>
> On Fri, Apr 10, 2020 at 10:38 AM Adam Feuer wrote:
> >
> >
1 - 100 of 299 matches
Mail list logo
