AVRco Service

Hello Rene.

Rolf retired from AVRCo a while back. AVRCo is now a free product and to a large extent has to be community based because effectively it is no longer funded. I maintain the compiler, assembler and Wizzard and have just released my latest version. Rolf's family have kindly continued to host the site including the download area, but there is no commercial activity on the site now. Many of the built in drivers do not work with the latest series of chips although basic ones like SysTick and serial do. Since you claim not to use drivers you should not have a problem. If you want to help by contributing drivers of your own that would be very welcome. Another of our users Udo Purwin has already contributed a number for the new Series 0 devices (often referred to as UPDI devices).

Your old license will have expired but the latest versions do not require it, and you no longer need your password to download it.

Welcome back and as I say, any contribution is very welcome.
Merlin.

:magic:

Software is a black art.

Thanks Merlin.
My compiler does the older AVR, which I'm used to, and still use while on stock and available. I'd be interested in the newer families. The EA, DA, DD and DB. They have a similar architecture plus the event engine and the CPLD. Unless already implemented, I'd do it. We may consider a Zoom session or so at one point.

Hi Rene.

What I have been working on is to make it simpler to create external drivers that, for example, do not need anything in the 'defines' block. A couple of drivers (notably SysTick and serial) are implemented as internal drivers but untested on these new devices. I am also designing (well just 'refining' now) a wizzard that can build external low level drivers that allow simplified access to the IO area to facilitate the building of real drivers, using ADTF files available from Microchip. These drivers use new features available to a new record type that allow functions procedures and properties from within a record and also allow limited parameterization of those records. I call these 'skeleton records>.

The features of the newer compiler versions are a superset of the old compiler so you are not starting from scratch if you want to learn how to use these features and I will be happy to support you.

Thanks a lot Merlin,
I'm absolutely no friend of these drivers, I never used one. Not even the tick. I also skipped the wizards.
They are just a few lines, and I'd rather know what they are doing. If questions arise, I can toggle a pin in it.
Eg. My timer tick.

interrupt Timer0; // the usual Tick 10ms
begin
Timer0Came:=1;
TCNT0:=timer0reload;
TCCR0:=$05;
end;

procedure InitTimer0;
begin
TCCR0:=0; //off
timer0reload:=148; //11.059MHz div1024, 92.59us, 108ticks, 256-108,
TCCR0:=$05;
TCNT0:=timer0reload;
TIMSK0:=$01;
end;

That's it. In the main, I wait for the flag to have occurred.
I'm rather concerned with the extended command set and and functionality on a bare bone level.