CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=2.2.4 2017-07-31T08:35:40+00:00 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 2016-02-10T23:40:10+00:00 Damien George damien.p.george@gmail.com 2016-02-10T16:32:57+00:00 urn:sha1:b33a7705966a743c5e4c0c3c3bb83e6d97b5e84d This patch adds support to fsusermount for multiple block devices (instead of just one). The maximum allowed is fixed at compile time by the size of the fs_user_mount array accessed via MP_STATE_PORT, which in turn is set by MICROPY_FATFS_VOLUMES. With this patch, stmhal (which is still tightly coupled to fsusermount) is also modified to support mounting multiple devices And the flash and SD card are now just two block devices that are mounted at start up if they exist (and they have special native code to make them more efficient). 2016-02-10T23:40:10+00:00 Damien George damien.p.george@gmail.com 2016-02-10T16:21:38+00:00 urn:sha1:3770cd2e7062d0844cee7b69ec9d9f80a2ad1206 You can now create (singleton) objects representing the flash and SD card, using: flash = pyb.Flash() sdcard = pyb.SDCard() These objects provide the block protocol. 2015-11-24T16:57:13+00:00 Damien George damien.p.george@gmail.com 2015-11-24T16:57:13+00:00 urn:sha1:65888e2006ad5aac6d613550aecea9956562eb59 2015-11-24T16:18:07+00:00 Damien George damien.p.george@gmail.com 2015-11-24T16:18:07+00:00 urn:sha1:e99e6c883d70eda894aba124c8ee0495dc90c350 Using SysTick to do the counting and dispatch of the flash storage idle handler is more efficient than requiring a dedicated hardware timer. No new counter is needed, just the existing uwTick variable. The processing is not actually done in the SysTick IRQ, it is deferred to the flash IRQ (which runs at lower priority). 2014-05-03T22:27:38+00:00 Damien George damien.p.george@gmail.com 2014-05-03T22:27:38+00:00 urn:sha1:04b9147e150d2d6fa3750f312fe328b6a71c1b28 Blanket wide to all .c and .h files. Some files originating from ST are difficult to deal with (license wise) so it was left out of those. Also merged modpyb.h, modos.h, modstm.h and modtime.h in stmhal/. 2014-04-16T22:08:36+00:00 Damien George damien.p.george@gmail.com 2014-04-16T22:08:36+00:00 urn:sha1:6d983539bcff2a540dd136a7e84e1db2b334528f Internal flash used for the filesystem is now written (from the cache) only after a 5s delay, or when a file is closed, or when the drive is unmounted from the host. This delay means that multiple writes can accumulate in the cache, and leads to less writes to the flash, making it last longer. It's implemented by a high-priority interrupt that takes care of flash erase and write, and flushing the cache. This is still only an interim solution for the flash filesystem. It eventually needs to be replaced with something that uses less RAM for the cache, something that can use more of the flash, and something that does proper wear levelling. 2014-03-17T13:31:35+00:00 Damien George damien.p.george@gmail.com 2014-03-17T13:31:35+00:00 urn:sha1:9e5ea4d768da3273b6d060cceffcc858e1c4827d