Re: Comment for AVR GitHub issue 16444 and PR 16443

Managed to find a fix here: https://github.com/apache/nuttx/pull/16457 On Tue, May 27, 2025 at 11:24 PM Matteo Golin wrote: > Thank you for your help KR! > > I also noticed this CONFIG_RAM_START=0x800100. Unfortunately, changing > that value to the proper 0x800200 did not really help the issue.

Re: Comment for AVR GitHub issue 16444 and PR 16443

Thank you for your help KR! I also noticed this CONFIG_RAM_START=0x800100. Unfortunately, changing that value to the proper 0x800200 did not really help the issue. I went ahead and generated the disassembly like you suggested, and it does appear that the .text section starts with jump instruction

Re: Comment for AVR GitHub issue 16444 and PR 16443

Thanks to you as well. I spotted an error in the config posted both in the issue #16444 and PR #16443. It is the CONFIG_RAM_START=0x800100 Unless I overlooked something, the RAM starts at address 0x200 (0x800200) for AtMega 2560. Not sure if that's what causing the problem though - as far

Re: Release branch out

+1 for 12.10 :-) Tomek On Tue, May 27, 2025 at 9:46 AM Alin Jerpelea wrote: > > Hi Raiden, > we can do 12.10 instead but there are some breaking changes which are > already in the master > Best regards > Alin > > On Tue, May 27, 2025 at 9:44 AM raiden00pl wrote: > > > hi, why not use release 12

Re: Comment for AVR GitHub issue 16444 and PR 16443

Thank you KR, I posted your message in that issue for reference. I have a BK-AVR128 board: https://aliexpress.com/item/1005006234334573.html and will test NuttX on it to confirm. If everything is working as expected I will submit the board support to the mainline. BR, Alan On Tue, May 27, 202

Re: Release branch out

Hi Kevin, we do releases every 3 months with 1 month of testing and atabilization period for each release. To give more people the opportunity of testing and reporting bugs I started sending those mails. I hope that we will have more testers on the release process and improve the release quality.

Comment for AVR GitHub issue 16444 and PR 16443

Hello, as mentioned in one of my previous e-mails to this list (RFC: decoupling ability to always panic from board_reset), I noticed #16444 and #16443 on GitHub. I found some time to look into this and I believe I found the reason for "If you add avr_lowputc calls in the board initialization

Re: Patch: fix AVR up_saveusercontext and other smaller changes

Hi KR, the patches have been submitted for review! Thanks for sending them . please follow the progress on https://github.com/apache/nuttx/pull/16451 Best regards Alin On Tue, May 27, 2025 at 10:11 AM wrote: > Hello, > > I would like to submit some patches related to AVR architecture. Their >

Patch: fix AVR up_saveusercontext and other smaller changes

Hello, I would like to submit some patches related to AVR architecture. Their description is as follows: 0001 - this patch fixes LED constants for breadxavr board. The code was developed based on other AVR boards, LED constants were taken from board that apparently has multiple status LEDs a

Re: Release branch out

Actually, stability is a more important argument here for not releasing 13.0 yet. If I see a major release of 13.0 I would expect it to be stable and well tested. 13.0 sounds quite proud for the project, no point in spoiling that impression with an unstable release. Even if we break the rule of "br

Re: Release branch out

Hi, I agree with Raiden00pl. Things do not feel very stable yet. STM side is fine however. There is also a RISC V RP235x arch coming, which could be a major thing. Maybe worth the thoughts Thanks for all the effort On Tue, 27 May 2025, 09:44 raiden00pl, wrote: > hi, why not use release 12.10?

Re: Release branch out

Hi Raiden, we can do 12.10 instead but there are some breaking changes which are already in the master Best regards Alin On Tue, May 27, 2025 at 9:44 AM raiden00pl wrote: > hi, why not use release 12.10? I don't think we're ready for 13.0. > Many changes were planned for 13.0, but almost nothin

Re: Release branch out

hi, why not use release 12.10? I don't think we're ready for 13.0. Many changes were planned for 13.0, but almost nothing was done :) wt., 27 maj 2025 o 09:37 Alin Jerpelea napisał(a): > Hi all, > > I will branch out the next release soon > - target date 02 Jun for branch out > - the new the bra

Release branch out

Hi all, I will branch out the next release soon - target date 02 Jun for branch out - the new the branch will be used testing and stabilization phase (fixes and security patches only) - RC0 should be submitted for community vote on 27 Jun - RC1 (if needed) should be submitted for community vote on