CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=6.0.x 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-06-07T06:03:45+00:00 Damien George damien.p.george@gmail.com 2017-06-07T06:00:18+00:00 urn:sha1:f86c57fedffcabbec94d4b56bb45cc627f48ab55 2017-02-15T05:39:30+00:00 Damien George damien.p.george@gmail.com 2017-02-15T05:39:30+00:00 urn:sha1:e5cc681cb1b5163b9ae3453df85344326baf9759 2016-10-21T05:26:01+00:00 Damien George damien.p.george@gmail.com 2016-10-18T00:06:20+00:00 urn:sha1:4ebdb1f2b217410cdc1cee0e0c0da8fceb7627f2 In order to have more fine-grained control over how builtin functions are constructed, the MP_DECLARE_CONST_FUN_OBJ macros are made more specific, with suffix of _0, _1, _2, _3, _VAR, _VAR_BETEEN or _KW. These names now match the MP_DEFINE_CONST_FUN_OBJ macros. 2015-12-09T09:56:36+00:00 neilh10 neilh20@wLLw.net 2015-12-08T22:02:34+00:00 urn:sha1:1be0fde45c8d84eaf04851af96f06aad8171b2b2 This is refactoring to enable support for the two USB PHYs available on some STM32F4 processors to be used at the same time. The F405/7 & F429 have two USB PHYs, others such as the F411 only have one PHY. This has been tested separately on a pyb10 (USB_FS PHY) and F429DISC (USB_HS PHY) to be able to invoke a REPL/USB. I have modified a PYBV10 to support two PHYs. The long term objective is to support a 2nd USB PHY to be brought up as a USB HOST, and possibly a single USB PHY to be OTG. 2015-02-13T14:02:51+00:00 Damien George damien.p.george@gmail.com 2015-02-03T22:37:50+00:00 urn:sha1:55d6218b9a17f23754bd00d2759800a1447599ca 2015-02-13T14:02:51+00:00 Damien George damien.p.george@gmail.com 2015-02-03T20:52:48+00:00 urn:sha1:39ce2db181ec1e06426e2a3a371d2cd535723a17 2015-02-13T14:02:51+00:00 Damien George damien.p.george@gmail.com 2014-11-01T21:26:06+00:00 urn:sha1:d39c7aa517b722161a7dd792fafc5096d58beec8 Different HID modes can be configured in Python. You can either use predefined mouse or keyboard, or write your own report descriptor.