raiden00pl commented on PR #14460:
URL: https://github.com/apache/nuttx/pull/14460#issuecomment-2628829807
@tmedicci doesn't this change deserve to increase a major version release
for NuttX? it may break a lot of small NuttX applications because it will
automatically increase the image siz
XuNeo opened a new pull request, #15740:
URL: https://github.com/apache/nuttx/pull/15740
## Summary
Renames `tools/gdb/nuttxgdb` → `tools/pynuttx/nxgdb`
Establishes `pynuttx` as the root directory for future Python package
development
Prepares for publishing `nxgdb`
nuttxpr commented on PR #15740:
URL: https://github.com/apache/nuttx/pull/15740#issuecomment-2628772867
[**\[Experimental Bot, please feedback
here\]**](https://github.com/search?q=repo%3Aapache%2Fnuttx+13552&type=issues)
Yes, this PR appears to meet the NuttX requirements. I
cederom opened a new issue, #2983:
URL: https://github.com/apache/nuttx-apps/issues/2983
This is a top-level task to track Python related activities. Please do not
remove.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub a
cederom opened a new issue, #15739:
URL: https://github.com/apache/nuttx/issues/15739
### Description
This is a top-level task to track Python related activities. Please do not
remove.
### Verification
- [x] I have verified before submitting the report.
--
This is an
cederom opened a new issue, #129:
URL: https://github.com/apache/nuttx-website/issues/129
* This is the top-level task to track the (online) documentation and website
related tasks. Please to not close.
--
This is an automated message from the Apache Git Service.
To respond to the message
cederom opened a new issue, #15738:
URL: https://github.com/apache/nuttx/issues/15738
### Is your feature request related to a problem? Please describe.
* This is the top level issue to track security related tasks, issues, and
pull requests.
### Describe the solution you'd lik
lupyuen commented on issue #15731:
URL: https://github.com/apache/nuttx/issues/15731#issuecomment-2628665853
> Whaaat did something bad happen??
5 Years Ago: We had Security Issues with a PineTime Smartwatch that we
opened up for Remote Testing :-)
https://github.com/lupyuen/r
lupyuen commented on issue #15731:
URL: https://github.com/apache/nuttx/issues/15731#issuecomment-2628661216
> I found a REST API to Pull Requests and Issues reference
Yep thanks I'm already using the GitHub API for our PR Review Bot :-)
I might try a scaled-down simpler impleme
cederom commented on issue #15731:
URL: https://github.com/apache/nuttx/issues/15731#issuecomment-2628657675
I found a REST API to Pull Requests and Issues reference, added to top
description. Its only to see if this is possible @lupyuen not really need to be
active right now and you can te
cederom commented on issue #15731:
URL: https://github.com/apache/nuttx/issues/15731#issuecomment-2628652493
Whaaat did something bad happen??
Basically we only operate on NuttX repos, so there should be no malware...
but anyone can send PR with anything true!!!
How to prevent
lupyuen commented on issue #15731:
URL: https://github.com/apache/nuttx/issues/15731#issuecomment-2628647886
> * Verify if Dashboard can be attached to GH PR automation as external
runner so we could have have a build and runtime tests results before merging a
PR.
Reminder to myself:
lupyuen commented on PR #2982:
URL: https://github.com/apache/nuttx-apps/pull/2982#issuecomment-2628640054
> `rv-virt: python` is being tested on the NuttX build farm (accessible
through nuttx-dashboard.org). Is it possible to trigger a test with a specific
apps version (to test this PR, fo
nuttxpr commented on PR #15736:
URL: https://github.com/apache/nuttx/pull/15736#issuecomment-2628112531
[**\[Experimental Bot, please feedback
here\]**](https://github.com/search?q=repo%3Aapache%2Fnuttx+13552&type=issues)
The PR mostly meets the NuttX requirements, but it is m
tmedicci commented on issue #15688:
URL: https://github.com/apache/nuttx/issues/15688#issuecomment-2628108584
https://github.com/apache/nuttx/pull/15736 applies the same changes for
ESP32-S2, ESP32-C3, ESP32-C6 and ESP32-H2 that were being affected by the same
bug as reported by @eren-terzi
eren-terzioglu opened a new issue, #15688:
URL: https://github.com/apache/nuttx/issues/15688
### Description / Steps to reproduce the issue
Hi,
After https://github.com/apache/nuttx/pull/14578 PR, Espressif devices
stopped booting.
Here is the error output for `esp32c6-d
tmedicci opened a new pull request, #15736:
URL: https://github.com/apache/nuttx/pull/15736
## Summary
- xtensa/esp32[s2|c3|c6|h2]: fix sched_[lock|unlock] boot crash
- Move the code to iram0 since sched_lock/sched_unlock is called in the
early boot phase.
## Impact
cederom opened a new issue, #15735:
URL: https://github.com/apache/nuttx/issues/15735
### Description
* Develop documented architecture for distributed runtime and build test
farm.
* Use only generic portable solutions with no OS-specific hacks (i.e. Docker
is Linux only).
* Ta
cederom opened a new issue, #15734:
URL: https://github.com/apache/nuttx/issues/15734
### Is your feature request related to a problem? Please describe.
* Find a way to attach DRUNX to `apache/nuttx` [1] and `apache/nuttx-apps`
[2] repositories in order to intercept incoming changes
cederom commented on PR #14552:
URL: https://github.com/apache/nuttx/pull/14552#issuecomment-2628054534
* It's a stm32f429 cpu, so you have all the stm32 "common" board stuff
inbetween.
*host is debian 12 or wsl.
* the problem happen just when running configure.sh, we've observed this
cederom commented on issue #15733:
URL: https://github.com/apache/nuttx/issues/15733#issuecomment-2628031130
Copy-Paste from https://github.com/apache/nuttx/issues/15730 for context :-)
> > [@fdcavalcanti](https://github.com/fdcavalcanti):
[@cederom](https://github.com/cederom) there
cederom commented on issue #15730:
URL: https://github.com/apache/nuttx/issues/15730#issuecomment-2628028847
Thank you @fdcavalcanti :-) Lets move ESP QEMU discussion to dedicated
thread https://github.com/apache/nuttx/issues/15733 :-)
--
This is an automated message from the Apache Git S
tmedicci commented on PR #2982:
URL: https://github.com/apache/nuttx-apps/pull/2982#issuecomment-2627988756
@lupyuen , `rv-virt: python` is being tested on the NuttX build farm
(accessible through nuttx-dashboard.org). Is it possible to trigger a test with
a specific apps version (to test t
tmedicci commented on issue #2884:
URL: https://github.com/apache/nuttx-apps/issues/2884#issuecomment-2627949363
Just submitted a new PR (https://github.com/apache/nuttx-apps/pull/2982)
that solves two issues on `TO-DO list`:
1. Generate interpreters/python/Setup.local and
interprete
tmedicci commented on PR #15732:
URL: https://github.com/apache/nuttx/pull/15732#issuecomment-2627865261
Amazing work, @Laczen!
Congratulations.
Apart from the `defconfig`, can you improve the testing method with clear
instructions on how to build and test it (considering that
fdcavalcanti commented on PR #15732:
URL: https://github.com/apache/nuttx/pull/15732#issuecomment-2627856099
Can you add a `defconfig` ready to use with this functionality? You can call
it `espnow`.
Also some documentation would be good. You can a brief description of this
to `Docume
fdcavalcanti commented on PR #15732:
URL: https://github.com/apache/nuttx/pull/15732#issuecomment-2627848828
Hi @Laczen that's a great contribution!
Please improve the PR description.
I'll take a look and run some tests on it.
--
This is an automated message from the Apache Git Servi
fdcavalcanti commented on issue #15730:
URL: https://github.com/apache/nuttx/issues/15730#issuecomment-2627810736
We use QEMU available for ESP32, ESP32S3 and ESP32C3. You can find them
[here](https://github.com/espressif/qemu).
All tests are Pytest based, but heavily use the
[pytest
nuttxpr commented on PR #2982:
URL: https://github.com/apache/nuttx-apps/pull/2982#issuecomment-2627782645
[**\[Experimental Bot, please feedback
here\]**](https://github.com/search?q=repo%3Aapache%2Fnuttx+13552&type=issues)
Yes, this PR appears to meet the NuttX requirements.
tmedicci opened a new pull request, #2982:
URL: https://github.com/apache/nuttx-apps/pull/2982
## Summary
- interpreters/python: add wrapper to initialize Python
- This wrapper application checks if the Python's modules are already
mounted (and mounts them, if not), sets the nece
nuttxpr commented on PR #15732:
URL: https://github.com/apache/nuttx/pull/15732#issuecomment-2627766490
[**\[Experimental Bot, please feedback
here\]**](https://github.com/search?q=repo%3Aapache%2Fnuttx+13552&type=issues)
No, this PR description does not fully meet the NuttX r
cederom commented on issue #15730:
URL: https://github.com/apache/nuttx/issues/15730#issuecomment-2627763159
> @fdcavalcanti: [@cederom](https://github.com/cederom) there are plenty of
QEMU tests on Espressif side, all pytest based. If there is computing power
available for running more QEM
Laczen opened a new pull request, #15732:
URL: https://github.com/apache/nuttx/pull/15732
## Summary
Espnow is a connectionless WiFi communication protocol that can be used to
exchange information between esp nodes.
## Impact
A espnow pktradio driver is proposed that all
fdcavalcanti commented on issue #15730:
URL: https://github.com/apache/nuttx/issues/15730#issuecomment-2627745438
@cederom there are plenty of QEMU tests on Espressif side, all pytest based.
If there is computing power available for running more QEMU tests, we could
think of a way to inte
cederom commented on issue #15730:
URL: https://github.com/apache/nuttx/issues/15730#issuecomment-2627742501
> @raiden00pl: [@cederom](https://github.com/cederom) hi, do we need this
long label `DRUNX Distrubutes` ? Can we use here some standardized way of
using labels? We have already
This is an automated email from the ASF dual-hosted git repository.
xiaoxiang pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/nuttx.git
from 8f9c1cbe73 xtensa/esp32s3: Fix esp32s3 sched_lock crash
add c1f9c730be gdb: add tool to check heap memory corru
xiaoxiang781216 merged PR #15726:
URL: https://github.com/apache/nuttx/pull/15726
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@nu
anchao closed issue #15688: [BUG] Espressif devices are not booting after PR
14578
URL: https://github.com/apache/nuttx/issues/15688
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comm
anchao commented on PR #15705:
URL: https://github.com/apache/nuttx/pull/15705#issuecomment-2627604862
> Hi @anchao
>
> About Espressif-related problems (#15688), #15728 and #15691 solves the
problem without changing the current locks. Can you please review it too?
>
> After fi
xiaoxiang781216 commented on PR #14552:
URL: https://github.com/apache/nuttx/pull/14552#issuecomment-2627597113
@cederom which defconfig is used? I try the master branch sim:nsh with sed
4.9 without problem:
```
xiaoxiang@LAPTOP-MCMVB0JB:~/backup/os/nuttx/nuttx$ ./tools/configure.sh
This is an automated email from the ASF dual-hosted git repository.
archer pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/nuttx.git
from 4606f1f9e1 feat: drop legacy pinmap for nsh config
add dc2ae56098 arch: Remove the abuse of spinlock in smp boot
anchao merged PR #15691:
URL: https://github.com/apache/nuttx/pull/15691
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@nuttx.apach
anchao merged PR #15728:
URL: https://github.com/apache/nuttx/pull/15728
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@nuttx.apach
geniusdo commented on issue #15502:
URL: https://github.com/apache/nuttx/issues/15502#issuecomment-2627505066
I can see timer drivers are usually coupled with hardware interrupt. I am a
bit confused with interrupt implementation in nuttx. Are there any materials
for me to understand how to
cederom commented on PR #14552:
URL: https://github.com/apache/nuttx/pull/14552#issuecomment-2627446272
Hello world :-)
There is a report of problem after this change @yezhonghui2024, details
below, please let us know if you can repeat on Debian 12 with sed 4.9 and if
this need a fix
cederom opened a new issue, #15731:
URL: https://github.com/apache/nuttx/issues/15731
### Is your feature request related to a problem? Please describe.
Dashboard will be a common place to gather, store, and review distributed
build and runtime logs from DRUNX (Distributed Runtime and
cederom commented on issue #15731:
URL: https://github.com/apache/nuttx/issues/15731#issuecomment-2627388044
Thank you @lupyuen :-) We are playing with GitHub Projects [1] to see if it
can be used to create a roadmap etc, you are Admin too so play around and lets
see how it works :-)
lupyuen commented on issue #15731:
URL: https://github.com/apache/nuttx/issues/15731#issuecomment-2627371000
I have an article about this. Stay tuned next weekend :-)
tmedicci commented on PR #14460:
URL: https://github.com/apache/nuttx/pull/14460#issuecomment-2627324457
As far as I understood from the previous discussion, we should:
1. Remove `CONFIG_SYSTEM_TIME64` from Kconfig;
2. Define `time_t` as `int64_t`;
Is that true, @cederom @pat
anchao commented on code in PR #15729:
URL: https://github.com/apache/nuttx/pull/15729#discussion_r1937200846
##
drivers/note/note_driver.c:
##
@@ -1841,7 +1841,7 @@ void sched_note_filter_mode(FAR struct
note_filter_named_mode_s *oldm,
irqstate_t irq_mask;
FAR struct not
michallenc commented on issue #12381:
URL: https://github.com/apache/nuttx/issues/12381#issuecomment-2627131639
> I started working on removing PWM_MULTICHAN some time ago:
https://github.com/raiden00pl/nuttx/tree/pwm_refactor
Nice!
> IMO this doesn't seem like a very interesti
tmedicci commented on PR #15729:
URL: https://github.com/apache/nuttx/pull/15729#issuecomment-2627088465
@hujun260 , can you please add more information about the proposed changes?
- The PR's description should be updated to include more information about
the proposed changes, why it'
tmedicci commented on PR #15705:
URL: https://github.com/apache/nuttx/pull/15705#issuecomment-2627028204
Hi @hujun260
About Espressif-related problems
(https://github.com/apache/nuttx/issues/15688),
https://github.com/apache/nuttx/pull/15728 and
https://github.com/apache/nuttx/pull
53 matches
Mail list logo
