ChibiOS Free Embedded RTOS

Binutils 2.26 (released in 2016) removed support for the "--mcu=$(MCU) --format=avr" options from the avr-size command.

Here's a patch to remove those options from the definition of ELFSIZE for AVR demos and tests.



However, when building for AVR targets, you so get the size of the resulting ELF file displayed twice



This could be fixed with a simple change to the AVR compiler rules, as the rule for %.sym already calls $(SZ) on the resulting elf file.

Hi,

Thanks, the AVR maintainer is very busy in RL now, I was about to move all the AVR stuff on the community repository because I cannot maintain it.

Interested in taking it under your wing for a while?

Giovanni

I don't have a ton of time on my hands, but I could take some AVR work under my wing for at least a few months.

My goal was to bring the AVR HAL closer to feature parity with some of the other platforms. My main focus was going to be writing a new EXTI driver that uses the AVR's PCINT pins so that PAL pad events work, and writing a SIO driver so that for custom serial protocols the overhead of the Serial driver can be avoided.

I don't do any AVR professionally, but a few of my personal projects still have Arduinos in them. Admittedly I have been replacing them with RP2040/RP2350 and slowly learning STM32.

I don't have any of the newer parts (XMEGA, megaAVR 0-series, AVR Dx, etc.), but I do have some of the older AVRs in my parts bin (ATmega8, ATmega32, ATmega162, ATmega644, ATmega48, ATmega168P, and a few ATtiny85s), along with the ATmega328P and ATmega2560 based Arduinos (Uno R3, Mega).

I do have an AVR JTAG debugger, so if some nasty bugs come up, it is debuggable.

Do you have a sourceforge account? I can enable you to access the repository directly so you can commit all the small fixes required.

Giovanni

I went and created a sourceforge account. Same username as here, "teknoman117".

If you want to DM me about maintenance rules / maintainer policy, please do so.

Hi,

You should have access to the repository now, do you know subversion?

Few recommendations: operate in your area (AVR), if there is need of changes in shared code then we need to discuss it first, try to not break backward compatibility if possible, look at the style guidelines, complex changes are best done in a branch -> keep the trunk code functional, make changes on both trunk and 21.11.x stable branch, feel free to ask anytime.

You may also join our discord, the other AVR maintainer should still be around but he is more busy with work now, name on discord is "tfateba", you may try to contact him.

BTW, for some reason the integration server Jenkins fails on some AVR demos, perhaps there something wrong with the compiler, in case of errors confirm by compiling locally.

Giovanni

In my 15 years in the tech industry thus far I've never actually had to use subversion =P. I'm sure I'll figure it out pretty quick. I do see that I have access now on Sourceforge.

I just joined the Discord, user "teknoman117" as well. I'll ping the current maintainer and work on contributing the small AVR specific fixes I shared in the forums. Are there any instructions on accessing the Jenkins server / CI logs so that I can see if I can fix the AVR integration tests?

Also, I did read about the GitHub mirrors and how your development is primarily done through SVN on Sourceforge and also posting patchsets in this forum. It looks like PR's are occasionally accepted into the ChibiOS-Contrib repository on GitHub? What are the relationships between the "upstream" on Sourceforge and the main and contrib repos on GitHub?

Actually I think it is simpler than git lol, you need few commands initially: checkout, update, add, revert and commit. On windows I recommend using TortoiseSVN.

Giovanni

Okay, I committed my small patches to trunk, figured I'd ask if you wanted me to push them to stable_21.11.x before I touched it

Good

Please also update 21.11.x, the HAL should be kept aligned until the 21.11.4 release.

Giovanni