The solution suggested works possibly with the application code written but
we have the same error using the call to the printf library functions.
Typically the linker puts these functions at the end, so in the upper 128K.
The trampoline fails anyway.
Any chance to fix definitively this issue?
Rin
A note about the use of the trampoline in the AVR256.
I was in trouble cause a wrong address in the upper 128K using the
trampoline itself due to a linker error (I suppose). At the moment I don't
use EICALL for this reason.
If someone has news about this issue I'm very interested to fix the proble
Hi
I'm using this (for example):
File eedata.c
#include "eedata.h"
TOTAL_DATA total_data;
ERROR_DATA error_data;
TOTAL_DATA __attribute__((section(".eeprom"))) e2total_data =
{0,0,0,0,0,0,0,0,0,0,0,0,0,0,0};
ERROR_DATA __attribute__((section(".eeprom"))) error_data = {0,0};
File eedata.h
#d
