CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=5.0.0-beta.3 2017-09-06T03:40:51+00:00 2017-09-06T03:40:51+00:00 Damien George damien.p.george@gmail.com 2017-09-06T03:40:51+00:00 urn:sha1:01dd7804b87d60b2deab16712eccb3b97351a9b7 This is to keep the top-level directory clean, to make it clear what is core and what is a port, and to allow the repository to grow with new ports in a sustainable way. 2017-07-31T08:35:40+00:00 Alexander Steffen devel.20.webmeister@spamgourmet.com 2017-06-30T07:22:17+00:00 urn:sha1:55f33240f3d7051d4213629e92437a36f1fac50e There were several different spellings of MicroPython present in comments, when there should be only one. 2017-07-18T01:57:39+00:00 Alexander Steffen devel.20.webmeister@spamgourmet.com 2017-06-29T21:14:58+00:00 urn:sha1:299bc625864b9e624ed599c94a5f95870516139a The code conventions suggest using header guards, but do not define how those should look like and instead point to existing files. However, not all existing files follow the same scheme, sometimes omitting header guards altogether, sometimes using non-standard names, making it easy to accidentally pick a "wrong" example. This commit ensures that all header files of the MicroPython project (that were not simply copied from somewhere else) follow the same pattern, that was already present in the majority of files, especially in the py folder. The rules are as follows. Naming convention: * start with the words MICROPY_INCLUDED * contain the full path to the file * replace special characters with _ In addition, there are no empty lines before #ifndef, between #ifndef and one empty line before #endif. #endif is followed by a comment containing the name of the guard macro. py/grammar.h cannot use header guards by design, since it has to be included multiple times in a single C file. Several other files also do not need header guards as they are only used internally and guaranteed to be included only once: * MICROPY_MPHALPORT_H * mpconfigboard.h * mpconfigport.h * mpthreadport.h * pin_defs_*.h * qstrdefs*.h 2017-03-30T06:55:21+00:00 Damien George damien.p.george@gmail.com 2017-03-30T06:55:21+00:00 urn:sha1:7876e54aa5ebd0daca0fa4cd7b0faaa424b1d23d By default the SDIO (F4) or SDMMC1 (L4, F7) is used as the SD card peripheral, but if a board config defines MICROPY_HW_SDMMC2_CK and other pins then the SD card driver will use SDMMC2. 2016-11-25T00:21:18+00:00 Damien George damien.p.george@gmail.com 2016-11-25T00:21:18+00:00 urn:sha1:652ca2017d8da647b30bddd4a8f782d05fa97a60 2016-06-29T13:28:49+00:00 dpslwk dps.lwk@gmail.com 2016-06-29T11:26:21+00:00 urn:sha1:b03df60f32c977a8a272cdeeaf1812f79918e69c 2016-05-05T13:51:20+00:00 Tobias Badertscher python@baerospace.ch 2016-03-22T10:28:35+00:00 urn:sha1:e64032d6fdeb079de2ace20b64899d1ceb6754f1 The main thing is to change the DMA code in a way that the structure DMA_Stream_TypeDef (which is similar to DMA_Channel_TypeDef on stm32l4) is no longer used outside of dma.c, as this structure only exists for the F4 series. Therefore I introduced a new structure (dma_descr_t) which handles all DMA specific stuff for configuration. Further the periphery (spi, i2c, sdcard, dac) does not need to know the internals of the dma. 2015-12-16T00:38:36+00:00 Tobias Badertscher python@baerospace.ch 2015-12-08T14:41:47+00:00 urn:sha1:c5d8ffef581fe83ccec276d0bfa8fcc15e9f9524 This includes SPI4, SPI5 and SPI6. 2015-12-02T22:55:57+00:00 Dave Hylands dhylands@gmail.com 2015-12-01T08:42:47+00:00 urn:sha1:0077958ad0d278c87620ee8ead9a9aea80f1663d 2015-11-24T15:44:16+00:00 Damien George damien.p.george@gmail.com 2015-11-24T15:40:59+00:00 urn:sha1:22bd23114af166980bad6ff00caaf97fdb1f2cf4 This can be generalised if/when more processing is needed by SysTick. Thanks to @chuckbook for the idea.