a1c991d921
Move boards to boards folder * boards: rename configs folder to boards This is the proposed layout after the change: boards: - folder containing board folders <board>: - name of each board drivers: - extra drivers specific for platform include: - header files for the boars scripts: - extra scripts specific for platform src: - board specific code tools: - extra tools specific for platform <config>: - board specific configuration(s) Note: <xxx> names are dependent on platform This is a logical change to aim to the arch layout but this is a huge change it should be done in several steps to lower the risk. Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> * Kconfig: replace configs with boards The change is needed after the path change Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> * Makefile: replace configs with boards The change is needed after the path change Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> * Makefile.*: replace configs with boards The change is needed after the path change Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> * Make.defs: replace configs with boards The change is needed after the path change Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> * .sh: replace configs with boards The change is needed after the path change Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> * .mk: replace configs with boards The change is needed after the path change Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> * .c & .h: replace configs with boards The change is needed after the path change Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> * .bat: replace configs with boards The change is needed after the path change Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> Approved-by: Gregory Nutt <gnutt@nuttx.org> |
||
---|---|---|
.. | ||
include | ||
nsh | ||
scripts | ||
src | ||
Kconfig | ||
README.txt |
STATUS ====== 05/17: The basic NSH configuration is functional and shows that there is 3-4KB of free heap space. However, attempts to extend this have failed. I suspect that 8KB of SRAM is insufficient to do much with the existing NSH configuration. Perhaps some fine tuning can improve this situation but at this point, I think this board is only useful for the initial STM32 F0 bring-up, perhaps for embedded solutions that do not use NSH and for general experimentation. There is also support for the Nucleo boards with the STM32 F072 and F092 MCUs. Those ports do not suffer from these problems and seem to work well in fairly complex configurations. Apparently 8KB is SRAM is not usable but the parts with larger 16KB and 32KB SRAMs are better matches.