On Tue, Apr 25, 2023, 6:10 AM Gregory Nutt wrote:
>
> On 4/24/2023 7:27 PM, Andrew Dennison wrote:
> > Are there any examples of a gdb setup to debug a userspace process? One
> key
> > issue is to setup the section offsets to match the final application
> > location once it has been loaded.
>
Th
Nathan, could you try:
https://github.com/apache/nuttx/blob/master/boards/sim/sim/sim/configs/adb/defconfig
I just try it work as expect in last mainline:
telnet 127.0.0.1 2323
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
Welcome to NuttShell(NSH) Telnet Server...
login: a
On Tue, Apr 25, 2023, 3:10 PM Gregory Nutt wrote:
>
> On 4/24/2023 7:27 PM, Andrew Dennison wrote:
> > Are there any examples of a gdb setup to debug a userspace process? One
> key
> > issue is to setup the section offsets to match the final application
> > location once it has been loaded.
>
> Y
>>> I was actually quite surprised that Nuttx applications are still
partially
>>> linked with a protected build and that all sections overlap (start
at 0)in
>>> the elf file. I had expected the application would be fully linked to
>>> virtual addresses as per linux and another RTOS I used pre
Hello world :-)
I was on a trip recently (and it happens quite often) so I was looking
for a PDF version of NuttX Documentation, kind of Handbook, but I did
not find one.
I got used to PDF Handbook style because it is all-in-one approach
that is also easily available and searchable offline.
As I
On Tue, Apr 25, 2023, 1:37 PM Tomek CEDRO wrote:
> Hello world :-)
>
> I was on a trip recently (and it happens quite often) so I was looking
> for a PDF version of NuttX Documentation, kind of Handbook, but I did
> not find one.
>
> I got used to PDF Handbook style because it is all-in-one appro
On Tue, Apr 25, 2023, 1:46 PM Brennan Ashton
wrote:
>
>
> On Tue, Apr 25, 2023, 1:37 PM Tomek CEDRO wrote:
>
>> Hello world :-)
>>
>> I was on a trip recently (and it happens quite often) so I was looking
>> for a PDF version of NuttX Documentation, kind of Handbook, but I did
>> not find one.
>
On Tue, Apr 25, 2023 at 8:37 AM Tomek CEDRO wrote:
> Hello world :-)
>
> I was on a trip recently (and it happens quite often) so I was looking
> for a PDF version of NuttX Documentation, kind of Handbook, but I did
> not find one.
>
> I got used to PDF Handbook style because it is all-in-one app
On Tue, Apr 25, 2023 at 8:55 AM Brennan Ashton
wrote:
> On Tue, Apr 25, 2023, 1:46 PM Brennan Ashton
> wrote:
>
> >
> >
> > On Tue, Apr 25, 2023, 1:37 PM Tomek CEDRO wrote:
> >
> >> Hello world :-)
> >>
> >> I was on a trip recently (and it happens quite often) so I was looking
> >> for a PDF v
Hi!
I had no problems debugging NuttX with protected mode on ESP32-S3
(esp32s3-devkit:knsh).
After launching OpenOCD (https://github.com/espressif/openocd-esp32) with
`-c 'set ESP_RTOS none' -c "set ESP_FLASH_SIZE 0"`, just load the
userspace's symbols with `add-symbol-file` (with the address of
Hi Tomek,
Some years ago Matias Nitsche (AKA v0id / protobits) started the
creation of a NuttX book, documenting many of internal OS functions.
But after some time he gave up, because he realized that NuttX is a
movable target. Same happens to Linux (although currently I think
Linux is more stabl
On Tue, Apr 25, 2023 at 2:55 PM Brennan Ashton wrote:
> (..)
> > It is easy enough to generate the PDF from the sphinx documentation if we
> > want that can you create an issue on the website project and I'll enable
> > that in a few weeks.
> Also I want to be very clear since this was incorrect
On 4/25/23, Brennan Ashton wrote:
>
> Others and I _extended_ and converted this to be what is now in
> Documentation it was a lot of work. This is the documentation for the
> project although it has been slow to convert all the readmes and the wiki
> to be here. I would love to see others help w
On Tue, Apr 25, 2023 at 3:01 PM Nathan Hartman wrote:
> On Tue, Apr 25, 2023 at 8:37 AM Tomek CEDRO wrote:
> > I would like to know what is the current and past approach to the
> > documentation, to plan the work and align the tasks (with other people
> > working on the documentation?). What is the
When I was originally developing the kernel mode, I wrote this:
https://cwiki.apache.org/confluence/display/NUTTX/Memory+Configurations
That was mostly my notes of what I had worked on and my roadmap that was
guiding me through the kernel mode development. I burned out on that
before finishin
Sorry, I know I am way to anal retentive:
In the past, documentation was partly in README files in various
directories in the repo, partly on the NuttX website which was running on
MediaWiki.
It was actually DocuWiki and was the landing page for the old nuttx.org
website (not that it matters)
On Tue, Apr 25, 2023 at 3:35 PM Alan C. Assis wrote:
> Hi Tomek,
>
> Some years ago Matias Nitsche (AKA v0id / protobits) started the
> creation of a NuttX book, documenting many of internal OS functions.
>
> But after some time he gave up, because he realized that NuttX is a
> movable target. Same
On Tue, Apr 25, 2023 at 3:59 PM Gregory Nutt wrote:
>
> Sorry, I know I am way to anal retentive:
> > In the past, documentation was partly in README files in various
> > directories in the repo, partly on the NuttX website which was running on
> > MediaWiki.
> It was actually DocuWiki and was the
Yes, using the Documentation/ as base to create a book is a good idea,
but it should focus on "OS Components" and "API Reference".
I don't think that the documentation should be limited to simple HowTo
and WhatIs documentation. I think it should have some technical meat
too! Like explanat
Thanks Alan! This is why I was a bit surprised why the documentation
is not direct part of the source code (i.e. documentation of the
file/module/function right in that file/module/function). Kivy does
that, it helps understanding the code, allows easy online/pdf
documentation out of it, and mo
On 4/25/23, Gregory Nutt wrote:
>
>> Yes, using the Documentation/ as base to create a book is a good idea,
>> but it should focus on "OS Components" and "API Reference".
>
> I don't think that the documentation should be limited to simple HowTo
> and WhatIs documentation. I think it should have
On 4/25/23, Alan C. Assis wrote:
> On 4/25/23, Gregory Nutt wrote:
>>
>>> Yes, using the Documentation/ as base to create a book is a good idea,
>>> but it should focus on "OS Components" and "API Reference".
>>
>> I don't think that the documentation should be limited to simple HowTo
>> and What
not yet, we are busy preparing the Chinese documentation.
On Tue, Apr 25, 2023 at 10:27 PM Alan C. Assis wrote:
> On 4/25/23, Alan C. Assis wrote:
> > On 4/25/23, Gregory Nutt wrote:
> >>
> >>> Yes, using the Documentation/ as base to create a book is a good idea,
> >>> but it should focus on
On Tue, Apr 25, 2023, 3:18 PM Gregory Nutt wrote:
>
> > Thanks Alan! This is why I was a bit surprised why the documentation
> > is not direct part of the source code (i.e. documentation of the
> > file/module/function right in that file/module/function). Kivy does
> > that, it helps understandin
That is indeed a great board.
I did a brief look into ESP32 NuttX BLE support and have more questions
than answers :) Also the USB host interface is not ported. So I was
thinking of picking Orange Pi 3G-IOT-B for prototyping and then go with
stage 2 cost reduction with ESP32-S3. My only concern is
Hello,
I'm starting to experiment with NuttX BLE support. I have a device that I
can successfully pair with my phone and I would like to try pairing it with
the NuttX based device. I chose ESP32 for my experiments. For now I enabled
(and fixed) esp32-devkitc:ble configuration, but that is basicall
On Tue, Apr 25, 2023, 5:36 PM Petro Karashchenko <
petro.karashche...@gmail.com> wrote:
> Hello,
>
> I'm starting to experiment with NuttX BLE support. I have a device that I
> can successfully pair with my phone and I would like to try pairing it with
> the NuttX based device. I chose ESP32 for m
On Tue, Apr 25, 2023, 5:41 PM Brennan Ashton
wrote:
>
> On Tue, Apr 25, 2023, 5:36 PM Petro Karashchenko <
> petro.karashche...@gmail.com> wrote:
>
>> Hello,
>>
>> I'm starting to experiment with NuttX BLE support. I have a device that I
>> can successfully pair with my phone and I would like to
Is this going to work on OSX? Or Linux only is verified?
вт, 25 квіт. 2023 р. о 19:45 Brennan Ashton
пише:
> On Tue, Apr 25, 2023, 5:41 PM Brennan Ashton
> wrote:
>
> >
> > On Tue, Apr 25, 2023, 5:36 PM Petro Karashchenko <
> > petro.karashche...@gmail.com> wrote:
> >
> >> Hello,
> >>
> >> I'm
Unfortunately this is coupled to the Linux kernel Bluetooth stack since it
is relying on the User Channel of the hcisocket which let's your
application (NuttX in this case) have a virtual HCI device and temporarily
provide it largely isolated control over it (you cannot scan from the host
anymore f
On Tue, Apr 25, 2023 at 5:47 PM Brennan Ashton wrote:
> On Tue, Apr 25, 2023, 3:18 PM Gregory Nutt wrote:
> > My experience with using Deoxygen on large, projects has been
> > disastrous. People don't always maintain the tags to the documentation
> > was wrong and so the auto-generated documentat
On Tue, Apr 25, 2023, 6:10 PM Tomek CEDRO wrote:
> On Tue, Apr 25, 2023 at 5:47 PM Brennan Ashton wrote:
> > On Tue, Apr 25, 2023, 3:18 PM Gregory Nutt wrote:
> > > My experience with using Deoxygen on large, projects has been
> > > disastrous. People don't always maintain the tags to the docume
On Tue, Apr 25, 2023 at 9:59 AM Gregory Nutt wrote:
> Sorry, I know I am way to anal retentive:
> > In the past, documentation was partly in README files in various
> > directories in the repo, partly on the NuttX website which was running on
> > MediaWiki.
> It was actually DocuWiki and was the
Ok. Thank you.
I was able to monitor traffic from Ubuntu bluetooth port and found out that
my device sends advertising reports not frequently, so I did a few more
tries with duplicates on NuttX ESP32 and finally was able to identify the
needed string. So what is the next step? How to pair with the
On Tue, Apr 25, 2023 at 6:54 PM Petro Karashchenko wrote:
> Is this going to work on OSX? Or Linux only is verified?
XCode has PacketLogger utility that should help :-)
Also you will see additional information when pressing Buetooth icon
with Alt key pressed :-)
Some folks recommend Ubertooth On
On 4/25/23, Brennan Ashton wrote:
>
> I should probably have added this in more detail to the docs, but see the
> testing section of the PR where I added it. I think it shows exactly what
> you are trying to do
>
> https://github.com/apache/nuttx/pull/1655
>
Petro is right, we need to improve the
On Tue, Apr 25, 2023 at 7:26 PM Brennan Ashton wrote:
> On Tue, Apr 25, 2023, 6:10 PM Tomek CEDRO wrote:
> (..)
> > After some consideration a "safer" approach may be more desirable for now:
> >
> > 1. Migrate all documentation to a separate Documentation/ as it is
> > currently done, so we do not
On Tue, Apr 25, 2023 at 1:10 PM Tomek CEDRO wrote:
> On Tue, Apr 25, 2023 at 5:47 PM Brennan Ashton wrote:
> > On Tue, Apr 25, 2023, 3:18 PM Gregory Nutt wrote:
> > > My experience with using Deoxygen on large, projects has been
> > > disastrous. People don't always maintain the tags to the docu
On Tue, Apr 25, 2023 at 7:26 PM Brennan Ashton wrote:
> Eh I don't think we should pull the docs apart. Its a pain to manage
> especially with sphinx if we start sprinkling the docs all over the place.
> it's also hard in my opinion to write clear cohesive docs thare do not get
> highly repetitive
On Tue, Apr 25, 2023 at 7:38 PM Nathan Hartman wrote:
> On Tue, Apr 25, 2023 at 1:10 PM Tomek CEDRO wrote:
> > (..)
> > After some consideration a "safer" approach may be more desirable for now:
> >
> > 1. Migrate all documentation to a separate Documentation/ as it is
> > currently done, so we do
On 4/25/2023 11:38 AM, Nathan Hartman wrote:
> I like the idea of keeping documentation in sync with the code(as much as
> possible given our volunteer-based project).
I wouldn't make a plan that depends on that. Engineers are notoriously
bad at maintaining documentation. And international pr
On Tue, Apr 25, 2023, 7:14 PM Gregory Nutt wrote:
> On 4/25/2023 11:38 AM, Nathan Hartman wrote:
>
> > I like the idea of keeping documentation in sync with the code(as much
> as
> > possible given our volunteer-based project).
>
> I wouldn't make a plan that depends on that. Engineers are not
The SAMA5 support has no driver for the secure fuse peripheral. Kconfig allows
you to “enable” it but there’s no underlying code.
Before I go ahead and create a character driver for this, is the omission for a
“good” reason?
The driver would handle the relatively straightforward management of
On Tue, Apr 25, 2023 at 8:14 PM Gregory Nutt wrote:
> Tomasz Cedro now owns nuttx.com and nuttx.org.
Yes the domains are for the project use, just let me know how you want
them configured, at this point they redirect to the main project site
:-)
I was thinking about maybe some showcases of the pr
On Tue, Apr 25, 2023, 7:45 PM Tomek CEDRO wrote:
> On Tue, Apr 25, 2023 at 8:14 PM Gregory Nutt wrote:
> > Tomasz Cedro now owns nuttx.com and nuttx.org.
>
> Yes the domains are for the project use, just let me know how you want
> them configured, at this point they redirect to the main project s
On 4/25/2023 12:32 PM, Tim Hardisty wrote:
The SAMA5 support has no driver for the secure fuse peripheral. Kconfig allows
you to “enable” it but there’s no underlying code.
Before I go ahead and create a character driver for this, is the omission for a
“good” reason?
The driver would handle t
On Tue, Apr 25, 2023 at 9:17 PM Gregory Nutt wrote:
> Searching for C files with "fuse" in the number under arch/, I find
> drivers for the ESP32, ESP32S2, ESP32S3, ESP32C3, BL602, and RTL8720C
>
> Other MCUs have have fuse header files, but no C drivers.
>
> There are alias like OTP (i.MXRT). PI
On Tue, Apr 25, 2023 at 3:12 PM Brennan Ashton
wrote:
> On Tue, Apr 25, 2023, 7:45 PM Tomek CEDRO wrote:
>
> > On Tue, Apr 25, 2023 at 8:14 PM Gregory Nutt wrote:
> > > Tomasz Cedro now owns nuttx.com and nuttx.org.
> >
> > Yes the domains are for the project use, just let me know how you want
>
Hi all,
When using external rtc the function up_rtc_initialize() in file
nuttx/sched/clock_initialize.c should not be called.
A small fix is attached.
Best regards
--- nx12.1-orig/nuttx/sched/clock/clock_initialize.c 2022-12-13
09:30:57.0 +0200
+++ nx12.1-new/nuttx/sched/cloc
49 matches
Mail list logo
