[fpc-devel] Writing to 16 bit timer registers on AVR (bug #34721)
Christo Crause
christo.crause at gmail.com
Sun Dec 23 06:58:33 CET 2018
According to AVR manuals 16 bit timer registers share a temp register which
requires a specific sequence for reading/writing: "To do a 16-bit write,
the high byte must be written before the low byte. For a 16-bit read, the
low byte must be read before the high byte." - from atmega328p 15.3
Accessing 16-bit Registers. I'm trying to patch the AVR code generator to
respect this sequence but I would appreciate some review of my attempt and
suggestions on how to improve it.
Attached please find a patch where I added code to avr/cgcpu methods
a_load_reg_ref and g_concatcopy. I try to identify 16 bit io registers by
checking whether the offset of the reference falls within 32 to srambase-1
and the size is OS_16/OS_S16 (or length=2). With this patch the compiler
generates (what I assume is) correct code for the following test cases
which should write to register 0x87 then 0x86 (-Wpatmega328p, so timer1 is
16-bit, -O2):
var x: uint16 = 1023;
ICR1 := x;
lds r0, 0x0101
sts 0x0087, r0
lds r0, 0x0100
sts 0x0086, r0
ICR1 := 1234;
ldi r18, 0xD2
ldi r19, 0x04
sts 0x0087, r19
sts 0x0086, r18
ICR1 := OCR1A; // should first read 0x88 then 0x89 and then write 0x87, 0x86
lds r19, 0x0088
lds r18, 0x0089
sts 0x0087, r18
sts 0x0086, r19
x := OCR1A; // read from io reg should be low byte first
lds r0, 0x0088
sts 0x0100, r0
lds r0, 0x0089
sts 0x0101, r0
Any further test cases I should consider (also other code which should not
trigger this modification) and ways to improve the patch would be
appreciated.
Regards,
Christo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freepascal.org/pipermail/fpc-devel/attachments/20181223/6e88d782/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cgcpu.patch
Type: text/x-patch
Size: 7807 bytes
Desc: not available
URL: <http://lists.freepascal.org/pipermail/fpc-devel/attachments/20181223/6e88d782/attachment.bin>
More information about the fpc-devel
mailing list