configuration files

[ChrisAtSamraksh]

If the configuration files for code / memory placement are changed, this change appears to need the change reflected in both the tinybooter and tinyclr.

Upon removal of the NOR external memory the radio would not initialize properly after the configuration files were changed and a new tinybooter and tinyclr were programmed.

[MichaelAtSamraksh]

I propose the relocation issue be fixed via automatic configuration from platform_selector.h

Benefit: Time saved in preventing the relocation config problem happening in the future to someone else. This is not the last time the address space layout will change. Benefit: We can trim the wasted memory region that occurs between the end of TinyBooter and the beginning of TinyCLR. Right now TinyCLR starts at 0x0802 0000 which makes it human friendly, but really TinyCLR should start at 0x0800 0000 + sizeof(TinyBooter).

I looked into code/memory placement when I removed the tinybooter in my private build last month. While the TINYCLR_SOLO preprocessor definition helps, the XML scatterfile configurations need to be conditionally changed to match the configuration set by the TINYCLR_SOLO preprocessor definition. Both the XML scatterfile for TinyCLR and the XML scatterfile for TinyBooter need to be changed to accommodate shifting native applications around.

• [x] Issue 1) Use TINYCLR_SOLO in Solutions\platform_selector.h
• [ ] Issue 2) Use TINYCLR_SOLO in Solutions\EmoteDotNow\TinyCLR\GNU_S\tinyclr_vector.cpp

#ifdef TINYCLR_SOLO
    *(__IO uint32_t *) VectorTableOffsetRegister |= (uint32_t) 0;
#else
    *(__IO uint32_t *) VectorTableOffsetRegister |= (uint32_t) TINYCLR_OFFSET;
#endif

• [ ] Issue 3) Create TINYCLR_OFFSET preprocessor definition. In platform_selector.h:

#define TINYCLR_OFFSET 0x20000

• [ ] In tinyclr_vector.cpp: (might be better to skip this and force the issue on the developer)

#ifndef TINYCLR_OFFSET
#define TINYCLR_OFFSET 0x20000
#endif

• [ ] Issue 4) Change Solutions\EmoteDotNow\TinyCLR\scatterfile_tinyclr_gcc.xml ... this is where I stopped because I didn't have time to test passing a configuration from the msbuild file to the XML scatter file used by GCC-ARM. But the gist is to conditionally use TINYCLR_SOLO and TINYCLR_OFFSET here. Also change Solutions\EmoteDotNow\TinyBooter\scatterfile_tinybooter_gcc.xml ... TinyBooter's scatterfile should complement TinyClr's scatterfile.
• [ ] Issue 5) Add conditional TINYCLR_SOLO and TINYCLR_OFFSET definitions in the TinyCLR.proj and TinyBooter.proj files that are overridden by a previous definition in the EmoteDotNow's overall dotnetmf.proj file, for a unified build.