[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-gcc-list] eicall & EIND
From: |
Tristan Gingold |
Subject: |
Re: [avr-gcc-list] eicall & EIND |
Date: |
Wed, 2 Jul 2008 12:41:41 +0200 |
On Jul 2, 2008, at 12:13 PM, Dusan Ferbas wrote:
Hi Tristan,
thanks for reply.
Gcc can generate code for bootloader.
Sure but there might be subtile bugs.
gcc and ld assumes EIND=0 which is not correct for a bootloader.
But I am not sure if eicall does not require EIND to be filled with
ones.
Spec (AVR_instr_doc0856.pdf) is saying, that EIND is concatenated
with Z (r30, r31),
so EIND=1 should be sufficient.
But when call 0x1f800 is compiled for ATmega128, all "unused" MS
bits are filled with ones.
Can I look at your patch what is it about (support for eicall) ?
Sure, it is in the mailing list archive. But it is for the simulator.
Tristan.
Dusan
At 11:27 2.7.2008, Tristan Gingold wrote:
On Jul 2, 2008, at 11:14 AM, Dusan Ferbas wrote:
Hi Tristan,
I noticed a notice about eicall support.
(2008-06-26 Tristan Gingold <address@hidden> Add support for
avr6 instructions: eijmp, eicall)
Can you point me to some link/resource/advice ?
This is a patch for avrtest (not yet committed) - and avrtest doesn't
support bootloader.
I have not fully followed your issue. But from what I understand gcc
can't generate code
for 256x bootloader.
Dusan Ferbas
www.etech.cz