From kauri.raba94 at gmail.com Mon Jun 5 13:18:01 2017 From: kauri.raba94 at gmail.com (Kauri Raba) Date: Mon, 5 Jun 2017 20:18:01 +0300 Subject: [Microbit-Python] Programming micro:bit with Thonny IDE Message-ID: Hello, I am developing a plug-in for Thonny IDE which allows to program micro:bit in MicroPython. One of the plug-in's key features is that it allows to quickly execute written scripts on micro:bit without flashing. If user is happy with the result, then the written script can be flashed on micro:bit. If you are curious and like to try it out then please check out the links below. More info about Thonny IDE: http://thonny.org/ More info about Thonny micro:bit plug-in: https://bitbucket.org/KauriRaba/thonny-microbit I am open to all the suggestions and ideas which help me to make this plug-in better. Also don't be afraid to report found bugs, that helps me alot! ;) Please leave suggestions and bug reports here: https://bitbucket.org/KauriRaba/thonny-microbit/issues/new All the best, Kauri -------------- next part -------------- An HTML attachment was scrubbed... URL: From lknoblauch at web.de Mon Jun 19 16:39:08 2017 From: lknoblauch at web.de (Ludwig Knoblauch) Date: Mon, 19 Jun 2017 22:39:08 +0200 Subject: [Microbit-Python] Missing attributes with MicroBitImage object Message-ID: <608f4439-972c-83d3-88e8-dc576761cafc@web.de> Hi all, I just started 3 days ago working with my brand-new *micro:bit* device. I'm new on this mailing list and up to now I couldn't find a better place to discuss the unavoidable initial pitfalls. Maybe I can find help here for some trivia. Even if not, a hint whom to address would be appreciated. While *ReadTheDocs* announces a nice set of attributes for MicroBitImage objects, I found two of them not being implemented, namely *fill()* and *blit(). *These two attributes cause the following error message: AttributeError: 'MicroBitImage' object has no attribute '/missing-attribute/' MicroPython v1.7-9-gbe020eb on 2016-04-18; micro:bit with nRF51822 Maybe this is a version problem? But my MicroPython development system seems to be up-to-date: *mu-0.9.13.linux*. Or could it be a firmware version problem with the micro:bit? Looks also up-to-date: Daplink Mode: Interface Interface Version: *0241* Git SHA: fa4132987102c51c110751d8bdb8a74aeb7b071b Any idea what went wrong? Regards and thanks in advance Ludwig. P.S.: The host computer runs under Linux Mint 17 (64 bit) with KDE desktop. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jim at groklearning.com Mon Jun 19 21:42:19 2017 From: jim at groklearning.com (Jim Mussared) Date: Tue, 20 Jun 2017 11:42:19 +1000 Subject: [Microbit-Python] Missing attributes with MicroBitImage object In-Reply-To: <608f4439-972c-83d3-88e8-dc576761cafc@web.de> References: <608f4439-972c-83d3-88e8-dc576761cafc@web.de> Message-ID: Hi Ludwig, fill and blit were added to the firmware in December/January -- https://github.com/bbcmicrobit/micropython/commits/master/source/microbit/microbitimage.cpp Looks like you do have the latest released Mu, but 0.9.3 was released before the fill/blit changes (mid December). If you're keen to get this working before the next Mu/uFlash release, you can build a firmware image yourself, then update your local copy of Mu or uFlash to use it. See instructions at https://github.com/bbcmicrobit/micropython When using uFlash directly, you can use the -r option to point to your newly built hex file. Off the top of my head I'm not sure if Mu has a corresponding argument, I've always just updated the contents of the hex file in contrib/uflash.py manually. Jim On 20 June 2017 at 06:39, Ludwig Knoblauch wrote: > Hi all, > > I just started 3 days ago working with my brand-new micro:bit device. I'm > new on this mailing list and up to now I couldn't find a better place to > discuss the unavoidable initial pitfalls. Maybe I can find help here for > some trivia. Even if not, a hint whom to address would be appreciated. > > While ReadTheDocs announces a nice set of attributes for MicroBitImage > objects, I found two of them not being implemented, namely fill() and > blit(). These two attributes cause the following error message: > > AttributeError: 'MicroBitImage' object has no attribute > 'missing-attribute' > > MicroPython v1.7-9-gbe020eb on 2016-04-18; micro:bit with nRF51822 > > Maybe this is a version problem? But my MicroPython development system seems > to be up-to-date: mu-0.9.13.linux. Or could it be a firmware version problem > with the micro:bit? Looks also up-to-date: > > Daplink Mode: Interface > Interface Version: 0241 > Git SHA: fa4132987102c51c110751d8bdb8a74aeb7b071b > > Any idea what went wrong? > > Regards and thanks in advance > > Ludwig. > > P.S.: The host computer runs under Linux Mint 17 (64 bit) with KDE desktop. > > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > From lknoblauch at web.de Tue Jun 20 05:34:46 2017 From: lknoblauch at web.de (Ludwig Knoblauch) Date: Tue, 20 Jun 2017 11:34:46 +0200 Subject: [Microbit-Python] Missing attributes with MicroBitImage object In-Reply-To: References: <608f4439-972c-83d3-88e8-dc576761cafc@web.de> Message-ID: <2c3fd568-4af4-30db-bff1-833a76806e39@web.de> Hi Jim, thanks a lot for the advice. This was exactly what I needed. Should be able now to crack the nut. Ludwig. Am 20.06.2017 um 03:42 schrieb Jim Mussared via Microbit: > Hi Ludwig, > > fill and blit were added to the firmware in December/January -- > https://github.com/bbcmicrobit/micropython/commits/master/source/microbit/microbitimage.cpp > > Looks like you do have the latest released Mu, but 0.9.3 was released > before the fill/blit changes (mid December). > > If you're keen to get this working before the next Mu/uFlash release, > you can build a firmware image yourself, then update your local copy > of Mu or uFlash to use it. See instructions at > https://github.com/bbcmicrobit/micropython When using uFlash > directly, you can use the -r option to point to your newly built hex > file. Off the top of my head I'm not sure if Mu has a corresponding > argument, I've always just updated the contents of the hex file in > contrib/uflash.py manually. > > Jim > > On 20 June 2017 at 06:39, Ludwig Knoblauch wrote: >> Hi all, >> >> I just started 3 days ago working with my brand-new micro:bit device. I'm >> new on this mailing list and up to now I couldn't find a better place to >> discuss the unavoidable initial pitfalls. Maybe I can find help here for >> some trivia. Even if not, a hint whom to address would be appreciated. >> >> While ReadTheDocs announces a nice set of attributes for MicroBitImage >> objects, I found two of them not being implemented, namely fill() and >> blit(). These two attributes cause the following error message: >> >> AttributeError: 'MicroBitImage' object has no attribute >> 'missing-attribute' >> >> MicroPython v1.7-9-gbe020eb on 2016-04-18; micro:bit with nRF51822 >> >> Maybe this is a version problem? But my MicroPython development system seems >> to be up-to-date: mu-0.9.13.linux. Or could it be a firmware version problem >> with the micro:bit? Looks also up-to-date: >> >> Daplink Mode: Interface >> Interface Version: 0241 >> Git SHA: fa4132987102c51c110751d8bdb8a74aeb7b071b >> >> Any idea what went wrong? >> >> Regards and thanks in advance >> >> Ludwig. >> >> P.S.: The host computer runs under Linux Mint 17 (64 bit) with KDE desktop. >> >> >> _______________________________________________ >> 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 > -- Heinrich-Reichard-Stra?e 48 64560 Riedstadt-Erfelden Tel: 06158 8787550 Fax: 06158 8787552 E-Mail: Lknoblauch at web.de