2011-07-05, 12:08:15
Well I got this all working in the end.
I would recomend modifying the linker script. It is important to remember to reserve the 4 addresses in the page BEFORE the bootloader, as the goto UserApp is placed there. That means most of the page with the goto UserApp in is available, but it is not suitable for use as an EEPROM page. So the last EEPROM page is best located 2 pages before the first page of the boot loader.
It is best to fix the address of the EEPROM pages, so modify the line in "DEE Emulation 16-bit.c"
from
__attribute__ ((space(psv), aligned(NUMBER_OF_INSTRUCTIONS_IN_PAGE * 2), noload));
to
__attribute__ ((space(psv), aligned(NUMBER_OF_INSTRUCTIONS_IN_PAGE * 2), address(EE_START_ADDR), noload));
Finally I was surprised to see the contents of my EEPROM pages preserved between firmware updates. I guess the ds30 Loader GUI or hex file does not contain instructions for programming these areas of "noload" flash.
Very pleased with the result!
I would recomend modifying the linker script. It is important to remember to reserve the 4 addresses in the page BEFORE the bootloader, as the goto UserApp is placed there. That means most of the page with the goto UserApp in is available, but it is not suitable for use as an EEPROM page. So the last EEPROM page is best located 2 pages before the first page of the boot loader.
It is best to fix the address of the EEPROM pages, so modify the line in "DEE Emulation 16-bit.c"
from
__attribute__ ((space(psv), aligned(NUMBER_OF_INSTRUCTIONS_IN_PAGE * 2), noload));
to
__attribute__ ((space(psv), aligned(NUMBER_OF_INSTRUCTIONS_IN_PAGE * 2), address(EE_START_ADDR), noload));
Finally I was surprised to see the contents of my EEPROM pages preserved between firmware updates. I guess the ds30 Loader GUI or hex file does not contain instructions for programming these areas of "noload" flash.
Very pleased with the result!