return
>
> I think it cannot be mixed. The only solution I can think of is making
> separate routines that access the IIC hardware registers directly without a
> call to any other - common - routine.
>
> Kind regards,
>
&g
registers directly without a call to any
other - common - routine.
Kind regards,
Rob
Van: jallib@googlegroups.com namens Rob CJ
Verzonden: donderdag 1 juni 2023 21:01
Aan: jallib@googlegroups.com
Onderwerp: Re: [jallib] Peripheral hardware and interrupts
Hi
Hi Vasile,
Good suggestion. I will give it a try.
Thanks.
Kind regards,
Rob
Van: jallib@googlegroups.com namens vsurducan
Verzonden: donderdag 1 juni 2023 20:58
Aan: jallib@googlegroups.com
Onderwerp: Re: [jallib] Peripheral hardware and interrupts
Hi Rob
Hi Rob,
Perhaps you should disable/enable interrupts within the I2c procedures and
not for the entire main program.
The way you did it, by writing a flag in the ISR and reading it in the main
is correct. If you need less delay between the main execution and interrupt
flag refresh, you should have
Hi all,
I have the following issue and I am interested in either your suggestions
or if you encountered the same problem. The example is based on the sample
program I made for the real time clock library DS3231.
The DS3231 has two alarms and uses the IIC interface. The device has an
interrupt
