gt; > Alin
>> > ________________
>> > Från: Tim Hardisty
>> > Skickat: den 7 oktober 2024 16:20
>> > Till: dev@nuttx.apache.org
>> > Ämne: Re: [VOTE] Apache NuttX 12.7.0 RC0 release
>> >
>> > Hi. It was because t
ull/13933
>
> Best regards
> Alin
>
> Från: Tim Hardisty
> Skickat: den 7 oktober 2024 16:20
> Till: dev@nuttx.apache.org
> Ämne: Re: [VOTE] Apache NuttX 12.7.0 RC0 release
>
> Hi. It was because the NuttX framebuffer driver *in LVGL*
/apache/nuttx/pull/13933
> >
> > Best regards
> > Alin
> >
> > Från: Tim Hardisty
> > Skickat: den 7 oktober 2024 16:20
> > Till: dev@nuttx.apache.org
> > Ämne: Re: [VOTE] Apache NuttX 12.7.0 RC0 release
> >
> > Hi. It was because the
b.com/apache/nuttx/pull/13933
>
> Best regards
> Alin
>
> Från: Tim Hardisty
> Skickat: den 7 oktober 2024 16:20
> Till: dev@nuttx.apache.org
> Ämne: Re: [VOTE] Apache NuttX 12.7.0 RC0 release
>
> Hi. It was because the NuttX framebu
Hi all ,
sim: fix sim smp boot regression
https://github.com/apache/nuttx/pull/13933
Best regards
Alin
Från: Tim Hardisty
Skickat: den 7 oktober 2024 16:20
Till: dev@nuttx.apache.org
Ämne: Re: [VOTE] Apache NuttX 12.7.0 RC0 release
Hi. It was because the NuttX
Hi.
It was because the NuttX framebuffer driver *in LVGL* rendered directly
to the NuttX /dev/fb0 device, causing tearing issues and artefacts. It
should have had a second buffer that LVGL rendered to rather than direct
to the device driver's framebuffer memory.
I raised a nuttx-apps issue h
Thank you Tim could you please pinpoint the issue with LCD / FB? Anyone
with that hardware help is more than welcome!! It would be great to have
graphics working + new lvgl in upcoming release :-)
I would go:
1. test on older release known to work. just to confirm working hardware.
2. try some rea
FYI, I tried RC0 on my SAMA5D2 custom board with no issues. My app and
LVGL demos (with LVGL V9.1 - with known issues - and V9.2) run OK as
does the FB example app, so I would think any issues are possibly
arch-specific rather than 100% down to LVGL.
I did try OSTEST but I gave up waiting for
I fully agree with Tomek. If possible, let's delay the release for a while
and fix what's broken, or at least find the broken configurations/features.
What I have tested so far:
- [X] sim/foc - fixed
- [X] sim/smp - **broken**
- [X] sim/nsh - OK
- [X] sim/crypto - OK
- [X] sim/elf - OK
- [X] sim/f
Hi all,
the voting is closed
We will fix the bugs and start the RC1 test and vote process
Please link fixes to this thread
Best regards
Alin
On Mon, 7 Oct 2024, 09:12 raiden00pl, wrote:
> I fully agree with Tomek. If possible, let's delay the release for a while
> and fix what's broken, or a
Please lets wait for LVGL 9.2.1 release, we have patches ready to get
in sync, this is quite important and demanded feature to land in a
release, and I am sure this will attract new users/developers to the
NuttX community because this will be also announced to the broad LVGL
community :-)
Also we
FYI you can no longer change LVGL version from Kconfig AFAIK, but you can force
the use of any version you want by checking out the version you want from the
LVGL repo but have to do a manual copy of the LVGL K config into the NuttX Apps
LVGL Kconfig. It’s a bit messy but works!
> On 5 Oct 202
@Tim and Tomek
My bad ! We are using 9.1.0 for 12.7.0 release
I was looking on an older branch . A simple PR will fix it after LVGL is
release
Best regards
Alin
On Sat, Oct 5, 2024 at 10:52 AM Tim Hardisty
wrote:
> 12.7 should be using LVGL 9.1. 9.1 has a specific frame buffer problem
> fixed
We have been trying to get more developers to test and vote the releases to
be able to catch bugs
the voting period is 72 hours usually scheduled over the weekend to give us
time to build and test
after each rejected RC due to errors we create a new RC and restart the
testing and voting process
t
12.7 should be using LVGL 9.1. 9.1 has a specific frame buffer problem fixed in
9.2.
I have a custom SAMA5D2 board with an LCD running NuttX master and LVGL 9.2 and
I will try the RC on Monday.
> On 5 Oct 2024, at 10:33, Alin Jerpelea wrote:
>
> Hi Tomek,
> Thanks for testing and providing f
-1 from me.
Too many things seem broken.
Since the last release there have been a lot of critical changes that are
most likely not very well tested.
It would be nice to have more community involvement in testing this
release.
For my part, I'll spend the next few days testing on the hardware I hav
Hi Tomek,
Thanks for testing and providing feedback.
1. There are memory leak problems reported
This is something that we should test on more boards
2. There are LVGL screen problems reported.
NuttX 12.7 uses LVGL 8.3.3 by default but this can be changed in the menu
config LVGL_VERSION
string "L
Hello,
I am not entirely clear how to participate in the release vote, I will have
to review the linked information again, but I have noticed that the Pico W
is not able to connect to a wireless network because of an issue that was
previously encountered a few releases ago. I am investigating this
Hello world :-)
There goes -1 from me, sorry :-P :-P
1. There are memory leak problems reported that I tried to confirm on
STM32F769. Is it ostest problem only or more general memory management
issue?
before ostest total/used: 483056 / 10112.
after ostest total/used: 483056 / 10200.
2. There ar
117042051712 331682051040
>> 41
>> >>3
>> >> Page:4194304 1187844075520 4075520
>> >> nsh> getprime
>> >> Set thread priority to 10
>> >> Set thread policy to SCHED_RR
>> &
: T-HEAD c908
> >> Platform Features : mfdeleg
> >> Platform HART Count : 1
> >> Platform IPI Device : clint
> >> Platform Timer Device : clint
> >> Platform Console Device : uart8250
> >> Platform HSM Device : -
f (R,W,X)
>> Domain0 Next Address : 0x0820
>> Domain0 Next Arg1 : 0x0a00
>> Domain0 Next Mode : S-mode
>> Domain0 SysReset : yes
>>
>>
>> Boot HART ID : 0
>> Boot HART Doma
maxfree nused
> nfree
> Kmem:2063416 117042051712 371522051040 41
> 3
> Page:4194304 118784 4075520 4075520
> nsh>
>
> -Ville
>
> From: yfliu2008
> Sent: Friday, October
10456
998176 51168 994272
35 5
Page: 10485760 1228800
9256960 9256960
nsh>
```
Original
From:"Alin Jerpelea"< jerpe...@gmail.com >;
Date:2024/10/3 16:35
To:"dev"< dev@nuttx.apache.org >;
Subject:[VOTE] Apac
On 10/3/2024 7:07 PM, yfliu2008 wrote:
- Two kernel mode configs `nsbi` and `knsh` both show used memory growth after
ostest.
I would consider memory leaks in core OS functions to be a major problem.
+1 but I've to check more for nucleo-h745
Results:
arm-none-eabi-gcc -v
Thread model: single
Supported LTO compression algorithms: zlib
gcc version 13.3.1 20240614 (15:13.3.rel1-1)
*nucleo-144:f746-pysim*
-rwxrwxr-x 1 bucher bucher 467588 Oct 3 13:25 nuttx
-rwxrwxr-x 1 bucher bucher 30
+1 for Milk-V Duo S, Ox64, Star64 and PinePhone
= Milk-V Duo S Compiler
+ riscv-none-elf-gcc -v
Using built-in specs.
COLLECT_GCC=riscv-none-elf-gcc
COLLECT_LTO_WRAPPER=/Users/luppy/xpack-riscv-none-elf-gcc-13.2.0-2/bin/../libexec/gcc/riscv-none-elf/13.2.0/lto-wrapper
Target: riscv-none-elf
Co
Hello all,
Apache NuttX 12.7.0 RC0 has been staged under [1] and it's
time to vote on accepting it for release. Voting will be open for 72hr.
A minimum of 3 binding +1 votes and more binding +1 than binding -1 are
required to pass.
The Apache requirements for approving a release can be found here
28 matches
Mail list logo
