From nevil.hunt at hotmail.co.uk Sat Apr 2 15:02:54 2016 From: nevil.hunt at hotmail.co.uk (Nevil Hunt) Date: Sat, 2 Apr 2016 20:02:54 +0100 Subject: [Microbit-Python] I2C Examples? Message-ID: Hi, I'm just staring to experiment with attaching I2C devices to the micro:bit. I've found the definition of the functions, i.e. microbit.i2c.read(addr, n, repeat=False) & microbit.i2c.write(addr, buf, repeat=False) but does anyone have any example programs showing how to make use of the above commands on a micro:bit? FYI I have the Microchip MCP23017 I/O Expander hooked up to a micro:bit but if anyone has examples of using these commands to talk to any device that would be useful. Regards, Nevil -------------- next part -------------- An HTML attachment was scrubbed... URL: From microbit at sheep.art.pl Sat Apr 2 15:39:27 2016 From: microbit at sheep.art.pl (Radomir Dopieralski) Date: Sat, 2 Apr 2016 21:39:27 +0200 Subject: [Microbit-Python] I2C Examples? In-Reply-To: References: Message-ID: <20160402213927.22a19477@ghostwheel> Not sure how useful that is to you, but I used I2C to talk to my quadruped robot, effectively controlling it from the Micro:bit. Here's a short writeup on that: https://hackaday.io/project/6050-tote/log/28596-microtote And here's the source code (for the Arduino and the Micro:bit parts): https://bitbucket.org/thesheep/micro-tote/src On Sat, 2 Apr 2016 20:02:54 +0100 Nevil Hunt wrote: > Hi, > > I'm just staring to experiment with attaching I2C devices to the > micro:bit. > I've found the definition of the functions, i.e. > > microbit.i2c.read(addr, n, repeat=False) > & > microbit.i2c.write(addr, buf, repeat=False) > > but does anyone have any example programs showing how to make use of > the above commands on a micro:bit? > FYI I have the Microchip MCP23017 I/O Expander hooked up to a > micro:bit but if anyone has examples of using these commands to talk > to any device that would be useful. > Regards, > > Nevil > > -- Radomir Dopieralski -- Radomir Dopieralski From david at thinkingbinaries.com Sat Apr 2 16:06:38 2016 From: david at thinkingbinaries.com (David Whale) Date: Sat, 2 Apr 2016 21:06:38 +0100 Subject: [Microbit-Python] I2C Examples? In-Reply-To: References: Message-ID: Hi Nevil, Use this as a working example: http://skpang.co.uk/blog/archives/454 and refer to page 9 onwards of the device data sheet for the register numbers and data values: http://ww1.microchip.com/downloads/en/DeviceDoc/21952b.pdf David -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrewferguson500 at gmail.com Mon Apr 4 09:27:19 2016 From: andrewferguson500 at gmail.com (Andrew Ferguson 500) Date: Mon, 4 Apr 2016 14:27:19 +0100 Subject: [Microbit-Python] Testing Point Documentation Message-ID: <6DB8FA52-D9C2-48F5-984F-9503945C6066@gmail.com> Hi, I managed to persuade my teacher to let me borrow a teacher Micro:bit over the Easter holidays (I'm in Scotland so the student devices haven't arrived yet), but unfortunately I seem to have broken it. (I was just using 'screen' to test serial communication, one minute it worked and the next the screen session had closed, the micro:bit status light was off and the USB chip on the micro:bit got very hot). I suspect it's probably irreversibly broken, but I noticed that on the back of the micro:bit there are several testing points that may provide some insight as to what went wrong if probed with a multimeter. Does anyone know if there are any docs relating to which testing point links to what? Thanks, Andrew From carlos.p.a.87 at gmail.com Mon Apr 4 09:35:40 2016 From: carlos.p.a.87 at gmail.com (Carlos P.A.) Date: Mon, 4 Apr 2016 14:35:40 +0100 Subject: [Microbit-Python] Testing Point Documentation In-Reply-To: <6DB8FA52-D9C2-48F5-984F-9503945C6066@gmail.com> References: <6DB8FA52-D9C2-48F5-984F-9503945C6066@gmail.com> Message-ID: I haven't seen any schematics out yet, that seems to be part of the documentation that still needs to be open sourced. From the top of my head I vaguely remember the test points at the back probably connected to the microcontroller in charge of the USB communication (and, I assume, the battery controller), so they might be a programming interface more than actual test points. Does you computer recognise the microbit at all? On 4 April 2016 at 14:27, Andrew Ferguson 500 wrote: > Hi, > > I managed to persuade my teacher to let me borrow a teacher Micro:bit over > the Easter holidays (I'm in Scotland so the student devices haven't arrived > yet), but unfortunately I seem to have broken it. (I was just using > 'screen' to test serial communication, one minute it worked and the next > the screen session had closed, the micro:bit status light was off and the > USB chip on the micro:bit got very hot). > > I suspect it's probably irreversibly broken, but I noticed that on the > back of the micro:bit there are several testing points that may provide > some insight as to what went wrong if probed with a multimeter. Does anyone > know if there are any docs relating to which testing point links to what? > > Thanks, > Andrew > > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrewferguson500 at gmail.com Mon Apr 4 09:44:23 2016 From: andrewferguson500 at gmail.com (Andrew Ferguson 500) Date: Mon, 4 Apr 2016 14:44:23 +0100 Subject: [Microbit-Python] Testing Point Documentation In-Reply-To: References: <6DB8FA52-D9C2-48F5-984F-9503945C6066@gmail.com> Message-ID: <73F6C28F-45C9-45E7-B725-69ECB6B61A9A@gmail.com> No, the computer does not recognise the micro:bit. If I power the micro:bit from the 2x AAA batteries nothing happens at all. (No light, no chips getting hot). Hopefully more stuff will be released as Free Software / open source soon (especially the DAL and the iOS and Android apps). On 4 Apr 2016, at 14:35, "Carlos P.A." wrote: > I haven't seen any schematics out yet, that seems to be part of the documentation that still needs to be open sourced. From the top of my head I vaguely remember the test points at the back probably connected to the microcontroller in charge of the USB communication (and, I assume, the battery controller), so they might be a programming interface more than actual test points. > > Does you computer recognise the microbit at all? > > On 4 April 2016 at 14:27, Andrew Ferguson 500 wrote: > Hi, > > I managed to persuade my teacher to let me borrow a teacher Micro:bit over the Easter holidays (I'm in Scotland so the student devices haven't arrived yet), but unfortunately I seem to have broken it. (I was just using 'screen' to test serial communication, one minute it worked and the next the screen session had closed, the micro:bit status light was off and the USB chip on the micro:bit got very hot). > > I suspect it's probably irreversibly broken, but I noticed that on the back of the micro:bit there are several testing points that may provide some insight as to what went wrong if probed with a multimeter. Does anyone know if there are any docs relating to which testing point links to what? > > Thanks, > Andrew > > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit -------------- next part -------------- An HTML attachment was scrubbed... URL: From damien.p.george at gmail.com Mon Apr 4 10:13:00 2016 From: damien.p.george at gmail.com (Damien George) Date: Mon, 4 Apr 2016 15:13:00 +0100 Subject: [Microbit-Python] Testing Point Documentation In-Reply-To: <73F6C28F-45C9-45E7-B725-69ECB6B61A9A@gmail.com> References: <6DB8FA52-D9C2-48F5-984F-9503945C6066@gmail.com> <73F6C28F-45C9-45E7-B725-69ECB6B61A9A@gmail.com> Message-ID: There was a problem with some of the microbit's having their USB chip get "hot" but I thought it was resolved. I'll ask Jonny about it. On Mon, Apr 4, 2016 at 2:44 PM, Andrew Ferguson 500 wrote: > No, the computer does not recognise the micro:bit. If I power the micro:bit > from the 2x AAA batteries nothing happens at all. (No light, no chips > getting hot). > > Hopefully more stuff will be released as Free Software / open source soon > (especially the DAL and the iOS and Android apps). > > > On 4 Apr 2016, at 14:35, "Carlos P.A." wrote: > > I haven't seen any schematics out yet, that seems to be part of the > documentation that still needs to be open sourced. From the top of my head I > vaguely remember the test points at the back probably connected to the > microcontroller in charge of the USB communication (and, I assume, the > battery controller), so they might be a programming interface more than > actual test points. > > Does you computer recognise the microbit at all? > > On 4 April 2016 at 14:27, Andrew Ferguson 500 > wrote: >> >> Hi, >> >> I managed to persuade my teacher to let me borrow a teacher Micro:bit over >> the Easter holidays (I'm in Scotland so the student devices haven't arrived >> yet), but unfortunately I seem to have broken it. (I was just using 'screen' >> to test serial communication, one minute it worked and the next the screen >> session had closed, the micro:bit status light was off and the USB chip on >> the micro:bit got very hot). >> >> I suspect it's probably irreversibly broken, but I noticed that on the >> back of the micro:bit there are several testing points that may provide some >> insight as to what went wrong if probed with a multimeter. Does anyone know >> if there are any docs relating to which testing point links to what? >> >> Thanks, >> Andrew >> >> >> _______________________________________________ >> Microbit mailing list >> Microbit at python.org >> https://mail.python.org/mailman/listinfo/microbit > > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > From radomir at dopieralski.pl Mon Apr 4 09:30:15 2016 From: radomir at dopieralski.pl (Radomir Dopieralski) Date: Mon, 4 Apr 2016 15:30:15 +0200 Subject: [Microbit-Python] Testing Point Documentation In-Reply-To: <6DB8FA52-D9C2-48F5-984F-9503945C6066@gmail.com> References: <6DB8FA52-D9C2-48F5-984F-9503945C6066@gmail.com> Message-ID: <20160404153015.3d06b6f8@ghostwheel> Hi, we are still waiting for BBC to release the promised technical documentation on the Micro:bit. I'm sure that the schematics and board layout designs are enough to figure out what those test points do, but until that is published, there is very little information. Then again, I doubt this would help you. What you describe really sounds like a failure in that USB chip, and I don't think you can do much about that. On Mon, 4 Apr 2016 14:27:19 +0100 Andrew Ferguson 500 wrote: > Hi, > > I managed to persuade my teacher to let me borrow a teacher Micro:bit > over the Easter holidays (I'm in Scotland so the student devices > haven't arrived yet), but unfortunately I seem to have broken it. (I > was just using 'screen' to test serial communication, one minute it > worked and the next the screen session had closed, the micro:bit > status light was off and the USB chip on the micro:bit got very hot). > > I suspect it's probably irreversibly broken, but I noticed that on > the back of the micro:bit there are several testing points that may > provide some insight as to what went wrong if probed with a > multimeter. Does anyone know if there are any docs relating to which > testing point links to what? > > Thanks, > Andrew > > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit -- Radomir Dopieralski From andrewferguson500 at gmail.com Mon Apr 4 10:24:08 2016 From: andrewferguson500 at gmail.com (Andrew Ferguson 500) Date: Mon, 4 Apr 2016 15:24:08 +0100 Subject: [Microbit-Python] Testing Point Documentation In-Reply-To: References: <6DB8FA52-D9C2-48F5-984F-9503945C6066@gmail.com> <73F6C28F-45C9-45E7-B725-69ECB6B61A9A@gmail.com> Message-ID: Thanks, it does get quite hot if left on for more than ~30 seconds. (After about 10 it is too hot to touch, after 20 it is very warm on the other side of the board. I haven't left it on for more than about 2-3 minutes). This was one of the teacher devices so it could be a slightly earlier version than the final student devices. On 4 Apr 2016, at 15:13, Damien George wrote: > There was a problem with some of the microbit's having their USB chip > get "hot" but I thought it was resolved. I'll ask Jonny about it. > > On Mon, Apr 4, 2016 at 2:44 PM, Andrew Ferguson 500 > wrote: >> No, the computer does not recognise the micro:bit. If I power the micro:bit >> from the 2x AAA batteries nothing happens at all. (No light, no chips >> getting hot). >> >> Hopefully more stuff will be released as Free Software / open source soon >> (especially the DAL and the iOS and Android apps). >> >> >> On 4 Apr 2016, at 14:35, "Carlos P.A." wrote: >> >> I haven't seen any schematics out yet, that seems to be part of the >> documentation that still needs to be open sourced. From the top of my head I >> vaguely remember the test points at the back probably connected to the >> microcontroller in charge of the USB communication (and, I assume, the >> battery controller), so they might be a programming interface more than >> actual test points. >> >> Does you computer recognise the microbit at all? >> >> On 4 April 2016 at 14:27, Andrew Ferguson 500 >> wrote: >>> >>> Hi, >>> >>> I managed to persuade my teacher to let me borrow a teacher Micro:bit over >>> the Easter holidays (I'm in Scotland so the student devices haven't arrived >>> yet), but unfortunately I seem to have broken it. (I was just using 'screen' >>> to test serial communication, one minute it worked and the next the screen >>> session had closed, the micro:bit status light was off and the USB chip on >>> the micro:bit got very hot). >>> >>> I suspect it's probably irreversibly broken, but I noticed that on the >>> back of the micro:bit there are several testing points that may provide some >>> insight as to what went wrong if probed with a multimeter. Does anyone know >>> if there are any docs relating to which testing point links to what? >>> >>> Thanks, >>> Andrew >>> >>> >>> _______________________________________________ >>> Microbit mailing list >>> Microbit at python.org >>> https://mail.python.org/mailman/listinfo/microbit >> >> >> _______________________________________________ >> Microbit mailing list >> Microbit at python.org >> https://mail.python.org/mailman/listinfo/microbit >> >> >> _______________________________________________ >> Microbit mailing list >> Microbit at python.org >> https://mail.python.org/mailman/listinfo/microbit >> > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit From ntoll at ntoll.org Mon Apr 4 10:22:28 2016 From: ntoll at ntoll.org (Nicholas H.Tollervey) Date: Mon, 4 Apr 2016 15:22:28 +0100 Subject: [Microbit-Python] Testing Point Documentation In-Reply-To: References: <6DB8FA52-D9C2-48F5-984F-9503945C6066@gmail.com> <73F6C28F-45C9-45E7-B725-69ECB6B61A9A@gmail.com> Message-ID: <570278A4.8010304@ntoll.org> If it has a tick mark on the front, top left corner (where the "hair" is), then I believe it's been checked for the overheating problem and passed. No tick = likely to be an earlier pre-solution version of the board. N. On 04/04/16 15:24, Andrew Ferguson 500 wrote: > Thanks, it does get quite hot if left on for more than ~30 seconds. > (After about 10 it is too hot to touch, after 20 it is very warm on > the other side of the board. I haven't left it on for more than about > 2-3 minutes). > > This was one of the teacher devices so it could be a slightly earlier > version than the final student devices. > > On 4 Apr 2016, at 15:13, Damien George > wrote: > >> There was a problem with some of the microbit's having their USB >> chip get "hot" but I thought it was resolved. I'll ask Jonny about >> it. >> >> On Mon, Apr 4, 2016 at 2:44 PM, Andrew Ferguson 500 >> wrote: >>> No, the computer does not recognise the micro:bit. If I power the >>> micro:bit from the 2x AAA batteries nothing happens at all. (No >>> light, no chips getting hot). >>> >>> Hopefully more stuff will be released as Free Software / open >>> source soon (especially the DAL and the iOS and Android apps). >>> >>> >>> On 4 Apr 2016, at 14:35, "Carlos P.A." >>> wrote: >>> >>> I haven't seen any schematics out yet, that seems to be part of >>> the documentation that still needs to be open sourced. From the >>> top of my head I vaguely remember the test points at the back >>> probably connected to the microcontroller in charge of the USB >>> communication (and, I assume, the battery controller), so they >>> might be a programming interface more than actual test points. >>> >>> Does you computer recognise the microbit at all? >>> >>> On 4 April 2016 at 14:27, Andrew Ferguson 500 >>> wrote: >>>> >>>> Hi, >>>> >>>> I managed to persuade my teacher to let me borrow a teacher >>>> Micro:bit over the Easter holidays (I'm in Scotland so the >>>> student devices haven't arrived yet), but unfortunately I seem >>>> to have broken it. (I was just using 'screen' to test serial >>>> communication, one minute it worked and the next the screen >>>> session had closed, the micro:bit status light was off and the >>>> USB chip on the micro:bit got very hot). >>>> >>>> I suspect it's probably irreversibly broken, but I noticed that >>>> on the back of the micro:bit there are several testing points >>>> that may provide some insight as to what went wrong if probed >>>> with a multimeter. Does anyone know if there are any docs >>>> relating to which testing point links to what? >>>> >>>> Thanks, Andrew >>>> >>>> >>>> _______________________________________________ Microbit >>>> mailing list Microbit at python.org >>>> https://mail.python.org/mailman/listinfo/microbit >>> >>> >>> _______________________________________________ Microbit mailing >>> list Microbit at python.org >>> https://mail.python.org/mailman/listinfo/microbit >>> >>> >>> _______________________________________________ Microbit mailing >>> list Microbit at python.org >>> https://mail.python.org/mailman/listinfo/microbit >>> >> _______________________________________________ Microbit mailing >> list Microbit at python.org >> https://mail.python.org/mailman/listinfo/microbit > _______________________________________________ Microbit mailing > list Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > From andrewferguson500 at gmail.com Mon Apr 4 10:46:21 2016 From: andrewferguson500 at gmail.com (Andrew Ferguson 500) Date: Mon, 4 Apr 2016 15:46:21 +0100 Subject: [Microbit-Python] Testing Point Documentation In-Reply-To: <570278A4.8010304@ntoll.org> References: <6DB8FA52-D9C2-48F5-984F-9503945C6066@gmail.com> <73F6C28F-45C9-45E7-B725-69ECB6B61A9A@gmail.com> <570278A4.8010304@ntoll.org> Message-ID: <061BBE1C-04D1-4B43-A61A-87DD3A1F0CF8@gmail.com> Hi Nicholas, Ah, my micro:bit does not have a tick, so that's probably the problem. Is there any more info anywhere about this overheating problem? (how it occurs, what can be done to avoid it, etc...). On 4 Apr 2016, at 15:22, "Nicholas H.Tollervey" wrote: > If it has a tick mark on the front, top left corner (where the "hair" > is), then I believe it's been checked for the overheating problem and > passed. No tick = likely to be an earlier pre-solution version of the board. > > N. > > On 04/04/16 15:24, Andrew Ferguson 500 wrote: >> Thanks, it does get quite hot if left on for more than ~30 seconds. >> (After about 10 it is too hot to touch, after 20 it is very warm on >> the other side of the board. I haven't left it on for more than about >> 2-3 minutes). >> >> This was one of the teacher devices so it could be a slightly earlier >> version than the final student devices. >> >> On 4 Apr 2016, at 15:13, Damien George >> wrote: >> >>> There was a problem with some of the microbit's having their USB >>> chip get "hot" but I thought it was resolved. I'll ask Jonny about >>> it. >>> >>> On Mon, Apr 4, 2016 at 2:44 PM, Andrew Ferguson 500 >>> wrote: >>>> No, the computer does not recognise the micro:bit. If I power the >>>> micro:bit from the 2x AAA batteries nothing happens at all. (No >>>> light, no chips getting hot). >>>> >>>> Hopefully more stuff will be released as Free Software / open >>>> source soon (especially the DAL and the iOS and Android apps). >>>> >>>> >>>> On 4 Apr 2016, at 14:35, "Carlos P.A." >>>> wrote: >>>> >>>> I haven't seen any schematics out yet, that seems to be part of >>>> the documentation that still needs to be open sourced. From the >>>> top of my head I vaguely remember the test points at the back >>>> probably connected to the microcontroller in charge of the USB >>>> communication (and, I assume, the battery controller), so they >>>> might be a programming interface more than actual test points. >>>> >>>> Does you computer recognise the microbit at all? >>>> >>>> On 4 April 2016 at 14:27, Andrew Ferguson 500 >>>> wrote: >>>>> >>>>> Hi, >>>>> >>>>> I managed to persuade my teacher to let me borrow a teacher >>>>> Micro:bit over the Easter holidays (I'm in Scotland so the >>>>> student devices haven't arrived yet), but unfortunately I seem >>>>> to have broken it. (I was just using 'screen' to test serial >>>>> communication, one minute it worked and the next the screen >>>>> session had closed, the micro:bit status light was off and the >>>>> USB chip on the micro:bit got very hot). >>>>> >>>>> I suspect it's probably irreversibly broken, but I noticed that >>>>> on the back of the micro:bit there are several testing points >>>>> that may provide some insight as to what went wrong if probed >>>>> with a multimeter. Does anyone know if there are any docs >>>>> relating to which testing point links to what? >>>>> >>>>> Thanks, Andrew >>>>> >>>>> >>>>> _______________________________________________ Microbit >>>>> mailing list Microbit at python.org >>>>> https://mail.python.org/mailman/listinfo/microbit >>>> >>>> >>>> _______________________________________________ Microbit mailing >>>> list Microbit at python.org >>>> https://mail.python.org/mailman/listinfo/microbit >>>> >>>> >>>> _______________________________________________ Microbit mailing >>>> list Microbit at python.org >>>> https://mail.python.org/mailman/listinfo/microbit >>>> >>> _______________________________________________ Microbit mailing >>> list Microbit at python.org >>> https://mail.python.org/mailman/listinfo/microbit >> _______________________________________________ Microbit mailing >> list Microbit at python.org >> https://mail.python.org/mailman/listinfo/microbit >> > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit From ntoll at ntoll.org Mon Apr 4 10:53:44 2016 From: ntoll at ntoll.org (Nicholas H.Tollervey) Date: Mon, 4 Apr 2016 15:53:44 +0100 Subject: [Microbit-Python] Testing Point Documentation In-Reply-To: <061BBE1C-04D1-4B43-A61A-87DD3A1F0CF8@gmail.com> References: <6DB8FA52-D9C2-48F5-984F-9503945C6066@gmail.com> <73F6C28F-45C9-45E7-B725-69ECB6B61A9A@gmail.com> <570278A4.8010304@ntoll.org> <061BBE1C-04D1-4B43-A61A-87DD3A1F0CF8@gmail.com> Message-ID: <57027FF8.3090903@ntoll.org> On 04/04/16 15:46, Andrew Ferguson 500 wrote: > Hi Nicholas, > > Ah, my micro:bit does not have a tick, so that's probably the > problem. > > Is there any more info anywhere about this overheating problem? (how > it occurs, what can be done to avoid it, etc...). > You should send it back to the BBC. Phil Meitiner (cc'd) is the guy to address it to, although I believe his contract finished at the end of last month. N. From nevil.hunt at hotmail.co.uk Mon Apr 4 13:52:34 2016 From: nevil.hunt at hotmail.co.uk (Nevil Hunt) Date: Mon, 4 Apr 2016 18:52:34 +0100 Subject: [Microbit-Python] I2C Examples? In-Reply-To: <20160402213927.22a19477@ghostwheel> References: , <20160402213927.22a19477@ghostwheel> Message-ID: It was a bit of a struggle to get it working but thanks to the help from David & Radomir I now have the MCP23017 working with the micro:bit! The I2C command format is slightly different from the Raspberry Pi and doesn't quite match the format given in the micro-python "readthedocs" but the code below works. (This chip defaults to "Bank 0" mode and I couldn't work out how the register mapping worked but the register mapping for "Bank 1" mode seemed much more straight forward so that's what I've used). from microbit import * import microbit import struct i2c.write(0x20,struct.pack(' Date: Sat, 2 Apr 2016 21:39:27 +0200 > From: microbit at sheep.art.pl > To: microbit at python.org > Subject: Re: [Microbit-Python] I2C Examples? > > Not sure how useful that is to you, but I used I2C to talk to my > quadruped robot, effectively controlling it from the Micro:bit. > > Here's a short writeup on that: > https://hackaday.io/project/6050-tote/log/28596-microtote > > And here's the source code (for the Arduino and the Micro:bit parts): > https://bitbucket.org/thesheep/micro-tote/src > > On Sat, 2 Apr 2016 20:02:54 +0100 > Nevil Hunt wrote: > > > Hi, > > > > I'm just staring to experiment with attaching I2C devices to the > > micro:bit. > > I've found the definition of the functions, i.e. > > > > microbit.i2c.read(addr, n, repeat=False) > > & > > microbit.i2c.write(addr, buf, repeat=False) > > > > but does anyone have any example programs showing how to make use of > > the above commands on a micro:bit? > > FYI I have the Microchip MCP23017 I/O Expander hooked up to a > > micro:bit but if anyone has examples of using these commands to talk > > to any device that would be useful. > > Regards, > > > > Nevil > > > > > > > -- > Radomir Dopieralski > > -- > Radomir Dopieralski > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit -------------- next part -------------- An HTML attachment was scrubbed... URL: From giles.booth at gmail.com Tue Apr 5 04:20:02 2016 From: giles.booth at gmail.com (Giles Booth) Date: Tue, 5 Apr 2016 09:20:02 +0100 Subject: [Microbit-Python] Testing Point Documentation In-Reply-To: <061BBE1C-04D1-4B43-A61A-87DD3A1F0CF8@gmail.com> References: <6DB8FA52-D9C2-48F5-984F-9503945C6066@gmail.com> <73F6C28F-45C9-45E7-B725-69ECB6B61A9A@gmail.com> <570278A4.8010304@ntoll.org> <061BBE1C-04D1-4B43-A61A-87DD3A1F0CF8@gmail.com> Message-ID: Hi Andrew - very interested to hear about this as I had the same experience with 3 out of 4 of my initial teacher microbits. One got very hot and died, another got very hot but remained working, a third runs much warmer than the 4th unit. The last unit that died was a replacement and had only been used in a classroom and never had anything attached to its GPIO pins. Phil Meitiner and BBC have been very helpful, sending me 5 more microbits to test - all ok but not tested with actual children, which was when my initial teacher units started to malfunction. Andrew, did you use the GPIO pins at all with yours or just USB? many thanks Giles On 4 April 2016 at 15:46, Andrew Ferguson 500 wrote: > Hi Nicholas, > > Ah, my micro:bit does not have a tick, so that's probably the problem. > > Is there any more info anywhere about this overheating problem? (how it > occurs, what can be done to avoid it, etc...). > > On 4 Apr 2016, at 15:22, "Nicholas H.Tollervey" wrote: > > > If it has a tick mark on the front, top left corner (where the "hair" > > is), then I believe it's been checked for the overheating problem and > > passed. No tick = likely to be an earlier pre-solution version of the > board. > > > > N. > > > > On 04/04/16 15:24, Andrew Ferguson 500 wrote: > >> Thanks, it does get quite hot if left on for more than ~30 seconds. > >> (After about 10 it is too hot to touch, after 20 it is very warm on > >> the other side of the board. I haven't left it on for more than about > >> 2-3 minutes). > >> > >> This was one of the teacher devices so it could be a slightly earlier > >> version than the final student devices. > >> > >> On 4 Apr 2016, at 15:13, Damien George > >> wrote: > >> > >>> There was a problem with some of the microbit's having their USB > >>> chip get "hot" but I thought it was resolved. I'll ask Jonny about > >>> it. > >>> > >>> On Mon, Apr 4, 2016 at 2:44 PM, Andrew Ferguson 500 > >>> wrote: > >>>> No, the computer does not recognise the micro:bit. If I power the > >>>> micro:bit from the 2x AAA batteries nothing happens at all. (No > >>>> light, no chips getting hot). > >>>> > >>>> Hopefully more stuff will be released as Free Software / open > >>>> source soon (especially the DAL and the iOS and Android apps). > >>>> > >>>> > >>>> On 4 Apr 2016, at 14:35, "Carlos P.A." > >>>> wrote: > >>>> > >>>> I haven't seen any schematics out yet, that seems to be part of > >>>> the documentation that still needs to be open sourced. From the > >>>> top of my head I vaguely remember the test points at the back > >>>> probably connected to the microcontroller in charge of the USB > >>>> communication (and, I assume, the battery controller), so they > >>>> might be a programming interface more than actual test points. > >>>> > >>>> Does you computer recognise the microbit at all? > >>>> > >>>> On 4 April 2016 at 14:27, Andrew Ferguson 500 > >>>> wrote: > >>>>> > >>>>> Hi, > >>>>> > >>>>> I managed to persuade my teacher to let me borrow a teacher > >>>>> Micro:bit over the Easter holidays (I'm in Scotland so the > >>>>> student devices haven't arrived yet), but unfortunately I seem > >>>>> to have broken it. (I was just using 'screen' to test serial > >>>>> communication, one minute it worked and the next the screen > >>>>> session had closed, the micro:bit status light was off and the > >>>>> USB chip on the micro:bit got very hot). > >>>>> > >>>>> I suspect it's probably irreversibly broken, but I noticed that > >>>>> on the back of the micro:bit there are several testing points > >>>>> that may provide some insight as to what went wrong if probed > >>>>> with a multimeter. Does anyone know if there are any docs > >>>>> relating to which testing point links to what? > >>>>> > >>>>> Thanks, Andrew > >>>>> > >>>>> > >>>>> _______________________________________________ Microbit > >>>>> mailing list Microbit at python.org > >>>>> https://mail.python.org/mailman/listinfo/microbit > >>>> > >>>> > >>>> _______________________________________________ Microbit mailing > >>>> list Microbit at python.org > >>>> https://mail.python.org/mailman/listinfo/microbit > >>>> > >>>> > >>>> _______________________________________________ Microbit mailing > >>>> list Microbit at python.org > >>>> https://mail.python.org/mailman/listinfo/microbit > >>>> > >>> _______________________________________________ Microbit mailing > >>> list Microbit at python.org > >>> https://mail.python.org/mailman/listinfo/microbit > >> _______________________________________________ Microbit mailing > >> list Microbit at python.org > >> https://mail.python.org/mailman/listinfo/microbit > >> > > > > _______________________________________________ > > Microbit mailing list > > Microbit at python.org > > https://mail.python.org/mailman/listinfo/microbit > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > -- Giles Booth www.suppertime.co.uk/blogmywiki -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrewferguson500 at gmail.com Tue Apr 5 04:38:47 2016 From: andrewferguson500 at gmail.com (Andrew Ferguson 500) Date: Tue, 5 Apr 2016 09:38:47 +0100 Subject: [Microbit-Python] Testing Point Documentation In-Reply-To: References: <6DB8FA52-D9C2-48F5-984F-9503945C6066@gmail.com> <73F6C28F-45C9-45E7-B725-69ECB6B61A9A@gmail.com> <570278A4.8010304@ntoll.org> <061BBE1C-04D1-4B43-A61A-87DD3A1F0CF8@gmail.com> Message-ID: Hi Giles, I've been in touch with Philip and he'll be sending me a replacement shortly (thanks Philip!). Below is a description of my usage of my micro:bit (taken from my email to Philip). Apart from two or three times where it was powered from the official 2x AAA battery charger, I've exclusively powered it over USB from the USB port on my laptop. (Sony VAIO VGN-C2S running Debian 7 GNU / Linux). When the issue developed, I was powering it from my laptop and hadn't powered it off batteries for at least four days. It has never been powered off a mains phone charger. When using it though USB I have always used the supplied USB cable. I am not aware of any ESD events, and when not in use I stored the micro:bit in the original anti-static bag. I'm not quite sure what you mean by 'grounded', the device was plugged into the laptop through USB but the laptop was not connected to mains. (If you mean something else, please let me know). The fault occurred whilst I was testing the serial output of the micro:bit. It was running a Python program to output some text and wait 1 second whenever the 'A' button was pressed. I was using the 'screen' utility to view the output. ('screen /dev/ttyACM0 115200'). Mid-way through the testing, the screen session exited, and I noticed that the power LED on the micro:bit had gone off. About ten seconds later I realised that the micro:bit was getting hot, and so I unplugged it from the computer. As far as I can think of there has been nothing else during the use of the device that could have caused this. I was the first person to use the device (the teacher used one of the other three devices that was sent). As far as use is concerned, I have flashed it with various different .hex files, but have not used the I/O ports at all so it has not been connected to any device which could have caused the problem. Giles, which chip on your micro:bit got hot? (On mine it was the USB serial chip), and how hot did they get - particularly the one that kept working? Mine got too hot to touch after about 20 seconds, and after about 30 the other side of the board got very hot as well. Andrew On 5 Apr 2016, at 09:20, Giles Booth wrote: > Hi Andrew - very interested to hear about this as I had the same experience with 3 out of 4 of my initial teacher microbits. One got very hot and died, another got very hot but remained working, a third runs much warmer than the 4th unit. The last unit that died was a replacement and had only been used in a classroom and never had anything attached to its GPIO pins. > > Phil Meitiner and BBC have been very helpful, sending me 5 more microbits to test - all ok but not tested with actual children, which was when my initial teacher units started to malfunction. > > Andrew, did you use the GPIO pins at all with yours or just USB? > > many thanks > > Giles > > On 4 April 2016 at 15:46, Andrew Ferguson 500 wrote: > Hi Nicholas, > > Ah, my micro:bit does not have a tick, so that's probably the problem. > > Is there any more info anywhere about this overheating problem? (how it occurs, what can be done to avoid it, etc...). > > On 4 Apr 2016, at 15:22, "Nicholas H.Tollervey" wrote: > > > If it has a tick mark on the front, top left corner (where the "hair" > > is), then I believe it's been checked for the overheating problem and > > passed. No tick = likely to be an earlier pre-solution version of the board. > > > > N. > > > > On 04/04/16 15:24, Andrew Ferguson 500 wrote: > >> Thanks, it does get quite hot if left on for more than ~30 seconds. > >> (After about 10 it is too hot to touch, after 20 it is very warm on > >> the other side of the board. I haven't left it on for more than about > >> 2-3 minutes). > >> > >> This was one of the teacher devices so it could be a slightly earlier > >> version than the final student devices. > >> > >> On 4 Apr 2016, at 15:13, Damien George > >> wrote: > >> > >>> There was a problem with some of the microbit's having their USB > >>> chip get "hot" but I thought it was resolved. I'll ask Jonny about > >>> it. > >>> > >>> On Mon, Apr 4, 2016 at 2:44 PM, Andrew Ferguson 500 > >>> wrote: > >>>> No, the computer does not recognise the micro:bit. If I power the > >>>> micro:bit from the 2x AAA batteries nothing happens at all. (No > >>>> light, no chips getting hot). > >>>> > >>>> Hopefully more stuff will be released as Free Software / open > >>>> source soon (especially the DAL and the iOS and Android apps). > >>>> > >>>> > >>>> On 4 Apr 2016, at 14:35, "Carlos P.A." > >>>> wrote: > >>>> > >>>> I haven't seen any schematics out yet, that seems to be part of > >>>> the documentation that still needs to be open sourced. From the > >>>> top of my head I vaguely remember the test points at the back > >>>> probably connected to the microcontroller in charge of the USB > >>>> communication (and, I assume, the battery controller), so they > >>>> might be a programming interface more than actual test points. > >>>> > >>>> Does you computer recognise the microbit at all? > >>>> > >>>> On 4 April 2016 at 14:27, Andrew Ferguson 500 > >>>> wrote: > >>>>> > >>>>> Hi, > >>>>> > >>>>> I managed to persuade my teacher to let me borrow a teacher > >>>>> Micro:bit over the Easter holidays (I'm in Scotland so the > >>>>> student devices haven't arrived yet), but unfortunately I seem > >>>>> to have broken it. (I was just using 'screen' to test serial > >>>>> communication, one minute it worked and the next the screen > >>>>> session had closed, the micro:bit status light was off and the > >>>>> USB chip on the micro:bit got very hot). > >>>>> > >>>>> I suspect it's probably irreversibly broken, but I noticed that > >>>>> on the back of the micro:bit there are several testing points > >>>>> that may provide some insight as to what went wrong if probed > >>>>> with a multimeter. Does anyone know if there are any docs > >>>>> relating to which testing point links to what? > >>>>> > >>>>> Thanks, Andrew > >>>>> > >>>>> > >>>>> _______________________________________________ Microbit > >>>>> mailing list Microbit at python.org > >>>>> https://mail.python.org/mailman/listinfo/microbit > >>>> > >>>> > >>>> _______________________________________________ Microbit mailing > >>>> list Microbit at python.org > >>>> https://mail.python.org/mailman/listinfo/microbit > >>>> > >>>> > >>>> _______________________________________________ Microbit mailing > >>>> list Microbit at python.org > >>>> https://mail.python.org/mailman/listinfo/microbit > >>>> > >>> _______________________________________________ Microbit mailing > >>> list Microbit at python.org > >>> https://mail.python.org/mailman/listinfo/microbit > >> _______________________________________________ Microbit mailing > >> list Microbit at python.org > >> https://mail.python.org/mailman/listinfo/microbit > >> > > > > _______________________________________________ > > Microbit mailing list > > Microbit at python.org > > https://mail.python.org/mailman/listinfo/microbit > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > > > > -- > Giles Booth > www.suppertime.co.uk/blogmywiki > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit -------------- next part -------------- An HTML attachment was scrubbed... URL: From giles.booth at gmail.com Tue Apr 5 06:20:45 2016 From: giles.booth at gmail.com (Giles Booth) Date: Tue, 5 Apr 2016 11:20:45 +0100 Subject: [Microbit-Python] Testing Point Documentation In-Reply-To: References: <6DB8FA52-D9C2-48F5-984F-9503945C6066@gmail.com> <73F6C28F-45C9-45E7-B725-69ECB6B61A9A@gmail.com> <570278A4.8010304@ntoll.org> <061BBE1C-04D1-4B43-A61A-87DD3A1F0CF8@gmail.com> Message-ID: Hi Andrew - it does sound very similar to my experience. The chip that got hot was the unlabelled one on the right when looking at the back of the board. I had assumed it was a power management chip, but it may well be the USB serial chip you describe. Your descriptions of times (20-30 seconds) and getting hot on both sides matches my experience. On 5 April 2016 at 09:38, Andrew Ferguson 500 wrote: > Hi Giles, > > I've been in touch with Philip and he'll be sending me a replacement > shortly (thanks Philip!). Below is a description of my usage of my > micro:bit (taken from my email to Philip). > > Apart from two or three times where it was powered from the official 2x > AAA battery charger, I've exclusively powered it over USB from the USB port > on my laptop. (Sony VAIO VGN-C2S running Debian 7 GNU / Linux). When the > issue developed, I was powering it from my laptop and hadn't powered it off > batteries for at least four days. It has never been powered off a mains > phone charger. > > When using it though USB I have always used the supplied USB cable. I am > not aware of any ESD events, and when not in use I stored the micro:bit in > the original anti-static bag. I'm not quite sure what you mean by > 'grounded', the device was plugged into the laptop through USB but the > laptop was not connected to mains. (If you mean something else, please let > me know). > > The fault occurred whilst I was testing the serial output of the > micro:bit. It was running a Python program to output some text and wait 1 > second whenever the 'A' button was pressed. I was using the 'screen' > utility to view the output. ('screen /dev/ttyACM0 115200'). Mid-way through > the testing, the screen session exited, and I noticed that the power LED on > the micro:bit had gone off. About ten seconds later I realised that the > micro:bit was getting hot, and so I unplugged it from the computer. > > As far as I can think of there has been nothing else during the use of the > device that could have caused this. I was the first person to use the > device (the teacher used one of the other three devices that was sent). As > far as use is concerned, I have flashed it with various different .hex > files, but have not used the I/O ports at all so it has not been connected > to any device which could have caused the problem. > > Giles, which chip on your micro:bit got hot? (On mine it was the USB > serial chip), and how hot did they get - particularly the one that kept > working? Mine got too hot to touch after about 20 seconds, and after about > 30 the other side of the board got very hot as well. > > Andrew > > On 5 Apr 2016, at 09:20, Giles Booth wrote: > > Hi Andrew - very interested to hear about this as I had the same > experience with 3 out of 4 of my initial teacher microbits. One got very > hot and died, another got very hot but remained working, a third runs much > warmer than the 4th unit. The last unit that died was a replacement and had > only been used in a classroom and never had anything attached to its GPIO > pins. > > Phil Meitiner and BBC have been very helpful, sending me 5 more microbits > to test - all ok but not tested with actual children, which was when my > initial teacher units started to malfunction. > > Andrew, did you use the GPIO pins at all with yours or just USB? > > many thanks > > Giles > > On 4 April 2016 at 15:46, Andrew Ferguson 500 > wrote: > >> Hi Nicholas, >> >> Ah, my micro:bit does not have a tick, so that's probably the problem. >> >> Is there any more info anywhere about this overheating problem? (how it >> occurs, what can be done to avoid it, etc...). >> >> On 4 Apr 2016, at 15:22, "Nicholas H.Tollervey" wrote: >> >> > If it has a tick mark on the front, top left corner (where the "hair" >> > is), then I believe it's been checked for the overheating problem and >> > passed. No tick = likely to be an earlier pre-solution version of the >> board. >> > >> > N. >> > >> > On 04/04/16 15:24, Andrew Ferguson 500 wrote: >> >> Thanks, it does get quite hot if left on for more than ~30 seconds. >> >> (After about 10 it is too hot to touch, after 20 it is very warm on >> >> the other side of the board. I haven't left it on for more than about >> >> 2-3 minutes). >> >> >> >> This was one of the teacher devices so it could be a slightly earlier >> >> version than the final student devices. >> >> >> >> On 4 Apr 2016, at 15:13, Damien George >> >> wrote: >> >> >> >>> There was a problem with some of the microbit's having their USB >> >>> chip get "hot" but I thought it was resolved. I'll ask Jonny about >> >>> it. >> >>> >> >>> On Mon, Apr 4, 2016 at 2:44 PM, Andrew Ferguson 500 >> >>> wrote: >> >>>> No, the computer does not recognise the micro:bit. If I power the >> >>>> micro:bit from the 2x AAA batteries nothing happens at all. (No >> >>>> light, no chips getting hot). >> >>>> >> >>>> Hopefully more stuff will be released as Free Software / open >> >>>> source soon (especially the DAL and the iOS and Android apps). >> >>>> >> >>>> >> >>>> On 4 Apr 2016, at 14:35, "Carlos P.A." >> >>>> wrote: >> >>>> >> >>>> I haven't seen any schematics out yet, that seems to be part of >> >>>> the documentation that still needs to be open sourced. From the >> >>>> top of my head I vaguely remember the test points at the back >> >>>> probably connected to the microcontroller in charge of the USB >> >>>> communication (and, I assume, the battery controller), so they >> >>>> might be a programming interface more than actual test points. >> >>>> >> >>>> Does you computer recognise the microbit at all? >> >>>> >> >>>> On 4 April 2016 at 14:27, Andrew Ferguson 500 >> >>>> wrote: >> >>>>> >> >>>>> Hi, >> >>>>> >> >>>>> I managed to persuade my teacher to let me borrow a teacher >> >>>>> Micro:bit over the Easter holidays (I'm in Scotland so the >> >>>>> student devices haven't arrived yet), but unfortunately I seem >> >>>>> to have broken it. (I was just using 'screen' to test serial >> >>>>> communication, one minute it worked and the next the screen >> >>>>> session had closed, the micro:bit status light was off and the >> >>>>> USB chip on the micro:bit got very hot). >> >>>>> >> >>>>> I suspect it's probably irreversibly broken, but I noticed that >> >>>>> on the back of the micro:bit there are several testing points >> >>>>> that may provide some insight as to what went wrong if probed >> >>>>> with a multimeter. Does anyone know if there are any docs >> >>>>> relating to which testing point links to what? >> >>>>> >> >>>>> Thanks, Andrew >> >>>>> >> >>>>> >> >>>>> _______________________________________________ Microbit >> >>>>> mailing list Microbit at python.org >> >>>>> https://mail.python.org/mailman/listinfo/microbit >> >>>> >> >>>> >> >>>> _______________________________________________ Microbit mailing >> >>>> list Microbit at python.org >> >>>> https://mail.python.org/mailman/listinfo/microbit >> >>>> >> >>>> >> >>>> _______________________________________________ Microbit mailing >> >>>> list Microbit at python.org >> >>>> https://mail.python.org/mailman/listinfo/microbit >> >>>> >> >>> _______________________________________________ Microbit mailing >> >>> list Microbit at python.org >> >>> https://mail.python.org/mailman/listinfo/microbit >> >> _______________________________________________ Microbit mailing >> >> list Microbit at python.org >> >> https://mail.python.org/mailman/listinfo/microbit >> >> >> > >> > _______________________________________________ >> > Microbit mailing list >> > Microbit at python.org >> > https://mail.python.org/mailman/listinfo/microbit >> _______________________________________________ >> Microbit mailing list >> Microbit at python.org >> https://mail.python.org/mailman/listinfo/microbit >> > > > > -- > Giles Booth > www.suppertime.co.uk/blogmywiki > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > > -- Giles Booth www.suppertime.co.uk/blogmywiki -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark at hotpy.org Wed Apr 6 18:34:39 2016 From: mark at hotpy.org (Mark Shannon) Date: Wed, 6 Apr 2016 23:34:39 +0100 Subject: [Microbit-Python] Sprints at PyCon Message-ID: <57058EFF.1030909@hotpy.org> Hi all, Is anyone interested in sprinting on the Microbit at PyCon this year? From ntoll at ntoll.org Thu Apr 7 03:13:06 2016 From: ntoll at ntoll.org (Nicholas H.Tollervey) Date: Thu, 7 Apr 2016 08:13:06 +0100 Subject: [Microbit-Python] Sprints at PyCon In-Reply-To: <57058EFF.1030909@hotpy.org> References: <57058EFF.1030909@hotpy.org> Message-ID: <57060882.5070503@ntoll.org> On 06/04/16 23:34, Mark Shannon wrote: > Hi all, > > Is anyone interested in sprinting on the Microbit at PyCon this year? > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit +1 :-) Damien, will you be there..? :-P N. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From ntoll at ntoll.org Thu Apr 7 03:26:36 2016 From: ntoll at ntoll.org (Nicholas H.Tollervey) Date: Thu, 7 Apr 2016 08:26:36 +0100 Subject: [Microbit-Python] Sprints at PyCon In-Reply-To: <57060882.5070503@ntoll.org> References: <57058EFF.1030909@hotpy.org> <57060882.5070503@ntoll.org> Message-ID: <57060BAC.9030606@ntoll.org> On 07/04/16 08:13, Nicholas H.Tollervey wrote: > On 06/04/16 23:34, Mark Shannon wrote: >> Hi all, >> >> Is anyone interested in sprinting on the Microbit at PyCon this year? >> _______________________________________________ >> Microbit mailing list >> Microbit at python.org >> https://mail.python.org/mailman/listinfo/microbit > > +1 :-) > > Damien, will you be there..? :-P > > N. > > > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > Also, I'll make sure I bring a number of devices for people to play with at the conference (and if they're going to continue working on it - they can keep 'em). Also, Mark, that file system work is outstanding. I'll have a play later today when I'm not at "real work" (tm). N. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From naomi.ceder at gmail.com Thu Apr 7 09:52:52 2016 From: naomi.ceder at gmail.com (Naomi Ceder) Date: Thu, 7 Apr 2016 08:52:52 -0500 Subject: [Microbit-Python] Sprints at PyCon In-Reply-To: <57060BAC.9030606@ntoll.org> References: <57058EFF.1030909@hotpy.org> <57060882.5070503@ntoll.org> <57060BAC.9030606@ntoll.org> Message-ID: +1. Speaking as the friendly PyCon Sprints organiser I'd suggest you add an entry to the PyCon Sprints page at https://us.pycon.org/2016/community/sprints/ and fill out the questionnaire to help us plan. This isn't a hard commitment, but it will make people aware and help us allocate space, etc. Cheers, Naomi On 7 April 2016 at 02:26, Nicholas H.Tollervey wrote: > On 07/04/16 08:13, Nicholas H.Tollervey wrote: > > On 06/04/16 23:34, Mark Shannon wrote: > >> Hi all, > >> > >> Is anyone interested in sprinting on the Microbit at PyCon this year? > >> _______________________________________________ > >> Microbit mailing list > >> Microbit at python.org > >> https://mail.python.org/mailman/listinfo/microbit > > > > +1 :-) > > > > Damien, will you be there..? :-P > > > > N. > > > > > > > > _______________________________________________ > > Microbit mailing list > > Microbit at python.org > > https://mail.python.org/mailman/listinfo/microbit > > > > Also, I'll make sure I bring a number of devices for people to play with > at the conference (and if they're going to continue working on it - they > can keep 'em). > > Also, Mark, that file system work is outstanding. I'll have a play later > today when I'm not at "real work" (tm). > > N. > > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > > -- Naomi Ceder https://plus.google.com/u/0/111396744045017339164/about -------------- next part -------------- An HTML attachment was scrubbed... URL: From willingc at willingconsulting.com Thu Apr 7 10:06:17 2016 From: willingc at willingconsulting.com (Carol Willing) Date: Thu, 07 Apr 2016 07:06:17 -0700 Subject: [Microbit-Python] Sprints at PyCon In-Reply-To: References: <57058EFF.1030909@hotpy.org> <57060882.5070503@ntoll.org> <57060BAC.9030606@ntoll.org> Message-ID: <811DCACE-5152-441C-B53B-61F77E59EE3D@willingconsulting.com> I would be up for a Microbit sprint. I love sprints :-) On 7 Apr 2016, at 6:52, Naomi Ceder wrote: > +1. > > Speaking as the friendly PyCon Sprints organiser I'd suggest you add an > entry to the PyCon Sprints page at > https://us.pycon.org/2016/community/sprints/ and fill out the questionnaire > to help us plan. This isn't a hard commitment, but it will make people > aware and help us allocate space, etc. > > Cheers, > Naomi > > On 7 April 2016 at 02:26, Nicholas H.Tollervey wrote: > >> On 07/04/16 08:13, Nicholas H.Tollervey wrote: >>> On 06/04/16 23:34, Mark Shannon wrote: >>>> Hi all, >>>> >>>> Is anyone interested in sprinting on the Microbit at PyCon this year? >>>> _______________________________________________ >>>> Microbit mailing list >>>> Microbit at python.org >>>> https://mail.python.org/mailman/listinfo/microbit >>> >>> +1 :-) >>> >>> Damien, will you be there..? :-P >>> >>> N. >>> >>> >>> >>> _______________________________________________ >>> Microbit mailing list >>> Microbit at python.org >>> https://mail.python.org/mailman/listinfo/microbit >>> >> >> Also, I'll make sure I bring a number of devices for people to play with >> at the conference (and if they're going to continue working on it - they >> can keep 'em). >> >> Also, Mark, that file system work is outstanding. I'll have a play later >> today when I'm not at "real work" (tm). >> >> N. >> >> >> _______________________________________________ >> Microbit mailing list >> Microbit at python.org >> https://mail.python.org/mailman/listinfo/microbit >> >> > > > -- > Naomi Ceder > https://plus.google.com/u/0/111396744045017339164/about > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit Carol Willing Research Software Engineer, Project Jupyter @ Cal Poly Director, Python Software Foundation From mal at egenix.com Thu Apr 7 10:21:31 2016 From: mal at egenix.com (M.-A. Lemburg) Date: Thu, 7 Apr 2016 16:21:31 +0200 Subject: [Microbit-Python] Sprints at PyCon In-Reply-To: <57058EFF.1030909@hotpy.org> References: <57058EFF.1030909@hotpy.org> Message-ID: <57066CEB.40205@egenix.com> On 07.04.2016 00:34, Mark Shannon wrote: > Hi all, > > Is anyone interested in sprinting on the Microbit at PyCon this year? I'd be interested in one at EuroPython: https://ep2016.europython.eu/en/events/sprints/ -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Experts (#1, Apr 07 2016) >>> Python Projects, Coaching and Consulting ... http://www.egenix.com/ >>> Python Database Interfaces ... http://products.egenix.com/ >>> Plone/Zope Database Interfaces ... http://zope.egenix.com/ ________________________________________________________________________ ::: We implement business ideas - efficiently in both time and costs ::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ http://www.malemburg.com/ From mail at kushaldas.in Thu Apr 7 10:20:09 2016 From: mail at kushaldas.in (Kushal Das) Date: Thu, 7 Apr 2016 19:50:09 +0530 Subject: [Microbit-Python] Sprints at PyCon In-Reply-To: <811DCACE-5152-441C-B53B-61F77E59EE3D@willingconsulting.com> References: <57058EFF.1030909@hotpy.org> <57060882.5070503@ntoll.org> <57060BAC.9030606@ntoll.org> <811DCACE-5152-441C-B53B-61F77E59EE3D@willingconsulting.com> Message-ID: <20160407142009.GA5738@kdas-laptop> On 07/04/16, Carol Willing wrote: > I would be up for a Microbit sprint. I love sprints :-) > Means we are already a group in the sprints :) We should stay in the same room of CPython :D Easier to jump around. Kushal -- Fedora Cloud Engineer CPython Core Developer https://kushaldas.in https://dgplug.org From carlos.p.a.87 at gmail.com Sat Apr 16 09:34:48 2016 From: carlos.p.a.87 at gmail.com (Carlos P.A.) Date: Sat, 16 Apr 2016 14:34:48 +0100 Subject: [Microbit-Python] Easy install of all the MicroPython toolchain with Vagrant and virtual machines Message-ID: Hi all, I've been through the process of getting the toolchain installed, and since I have several machines and use different operating systems in most of them I wanted to get an easy and repeatable way to get everything up and running easily. I heard about Vagrant before, so I though this would be a perfect use case for it :) Maybe more people will find it useful as well? https://github.com/carlosperate/microbit-micropython-dev-env Regards, Carlos -------------- next part -------------- An HTML attachment was scrubbed... URL: From nevil.hunt at hotmail.co.uk Mon Apr 18 13:17:05 2016 From: nevil.hunt at hotmail.co.uk (Nevil Hunt) Date: Mon, 18 Apr 2016 18:17:05 +0100 Subject: [Microbit-Python] Maximum Size of Microbit Python Program? Message-ID: Hi, I think I may have exceeded the maximum size a microbit Python Program can be! My program compiles OK. Appears to download OK. But then doesn't run. There is no error message during the download and no error message on the microbit. I'm fairly sure it's the program's size that's the problem as I've experimented gradually reducing the size of the program until it started to work again. Does anyone know what is the maximum size a microbit Python Program can be? And what is it limited by? Is it the size available in the micro:bit's Flash? And how do I know how big my program is? Is it simply down to the size of the Hex file? (I have a working program which is 590k and one that doesn't run which is 595k) Thanks, Nevil -------------- next part -------------- An HTML attachment was scrubbed... URL: From coryanws at gmail.com Wed Apr 20 05:25:49 2016 From: coryanws at gmail.com (Coryan W-S) Date: Wed, 20 Apr 2016 10:25:49 +0100 Subject: [Microbit-Python] Microbit Digest, Vol 11, Issue 10 In-Reply-To: References: Message-ID: Hello Nevil, I may be wrong about some of these, but I believe the following are true: - The maximum size of the flash memory on an nRF51822 is 256 kilobytes - The width of the "Size" field in a MicroPython program header is 16 bits, which limits its size to 65 kilobytes. - The Mu IDE will refuse to flash scripts that are larger than 8192 bytes The smallest of these is Mu's limit of 8kb, so that'd be the limit you'd hit first. Note that the actual size of the hex files you are generating will be larger than this, as they're in Intel Hex, not pure binary. Hope that helps! - Coryan On Tue, Apr 19, 2016 at 5:00 PM, wrote: > Send Microbit mailing list submissions to > microbit at python.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mail.python.org/mailman/listinfo/microbit > or, via email, send a message with subject or body 'help' to > microbit-request at python.org > > You can reach the person managing the list at > microbit-owner at python.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Microbit digest..." > > > Today's Topics: > > 1. Maximum Size of Microbit Python Program? (Nevil Hunt) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 18 Apr 2016 18:17:05 +0100 > From: Nevil Hunt > To: "microbit at python.org" > Subject: [Microbit-Python] Maximum Size of Microbit Python Program? > Message-ID: > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > > I think I may have exceeded the maximum size a microbit Python Program can > be! > My program compiles OK. Appears to download OK. But then doesn't run. > There is no error message during the download and no error message on the > microbit. > I'm fairly sure it's the program's size that's the problem as I've > experimented gradually reducing the size of the program until it started to > work again. > > Does anyone know what is the maximum size a microbit Python Program can be? > And what is it limited by? Is it the size available in the micro:bit's > Flash? > And how do I know how big my program is? Is it simply down to the size of > the Hex file? > (I have a working program which is 590k and one that doesn't run which is > 595k) > > Thanks, > > Nevil > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://mail.python.org/pipermail/microbit/attachments/20160418/5b64fb20/attachment-0001.html > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > > > ------------------------------ > > End of Microbit Digest, Vol 11, Issue 10 > **************************************** > -------------- next part -------------- An HTML attachment was scrubbed... URL: From coryanws at gmail.com Wed Apr 20 05:47:43 2016 From: coryanws at gmail.com (Coryan W-S) Date: Wed, 20 Apr 2016 10:47:43 +0100 Subject: [Microbit-Python] Minimal MP-to-hex tool Message-ID: Hi all, I've put together a stripped-down Python script that'll take your MicroPython and convert it into a hex file suitable for flashing a Micro:Bit. You can run it right from the command line, or import its class interface if you want to set up some sort of automated build script. It also converts hex files back into their original MicroPython. Hope it might be of help to somebody - you can find it here: https://github.com/coryanws/MicroLite Best, - Coryan -------------- next part -------------- An HTML attachment was scrubbed... URL: From ntoll at ntoll.org Wed Apr 20 05:58:25 2016 From: ntoll at ntoll.org (Nicholas H.Tollervey) Date: Wed, 20 Apr 2016 10:58:25 +0100 Subject: [Microbit-Python] Minimal MP-to-hex tool In-Reply-To: References: Message-ID: <571752C1.2050000@ntoll.org> Hi Coryan, The uflash tool already does this. :-) https://uflash.readthedocs.org/en/latest/ It's what Mu uses and is also a stand-alone tool. N. On 20/04/16 10:47, Coryan W-S wrote: > Hi all, > > I've put together a stripped-down Python script that'll take your > MicroPython and convert it into a hex file suitable for flashing a > Micro:Bit. You can run it right from the command line, or import its > class interface if you want to set up some sort of automated build > script. It also converts hex files back into their original MicroPython. > > Hope it might be of help to somebody - you can find it here: > https://github.com/coryanws/MicroLite > > Best, > - Coryan > > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From ntoll at ntoll.org Wed Apr 20 06:00:55 2016 From: ntoll at ntoll.org (Nicholas H.Tollervey) Date: Wed, 20 Apr 2016 11:00:55 +0100 Subject: [Microbit-Python] Minimal MP-to-hex tool In-Reply-To: References: Message-ID: <57175357.1080807@ntoll.org> Sorry, I didn't make myself clear... I think it's wonderful that we have many flowers bloom. Just wanted to point out uFlash just in case we're re-inventing wheels etc... ;-) N. On 20/04/16 10:47, Coryan W-S wrote: > Hi all, > > I've put together a stripped-down Python script that'll take your > MicroPython and convert it into a hex file suitable for flashing a > Micro:Bit. You can run it right from the command line, or import its > class interface if you want to set up some sort of automated build > script. It also converts hex files back into their original MicroPython. > > Hope it might be of help to somebody - you can find it here: > https://github.com/coryanws/MicroLite > > Best, > - Coryan > > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From coryanws at gmail.com Wed Apr 20 15:44:01 2016 From: coryanws at gmail.com (Coryan W-S) Date: Wed, 20 Apr 2016 20:44:01 +0100 Subject: [Microbit-Python] Minimal MP-to-hex tool Message-ID: Aha, I see - I didn't realise uflash was a standalone tool too! Thanks for the heads-up ntoll; it definitely wasn't my intention to tread on any toes. The first thing I did after receiving a Micro:Bit was stumble across your article on how MicroPython made its way onto the Micro:Bit, so it's pretty cool to hear from you! :) I was, I think, able to make some improvements to the MP-to-hex function in uflash - the hex files I've been generating seem to be a bit smaller than those made by Mu. I could add these improvements to my fork of uflash if you'd be interested in having a look? It'd be awesome to contribute some code to your project! Best, - Coryan -------------- next part -------------- An HTML attachment was scrubbed... URL: From ntoll at ntoll.org Thu Apr 21 02:58:51 2016 From: ntoll at ntoll.org (Nicholas H.Tollervey) Date: Thu, 21 Apr 2016 07:58:51 +0100 Subject: [Microbit-Python] Minimal MP-to-hex tool In-Reply-To: References: Message-ID: <57187A2B.2010304@ntoll.org> On 20/04/16 20:44, Coryan W-S wrote: > Aha, I see - I didn't realise uflash was a standalone tool too! Thanks > for the heads-up ntoll; it definitely wasn't my intention to tread on > any toes. The first thing I did after receiving a Micro:Bit was stumble > across your article on how MicroPython made its way onto the Micro:Bit, > so it's pretty cool to hear from you! :) > You're most definitely not stepping on anybody's toes by writing code. Keep it up! :-) > I was, I think, able to make some improvements to the MP-to-hex function > in uflash - the hex files I've been generating seem to be a bit smaller > than those made by Mu. I could add these improvements to my fork of > uflash if you'd be interested in having a look? It'd be awesome to > contribute some code to your project! > Send over a PR and let's see! :-) N. > Best, > - Coryan > > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From ntoll at ntoll.org Thu Apr 21 03:21:12 2016 From: ntoll at ntoll.org (Nicholas H.Tollervey) Date: Thu, 21 Apr 2016 08:21:12 +0100 Subject: [Microbit-Python] Sprints at PyCon In-Reply-To: <57058EFF.1030909@hotpy.org> References: <57058EFF.1030909@hotpy.org> Message-ID: <57187F68.20103@ntoll.org> On 06/04/16 23:34, Mark Shannon wrote: > Hi all, > > Is anyone interested in sprinting on the Microbit at PyCon this year? > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit OK... at Naomi's prompting, I'll fill in the required forms to make "MicroPython / micro:bit" a "real" sprint. I'm going to be in Portland until Saturday. N. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From ntoll at ntoll.org Thu Apr 21 03:49:24 2016 From: ntoll at ntoll.org (Nicholas H.Tollervey) Date: Thu, 21 Apr 2016 08:49:24 +0100 Subject: [Microbit-Python] Sprints at PyCon In-Reply-To: <57187F68.20103@ntoll.org> References: <57058EFF.1030909@hotpy.org> <57187F68.20103@ntoll.org> Message-ID: <57188604.7040209@ntoll.org> OK... I've filled in the "newcomer friendliness form" and added us to this page on the conference wiki: https://us.pycon.org/2016/community/sprints/ I'm going to write up a short plan of action for the sprint to cover various eventualities. ;-) N. On 21/04/16 08:21, Nicholas H.Tollervey wrote: > On 06/04/16 23:34, Mark Shannon wrote: >> Hi all, >> >> Is anyone interested in sprinting on the Microbit at PyCon this year? >> _______________________________________________ >> Microbit mailing list >> Microbit at python.org >> https://mail.python.org/mailman/listinfo/microbit > > > OK... at Naomi's prompting, I'll fill in the required forms to make > "MicroPython / micro:bit" a "real" sprint. > > I'm going to be in Portland until Saturday. > > N. > > > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From nevil.hunt at hotmail.co.uk Thu Apr 21 08:03:10 2016 From: nevil.hunt at hotmail.co.uk (Nevil Hunt) Date: Thu, 21 Apr 2016 13:03:10 +0100 Subject: [Microbit-Python] =?cp1256?q?Maximum_Size_of_Microbit_Python_Pro?= =?cp1256?b?Z3JhbT/+?= In-Reply-To: References: , Message-ID: Hi Coryan, Thanks for the info. I'm programming using the Web interface rather than the stand alone Mu - whether that makes any difference to the size of the Hex file I don't know. The Hex files from my Block programs seem to be 500 -573k The Hex files from my Python programs seem to be 573 -595k where all programs up to 590k run OK. It's just the 595k one that doesn't I don't know how the Hex file maps to the 256k, 65k & 8k you mention. My concerns are two fold 1) Exceeding the size is silent - there is no error/warning when compiling or downloading 2) My program isn't that big! Only ~150 lines of code I suspect it just need some s/w switch changing but that level of detail is beyond me! Regards, Nevil Date: Wed, 20 Apr 2016 10:25:49 +0100 From: coryanws at gmail.com To: microbit at python.org Subject: Re: [Microbit-Python] Microbit Digest, Vol 11, Issue 10 Hello Nevil, I may be wrong about some of these, but I believe the following are true: - The maximum size of the flash memory on an nRF51822 is 256 kilobytes - The width of the "Size" field in a MicroPython program header is 16 bits, which limits its size to 65 kilobytes. - The Mu IDE will refuse to flash scripts that are larger than 8192 bytes The smallest of these is Mu's limit of 8kb, so that'd be the limit you'd hit first. Note that the actual size of the hex files you are generating will be larger than this, as they're in Intel Hex, not pure binary. Hope that helps! - Coryan On Tue, Apr 19, 2016 at 5:00 PM, wrote: Send Microbit mailing list submissions to microbit at python.org To subscribe or unsubscribe via the World Wide Web, visit https://mail.python.org/mailman/listinfo/microbit or, via email, send a message with subject or body 'help' to microbit-request at python.org You can reach the person managing the list at microbit-owner at python.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Microbit digest..." Today's Topics: 1. Maximum Size of Microbit Python Program? (Nevil Hunt) ---------------------------------------------------------------------- Message: 1 Date: Mon, 18 Apr 2016 18:17:05 +0100 From: Nevil Hunt To: "microbit at python.org" Subject: [Microbit-Python] Maximum Size of Microbit Python Program? Message-ID: Content-Type: text/plain; charset="iso-8859-1" Hi, I think I may have exceeded the maximum size a microbit Python Program can be! My program compiles OK. Appears to download OK. But then doesn't run. There is no error message during the download and no error message on the microbit. I'm fairly sure it's the program's size that's the problem as I've experimented gradually reducing the size of the program until it started to work again. Does anyone know what is the maximum size a microbit Python Program can be? And what is it limited by? Is it the size available in the micro:bit's Flash? And how do I know how big my program is? Is it simply down to the size of the Hex file? (I have a working program which is 590k and one that doesn't run which is 595k) Thanks, Nevil -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Subject: Digest Footer _______________________________________________ Microbit mailing list Microbit at python.org https://mail.python.org/mailman/listinfo/microbit ------------------------------ End of Microbit Digest, Vol 11, Issue 10 **************************************** _______________________________________________ Microbit mailing list Microbit at python.org https://mail.python.org/mailman/listinfo/microbit -------------- next part -------------- An HTML attachment was scrubbed... URL: From coryanws at gmail.com Fri Apr 22 06:03:45 2016 From: coryanws at gmail.com (Coryan W-S) Date: Fri, 22 Apr 2016 11:03:45 +0100 Subject: [Microbit-Python] MicroPython Interpreter Build Message-ID: Hi All, I'm quite keen to have a fiddle around with the MicroPython interpreter we're using on the MicroBit. At the moment, I'm able to build the "Unix" port of MicroPython from source, but I'd now quite like to have a go at building the interpreter that's running on the MicroBit. Is anyone able to tell me a bit about how to do this? Ideally I'd like to get to a point where I can build the same interpreter that's pasted into uflash as a heredoc, then see if it's possible to make it do more cool things. I'm currently building on an Ubuntu-like Linux box, but can build in another environment if it'd make things easier. Thankyou for your help! - Coryan -------------- next part -------------- An HTML attachment was scrubbed... URL: From ntoll at ntoll.org Fri Apr 22 06:14:32 2016 From: ntoll at ntoll.org (Nicholas H.Tollervey) Date: Fri, 22 Apr 2016 11:14:32 +0100 Subject: [Microbit-Python] MicroPython Interpreter Build In-Reply-To: References: Message-ID: <5719F988.5040607@ntoll.org> Hi Coryan, Everything you need should be in the README in this GitHub repository. https://github.com/bbcmicrobit/micropython Please shout if it doesn't work..! N. On 22/04/16 11:03, Coryan W-S wrote: > Hi All, > > I'm quite keen to have a fiddle around with the MicroPython interpreter > we're using on the MicroBit. At the moment, I'm able to build the "Unix" > port of MicroPython from source, but I'd now quite like to have a go at > building the interpreter that's running on the MicroBit. > > Is anyone able to tell me a bit about how to do this? Ideally I'd like > to get to a point where I can build the same interpreter that's pasted > into uflash as a heredoc, then see if it's possible to make it do more > cool things. > > I'm currently building on an Ubuntu-like Linux box, but can build in > another environment if it'd make things easier. > > Thankyou for your help! > - Coryan > > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From joe.t.glancy at gmail.com Fri Apr 22 08:04:40 2016 From: joe.t.glancy at gmail.com (Joe Glancy) Date: Fri, 22 Apr 2016 12:04:40 +0000 Subject: [Microbit-Python] MicroPython Interpreter Build In-Reply-To: <5719F988.5040607@ntoll.org> References: <5719F988.5040607@ntoll.org> Message-ID: There are a couple of issues that can crop up for various reasons depending on system configuration, but it should work fine as long as you follow the dev guide :) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: images.jpg Type: image/jpeg Size: 9626 bytes Desc: not available URL: From carlos.p.a.87 at gmail.com Fri Apr 22 11:03:48 2016 From: carlos.p.a.87 at gmail.com (Carlos P.A.) Date: Fri, 22 Apr 2016 16:03:48 +0100 Subject: [Microbit-Python] MicroPython Interpreter Build In-Reply-To: References: <5719F988.5040607@ntoll.org> Message-ID: If you don't mind running the build system in a virtual machine you could use Vagrant to set it up with a 1 line command. Alternatively you could have a look at the shell script running in the Vagrant file to see how it's setting up Ubuntu. https://github.com/carlosperate/microbit-micropython-dev-env On 22 Apr 2016 13:05, "Joe Glancy" wrote: > There are a couple of issues that can crop up for various reasons > depending on system configuration, but it should work fine as long as you > follow the dev guide :) > > > > > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: images.jpg Type: image/jpeg Size: 9626 bytes Desc: not available URL: From ntoll at ntoll.org Mon Apr 25 08:38:17 2016 From: ntoll at ntoll.org (Nicholas H.Tollervey) Date: Mon, 25 Apr 2016 13:38:17 +0100 Subject: [Microbit-Python] Start-up user guide examples... Message-ID: <571E0FB9.8090004@ntoll.org> Hi Folks, The people from Farnell (the company that'll be manufacturing and selling the devices to re-sellers) are putting together a "start-up guide" to be printed and included in the box. They would like to include some short Python code that'll be fun for kids, educational and short-ish. So, I wonder what people on this list can come up with. It needs to work with a "vanilla" device - i.e. no peripherals - and be the very first Python code the kids uses with the device. Make it fun! N. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From a.grandi at gmail.com Mon Apr 25 08:48:16 2016 From: a.grandi at gmail.com (a.grandi at gmail.com) Date: Mon, 25 Apr 2016 13:48:16 +0100 Subject: [Microbit-Python] Start-up user guide examples... In-Reply-To: <571E0FB9.8090004@ntoll.org> References: <571E0FB9.8090004@ntoll.org> Message-ID: Hi Nicholas, I think this is a very simple and funny one https://gist.github.com/andreagrandi/1e2f6e591f218ba612d9 :) Feel free to include it. On 25 April 2016 at 13:38, Nicholas H.Tollervey wrote: > Hi Folks, > > The people from Farnell (the company that'll be manufacturing and > selling the devices to re-sellers) are putting together a "start-up > guide" to be printed and included in the box. > > They would like to include some short Python code that'll be fun for > kids, educational and short-ish. > > So, I wonder what people on this list can come up with. It needs to work > with a "vanilla" device - i.e. no peripherals - and be the very first > Python code the kids uses with the device. > > Make it fun! > > N. > > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > -- Andrea Grandi - Software Engineer Website: https://www.andreagrandi.it Twitter: https://twitter.com/andreagrandi GitHub: https://github.com/andreagrandi PGP: 7238 74F6 886D 5994 323F 1781 8CFB 47AD C384 F0CC From carlos.p.a.87 at gmail.com Mon Apr 25 08:50:30 2016 From: carlos.p.a.87 at gmail.com (Carlos P.A.) Date: Mon, 25 Apr 2016 13:50:30 +0100 Subject: [Microbit-Python] Start-up user guide examples... In-Reply-To: References: <571E0FB9.8090004@ntoll.org> Message-ID: Is there is no definition of "short-ish"? I would have though that being printed media they'd have a general idea of number of characters per line, and number of lines they could devote to this? On 25 April 2016 at 13:48, a.grandi at gmail.com wrote: > Hi Nicholas, > > I think this is a very simple and funny one > https://gist.github.com/andreagrandi/1e2f6e591f218ba612d9 :) > > Feel free to include it. > > On 25 April 2016 at 13:38, Nicholas H.Tollervey wrote: > > Hi Folks, > > > > The people from Farnell (the company that'll be manufacturing and > > selling the devices to re-sellers) are putting together a "start-up > > guide" to be printed and included in the box. > > > > They would like to include some short Python code that'll be fun for > > kids, educational and short-ish. > > > > So, I wonder what people on this list can come up with. It needs to work > > with a "vanilla" device - i.e. no peripherals - and be the very first > > Python code the kids uses with the device. > > > > Make it fun! > > > > N. > > > > > > _______________________________________________ > > Microbit mailing list > > Microbit at python.org > > https://mail.python.org/mailman/listinfo/microbit > > > > > > -- > Andrea Grandi - Software Engineer > Website: https://www.andreagrandi.it > Twitter: https://twitter.com/andreagrandi > GitHub: https://github.com/andreagrandi > PGP: 7238 74F6 886D 5994 323F 1781 8CFB 47AD C384 F0CC > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ntoll at ntoll.org Mon Apr 25 09:03:50 2016 From: ntoll at ntoll.org (Nicholas H.Tollervey) Date: Mon, 25 Apr 2016 14:03:50 +0100 Subject: [Microbit-Python] Start-up user guide examples... In-Reply-To: References: <571E0FB9.8090004@ntoll.org> Message-ID: <571E15B6.3060408@ntoll.org> On 25/04/16 13:50, Carlos P.A. wrote: > Is there is no definition of "short-ish"? I would have though that being > printed media they'd have a general idea of number of characters per > line, and number of lines they could devote to this? > I've already asked for guidance about this and will report back. In the meantime let's say "short" means it'll take 10-15mins for a kid to type in. :-) N. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From ntoll at ntoll.org Mon Apr 25 09:04:23 2016 From: ntoll at ntoll.org (Nicholas H.Tollervey) Date: Mon, 25 Apr 2016 14:04:23 +0100 Subject: [Microbit-Python] Start-up user guide examples... In-Reply-To: References: <571E0FB9.8090004@ntoll.org> Message-ID: <571E15D7.20101@ntoll.org> Microbit battering... ;-) N, On 25/04/16 13:48, a.grandi at gmail.com wrote: > Hi Nicholas, > > I think this is a very simple and funny one > https://gist.github.com/andreagrandi/1e2f6e591f218ba612d9 :) > > Feel free to include it. > > On 25 April 2016 at 13:38, Nicholas H.Tollervey wrote: >> Hi Folks, >> >> The people from Farnell (the company that'll be manufacturing and >> selling the devices to re-sellers) are putting together a "start-up >> guide" to be printed and included in the box. >> >> They would like to include some short Python code that'll be fun for >> kids, educational and short-ish. >> >> So, I wonder what people on this list can come up with. It needs to work >> with a "vanilla" device - i.e. no peripherals - and be the very first >> Python code the kids uses with the device. >> >> Make it fun! >> >> N. >> >> >> _______________________________________________ >> Microbit mailing list >> Microbit at python.org >> https://mail.python.org/mailman/listinfo/microbit >> > > > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From david at thinkingbinaries.com Mon Apr 25 09:47:18 2016 From: david at thinkingbinaries.com (David Whale) Date: Mon, 25 Apr 2016 14:47:18 +0100 Subject: [Microbit-Python] Start-up user guide examples... In-Reply-To: <571E0FB9.8090004@ntoll.org> References: <571E0FB9.8090004@ntoll.org> Message-ID: Hi Nicholas, Please feel free to use my chase game. https://github.com/whaleygeek/microbit_python/blob/master/chase/chase.py I originally used this at CBBC Live and Digital in Hull last year- it was tested by lots and lots of children and parents (we had a footfall in the tens of thousands over the whole weekend, so the concept was well tested!) I've just rewritten it in Python for you :-) The game is self-explanatory, and *very* addictive! Highest possible score is 8. The game lasts for up to 1 minute (which was part of the design for a 'walk by activity for people to engage with'). David. ___________________________________________________________ David Whale, B.Sc (Hons), MIET *Software Engineer and IET Schools Liaison Officer, Essex* On 25 April 2016 at 13:38, Nicholas H.Tollervey wrote: > Hi Folks, > > The people from Farnell (the company that'll be manufacturing and > selling the devices to re-sellers) are putting together a "start-up > guide" to be printed and included in the box. > > They would like to include some short Python code that'll be fun for > kids, educational and short-ish. > > So, I wonder what people on this list can come up with. It needs to work > with a "vanilla" device - i.e. no peripherals - and be the very first > Python code the kids uses with the device. > > Make it fun! > > N. > > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > > -------------- next part -------------- An HTML attachment was scrubbed... URL: