Opening this PR as a place to discuss changes, etc.
The current documentation seems outdated or something as the options have different names/usages (i.e. --big vs --rom X, and --sdram vs --ram X)
Here are just a few other things that needed modification in order to work with the current build:
[x] building for non-seed required editing to be up to date with current board APIs (i.e. changing separate process controls functions to hw.ProcessAllControls())
[x] for --big builds, the Makefile was missing the -DBOOT_VOLATILE C_DEF making them not run.
[x] we'll want to update the bootloader to the most recent version (v1.1 for the moment).
I'm working on making an example that uses a lot more space to see how that goes, but the heap SDRAM usage is working with a big delay line, and I've got it running from the internal SRAM without issue.
Just a few other things that tie into the bootloader stuff a bit as well, but stood out specifically for using this.
The way everything is set up for running from SDRAM or not relies on recompiling the library to set the VOLATILE related flags (i.e. VECT table offset, and the internal flag for System/Seed init stuff). Long term this is not ideal since it would require rebuilding the library when making programs with different options.
stephenhensley
commented
2 years ago
Opening this PR as a place to discuss changes, etc.
The current documentation seems outdated or something as the options have different names/usages (i.e.
--bigvs--rom X, and--sdramvs--ram X)Here are just a few other things that needed modification in order to work with the current build:
hw.ProcessAllControls())--bigbuilds, the Makefile was missing the-DBOOT_VOLATILEC_DEF making them not run.I'm working on making an example that uses a lot more space to see how that goes, but the heap SDRAM usage is working with a big delay line, and I've got it running from the internal SRAM without issue.
Just a few other things that tie into the bootloader stuff a bit as well, but stood out specifically for using this.
The way everything is set up for running from SDRAM or not relies on recompiling the library to set the
VOLATILErelated flags (i.e. VECT table offset, and the internal flag for System/Seed init stuff). Long term this is not ideal since it would require rebuilding the library when making programs with different options.