Is there any progress in the topic? We also eager to have atxmega in the avr programmer. News from 6.1.0 update : Release changes in Compiler New: Additional 19 MCU supported AT90PWM161 ATMEGA168PB ATMEGA3250A ATMEGA3250PA ATMEGA325PA ATMEGA3290A ATMEGA6450P ATMEGA645P ATMEGA6490P ATTINY1634 ATTINY...

Dear Team Mikroe,

Do you support the ATmega168PB µC on mikroPascal PRO for AVR?

Best regards.

SP

I'm losing all the convenience and speed of development, provided by mikroPascal. And I didn't talk about debugging abilities. I hope you're hear us. +1 Now I can't use ARDUINO compiler and mikroPascal .... Now, I Must use ATMEL Studio. And it's not faster than mikroPascal! Please add, all ATxMega ...

Hi

can you support ATxMEGA8E ?
I know that I must use external programming tool.

Best regards.

Stéf

Hi,

I have same problem with MikroPascal Pro for AVR.

Regards

marina.petrovic wrote:Please, can you try to use PB3 pin for OC0B on your ATMEGA164PA that you mention that you have?

PB3 is OC0A and PB4 is OC0B

I already tried with PB4.

Regard

OC0B (Timer/Counter0 output compare match B output) - PD5 pin OC0A (Timer/Counter0 output compare match A output) - PD6 pin For ATMEGA88 it's OC0A (Timer/Counter0 output compare match A output) - PD5 pin OC0B (Timer/Counter0 output compare match B output) - PD6 pin The project/code in our compiler ...

Thank you marina but where do you see other port in code? program PWM_Test; var current_duty : byte; current_duty1 : byte; begin DDB0_bit := 0; // Set PORTB pin 0 as input DDB1_bit := 0; // Set PORTB pin 1 as input DDC0_bit := 0; // Set PORTC pin 0 as input DDC1_bit := 0; // Set PORTC pin 1 as input...

Hi,

How can I use only OC0B output with my atmega88?

The lib. work fine with 0C0A but and I don't found doc or sample...

Regards

Stéf.

Hi, I don't have any code sorry but I think you must use timer interrupt with 2 variables, "_up" et "_down" duty cycle is equal to 50% when "_up" = "_down". procedure on_Interrupt begin inc(global_counter) if (global_counter > _up) then Begin global_counter = 0 portx.x = 0 end if (global_counter > _...

Hello,

When will you add support for atTiny4, atTiny5, atTiny9 and atTiny10?

Regards

Stéf

hi, You can do this : {$DEFINE flag_1} var {$IFDEF flag_1} PortR_ : sbit at PORTB.0; PortV_ : sbit at PORTB.1; PortB_ : sbit at PORTB.2; {$ENDIF} {$IFDEF flag_2} PortR_ : sbit at PORTC.0; PortV_ : sbit at PORTC.1; PortB_ : sbit at PORTC.2; {$ENDIF} Begin PortR_ := 1; PortV_ := 0; PortB_ := 1; end; I...

Hi,
I work with your board near 1 year.
I have a little wish . Can you include other programmer like AVRISP or STK500 for exemple.
I explain, for flashing my PCB, I must compile with your compilateur and flash with AVR Studio ...

Best regards.

Stéphane PEREZ

(sorry for my poor english)

Hi, I work with your compiler near 1 year. I have a little wish ;) . Can you include other µC compilateur like AVRISP or STK500 for exemple. I explain, for flashing my PCB, I must compile with your compilateur and flash with AVR Studio :( ... Best regards. Stéphane PEREZ (sorry for my poor english)

You can have a constant of compilation like MPAS_COMPIL_NUMB . To each new compilation, it's automaticaly incremented. Like that, into our code, we can know what is the build number's of my firmware. If I use a LCD or RS232 liaison, it's can be integrate in the code. LCD_Out(1,1,'Firmware 1.1.'+ Int...