From humphrey.robert at orange.fr Tue Aug 2 08:37:57 2016 From: humphrey.robert at orange.fr (Robert Humphrey) Date: Tue, 2 Aug 2016 14:37:57 +0200 Subject: [Microbit-Python] Can't get MU to run on MACbookAir Message-ID: I have installed MU from GitHub latest MU-3 30/07/2016 but it errors out on every statement. What haven?t I loaded? Op Sys OSX El Capitaine Example code:- -------------- next part -------------- A non-text attachment was scrubbed... Name: MUproblem.pdf Type: application/pdf Size: 133030 bytes Desc: not available URL: From carlos.p.a.87 at gmail.com Tue Aug 2 10:02:39 2016 From: carlos.p.a.87 at gmail.com (Carlos P.A.) Date: Tue, 2 Aug 2016 15:02:39 +0100 Subject: [Microbit-Python] Can't get MU to run on MACbookAir In-Reply-To: References: Message-ID: Hi Robert, I might be mistaken, but all those are probably styling annotations identified by the checker. Have a look at pep-8, the Python style guide, and you should be able to see reasoning behind it. https://www.python.org/dev/peps/pep-0008/ On 2 August 2016 at 13:37, Robert Humphrey wrote: > I have installed MU from GitHub latest MU-3 30/07/2016 but it errors > out on every statement. What haven?t I loaded? > > Op Sys OSX El Capitaine > > Example code:- > > > _______________________________________________ > 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 Tue Aug 2 10:05:13 2016 From: ntoll at ntoll.org (Nicholas H.Tollervey) Date: Tue, 2 Aug 2016 15:05:13 +0100 Subject: [Microbit-Python] Can't get MU to run on MACbookAir In-Reply-To: References: Message-ID: On 02/08/16 13:37, Robert Humphrey wrote: > I have installed MU from GitHub latest MU-3 30/07/2016 but it errors out on every statement. What haven?t I loaded? > > Op Sys OSX El Capitaine > > Example code:- > > > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > Hi Robert, Thanks for the feedback. In future, please just attach the PNG image file rather than sticking the screen shot in a PDF - it's just simpler and I don't have to twist my neck to see what you're up to (I sprained it trampolining over the weekend). :-) So, I'm trying to work out what exactly you mean. Do you mean that Mu has an error in it and crashes OR that Mu is reporting errors for every line in your code? Looking at your screenshot, I believe you're reporting the latter. If so, these are not errors! Rather, they are code quality feedback annotations. Your code probably will still work, but it has stylistic problems. For example, I can see from lines 5-8 you use a comment "#" without following it with a space (to aid readability). If you click on the red arrow next to each line a little post-it note will appear to explain why the line has been flagged. Such code quality checking is advisory! Unless you get syntax errors your code will run (although it may still contain bugs because it doesn't work as you expect). If you're interested in the conventions Mu uses for checking the quality of your code you should read up on PEP-8 - the style guide for Python programming (it's like the style guide newspapers use to guide their journalists in writing in an idiomatic and "house" style). https://www.python.org/dev/peps/pep-0008/ PEP-8 was written by Python's creator Guido van Rossum and a couple of other collaborators (including Nick Coghlan, who may be subscribed to this list). It's their vision of well written, idiomatic Python. Many Python programmers, myself included, use it for guidance when writing code. You are free to ignore it though. As PEP-8 itself says, "a foolish consistency is the hobgoblin of little minds". :-) Hope this helps, and more than happy to answer any questions you may have. 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 mark at hotpy.org Tue Aug 2 11:18:45 2016 From: mark at hotpy.org (Mark Shannon) Date: Tue, 2 Aug 2016 08:18:45 -0700 Subject: [Microbit-Python] Can't get MU to run on MACbookAir In-Reply-To: References: Message-ID: Hi, Perhaps we shouldn't be inflicting PEP8 on unsuspecting students ;) Pyflakes at least attempts to highlight errors. PEP8 is just annoying if you don't agree with its somewhat subjective decisions and more importantly will drown out any real errors that pyflakes might find. Cheers, Mark. On 02/08/16 07:05, Nicholas H.Tollervey wrote: > On 02/08/16 13:37, Robert Humphrey wrote: >> I have installed MU from GitHub latest MU-3 30/07/2016 but it errors out on every statement. What haven?t I loaded? >> >> Op Sys OSX El Capitaine >> >> Example code:- >> >> >> >> _______________________________________________ >> Microbit mailing list >> Microbit at python.org >> https://mail.python.org/mailman/listinfo/microbit >> > > Hi Robert, > > Thanks for the feedback. > > In future, please just attach the PNG image file rather than sticking > the screen shot in a PDF - it's just simpler and I don't have to twist > my neck to see what you're up to (I sprained it trampolining over the > weekend). :-) > > So, I'm trying to work out what exactly you mean. Do you mean that Mu > has an error in it and crashes OR that Mu is reporting errors for every > line in your code? Looking at your screenshot, I believe you're > reporting the latter. > > If so, these are not errors! > > Rather, they are code quality feedback annotations. Your code probably > will still work, but it has stylistic problems. For example, I can see > from lines 5-8 you use a comment "#" without following it with a space > (to aid readability). If you click on the red arrow next to each line a > little post-it note will appear to explain why the line has been flagged. > > Such code quality checking is advisory! Unless you get syntax errors > your code will run (although it may still contain bugs because it > doesn't work as you expect). > > If you're interested in the conventions Mu uses for checking the quality > of your code you should read up on PEP-8 - the style guide for Python > programming (it's like the style guide newspapers use to guide their > journalists in writing in an idiomatic and "house" style). > > https://www.python.org/dev/peps/pep-0008/ > > PEP-8 was written by Python's creator Guido van Rossum and a couple of > other collaborators (including Nick Coghlan, who may be subscribed to > this list). It's their vision of well written, idiomatic Python. Many > Python programmers, myself included, use it for guidance when writing code. > > You are free to ignore it though. As PEP-8 itself says, "a foolish > consistency is the hobgoblin of little minds". > > :-) > > Hope this helps, and more than happy to answer any questions you may have. > > N. > > > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > From humphrey.robert at orange.fr Tue Aug 2 11:35:40 2016 From: humphrey.robert at orange.fr (Robert Humphrey) Date: Tue, 2 Aug 2016 17:35:40 +0200 Subject: [Microbit-Python] Can't get MU to run on MACbookAir In-Reply-To: References: Message-ID: Thanks for the response. I find it hard work trying to install Micro Python, and thanks for bearing with me. The attached screen shot is typical. It appears that there in?t a library to import. I followed your link via Pep-8, installed Python 3.6, installed Active tcl 8.6. Ran Python 3.6 and get errors. I re-tried MU and again it appears that there are no libraries to import. Is there a simple way to get all this working as I can get Python to work interactively from the net at W3. microbit.Pythonanywhere.com, but no luck locally. Bob > ote: > > On 02/08/16 13:37, Robert Humphrey wrote: >> I have installed MU from GitHub latest MU-3 30/07/2016 but it errors out on every statement. What haven?t I loaded? >> >> Op Sys OSX El Capitaine >> >> Example code:- >> >> >> >> _______________________________________________ >> Microbit mailing list >> Microbit at python.org >> https://mail.python.org/mailman/listinfo/microbit >> > > Hi Robert, > > Thanks for the feedback. > > In future, please just attach the PNG image file rather than sticking > the screen shot in a PDF - it's just simpler and I don't have to twist > my neck to see what you're up to (I sprained it trampolining over the > weekend). :-) > > So, I'm trying to work out what exactly you mean. Do you mean that Mu > has an error in it and crashes OR that Mu is reporting errors for every > line in your code? Looking at your screenshot, I believe you're > reporting the latter. > > If so, these are not errors! > > Rather, they are code quality feedback annotations. Your code probably > will still work, but it has stylistic problems. For example, I can see > from lines 5-8 you use a comment "#" without following it with a space > (to aid readability). If you click on the red arrow next to each line a > little post-it note will appear to explain why the line has been flagged. > > Such code quality checking is advisory! Unless you get syntax errors > your code will run (although it may still contain bugs because it > doesn't work as you expect). > > If you're interested in the conventions Mu uses for checking the quality > of your code you should read up on PEP-8 - the style guide for Python > programming (it's like the style guide newspapers use to guide their > journalists in writing in an idiomatic and "house" style). > > https://www.python.org/dev/peps/pep-0008/ > > PEP-8 was written by Python's creator Guido van Rossum and a couple of > other collaborators (including Nick Coghlan, who may be subscribed to > this list). It's their vision of well written, idiomatic Python. Many > Python programmers, myself included, use it for guidance when writing code. > > You are free to ignore it though. As PEP-8 itself says, "a foolish > consistency is the hobgoblin of little minds". > > :-) > > Hope this helps, and more than happy to answer any questions you may have. > > N. > > _______________________________________________ > 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: Screen Shot 2016-08-02 at 17.29.08.png Type: image/png Size: 506063 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2016-08-02 at 17.22.06.png Type: image/png Size: 729722 bytes Desc: not available URL: From ntoll at ntoll.org Wed Aug 3 07:12:36 2016 From: ntoll at ntoll.org (Nicholas H.Tollervey) Date: Wed, 3 Aug 2016 12:12:36 +0100 Subject: [Microbit-Python] Can't get MU to run on MACbookAir In-Reply-To: References: Message-ID: <8d08818e-5526-4ffa-d282-bfe44791b225@ntoll.org> Hi Bob, From the screenshots, it appears that Mu is working fine on your Macbook. I'm trying to work out what it is that *isn't* working for you. Please bear with me if any of the following is obvious ~ I just want to make sure you've set yourself up properly. 1) Mu is working. 2) Plug in a micro:bit device to your Macbook via USB. 3) Click on the flash button and your script (in the Mu editor) will be transferred (flashed) onto the micro:bit (should take around 6 seconds). If there are any errors they'll scroll across the micro:bit's display. 4) Click on the REPL button to get access to the interactive prompt for the version of Python running on the micro:bit. You don't need to install Python 3.6 onto your Macbook - you should be using the version of Python *on* the actual device itself. For this to work you flash the device with the MicroPython runtime as I described in step 3 above. Following that, you get access to the Python prompt by clicking the REPL button. Does this make sense? Best of luck, N. On 02/08/16 16:35, Robert Humphrey wrote: > Thanks for the response. I find it hard work trying to install Micro > Python, and thanks for bearing with me. The attached screen shot is > typical. It appears that there in?t a library to import. > > I followed your link via Pep-8, installed Python 3.6, installed Active > tcl 8.6. Ran Python 3.6 and get errors. I re-tried MU and again it > appears that there are no libraries to import. Is there a simple way to > get all this working as I can get Python to work interactively from the > net at W3. microbit.Pythonanywhere.com > , but no luck locally. > Bob > > > >> ote: >> >> On 02/08/16 13:37, Robert Humphrey wrote: >>> I have installed MU from GitHub latest MU-3 30/07/2016 but it >>> errors out on every statement. What haven?t I loaded? >>> >>> Op Sys OSX El Capitaine >>> >>> Example code:- >>> >>> >>> >>> _______________________________________________ >>> Microbit mailing list >>> Microbit at python.org >>> https://mail.python.org/mailman/listinfo/microbit >>> >> >> Hi Robert, >> >> Thanks for the feedback. >> >> In future, please just attach the PNG image file rather than sticking >> the screen shot in a PDF - it's just simpler and I don't have to twist >> my neck to see what you're up to (I sprained it trampolining over the >> weekend). :-) >> >> So, I'm trying to work out what exactly you mean. Do you mean that Mu >> has an error in it and crashes OR that Mu is reporting errors for every >> line in your code? Looking at your screenshot, I believe you're >> reporting the latter. >> >> If so, these are not errors! >> >> Rather, they are code quality feedback annotations. Your code probably >> will still work, but it has stylistic problems. For example, I can see >> from lines 5-8 you use a comment "#" without following it with a space >> (to aid readability). If you click on the red arrow next to each line a >> little post-it note will appear to explain why the line has been flagged. >> >> Such code quality checking is advisory! Unless you get syntax errors >> your code will run (although it may still contain bugs because it >> doesn't work as you expect). >> >> If you're interested in the conventions Mu uses for checking the quality >> of your code you should read up on PEP-8 - the style guide for Python >> programming (it's like the style guide newspapers use to guide their >> journalists in writing in an idiomatic and "house" style). >> >> https://www.python.org/dev/peps/pep-0008/ >> >> PEP-8 was written by Python's creator Guido van Rossum and a couple of >> other collaborators (including Nick Coghlan, who may be subscribed to >> this list). It's their vision of well written, idiomatic Python. Many >> Python programmers, myself included, use it for guidance when writing >> code. >> >> You are free to ignore it though. As PEP-8 itself says, "a foolish >> consistency is the hobgoblin of little minds". >> >> :-) >> >> Hope this helps, and more than happy to answer any questions you may have. >> >> N. >> >> _______________________________________________ >> 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 -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From carlos.p.a.87 at gmail.com Wed Aug 3 07:18:00 2016 From: carlos.p.a.87 at gmail.com (Carlos P.A.) Date: Wed, 3 Aug 2016 12:18:00 +0100 Subject: [Microbit-Python] Can't get MU to run on MACbookAir In-Reply-To: References: Message-ID: Hi Robert, MicroPython is a reimplementation of Python 3 that primarily targets microcontrollers. It is possible to install Micropython on macOS or Linux, but for the microbit you run MicroPython directly on the target, not your PC. What MU does is pack your Python script together with MicroPython for the microbit and then loads that into the microbit itself. When you click on the REPL, that is a connection to the microbit and the code you type and excute there is sent to the microbit with the results sent back to your computer. If you would like to run a Python script on your computer that talks to the microbit, there is a project called microperi ( https://github.com/JoeGlancy/microperi) that implements a Python module that replicates the same API that the microbit has. However, please do not confuse these two different approaches, as the general microbit MicroPython approach is to run micropython on your microbit, not your PC. Regards, Carlos On 2 August 2016 at 16:35, Robert Humphrey wrote: > Thanks for the response. I find it hard work trying to install Micro > Python, and thanks for bearing with me. The attached screen shot is > typical. It appears that there in?t a library to import. > > I followed your link via Pep-8, installed Python 3.6, installed Active > tcl 8.6. Ran Python 3.6 and get errors. I re-tried MU and again it > appears that there are no libraries to import. Is there a simple way to get > all this working as I can get Python to work interactively from the net at > W3. microbit.Pythonanywhere.com , > but no luck locally. > Bob > > > > ote: > > > On 02/08/16 13:37, Robert Humphrey wrote: > > I have installed MU from GitHub latest MU-3 30/07/2016 but it errors > out on every statement. What haven?t I loaded? > > Op Sys OSX El Capitaine > > Example code:- > > > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > > > Hi Robert, > > Thanks for the feedback. > > In future, please just attach the PNG image file rather than sticking > the screen shot in a PDF - it's just simpler and I don't have to twist > my neck to see what you're up to (I sprained it trampolining over the > weekend). :-) > > So, I'm trying to work out what exactly you mean. Do you mean that Mu > has an error in it and crashes OR that Mu is reporting errors for every > line in your code? Looking at your screenshot, I believe you're > reporting the latter. > > If so, these are not errors! > > Rather, they are code quality feedback annotations. Your code probably > will still work, but it has stylistic problems. For example, I can see > from lines 5-8 you use a comment "#" without following it with a space > (to aid readability). If you click on the red arrow next to each line a > little post-it note will appear to explain why the line has been flagged. > > Such code quality checking is advisory! Unless you get syntax errors > your code will run (although it may still contain bugs because it > doesn't work as you expect). > > If you're interested in the conventions Mu uses for checking the quality > of your code you should read up on PEP-8 - the style guide for Python > programming (it's like the style guide newspapers use to guide their > journalists in writing in an idiomatic and "house" style). > > https://www.python.org/dev/peps/pep-0008/ > > PEP-8 was written by Python's creator Guido van Rossum and a couple of > other collaborators (including Nick Coghlan, who may be subscribed to > this list). It's their vision of well written, idiomatic Python. Many > Python programmers, myself included, use it for guidance when writing code. > > You are free to ignore it though. As PEP-8 itself says, "a foolish > consistency is the hobgoblin of little minds". > > :-) > > Hope this helps, and more than happy to answer any questions you may have. > > N. > > _______________________________________________ > 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2016-08-02 at 17.22.06.png Type: image/png Size: 729722 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2016-08-02 at 17.29.08.png Type: image/png Size: 506063 bytes Desc: not available URL: From humphrey.robert at orange.fr Wed Aug 3 09:55:07 2016 From: humphrey.robert at orange.fr (Robert Humphrey) Date: Wed, 3 Aug 2016 15:55:07 +0200 Subject: [Microbit-Python] Can't get MU to run on MACbookAir In-Reply-To: <8d08818e-5526-4ffa-d282-bfe44791b225@ntoll.org> References: <8d08818e-5526-4ffa-d282-bfe44791b225@ntoll.org> Message-ID: <9DA90E47-9A90-4D2F-98C8-C8E874F9DB48@orange.fr> Yes, sort of. The Microbit has 32K memory. Are you saying that a Python 3.6 19Mb zip file expands into 32K on the Microbit ?? That can?t be right - can it? Regarding Python 3.6 on a MAC. I think you are saying that I should not have Python 3.6 on the MAC at all, but MU on the MAC My Microbit has not arrived yet - I am just trying to understand Python (or something) pre arrival. MUST I always have the microbit attached to the MAC to write code? If not then why when I write a line of code from microbit import * do I get the message IMPORT error ?No module named microbit? Please see the attached screen shot on last E-mail. If I use the web based interactive version, my Python code doesn?t seem to have errors As regards MU, the screen shot shows ?errors" on every line or are these some form of helpful comments? Yes, it does produce a .hex file (which has data in it). What is syntactically incorrect with the statement:- from microbit import * When I click the CHECK button, I get ? from microbit import * ? used; unable to detect undefined names [In English we would understand that ?If you say words I don?t understand, I can?t help you?] Please Bear with this old duffer - remember that in my day, hard drives were only 25Mb, dates were held as compressed ASCII 5 byte strings (years ran from 0-9 and A-Z), Lowercase and fonts had not arrived and TELEX was new and FAX hadn?t arrived. Input was by paper tape or punched card and VDUs - (Screens to you) were for the computer operator. ROM was made from diode arrays and memory was magnetic core. My first home computer has 256 bytes of data and Binary had 3 states - Off, On and don?t know (Voltage region between -0.3 to +0.3 volts) and programmed in Hex machine code. Thanks Bob > On 03 Aug 2016, at 13:12, Nicholas H.Tollervey wrote: > > Hi Bob, > > From the screenshots, it appears that Mu is working fine on your > Macbook. I'm trying to work out what it is that *isn't* working for you. > > Please bear with me if any of the following is obvious ~ I just want to > make sure you've set yourself up properly. > > 1) Mu is working. > 2) Plug in a micro:bit device to your Macbook via USB. > 3) Click on the flash button and your script (in the Mu editor) will be > transferred (flashed) onto the micro:bit (should take around 6 seconds). > If there are any errors they'll scroll across the micro:bit's display. > 4) Click on the REPL button to get access to the interactive prompt for > the version of Python running on the micro:bit. > > You don't need to install Python 3.6 onto your Macbook - you should be > using the version of Python *on* the actual device itself. For this to > work you flash the device with the MicroPython runtime as I described in > step 3 above. Following that, you get access to the Python prompt by > clicking the REPL button. > > Does this make sense? > > Best of luck, > > N. > > On 02/08/16 16:35, Robert Humphrey wrote: >> Thanks for the response. I find it hard work trying to install Micro >> Python, and thanks for bearing with me. The attached screen shot is >> typical. It appears that there in?t a library to import. >> >> I followed your link via Pep-8, installed Python 3.6, installed Active >> tcl 8.6. Ran Python 3.6 and get errors. I re-tried MU and again it >> appears that there are no libraries to import. Is there a simple way to >> get all this working as I can get Python to work interactively from the >> net at W3. microbit.Pythonanywhere.com >> >, but no luck locally. >> Bob >> >> >> >>> ote: >>> >>> On 02/08/16 13:37, Robert Humphrey wrote: >>>> I have installed MU from GitHub latest MU-3 30/07/2016 but it >>>> errors out on every statement. What haven?t I loaded? >>>> >>>> Op Sys OSX El Capitaine >>>> >>>> Example code:- >>>> >>>> >>>> >>>> _______________________________________________ >>>> Microbit mailing list >>>> Microbit at python.org > >>>> https://mail.python.org/mailman/listinfo/microbit >>>> >>> >>> Hi Robert, >>> >>> Thanks for the feedback. >>> >>> In future, please just attach the PNG image file rather than sticking >>> the screen shot in a PDF - it's just simpler and I don't have to twist >>> my neck to see what you're up to (I sprained it trampolining over the >>> weekend). :-) >>> >>> So, I'm trying to work out what exactly you mean. Do you mean that Mu >>> has an error in it and crashes OR that Mu is reporting errors for every >>> line in your code? Looking at your screenshot, I believe you're >>> reporting the latter. >>> >>> If so, these are not errors! >>> >>> Rather, they are code quality feedback annotations. Your code probably >>> will still work, but it has stylistic problems. For example, I can see >>> from lines 5-8 you use a comment "#" without following it with a space >>> (to aid readability). If you click on the red arrow next to each line a >>> little post-it note will appear to explain why the line has been flagged. >>> >>> Such code quality checking is advisory! Unless you get syntax errors >>> your code will run (although it may still contain bugs because it >>> doesn't work as you expect). >>> >>> If you're interested in the conventions Mu uses for checking the quality >>> of your code you should read up on PEP-8 - the style guide for Python >>> programming (it's like the style guide newspapers use to guide their >>> journalists in writing in an idiomatic and "house" style). >>> >>> https://www.python.org/dev/peps/pep-0008/ >>> >>> PEP-8 was written by Python's creator Guido van Rossum and a couple of >>> other collaborators (including Nick Coghlan, who may be subscribed to >>> this list). It's their vision of well written, idiomatic Python. Many >>> Python programmers, myself included, use it for guidance when writing >>> code. >>> >>> You are free to ignore it though. As PEP-8 itself says, "a foolish >>> consistency is the hobgoblin of little minds". >>> >>> :-) >>> >>> Hope this helps, and more than happy to answer any questions you may have. >>> >>> N. >>> >>> _______________________________________________ >>> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From microbit at sheep.art.pl Wed Aug 3 10:11:44 2016 From: microbit at sheep.art.pl (Radomir Dopieralski) Date: Wed, 3 Aug 2016 16:11:44 +0200 Subject: [Microbit-Python] Can't get MU to run on MACbookAir In-Reply-To: <9DA90E47-9A90-4D2F-98C8-C8E874F9DB48@orange.fr> References: <8d08818e-5526-4ffa-d282-bfe44791b225@ntoll.org> <9DA90E47-9A90-4D2F-98C8-C8E874F9DB48@orange.fr> Message-ID: <20160803161144.06ce2957@ghostwheel> You can install Python om your mac or pc, and use that to learn to program, but the programs that are written for the micro:bit will not work. The language is the same, but the hardware it runs on offers completely different features, and the libraries are different too. You also use different tools on both of them -- the Mu editor on the micro:bit, some programming editor or IDE and a python interpreter on your PC. You could compare it to natural languages: both literary critics and mathematicians may be speaking English, but the vocabulary they use, and the ideas they are trying to express are completely different, and they would still not understand each other. It's similar with Python on the PC and on the micro:bit -- the syntax is the same, but the commands you have available are different -- because the devices are very different. So a program written for one will not work on the other. As for the "from microbit import *" thing -- that imports everything that is available in the microbit module to the local namespace. However, the Mu editor doesn't know what is available in the "microbit" module (because it doesn't have access to it, as it can't run on your computer, only on the micro:bit), and so it's unable to determine what names are actually getting imported there. Since it doesn't know what names are available, it can't further help you by spotting misspellings or use of undefined names. That's what this warning is about. If you want to get rid of it, you can explicitly import the names you need, for instance "from microbit import pin0, pin1". I hope that helps. On Wed, 3 Aug 2016 15:55:07 +0200 Robert Humphrey wrote: > Yes, sort of. The Microbit has 32K memory. Are you saying that a > Python 3.6 19Mb zip file expands into 32K on the Microbit ?? That > can?t be right - can it? > > > Regarding Python 3.6 on a MAC. I think you are saying that I should > not have Python 3.6 on the MAC at all, but MU on the MAC My Microbit > has not arrived yet - I am just trying to understand Python (or > something) pre arrival. MUST I always have the microbit attached to > the MAC to write code? If not then why when I write a line of code > > from microbit import * do I get the message IMPORT error ?No module > named microbit? Please see the attached screen shot on last E-mail. > If I use the web based interactive version, my Python code doesn?t > seem to have errors > > As regards MU, the screen shot shows ?errors" on every line or are > these some form of helpful comments? Yes, it does produce a .hex > file (which has data in it). > > What is syntactically incorrect with the statement:- > from microbit import * > > When I click the CHECK button, I get > ? from microbit import * ? used; unable to detect undefined names > [In English we would understand that ?If you say words I don?t > understand, I can?t help you?] > > Please > Bear with this old duffer - remember that in my day, hard drives > were only 25Mb, dates were held as compressed ASCII 5 byte strings > (years ran from 0-9 and A-Z), Lowercase and fonts had not arrived and > TELEX was new and FAX hadn?t arrived. Input was by paper tape or > punched card and VDUs - (Screens to you) were for the computer > operator. ROM was made from diode arrays and memory was magnetic > core. My first home computer has 256 bytes of data and Binary had 3 > states - Off, On and don?t know (Voltage region between -0.3 to +0.3 > volts) and programmed in Hex machine code. > > Thanks Bob > > > > > > > On 03 Aug 2016, at 13:12, Nicholas H.Tollervey > > wrote: > > > > Hi Bob, > > > > From the screenshots, it appears that Mu is working fine on your > > Macbook. I'm trying to work out what it is that *isn't* working for > > you. > > > > Please bear with me if any of the following is obvious ~ I just > > want to make sure you've set yourself up properly. > > > > 1) Mu is working. > > 2) Plug in a micro:bit device to your Macbook via USB. > > 3) Click on the flash button and your script (in the Mu editor) > > will be transferred (flashed) onto the micro:bit (should take > > around 6 seconds). If there are any errors they'll scroll across > > the micro:bit's display. 4) Click on the REPL button to get access > > to the interactive prompt for the version of Python running on the > > micro:bit. > > > > You don't need to install Python 3.6 onto your Macbook - you should > > be using the version of Python *on* the actual device itself. For > > this to work you flash the device with the MicroPython runtime as I > > described in step 3 above. Following that, you get access to the > > Python prompt by clicking the REPL button. > > > > Does this make sense? > > > > Best of luck, > > > > N. > > > > On 02/08/16 16:35, Robert Humphrey wrote: > >> Thanks for the response. I find it hard work trying to install > >> Micro Python, and thanks for bearing with me. The attached screen > >> shot is typical. It appears that there in?t a library to import. > >> > >> I followed your link via Pep-8, installed Python 3.6, installed > >> Active tcl 8.6. Ran Python 3.6 and get errors. I re-tried MU and > >> again it appears that there are no libraries to import. Is there a > >> simple way to get all this working as I can get Python to work > >> interactively from the net at W3. microbit.Pythonanywhere.com > >> > >> >> >, but no luck locally. Bob > >> > >> > >> > >>> ote: > >>> > >>> On 02/08/16 13:37, Robert Humphrey wrote: > >>>> I have installed MU from GitHub latest MU-3 30/07/2016 but it > >>>> errors out on every statement. What haven?t I loaded? > >>>> > >>>> Op Sys OSX El Capitaine > >>>> > >>>> Example code:- > >>>> > >>>> > >>>> > >>>> _______________________________________________ > >>>> Microbit mailing list > >>>> Microbit at python.org > >>>> > > >>>> https://mail.python.org/mailman/listinfo/microbit > >>>> > >>> > >>> Hi Robert, > >>> > >>> Thanks for the feedback. > >>> > >>> In future, please just attach the PNG image file rather than > >>> sticking the screen shot in a PDF - it's just simpler and I don't > >>> have to twist my neck to see what you're up to (I sprained it > >>> trampolining over the weekend). :-) > >>> > >>> So, I'm trying to work out what exactly you mean. Do you mean > >>> that Mu has an error in it and crashes OR that Mu is reporting > >>> errors for every line in your code? Looking at your screenshot, I > >>> believe you're reporting the latter. > >>> > >>> If so, these are not errors! > >>> > >>> Rather, they are code quality feedback annotations. Your code > >>> probably will still work, but it has stylistic problems. For > >>> example, I can see from lines 5-8 you use a comment "#" without > >>> following it with a space (to aid readability). If you click on > >>> the red arrow next to each line a little post-it note will appear > >>> to explain why the line has been flagged. > >>> > >>> Such code quality checking is advisory! Unless you get syntax > >>> errors your code will run (although it may still contain bugs > >>> because it doesn't work as you expect). > >>> > >>> If you're interested in the conventions Mu uses for checking the > >>> quality of your code you should read up on PEP-8 - the style > >>> guide for Python programming (it's like the style guide > >>> newspapers use to guide their journalists in writing in an > >>> idiomatic and "house" style). > >>> > >>> https://www.python.org/dev/peps/pep-0008/ > >>> > >>> PEP-8 was written by Python's creator Guido van Rossum and a > >>> couple of other collaborators (including Nick Coghlan, who may be > >>> subscribed to this list). It's their vision of well written, > >>> idiomatic Python. Many Python programmers, myself included, use > >>> it for guidance when writing code. > >>> > >>> You are free to ignore it though. As PEP-8 itself says, "a foolish > >>> consistency is the hobgoblin of little minds". > >>> > >>> :-) > >>> > >>> Hope this helps, and more than happy to answer any questions you > >>> may have. > >>> > >>> N. > >>> > >>> _______________________________________________ > >>> 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 > > -- Radomir Dopieralski -- Radomir Dopieralski From david at thinkingbinaries.com Wed Aug 3 10:27:41 2016 From: david at thinkingbinaries.com (David Whale) Date: Wed, 3 Aug 2016 15:27:41 +0100 Subject: [Microbit-Python] Can't get MU to run on MACbookAir In-Reply-To: References: Message-ID: Hi Robert, You might find this video useful. https://youtu.be/hUIObK3MHL8 The last 10 mins or so demonstrate how to use mu both interactively and also in order to store a program on your micro:bit Hope it helps David On 3 Aug 2016 12:18 pm, "Carlos P.A." wrote: > Hi Robert, > > MicroPython is a reimplementation of Python 3 that primarily targets > microcontrollers. It is possible to install Micropython on macOS or Linux, > but for the microbit you run MicroPython directly on the target, not your > PC. > > What MU does is pack your Python script together with MicroPython for the > microbit and then loads that into the microbit itself. When you click on > the REPL, that is a connection to the microbit and the code you type and > excute there is sent to the microbit with the results sent back to your > computer. > > If you would like to run a Python script on your computer that talks to > the microbit, there is a project called microperi ( > https://github.com/JoeGlancy/microperi) that implements a Python module > that replicates the same API that the microbit has. However, please do not > confuse these two different approaches, as the general microbit MicroPython > approach is to run micropython on your microbit, not your PC. > > Regards, > Carlos > > > > On 2 August 2016 at 16:35, Robert Humphrey > wrote: > >> Thanks for the response. I find it hard work trying to install Micro >> Python, and thanks for bearing with me. The attached screen shot is >> typical. It appears that there in?t a library to import. >> >> I followed your link via Pep-8, installed Python 3.6, installed Active >> tcl 8.6. Ran Python 3.6 and get errors. I re-tried MU and again it >> appears that there are no libraries to import. Is there a simple way to get >> all this working as I can get Python to work interactively from the net at >> W3. microbit.Pythonanywhere.com , >> but no luck locally. >> Bob >> >> >> >> ote: >> >> >> On 02/08/16 13:37, Robert Humphrey wrote: >> >> I have installed MU from GitHub latest MU-3 30/07/2016 but it errors >> out on every statement. What haven?t I loaded? >> >> Op Sys OSX El Capitaine >> >> Example code:- >> >> >> >> _______________________________________________ >> Microbit mailing list >> Microbit at python.org >> https://mail.python.org/mailman/listinfo/microbit >> >> >> Hi Robert, >> >> Thanks for the feedback. >> >> In future, please just attach the PNG image file rather than sticking >> the screen shot in a PDF - it's just simpler and I don't have to twist >> my neck to see what you're up to (I sprained it trampolining over the >> weekend). :-) >> >> So, I'm trying to work out what exactly you mean. Do you mean that Mu >> has an error in it and crashes OR that Mu is reporting errors for every >> line in your code? Looking at your screenshot, I believe you're >> reporting the latter. >> >> If so, these are not errors! >> >> Rather, they are code quality feedback annotations. Your code probably >> will still work, but it has stylistic problems. For example, I can see >> from lines 5-8 you use a comment "#" without following it with a space >> (to aid readability). If you click on the red arrow next to each line a >> little post-it note will appear to explain why the line has been flagged. >> >> Such code quality checking is advisory! Unless you get syntax errors >> your code will run (although it may still contain bugs because it >> doesn't work as you expect). >> >> If you're interested in the conventions Mu uses for checking the quality >> of your code you should read up on PEP-8 - the style guide for Python >> programming (it's like the style guide newspapers use to guide their >> journalists in writing in an idiomatic and "house" style). >> >> https://www.python.org/dev/peps/pep-0008/ >> >> PEP-8 was written by Python's creator Guido van Rossum and a couple of >> other collaborators (including Nick Coghlan, who may be subscribed to >> this list). It's their vision of well written, idiomatic Python. Many >> Python programmers, myself included, use it for guidance when writing >> code. >> >> You are free to ignore it though. As PEP-8 itself says, "a foolish >> consistency is the hobgoblin of little minds". >> >> :-) >> >> Hope this helps, and more than happy to answer any questions you may have. >> >> N. >> >> _______________________________________________ >> 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2016-08-02 at 17.22.06.png Type: image/png Size: 729722 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2016-08-02 at 17.29.08.png Type: image/png Size: 506063 bytes Desc: not available URL: From ntoll at ntoll.org Wed Aug 3 10:46:59 2016 From: ntoll at ntoll.org (Nicholas H.Tollervey) Date: Wed, 3 Aug 2016 15:46:59 +0100 Subject: [Microbit-Python] Can't get MU to run on MACbookAir In-Reply-To: <9DA90E47-9A90-4D2F-98C8-C8E874F9DB48@orange.fr> References: <8d08818e-5526-4ffa-d282-bfe44791b225@ntoll.org> <9DA90E47-9A90-4D2F-98C8-C8E874F9DB48@orange.fr> Message-ID: Hi Bob, Comments in-line below. :-) N. On 03/08/16 14:55, Robert Humphrey wrote: > Yes, sort of. The Microbit has 32K memory. Are you saying that a > Python 3.6 19Mb zip file expands into 32K on the Microbit ?? That > can?t be right - can it? > The 19mb 3.6 version of Python you downloaded from python.org is not the same as the version of Python on the micro:bit. Python 3.6 for your computer comes with a bunch of libraries and tools. Python on the micro:bit is, in fact, MicroPython - an amazing project since it reimplements Python 3 but for constrained computing environments like the micro:bit. However, MicroPython doesn't come with all the libraries and tools, it's only just large enough to fit on the micro:bit..! Having said that, MicroPython is still Python and remarkably powerful. I'm sure you'll have fun working through the tutorials! > > Regarding Python 3.6 on a MAC. I think you are saying that I should not > have Python 3.6 on the MAC at all, but MU on the MAC Having Python on your Mac is a good idea since you'll be able to play with Python. However, a Mac is not a micro:bit and, as a result, the version of Python on the Mac won't include the micro:bit libraries we use in our documentation. > My Microbit has not arrived yet - I am just trying to understand Python > (or something) pre arrival. MUST I always have the microbit attached to > the MAC to write code? You can write code without the device being plugged in. However, you still need a device upon which to run the code. Hence, once you plug it in, you simply click "flash" to put your code on the device. > If not then why when I write a line of code > > from microbit import * do I get the message IMPORT error ?No module > named microbit? Please see the attached screen shot on last E-mail. If As I think I may have mentioned - these are not errors. These are style guides. I think, in future, I'll follow some advice that Radomir suggested: colour error messages in red and stylistic messages in blue so they don't look so problematic. > I use the web based interactive version, my Python code doesn?t seem to > have errors > Writing code in an editor is not the same as running it. Mu is simply trying to help you write stylistic Python so that it's easy for others to understand. The web based editor (which I also wrote) is rather limited so doesn't check your code for style. To be clear, what you're seeing are not errors - just style guidance. > As regards MU, the screen shot shows ?errors" on every line or are Nope... they're not errors! :-) > these some form of helpful comments? Yes, it does produce a .hex file > (which has data in it). Great, these are helpful comments. If you get a .hex file then everything is ready for when you plug in your micro:bit. At that point, when you click "flash" Mu will detect where your device is and copy over your code for you. If it can't find it, it'll simply ask you where it is (you choose from a file system dialogue). > > What is syntactically incorrect with the statement:- > from microbit import * > > When I click the CHECK button, I get > ? from microbit import * ? used; unable to detect undefined names [In > English we would understand that ?If you say words I don?t understand, I > can?t help you?] > OK... I've just read Radomir's reply. He's nailed it. I can't improve on his explanation of this message. > Please > Bear with this old duffer - remember that in my day, hard drives were > only 25Mb, dates were held as compressed ASCII 5 byte strings (years ran > from 0-9 and A-Z), Lowercase and fonts had not arrived and TELEX was new > and FAX hadn?t arrived. Input was by paper tape or punched card and > VDUs - (Screens to you) were for the computer operator. ROM was made > from diode arrays and memory was magnetic core. My first home computer > has 256 bytes of data and Binary had 3 states - Off, On and don?t know > (Voltage region between -0.3 to +0.3 volts) and programmed in Hex > machine code. Oh boy! That sounds amazing. You should write up your experiences from "back in the day" (as it were) and compare / contrast them to your experience with MicroPython on the micro:bit. I'd love to read something like that! Here I was thinking I was old because I remember the old 8-bit machines I used as a kid in the 1980s (such as the original BBC micro). So, please don't worry about old-duffer-hood. :-) Happy to help in any way that I can, and, as I think you're finding out, the Python community is friendly, helpful, well organised and full of opportunity to learn. Just dive in and ask! Best wishes, N. > > Thanks Bob > > > > > >> On 03 Aug 2016, at 13:12, Nicholas H.Tollervey > > wrote: >> >> Hi Bob, >> >> From the screenshots, it appears that Mu is working fine on your >> Macbook. I'm trying to work out what it is that *isn't* working for you. >> >> Please bear with me if any of the following is obvious ~ I just want to >> make sure you've set yourself up properly. >> >> 1) Mu is working. >> 2) Plug in a micro:bit device to your Macbook via USB. >> 3) Click on the flash button and your script (in the Mu editor) will be >> transferred (flashed) onto the micro:bit (should take around 6 seconds). >> If there are any errors they'll scroll across the micro:bit's display. >> 4) Click on the REPL button to get access to the interactive prompt for >> the version of Python running on the micro:bit. >> >> You don't need to install Python 3.6 onto your Macbook - you should be >> using the version of Python *on* the actual device itself. For this to >> work you flash the device with the MicroPython runtime as I described in >> step 3 above. Following that, you get access to the Python prompt by >> clicking the REPL button. >> >> Does this make sense? >> >> Best of luck, >> >> N. >> >> On 02/08/16 16:35, Robert Humphrey wrote: >>> Thanks for the response. I find it hard work trying to install Micro >>> Python, and thanks for bearing with me. The attached screen shot is >>> typical. It appears that there in?t a library to import. >>> >>> I followed your link via Pep-8, installed Python 3.6, installed Active >>> tcl 8.6. Ran Python 3.6 and get errors. I re-tried MU and again it >>> appears that there are no libraries to import. Is there a simple way to >>> get all this working as I can get Python to work interactively from the >>> net at W3. microbit.Pythonanywhere.com >>> >>> >> >, but no luck locally. >>> Bob >>> >>> >>> >>>> ote: >>>> >>>> On 02/08/16 13:37, Robert Humphrey wrote: >>>>> I have installed MU from GitHub latest MU-3 30/07/2016 but it >>>>> errors out on every statement. What haven?t I loaded? >>>>> >>>>> Op Sys OSX El Capitaine >>>>> >>>>> Example code:- >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Microbit mailing list >>>>> Microbit at python.org >>>>> >>>>> https://mail.python.org/mailman/listinfo/microbit >>>>> >>>> >>>> Hi Robert, >>>> >>>> Thanks for the feedback. >>>> >>>> In future, please just attach the PNG image file rather than sticking >>>> the screen shot in a PDF - it's just simpler and I don't have to twist >>>> my neck to see what you're up to (I sprained it trampolining over the >>>> weekend). :-) >>>> >>>> So, I'm trying to work out what exactly you mean. Do you mean that Mu >>>> has an error in it and crashes OR that Mu is reporting errors for every >>>> line in your code? Looking at your screenshot, I believe you're >>>> reporting the latter. >>>> >>>> If so, these are not errors! >>>> >>>> Rather, they are code quality feedback annotations. Your code probably >>>> will still work, but it has stylistic problems. For example, I can see >>>> from lines 5-8 you use a comment "#" without following it with a space >>>> (to aid readability). If you click on the red arrow next to each line a >>>> little post-it note will appear to explain why the line has been >>>> flagged. >>>> >>>> Such code quality checking is advisory! Unless you get syntax errors >>>> your code will run (although it may still contain bugs because it >>>> doesn't work as you expect). >>>> >>>> If you're interested in the conventions Mu uses for checking the quality >>>> of your code you should read up on PEP-8 - the style guide for Python >>>> programming (it's like the style guide newspapers use to guide their >>>> journalists in writing in an idiomatic and "house" style). >>>> >>>> https://www.python.org/dev/peps/pep-0008/ >>>> >>>> PEP-8 was written by Python's creator Guido van Rossum and a couple of >>>> other collaborators (including Nick Coghlan, who may be subscribed to >>>> this list). It's their vision of well written, idiomatic Python. Many >>>> Python programmers, myself included, use it for guidance when writing >>>> code. >>>> >>>> You are free to ignore it though. As PEP-8 itself says, "a foolish >>>> consistency is the hobgoblin of little minds". >>>> >>>> :-) >>>> >>>> Hope this helps, and more than happy to answer any questions you may >>>> have. >>>> >>>> N. >>>> >>>> _______________________________________________ >>>> 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 > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From humphrey.robert at orange.fr Wed Aug 3 12:25:30 2016 From: humphrey.robert at orange.fr (Robert Humphrey) Date: Wed, 3 Aug 2016 18:25:30 +0200 Subject: [Microbit-Python] Can't get MU to run on MACbookAir In-Reply-To: References: <8d08818e-5526-4ffa-d282-bfe44791b225@ntoll.org> <9DA90E47-9A90-4D2F-98C8-C8E874F9DB48@orange.fr> Message-ID: <45F67ABA-81B3-4676-AE82-FC5C48E40DB9@orange.fr> Great - thanks for the reply. I am hoping that my daughter brings me over my Microbit in a week or twos time. Bob > On 03 Aug 2016, at 16:46, Nicholas H.Tollervey wrote: > > Hi Bob, > > Comments in-line below. :-) > > N. > > On 03/08/16 14:55, Robert Humphrey wrote: >> Yes, sort of. The Microbit has 32K memory. Are you saying that a >> Python 3.6 19Mb zip file expands into 32K on the Microbit ?? That >> can?t be right - can it? >> > > The 19mb 3.6 version of Python you downloaded from python.org is not the > same as the version of Python on the micro:bit. Python 3.6 for your > computer comes with a bunch of libraries and tools. Python on the > micro:bit is, in fact, MicroPython - an amazing project since it > reimplements Python 3 but for constrained computing environments like > the micro:bit. However, MicroPython doesn't come with all the libraries > and tools, it's only just large enough to fit on the micro:bit..! > > Having said that, MicroPython is still Python and remarkably powerful. > I'm sure you'll have fun working through the tutorials! > >> >> Regarding Python 3.6 on a MAC. I think you are saying that I should not >> have Python 3.6 on the MAC at all, but MU on the MAC > > Having Python on your Mac is a good idea since you'll be able to play > with Python. However, a Mac is not a micro:bit and, as a result, the > version of Python on the Mac won't include the micro:bit libraries we > use in our documentation. > >> My Microbit has not arrived yet - I am just trying to understand Python >> (or something) pre arrival. MUST I always have the microbit attached to >> the MAC to write code? > > You can write code without the device being plugged in. However, you > still need a device upon which to run the code. Hence, once you plug it > in, you simply click "flash" to put your code on the device. > >> If not then why when I write a line of code >> >> from microbit import * do I get the message IMPORT error ?No module >> named microbit? Please see the attached screen shot on last E-mail. If > > As I think I may have mentioned - these are not errors. These are style > guides. I think, in future, I'll follow some advice that Radomir > suggested: colour error messages in red and stylistic messages in blue > so they don't look so problematic. > >> I use the web based interactive version, my Python code doesn?t seem to >> have errors >> > > Writing code in an editor is not the same as running it. Mu is simply > trying to help you write stylistic Python so that it's easy for others > to understand. The web based editor (which I also wrote) is rather > limited so doesn't check your code for style. > > To be clear, what you're seeing are not errors - just style guidance. > >> As regards MU, the screen shot shows ?errors" on every line or are > > Nope... they're not errors! :-) > >> these some form of helpful comments? Yes, it does produce a .hex file >> (which has data in it). > > Great, these are helpful comments. > > If you get a .hex file then everything is ready for when you plug in > your micro:bit. At that point, when you click "flash" Mu will detect > where your device is and copy over your code for you. If it can't find > it, it'll simply ask you where it is (you choose from a file system > dialogue). > >> >> What is syntactically incorrect with the statement:- >> from microbit import * >> >> When I click the CHECK button, I get >> ? from microbit import * ? used; unable to detect undefined names [In >> English we would understand that ?If you say words I don?t understand, I >> can?t help you?] >> > > OK... I've just read Radomir's reply. He's nailed it. I can't improve on > his explanation of this message. > >> Please >> Bear with this old duffer - remember that in my day, hard drives were >> only 25Mb, dates were held as compressed ASCII 5 byte strings (years ran >> from 0-9 and A-Z), Lowercase and fonts had not arrived and TELEX was new >> and FAX hadn?t arrived. Input was by paper tape or punched card and >> VDUs - (Screens to you) were for the computer operator. ROM was made >> from diode arrays and memory was magnetic core. My first home computer >> has 256 bytes of data and Binary had 3 states - Off, On and don?t know >> (Voltage region between -0.3 to +0.3 volts) and programmed in Hex >> machine code. > > Oh boy! That sounds amazing. You should write up your experiences from > "back in the day" (as it were) and compare / contrast them to your > experience with MicroPython on the micro:bit. I'd love to read something > like that! > > Here I was thinking I was old because I remember the old 8-bit machines > I used as a kid in the 1980s (such as the original BBC micro). > > So, please don't worry about old-duffer-hood. :-) > > Happy to help in any way that I can, and, as I think you're finding out, > the Python community is friendly, helpful, well organised and full of > opportunity to learn. Just dive in and ask! > > Best wishes, > > N. > >> >> Thanks Bob >> >> >> >> >> >>> On 03 Aug 2016, at 13:12, Nicholas H.Tollervey >>> >> wrote: >>> >>> Hi Bob, >>> >>> From the screenshots, it appears that Mu is working fine on your >>> Macbook. I'm trying to work out what it is that *isn't* working for you. >>> >>> Please bear with me if any of the following is obvious ~ I just want to >>> make sure you've set yourself up properly. >>> >>> 1) Mu is working. >>> 2) Plug in a micro:bit device to your Macbook via USB. >>> 3) Click on the flash button and your script (in the Mu editor) will be >>> transferred (flashed) onto the micro:bit (should take around 6 seconds). >>> If there are any errors they'll scroll across the micro:bit's display. >>> 4) Click on the REPL button to get access to the interactive prompt for >>> the version of Python running on the micro:bit. >>> >>> You don't need to install Python 3.6 onto your Macbook - you should be >>> using the version of Python *on* the actual device itself. For this to >>> work you flash the device with the MicroPython runtime as I described in >>> step 3 above. Following that, you get access to the Python prompt by >>> clicking the REPL button. >>> >>> Does this make sense? >>> >>> Best of luck, >>> >>> N. >>> >>> On 02/08/16 16:35, Robert Humphrey wrote: >>>> Thanks for the response. I find it hard work trying to install Micro >>>> Python, and thanks for bearing with me. The attached screen shot is >>>> typical. It appears that there in?t a library to import. >>>> >>>> I followed your link via Pep-8, installed Python 3.6, installed Active >>>> tcl 8.6. Ran Python 3.6 and get errors. I re-tried MU and again it >>>> appears that there are no libraries to import. Is there a simple way to >>>> get all this working as I can get Python to work interactively from the >>>> net at W3. microbit.Pythonanywhere.com >>>> > >>>> >>>> >>, but no luck locally. >>>> Bob >>>> >>>> >>>> >>>>> ote: >>>>> >>>>> On 02/08/16 13:37, Robert Humphrey wrote: >>>>>> I have installed MU from GitHub latest MU-3 30/07/2016 but it >>>>>> errors out on every statement. What haven?t I loaded? >>>>>> >>>>>> Op Sys OSX El Capitaine >>>>>> >>>>>> Example code:- >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Microbit mailing list >>>>>> Microbit at python.org >>>>>> > > >>>>>> https://mail.python.org/mailman/listinfo/microbit >>>>>> >>>>> >>>>> Hi Robert, >>>>> >>>>> Thanks for the feedback. >>>>> >>>>> In future, please just attach the PNG image file rather than sticking >>>>> the screen shot in a PDF - it's just simpler and I don't have to twist >>>>> my neck to see what you're up to (I sprained it trampolining over the >>>>> weekend). :-) >>>>> >>>>> So, I'm trying to work out what exactly you mean. Do you mean that Mu >>>>> has an error in it and crashes OR that Mu is reporting errors for every >>>>> line in your code? Looking at your screenshot, I believe you're >>>>> reporting the latter. >>>>> >>>>> If so, these are not errors! >>>>> >>>>> Rather, they are code quality feedback annotations. Your code probably >>>>> will still work, but it has stylistic problems. For example, I can see >>>>> from lines 5-8 you use a comment "#" without following it with a space >>>>> (to aid readability). If you click on the red arrow next to each line a >>>>> little post-it note will appear to explain why the line has been >>>>> flagged. >>>>> >>>>> Such code quality checking is advisory! Unless you get syntax errors >>>>> your code will run (although it may still contain bugs because it >>>>> doesn't work as you expect). >>>>> >>>>> If you're interested in the conventions Mu uses for checking the quality >>>>> of your code you should read up on PEP-8 - the style guide for Python >>>>> programming (it's like the style guide newspapers use to guide their >>>>> journalists in writing in an idiomatic and "house" style). >>>>> >>>>> https://www.python.org/dev/peps/pep-0008/ >>>>> >>>>> PEP-8 was written by Python's creator Guido van Rossum and a couple of >>>>> other collaborators (including Nick Coghlan, who may be subscribed to >>>>> this list). It's their vision of well written, idiomatic Python. Many >>>>> Python programmers, myself included, use it for guidance when writing >>>>> code. >>>>> >>>>> You are free to ignore it though. As PEP-8 itself says, "a foolish >>>>> consistency is the hobgoblin of little minds". >>>>> >>>>> :-) >>>>> >>>>> Hope this helps, and more than happy to answer any questions you may >>>>> have. >>>>> >>>>> N. >>>>> >>>>> _______________________________________________ >>>>> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From david at thinkingbinaries.com Wed Aug 3 13:17:00 2016 From: david at thinkingbinaries.com (David Whale) Date: Wed, 3 Aug 2016 18:17:00 +0100 Subject: [Microbit-Python] Can't get MU to run on MACbookAir In-Reply-To: <45F67ABA-81B3-4676-AE82-FC5C48E40DB9@orange.fr> References: <8d08818e-5526-4ffa-d282-bfe44791b225@ntoll.org> <9DA90E47-9A90-4D2F-98C8-C8E874F9DB48@orange.fr> <45F67ABA-81B3-4676-AE82-FC5C48E40DB9@orange.fr> Message-ID: Regarding... *>>What is syntactically incorrect with the statement:-* *>>from microbit import * * *>>When I click the CHECK button, I get* *>> ? from microbit import * ? used; unable to detect undefined names [In English we would understand that ?If you say words I don?t understand, I can?t help you?]* and.. *>>OK... I've just read Radomir's reply. He's nailed it. I can't improve on* *>>his explanation of this message.* Nicholas, this is a very confusing message indeed! - why does Mu not know what is in the microbit package, as Mu is written to develop code for the micro:bit and surely if it is doing code completion, it must have access to the 'known' directory of methods that the microbit libraries use? For a newbie, such a message is confusing - can it be suppressed, or the underlying visibility issue with the microbit module within Mu be fixed? The first experience is when you first do that import, and it should be a good experience, not one that bombards you with warnings that look like errors! Many thanks! David ___________________________________________________________ David Whale, B.Sc (Hons), MIET *Software Engineer and IET Schools Liaison Officer, Essex* On 3 August 2016 at 17:25, Robert Humphrey wrote: > Great - thanks for the reply. I am hoping that my daughter brings me over > my Microbit in a week or twos time. > Bob > > On 03 Aug 2016, at 16:46, Nicholas H.Tollervey wrote: > > Hi Bob, > > Comments in-line below. :-) > > N. > > On 03/08/16 14:55, Robert Humphrey wrote: > > Yes, sort of. The Microbit has 32K memory. Are you saying that a > Python 3.6 19Mb zip file expands into 32K on the Microbit ?? That > can?t be right - can it? > > > The 19mb 3.6 version of Python you downloaded from python.org is not the > same as the version of Python on the micro:bit. Python 3.6 for your > computer comes with a bunch of libraries and tools. Python on the > micro:bit is, in fact, MicroPython - an amazing project since it > reimplements Python 3 but for constrained computing environments like > the micro:bit. However, MicroPython doesn't come with all the libraries > and tools, it's only just large enough to fit on the micro:bit..! > > Having said that, MicroPython is still Python and remarkably powerful. > I'm sure you'll have fun working through the tutorials! > > > Regarding Python 3.6 on a MAC. I think you are saying that I should not > have Python 3.6 on the MAC at all, but MU on the MAC > > > Having Python on your Mac is a good idea since you'll be able to play > with Python. However, a Mac is not a micro:bit and, as a result, the > version of Python on the Mac won't include the micro:bit libraries we > use in our documentation. > > My Microbit has not arrived yet - I am just trying to understand Python > (or something) pre arrival. MUST I always have the microbit attached to > the MAC to write code? > > > You can write code without the device being plugged in. However, you > still need a device upon which to run the code. Hence, once you plug it > in, you simply click "flash" to put your code on the device. > > If not then why when I write a line of code > > from microbit import * do I get the message IMPORT error ?No module > named microbit? Please see the attached screen shot on last E-mail. If > > > As I think I may have mentioned - these are not errors. These are style > guides. I think, in future, I'll follow some advice that Radomir > suggested: colour error messages in red and stylistic messages in blue > so they don't look so problematic. > > I use the web based interactive version, my Python code doesn?t seem to > have errors > > > Writing code in an editor is not the same as running it. Mu is simply > trying to help you write stylistic Python so that it's easy for others > to understand. The web based editor (which I also wrote) is rather > limited so doesn't check your code for style. > > To be clear, what you're seeing are not errors - just style guidance. > > As regards MU, the screen shot shows ?errors" on every line or are > > > Nope... they're not errors! :-) > > these some form of helpful comments? Yes, it does produce a .hex file > (which has data in it). > > > Great, these are helpful comments. > > If you get a .hex file then everything is ready for when you plug in > your micro:bit. At that point, when you click "flash" Mu will detect > where your device is and copy over your code for you. If it can't find > it, it'll simply ask you where it is (you choose from a file system > dialogue). > > > What is syntactically incorrect with the statement:- > from microbit import * > > When I click the CHECK button, I get > ? from microbit import * ? used; unable to detect undefined names [In > English we would understand that ?If you say words I don?t understand, I > can?t help you?] > > > OK... I've just read Radomir's reply. He's nailed it. I can't improve on > his explanation of this message. > > Please > Bear with this old duffer - remember that in my day, hard drives were > only 25Mb, dates were held as compressed ASCII 5 byte strings (years ran > from 0-9 and A-Z), Lowercase and fonts had not arrived and TELEX was new > and FAX hadn?t arrived. Input was by paper tape or punched card and > VDUs - (Screens to you) were for the computer operator. ROM was made > from diode arrays and memory was magnetic core. My first home computer > has 256 bytes of data and Binary had 3 states - Off, On and don?t know > (Voltage region between -0.3 to +0.3 volts) and programmed in Hex > machine code. > > > Oh boy! That sounds amazing. You should write up your experiences from > "back in the day" (as it were) and compare / contrast them to your > experience with MicroPython on the micro:bit. I'd love to read something > like that! > > Here I was thinking I was old because I remember the old 8-bit machines > I used as a kid in the 1980s (such as the original BBC micro). > > So, please don't worry about old-duffer-hood. :-) > > Happy to help in any way that I can, and, as I think you're finding out, > the Python community is friendly, helpful, well organised and full of > opportunity to learn. Just dive in and ask! > > Best wishes, > > N. > > > Thanks Bob > > > > > > On 03 Aug 2016, at 13:12, Nicholas H.Tollervey >> wrote: > > Hi Bob, > > From the screenshots, it appears that Mu is working fine on your > Macbook. I'm trying to work out what it is that *isn't* working for you. > > Please bear with me if any of the following is obvious ~ I just want to > make sure you've set yourself up properly. > > 1) Mu is working. > 2) Plug in a micro:bit device to your Macbook via USB. > 3) Click on the flash button and your script (in the Mu editor) will be > transferred (flashed) onto the micro:bit (should take around 6 seconds). > If there are any errors they'll scroll across the micro:bit's display. > 4) Click on the REPL button to get access to the interactive prompt for > the version of Python running on the micro:bit. > > You don't need to install Python 3.6 onto your Macbook - you should be > using the version of Python *on* the actual device itself. For this to > work you flash the device with the MicroPython runtime as I described in > step 3 above. Following that, you get access to the Python prompt by > clicking the REPL button. > > Does this make sense? > > Best of luck, > > N. > > On 02/08/16 16:35, Robert Humphrey wrote: > > Thanks for the response. I find it hard work trying to install Micro > Python, and thanks for bearing with me. The attached screen shot is > typical. It appears that there in?t a library to import. > > I followed your link via Pep-8, installed Python 3.6, installed Active > tcl 8.6. Ran Python 3.6 and get errors. I re-tried MU and again it > appears that there are no libraries to import. Is there a simple way to > get all this working as I can get Python to work interactively from the > net at W3. microbit.Pythonanywhere.com > > > >, but no luck locally. > Bob > > > > ote: > > On 02/08/16 13:37, Robert Humphrey wrote: > > I have installed MU from GitHub latest MU-3 30/07/2016 but it > errors out on every statement. What haven?t I loaded? > > Op Sys OSX El Capitaine > > Example code:- > > > > _______________________________________________ > Microbit mailing list > Microbit at python.org > > < > mailto:Microbit at python.org > > https://mail.python.org/mailman/listinfo/microbit > > > Hi Robert, > > Thanks for the feedback. > > In future, please just attach the PNG image file rather than sticking > the screen shot in a PDF - it's just simpler and I don't have to twist > my neck to see what you're up to (I sprained it trampolining over the > weekend). :-) > > So, I'm trying to work out what exactly you mean. Do you mean that Mu > has an error in it and crashes OR that Mu is reporting errors for every > line in your code? Looking at your screenshot, I believe you're > reporting the latter. > > If so, these are not errors! > > Rather, they are code quality feedback annotations. Your code probably > will still work, but it has stylistic problems. For example, I can see > from lines 5-8 you use a comment "#" without following it with a space > (to aid readability). If you click on the red arrow next to each line a > little post-it note will appear to explain why the line has been > flagged. > > Such code quality checking is advisory! Unless you get syntax errors > your code will run (although it may still contain bugs because it > doesn't work as you expect). > > If you're interested in the conventions Mu uses for checking the quality > of your code you should read up on PEP-8 - the style guide for Python > programming (it's like the style guide newspapers use to guide their > journalists in writing in an idiomatic and "house" style). > > https://www.python.org/dev/peps/pep-0008/ > > PEP-8 was written by Python's creator Guido van Rossum and a couple of > other collaborators (including Nick Coghlan, who may be subscribed to > this list). It's their vision of well written, idiomatic Python. Many > Python programmers, myself included, use it for guidance when writing > code. > > You are free to ignore it though. As PEP-8 itself says, "a foolish > consistency is the hobgoblin of little minds". > > :-) > > Hope this helps, and more than happy to answer any questions you may > have. > > N. > > _______________________________________________ > 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From antonywatts at me.com Fri Aug 5 07:30:26 2016 From: antonywatts at me.com (Antony Watts) Date: Fri, 05 Aug 2016 12:30:26 +0100 Subject: [Microbit-Python] MAC help Message-ID: <5572B0E0-0525-4B4A-88E7-E45EA9D767A5@me.com> Hi I don?t suppose there is anyway to stop my Mac flashing up these three annoying windows? New Network Interface - when connecting the microbit Disk not Ejected Properly - every time I flash a new program Flashing ??? on the microbit - every time I flash a program Regards Antony Watts From hot.toast at yahoo.co.uk Sun Aug 7 07:38:41 2016 From: hot.toast at yahoo.co.uk (hot.toast) Date: Sun, 7 Aug 2016 12:38:41 +0100 Subject: [Microbit-Python] Differences between BBC: microbit and pyboard Message-ID: I'm getting confused over the differences between running micropython on the pyboard and on the BBC:microbit. I have been playing with the pyboard for a number of months and have a reasonable understanding of how to use micropython on that platform. But it is my current belief that the BBC:microbit does not ship with a python interpreter and that I have to roll my own using yotta and copy the resultant hex file to the microbit before i can get a REPL prompt . 1. Is that belief correct? (I don't seem to have to load the firmware using DFU like on the pyboard) 2. I have successfully complied basic micropython to a .hex file using the web interface and got this running on my microbit, so I know the board is working correctly. 3. I have tried to follow the instructions on https://github.com/bbcmicrobit/micropython/README.md. using a Linux Mint 17.3 system but when I get to "yt build" (or make all) I get the following error [102/291] Building CXX object ym/ble-nrf51822/source/CMakeFiles/ble-nrf51822.dir/adsafdas/micropython-master/yotta_modules/ble-nrf51822/source/nRF5xn.cpp.o ninja: build stopped: subcommand failed. error: command ['ninja'] failed Any ideas where to go next? From carlos.p.a.87 at gmail.com Sun Aug 7 08:06:08 2016 From: carlos.p.a.87 at gmail.com (Carlos P.A.) Date: Sun, 7 Aug 2016 13:06:08 +0100 Subject: [Microbit-Python] Differences between BBC: microbit and pyboard In-Reply-To: References: Message-ID: The hex file you've downloaded from the website packs micropython together with your script file. Admittedly it's not the latest version, as it is missing things like the radio and voice modules, but it has REPL access. If you want to use the latest version of micropython you don't have to compile it from source, the flash utility uflash and the code editor Mu contain it already : https://github.com/ntoll/uflash https://github.com/ntoll/mu I'm on mobile, so I cannot easily check online, but I was under the impression that the README contains all required packages, there is also an issue in the github repository that had more detailed steps for debian (which should be transferable), and you could also check the "compiler install scrip" I put together a little while ago for https://github.com/carlosperate/microbit-dev-env . Other than that the error is not very explicit, is that all it printed about it? Could you copy the entire output in a file and post it? On 7 Aug 2016 12:40, "hot.toast via Microbit" wrote: > > I'm getting confused over the differences between running micropython on the pyboard and on the BBC:microbit. > > I have been playing with the pyboard for a number of months and have a reasonable understanding of how to use micropython on that platform. But it is my current belief that the BBC:microbit does not ship with a python interpreter and that I have to roll my own using yotta and copy the resultant hex file to the microbit before i can get a REPL prompt . > > 1. Is that belief correct? (I don't seem to have to load the firmware using DFU like on the pyboard) > > 2. I have successfully complied basic micropython to a .hex file using the web interface and got this running on my microbit, so I know the board is working correctly. > > 3. I have tried to follow the instructions on https://github.com/bbcmicrobit/micropython/README.md. using a Linux Mint 17.3 system but when I get to "yt build" (or make all) I get the following error > > [102/291] Building CXX object ym/ble-nrf51822/source/CMakeFiles/ble-nrf51822.dir/adsafdas/micropython-master/yotta_modules/ble-nrf51822/source/nRF5xn.cpp.o > ninja: build stopped: subcommand failed. > error: command ['ninja'] failed > > Any ideas where to go next? > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben at benmr.com Sun Aug 7 08:41:37 2016 From: ben at benmr.com (Ben Mustill-Rose) Date: Sun, 7 Aug 2016 13:41:37 +0100 Subject: [Microbit-Python] Differences between BBC: microbit and pyboard In-Reply-To: References: Message-ID: Hi, Run yt up and then try yt build again. I have no idea why you have to do this but I've received the same error a few times & doing this always solved it. Having said this, as Carlos says, the easier (but less interesting) way of getting a generic MicroPython hex file is to just extract the runtime from uFlash. From memory the relevant line is 314. Cheers, Ben. On 8/7/16, Carlos P.A. wrote: > The hex file you've downloaded from the website packs micropython together > with your script file. Admittedly it's not the latest version, as it is > missing things like the radio and voice modules, but it has REPL access. > > If you want to use the latest version of micropython you don't have to > compile it from source, the flash utility uflash and the code editor Mu > contain it already : > https://github.com/ntoll/uflash > https://github.com/ntoll/mu > > I'm on mobile, so I cannot easily check online, but I was under the > impression that the README contains all required packages, there is also an > issue in the github repository that had more detailed steps for debian > (which should be transferable), and you could also check the "compiler > install scrip" I put together a little while ago for > https://github.com/carlosperate/microbit-dev-env . > > Other than that the error is not very explicit, is that all it printed > about it? Could you copy the entire output in a file and post it? > > On 7 Aug 2016 12:40, "hot.toast via Microbit" wrote: >> >> I'm getting confused over the differences between running micropython on > the pyboard and on the BBC:microbit. >> >> I have been playing with the pyboard for a number of months and have a > reasonable understanding of how to use micropython on that platform. But it > is my current belief that the BBC:microbit does not ship with a python > interpreter and that I have to roll my own using yotta and copy the > resultant hex file to the microbit before i can get a REPL prompt . >> >> 1. Is that belief correct? (I don't seem to have to load the firmware > using DFU like on the pyboard) >> >> 2. I have successfully complied basic micropython to a .hex file using > the web interface and got this running on my microbit, so I know the board > is working correctly. >> >> 3. I have tried to follow the instructions on > https://github.com/bbcmicrobit/micropython/README.md. using a Linux Mint > 17.3 system but when I get to "yt build" (or make all) I get the following > error >> >> [102/291] Building CXX object > ym/ble-nrf51822/source/CMakeFiles/ble-nrf51822.dir/adsafdas/micropython-master/yotta_modules/ble-nrf51822/source/nRF5xn.cpp.o >> ninja: build stopped: subcommand failed. >> error: command ['ninja'] failed >> >> Any ideas where to go next? >> _______________________________________________ >> Microbit mailing list >> Microbit at python.org >> https://mail.python.org/mailman/listinfo/microbit > From carlos.p.a.87 at gmail.com Sun Aug 7 08:58:24 2016 From: carlos.p.a.87 at gmail.com (Carlos P.A.) Date: Sun, 07 Aug 2016 12:58:24 +0000 Subject: [Microbit-Python] Differences between BBC: microbit and pyboard In-Reply-To: References: Message-ID: You can also run uflash without giving it any python file and it will copy the runtime on its own. On Sun, 7 Aug 2016, 13:42 Ben Mustill-Rose, wrote: > Hi, > > Run > yt up > and then try > yt build > again. I have no idea why you have to do this but I've received the > same error a few times & doing this always solved it. > > Having said this, as Carlos says, the easier (but less interesting) > way of getting a generic MicroPython hex file is to just extract the > runtime from uFlash. From memory the relevant line is 314. > > Cheers, > Ben. > > On 8/7/16, Carlos P.A. wrote: > > The hex file you've downloaded from the website packs micropython > together > > with your script file. Admittedly it's not the latest version, as it is > > missing things like the radio and voice modules, but it has REPL access. > > > > If you want to use the latest version of micropython you don't have to > > compile it from source, the flash utility uflash and the code editor Mu > > contain it already : > > https://github.com/ntoll/uflash > > https://github.com/ntoll/mu > > > > I'm on mobile, so I cannot easily check online, but I was under the > > impression that the README contains all required packages, there is also > an > > issue in the github repository that had more detailed steps for debian > > (which should be transferable), and you could also check the "compiler > > install scrip" I put together a little while ago for > > https://github.com/carlosperate/microbit-dev-env . > > > > Other than that the error is not very explicit, is that all it printed > > about it? Could you copy the entire output in a file and post it? > > > > On 7 Aug 2016 12:40, "hot.toast via Microbit" > wrote: > >> > >> I'm getting confused over the differences between running micropython on > > the pyboard and on the BBC:microbit. > >> > >> I have been playing with the pyboard for a number of months and have a > > reasonable understanding of how to use micropython on that platform. But > it > > is my current belief that the BBC:microbit does not ship with a python > > interpreter and that I have to roll my own using yotta and copy the > > resultant hex file to the microbit before i can get a REPL prompt . > >> > >> 1. Is that belief correct? (I don't seem to have to load the firmware > > using DFU like on the pyboard) > >> > >> 2. I have successfully complied basic micropython to a .hex file using > > the web interface and got this running on my microbit, so I know the > board > > is working correctly. > >> > >> 3. I have tried to follow the instructions on > > https://github.com/bbcmicrobit/micropython/README.md. using a Linux Mint > > 17.3 system but when I get to "yt build" (or make all) I get the > following > > error > >> > >> [102/291] Building CXX object > > > ym/ble-nrf51822/source/CMakeFiles/ble-nrf51822.dir/adsafdas/micropython-master/yotta_modules/ble-nrf51822/source/nRF5xn.cpp.o > >> ninja: build stopped: subcommand failed. > >> error: command ['ninja'] failed > >> > >> Any ideas where to go next? > >> _______________________________________________ > >> 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 hot.toast at yahoo.co.uk Sun Aug 7 09:31:37 2016 From: hot.toast at yahoo.co.uk (hot.toast) Date: Sun, 7 Aug 2016 14:31:37 +0100 Subject: [Microbit-Python] Differences between BBC: microbit and pyboard In-Reply-To: References: Message-ID: Below is the full output from yt build. I tried yt up followed by yt build (as Ben suggested) but this didn't prevent the error. sudo yt build info: generate for target: bbc-microbit-classic-gcc-nosd 0.2.3 at /home/xxx/Projects/Python/MicroBit/micropython-master/yotta_targets/bbc-microbit-classic-gcc-nosd GCC version is: 4.9.3 -- The ASM compiler identification is GNU -- Found assembler: /usr/bin/arm-none-eabi-gcc suppressing warnings from ble-nrf51822 suppressing warnings from nrf51-sdk fatal: Not a git repository (or any parent up to mount point /home) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). fatal: Not a git repository (or any parent up to mount point /home) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). suppressing ALL warnings from mbed-classic, ble, ble-nrf51822 & nrf51-sdk -- Configuring done -- Generating done -- Build files have been written to: /home/xxx/Projects/Python/MicroBit/micropython-master/build/bbc-microbit-classic-gcc-nosd [102/292] Building CXX object ym/ble-nrf51822/source/CMakeFiles/ble-nrf51...roBit/micropython-master/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp.oThis FAILED: /usr/bin/arm-none-eabi-g++ -DYOTTA_MODULE_NAME=ble-nrf51822 -fno-exceptions -fno-unwind-tables -ffunction-sections -fdata-sections -Wall -Wextra -fno-rtti -fno-threadsafe-statics -mcpu=cortex-m0 -mthumb -D__thumb2__ -Os -g -gdwarf-3 -DNDEBUG -Igenerated/include -I/home/xxx/Projects/Python/MicroBit/micropython-master -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/mbed-classic -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/microbit-dal -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/ble -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/ble-nrf51822 -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/nrf51-sdk -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/ble-nrf51822/source/btle -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/ble-nrf51822/source/btle/custom -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/ble-nrf51822/source/common -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/ble_radio_notification -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/ble_services/ble_dfu -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/common -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/device_manager -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/device_manager/config -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/peer_manager -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/nrf51-sdk/source/nordic_sdk/components/device -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/ble_flash -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/delay -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/hal -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/pstorage -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/pstorage/config -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/bootloader_dfu -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/bootloader_dfu/hci_transport -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/crc16 -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/hci -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/scheduler -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/timer -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/util -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/fds -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/fstorage -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/experimental_section_vars -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/nrf51-sdk/source/nordic_sdk/components/softdevice/common/softdevice_handler -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/nrf51-sdk/source/nordic_sdk/components/softdevice/s130/headers -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/nrf51-sdk/source/nordic_sdk/components/toolchain -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/mbed-classic/api -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/mbed-classic/hal -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/mbed-classic/targets/hal -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/mbed-classic/targets/cmsis -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/mbed-classic/targets -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/mbed-classic/targets/cmsis/TARGET_NORDIC -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/mbed-classic/targets/cmsis/TARGET_NORDIC/TARGET_MCU_NRF51822 -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/mbed-classic/targets/cmsis/TARGET_NORDIC/TARGET_MCU_NRF51822/TOOLCHAIN_GCC_ARM -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/mbed-classic/targets/cmsis/TARGET_NORDIC/TARGET_MCU_NRF51822/TOOLCHAIN_GCC_ARM/TARGET_MCU_NRF51_16K_S110 -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822 -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/TARGET_NRF51_MICROBIT -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components/libraries -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components/libraries/scheduler -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components/libraries/crc16 -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components/libraries/util -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/s110_nrf51822_8_0_0 -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/s130_nrf51822_1_0_0 -I/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/ble-nrf51822/source -DTOOLCHAIN_GCC -DTOOLCHAIN_GCC_ARM -DMBED_OPERATORS -DNRF51 -DTARGET_NORDIC -DTARGET_M0 -D__MBED__=1 -DMCU_NORDIC_16K -DTARGET_NRF51_MICROBIT -DTARGET_MCU_NORDIC_16K -DTARGET_MCU_NRF51_16K_S110 -DTARGET_NRF_LFCLK_RC -DTARGET_MCU_NORDIC_16K -D__CORTEX_M0 -DARM_MATH_CM0 -DNO_BLE -include "/home/xxx/Projects/Python/MicroBit/micropython-master/build/bbc-microbit-classic-gcc-nosd/yotta_config.h" -Wno-sign-compare -Wno-unused-variable -Wno-unused-parameter -Wno-unused-function -Wno-missing-field-initializers -w -MMD -MT ym/ble-nrf51822/source/CMakeFiles/ble-nrf51822.dir/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp.o -MF "ym/ble-nrf51822/source/CMakeFiles/ble-nrf51822.dir/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp.o.d" -o ym/ble-nrf51822/source/CMakeFiles/ble-nrf51822.dir/home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp.o -c /home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp /home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp: In member function 'virtual ble_error_t nRF5xGap::setWhitelist(const Gap::Whitelist_t&)': /home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp:689:59: error: 'BLEProtocol::AddressType_t' is not a class or namespace if (whitelistIn.addresses[i].type == BLEProtocol::AddressType_t::RANDOM_PRIVATE_NON_RESOLVABLE) { ^ /home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp: In member function 'ble_error_t nRF5xGap::generateStackWhitelist(ble_gap_whitelist_t&)': /home/xxx/Projects/Python/MicroBit/micropython-master/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp:906:61: error: 'BLEProtocol::AddressType_t' is not a class or namespace if (whitelistAddresses[i].addr_type == BLEProtocol::AddressType_t::RANDOM_PRIVATE_RESOLVABLE) { ^ [102/292] Building CXX object ym/ble-nrf51822/source/CMakeFiles/ble-nrf51...oBit/micropython-master/yotta_modules/ble-nrf51822/source/btle/btle.cpp.o ninja: build stopped: subcommand failed. error: command ['ninja'] failed On 07/08/16 13:06, Carlos P.A. wrote: > The hex file you've downloaded from the website packs micropython together > with your script file. Admittedly it's not the latest version, as it is > missing things like the radio and voice modules, but it has REPL access. > > If you want to use the latest version of micropython you don't have to > compile it from source, the flash utility uflash and the code editor Mu > contain it already : > https://github.com/ntoll/uflash > https://github.com/ntoll/mu > > I'm on mobile, so I cannot easily check online, but I was under the > impression that the README contains all required packages, there is also an > issue in the github repository that had more detailed steps for debian > (which should be transferable), and you could also check the "compiler > install scrip" I put together a little while ago for > https://github.com/carlosperate/microbit-dev-env . > > Other than that the error is not very explicit, is that all it printed > about it? Could you copy the entire output in a file and post it? > > On 7 Aug 2016 12:40, "hot.toast via Microbit" wrote: >> I'm getting confused over the differences between running micropython on > the pyboard and on the BBC:microbit. >> I have been playing with the pyboard for a number of months and have a > reasonable understanding of how to use micropython on that platform. But it > is my current belief that the BBC:microbit does not ship with a python > interpreter and that I have to roll my own using yotta and copy the > resultant hex file to the microbit before i can get a REPL prompt . >> 1. Is that belief correct? (I don't seem to have to load the firmware > using DFU like on the pyboard) >> 2. I have successfully complied basic micropython to a .hex file using > the web interface and got this running on my microbit, so I know the board > is working correctly. >> 3. I have tried to follow the instructions on > https://github.com/bbcmicrobit/micropython/README.md. using a Linux Mint > 17.3 system but when I get to "yt build" (or make all) I get the following > error >> [102/291] Building CXX object > ym/ble-nrf51822/source/CMakeFiles/ble-nrf51822.dir/adsafdas/micropython-master/yotta_modules/ble-nrf51822/source/nRF5xn.cpp.o >> ninja: build stopped: subcommand failed. >> error: command ['ninja'] failed >> >> Any ideas where to go next? >> _______________________________________________ >> 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 madtom1999 at googlemail.com Mon Aug 8 05:02:03 2016 From: madtom1999 at googlemail.com (Tom) Date: Mon, 8 Aug 2016 10:02:03 +0100 Subject: [Microbit-Python] Build micropython problem Message-ID: <85efc26e-3186-8ae8-1bf6-647c234fceaa@googlemail.com> I'm on Xubuntu 16.04 and have followed the README.md in the micropython git latest and on "yt build" I get the following ------------------------------------ info: generate for target: bbc-microbit-classic-gcc-nosd 0.2.3 at /home/tom/Programming/microbit/micropython/yotta_targets/bbc-microbit-classic-gcc-nosd GCC version is: 4.9.3 suppressing warnings from ble-nrf51822 suppressing warnings from nrf51-sdk suppressing ALL warnings from mbed-classic, ble, ble-nrf51822 & nrf51-sdk -- Configuring done -- Generating done -- Build files have been written to: /home/tom/Programming/microbit/micropython/build/bbc-microbit-classic-gcc-nosd [101/291] Building CXX object ym/ble-n...les/ble-nrf51822/source/nRF5xGap.cpp.o FAILED: /usr/bin/arm-none-eabi-g++ -DYOTTA_MODULE_NAME=ble-nrf51822 -Igenerated/include -I/home/tom/Programming/microbit/micropython -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic -I/home/tom/Programming/microbit/micropython/yotta_modules/microbit-dal -I/home/tom/Programming/microbit/micropython/yotta_modules/ble -I/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822 -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk -I/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/btle -I/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/btle/custom -I/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/common -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/ble_radio_notification -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/ble_services/ble_dfu -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/common -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/device_manager -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/device_manager/config -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/peer_manager -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/device -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/ble_flash -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/delay -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/hal -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/pstorage -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/pstorage/config -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/bootloader_dfu -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/bootloader_dfu/hci_transport -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/crc16 -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/hci -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/scheduler -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/timer -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/util -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/fds -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/fstorage -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/experimental_section_vars -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/softdevice/common/softdevice_handler -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/softdevice/s130/headers -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/toolchain -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/api -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/hal -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/cmsis -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/cmsis/TARGET_NORDIC -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/cmsis/TARGET_NORDIC/TARGET_MCU_NRF51822 -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/cmsis/TARGET_NORDIC/TARGET_MCU_NRF51822/TOOLCHAIN_GCC_ARM -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/cmsis/TARGET_NORDIC/TARGET_MCU_NRF51822/TOOLCHAIN_GCC_ARM/TARGET_MCU_NRF51_16K_S110 -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822 -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/TARGET_NRF51_MICROBIT -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/s110_nrf51822_8_0_0 -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components/libraries -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components/libraries/util -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components/libraries/scheduler -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components/libraries/crc16 -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/s130_nrf51822_1_0_0 -I/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source -fno-exceptions -fno-unwind-tables -ffunction-sections -fdata-sections -Wall -Wextra -fno-rtti -fno-threadsafe-statics -mcpu=cortex-m0 -mthumb -D__thumb2__ -Os -g -gdwarf-3 -DNDEBUG -DTOOLCHAIN_GCC -DTOOLCHAIN_GCC_ARM -DMBED_OPERATORS -DNRF51 -DTARGET_NORDIC -DTARGET_M0 -D__MBED__=1 -DMCU_NORDIC_16K -DTARGET_NRF51_MICROBIT -DTARGET_MCU_NORDIC_16K -DTARGET_MCU_NRF51_16K_S110 -DTARGET_NRF_LFCLK_RC -DTARGET_MCU_NORDIC_16K -D__CORTEX_M0 -DARM_MATH_CM0 -DNO_BLE -include "/home/tom/Programming/microbit/micropython/build/bbc-microbit-classic-gcc-nosd/yotta_config.h" -Wno-sign-compare -Wno-unused-variable -Wno-unused-parameter -Wno-unused-function -Wno-missing-field-initializers -w -MMD -MT ym/ble-nrf51822/source/CMakeFiles/ble-nrf51822.dir/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp.o -MF ym/ble-nrf51822/source/CMakeFiles/ble-nrf51822.dir/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp.o.d -o ym/ble-nrf51822/source/CMakeFiles/ble-nrf51822.dir/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp.o -c /home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp /home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp: In member function 'virtual ble_error_t nRF5xGap::setWhitelist(const Gap::Whitelist_t&)': /home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp:689:59: error: 'BLEProtocol::AddressType_t' is not a class or namespace if (whitelistIn.addresses[i].type == BLEProtocol::AddressType_t::RANDOM_PRIVATE_NON_RESOLVABLE) { ^ /home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp: In member function 'ble_error_t nRF5xGap::generateStackWhitelist(ble_gap_whitelist_t&)': /home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp:906:61: error: 'BLEProtocol::AddressType_t' is not a class or namespace if (whitelistAddresses[i].addr_type == BLEProtocol::AddressType_t::RANDOM_PRIVATE_RESOLVABLE) { ^ [101/291] Building CXX object ym/ble-n...dules/ble-nrf51822/source/nRF5xn.cpp.o ninja: build stopped: subcommand failed. error: command ['ninja'] failed ----------------------------------------------------------- Where have I gone wrong? Tom From damien.p.george at gmail.com Mon Aug 8 09:09:21 2016 From: damien.p.george at gmail.com (Damien George) Date: Mon, 8 Aug 2016 23:09:21 +1000 Subject: [Microbit-Python] Build micropython problem In-Reply-To: <85efc26e-3186-8ae8-1bf6-647c234fceaa@googlemail.com> References: <85efc26e-3186-8ae8-1bf6-647c234fceaa@googlemail.com> Message-ID: I don't know what is wrong here. I tried checking out a clean copy of the project and building from scratch, and it went fine (on Arch Linux with arm-none-eabi-gcc v 6.1.1). On 8 August 2016 at 19:02, Tom via Microbit wrote: > I'm on Xubuntu 16.04 and have followed the README.md in the micropython git > latest and on "yt build" I get the following > ------------------------------------ > info: generate for target: bbc-microbit-classic-gcc-nosd 0.2.3 at > /home/tom/Programming/microbit/micropython/yotta_targets/bbc-microbit-classic-gcc-nosd > GCC version is: 4.9.3 > suppressing warnings from ble-nrf51822 > suppressing warnings from nrf51-sdk > suppressing ALL warnings from mbed-classic, ble, ble-nrf51822 & nrf51-sdk > -- Configuring done > -- Generating done > -- Build files have been written to: > /home/tom/Programming/microbit/micropython/build/bbc-microbit-classic-gcc-nosd > [101/291] Building CXX object > ym/ble-n...les/ble-nrf51822/source/nRF5xGap.cpp.o > FAILED: /usr/bin/arm-none-eabi-g++ -DYOTTA_MODULE_NAME=ble-nrf51822 > -Igenerated/include -I/home/tom/Programming/microbit/micropython > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic > -I/home/tom/Programming/microbit/micropython/yotta_modules/microbit-dal > -I/home/tom/Programming/microbit/micropython/yotta_modules/ble > -I/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822 > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk > -I/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/btle > -I/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/btle/custom > -I/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/common > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/ble_radio_notification > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/ble_services/ble_dfu > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/common > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/device_manager > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/device_manager/config > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/peer_manager > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/device > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/ble_flash > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/delay > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/hal > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/pstorage > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/pstorage/config > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/bootloader_dfu > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/bootloader_dfu/hci_transport > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/crc16 > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/hci > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/scheduler > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/timer > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/util > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/fds > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/fstorage > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/experimental_section_vars > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/softdevice/common/softdevice_handler > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/softdevice/s130/headers > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/toolchain > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/api > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/hal > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/cmsis > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/cmsis/TARGET_NORDIC > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/cmsis/TARGET_NORDIC/TARGET_MCU_NRF51822 > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/cmsis/TARGET_NORDIC/TARGET_MCU_NRF51822/TOOLCHAIN_GCC_ARM > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/cmsis/TARGET_NORDIC/TARGET_MCU_NRF51822/TOOLCHAIN_GCC_ARM/TARGET_MCU_NRF51_16K_S110 > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822 > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/TARGET_NRF51_MICROBIT > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/s110_nrf51822_8_0_0 > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components/libraries > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components/libraries/util > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components/libraries/scheduler > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components/libraries/crc16 > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/s130_nrf51822_1_0_0 > -I/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source > -fno-exceptions -fno-unwind-tables -ffunction-sections -fdata-sections -Wall > -Wextra -fno-rtti -fno-threadsafe-statics -mcpu=cortex-m0 -mthumb > -D__thumb2__ -Os -g -gdwarf-3 -DNDEBUG -DTOOLCHAIN_GCC -DTOOLCHAIN_GCC_ARM > -DMBED_OPERATORS -DNRF51 -DTARGET_NORDIC -DTARGET_M0 -D__MBED__=1 > -DMCU_NORDIC_16K -DTARGET_NRF51_MICROBIT -DTARGET_MCU_NORDIC_16K > -DTARGET_MCU_NRF51_16K_S110 -DTARGET_NRF_LFCLK_RC -DTARGET_MCU_NORDIC_16K > -D__CORTEX_M0 -DARM_MATH_CM0 -DNO_BLE -include > "/home/tom/Programming/microbit/micropython/build/bbc-microbit-classic-gcc-nosd/yotta_config.h" > -Wno-sign-compare -Wno-unused-variable -Wno-unused-parameter > -Wno-unused-function -Wno-missing-field-initializers -w -MMD -MT > ym/ble-nrf51822/source/CMakeFiles/ble-nrf51822.dir/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp.o > -MF > ym/ble-nrf51822/source/CMakeFiles/ble-nrf51822.dir/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp.o.d > -o > ym/ble-nrf51822/source/CMakeFiles/ble-nrf51822.dir/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp.o > -c > /home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp > /home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp: > In member function 'virtual ble_error_t nRF5xGap::setWhitelist(const > Gap::Whitelist_t&)': > /home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp:689:59: > error: 'BLEProtocol::AddressType_t' is not a class or namespace > if (whitelistIn.addresses[i].type == > BLEProtocol::AddressType_t::RANDOM_PRIVATE_NON_RESOLVABLE) { > ^ > /home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp: > In member function 'ble_error_t > nRF5xGap::generateStackWhitelist(ble_gap_whitelist_t&)': > /home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp:906:61: > error: 'BLEProtocol::AddressType_t' is not a class or namespace > if (whitelistAddresses[i].addr_type == > BLEProtocol::AddressType_t::RANDOM_PRIVATE_RESOLVABLE) { > ^ > [101/291] Building CXX object > ym/ble-n...dules/ble-nrf51822/source/nRF5xn.cpp.o > ninja: build stopped: subcommand failed. > error: command ['ninja'] failed > ----------------------------------------------------------- > Where have I gone wrong? > Tom > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit From joe.t.glancy at gmail.com Mon Aug 8 10:52:05 2016 From: joe.t.glancy at gmail.com (Joe Glancy) Date: Mon, 08 Aug 2016 14:52:05 +0000 Subject: [Microbit-Python] Build micropython problem In-Reply-To: References: <85efc26e-3186-8ae8-1bf6-647c234fceaa@googlemail.com> Message-ID: Always try rebuilding from scratch. I've had two makefiles (for completely different things) recently which resulted in an error, but where a `make clean` and `make` seemed to fix the issue. At any rate, strange it should be an issue with Nordic's BLE driver. On Mon, 8 Aug 2016, 14:09 Damien George, wrote: > I don't know what is wrong here. I tried checking out a clean copy of > the project and building from scratch, and it went fine (on Arch Linux > with arm-none-eabi-gcc v 6.1.1). > > > On 8 August 2016 at 19:02, Tom via Microbit wrote: > > I'm on Xubuntu 16.04 and have followed the README.md in the micropython > git > > latest and on "yt build" I get the following > > ------------------------------------ > > info: generate for target: bbc-microbit-classic-gcc-nosd 0.2.3 at > > > /home/tom/Programming/microbit/micropython/yotta_targets/bbc-microbit-classic-gcc-nosd > > GCC version is: 4.9.3 > > suppressing warnings from ble-nrf51822 > > suppressing warnings from nrf51-sdk > > suppressing ALL warnings from mbed-classic, ble, ble-nrf51822 & nrf51-sdk > > -- Configuring done > > -- Generating done > > -- Build files have been written to: > > > /home/tom/Programming/microbit/micropython/build/bbc-microbit-classic-gcc-nosd > > [101/291] Building CXX object > > ym/ble-n...les/ble-nrf51822/source/nRF5xGap.cpp.o > > FAILED: /usr/bin/arm-none-eabi-g++ -DYOTTA_MODULE_NAME=ble-nrf51822 > > -Igenerated/include -I/home/tom/Programming/microbit/micropython > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic > > -I/home/tom/Programming/microbit/micropython/yotta_modules/microbit-dal > > -I/home/tom/Programming/microbit/micropython/yotta_modules/ble > > -I/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822 > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/btle > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/btle/custom > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/common > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/ble_radio_notification > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/ble_services/ble_dfu > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/common > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/device_manager > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/device_manager/config > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/peer_manager > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/device > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/ble_flash > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/delay > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/hal > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/pstorage > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/pstorage/config > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/bootloader_dfu > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/bootloader_dfu/hci_transport > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/crc16 > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/hci > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/scheduler > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/timer > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/util > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/fds > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/fstorage > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/experimental_section_vars > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/softdevice/common/softdevice_handler > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/softdevice/s130/headers > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/toolchain > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/api > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/hal > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/cmsis > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/cmsis/TARGET_NORDIC > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/cmsis/TARGET_NORDIC/TARGET_MCU_NRF51822 > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/cmsis/TARGET_NORDIC/TARGET_MCU_NRF51822/TOOLCHAIN_GCC_ARM > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/cmsis/TARGET_NORDIC/TARGET_MCU_NRF51822/TOOLCHAIN_GCC_ARM/TARGET_MCU_NRF51_16K_S110 > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822 > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/TARGET_NRF51_MICROBIT > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/s110_nrf51822_8_0_0 > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components/libraries > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components/libraries/util > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components/libraries/scheduler > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components/libraries/crc16 > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/s130_nrf51822_1_0_0 > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source > > -fno-exceptions -fno-unwind-tables -ffunction-sections -fdata-sections > -Wall > > -Wextra -fno-rtti -fno-threadsafe-statics -mcpu=cortex-m0 -mthumb > > -D__thumb2__ -Os -g -gdwarf-3 -DNDEBUG -DTOOLCHAIN_GCC > -DTOOLCHAIN_GCC_ARM > > -DMBED_OPERATORS -DNRF51 -DTARGET_NORDIC -DTARGET_M0 -D__MBED__=1 > > -DMCU_NORDIC_16K -DTARGET_NRF51_MICROBIT -DTARGET_MCU_NORDIC_16K > > -DTARGET_MCU_NRF51_16K_S110 -DTARGET_NRF_LFCLK_RC > -DTARGET_MCU_NORDIC_16K > > -D__CORTEX_M0 -DARM_MATH_CM0 -DNO_BLE -include > > > "/home/tom/Programming/microbit/micropython/build/bbc-microbit-classic-gcc-nosd/yotta_config.h" > > -Wno-sign-compare -Wno-unused-variable -Wno-unused-parameter > > -Wno-unused-function -Wno-missing-field-initializers -w -MMD -MT > > > ym/ble-nrf51822/source/CMakeFiles/ble-nrf51822.dir/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp.o > > -MF > > > ym/ble-nrf51822/source/CMakeFiles/ble-nrf51822.dir/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp.o.d > > -o > > > ym/ble-nrf51822/source/CMakeFiles/ble-nrf51822.dir/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp.o > > -c > > > /home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp > > > /home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp: > > In member function 'virtual ble_error_t nRF5xGap::setWhitelist(const > > Gap::Whitelist_t&)': > > > /home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp:689:59: > > error: 'BLEProtocol::AddressType_t' is not a class or namespace > > if (whitelistIn.addresses[i].type == > > BLEProtocol::AddressType_t::RANDOM_PRIVATE_NON_RESOLVABLE) { > > ^ > > > /home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp: > > In member function 'ble_error_t > > nRF5xGap::generateStackWhitelist(ble_gap_whitelist_t&)': > > > /home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp:906:61: > > error: 'BLEProtocol::AddressType_t' is not a class or namespace > > if (whitelistAddresses[i].addr_type == > > BLEProtocol::AddressType_t::RANDOM_PRIVATE_RESOLVABLE) { > > ^ > > [101/291] Building CXX object > > ym/ble-n...dules/ble-nrf51822/source/nRF5xn.cpp.o > > ninja: build stopped: subcommand failed. > > error: command ['ninja'] failed > > ----------------------------------------------------------- > > Where have I gone wrong? > > Tom > > > > _______________________________________________ > > 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 madtom1999 at googlemail.com Mon Aug 8 11:11:28 2016 From: madtom1999 at googlemail.com (Tom) Date: Mon, 8 Aug 2016 16:11:28 +0100 Subject: [Microbit-Python] Build micropython problem In-Reply-To: References: <85efc26e-3186-8ae8-1bf6-647c234fceaa@googlemail.com> Message-ID: There is no "make clean" alas! Tom On 08/08/16 15:52, Joe Glancy wrote: > > Always try rebuilding from scratch. I've had two makefiles (for > completely different things) recently which resulted in an error, but > where a `make clean` and `make` seemed to fix the issue. At any rate, > strange it should be an issue with Nordic's BLE driver. > > > On Mon, 8 Aug 2016, 14:09 Damien George, > wrote: > > I don't know what is wrong here. I tried checking out a clean copy of > the project and building from scratch, and it went fine (on Arch Linux > with arm-none-eabi-gcc v 6.1.1). > > > On 8 August 2016 at 19:02, Tom via Microbit > wrote: > > I'm on Xubuntu 16.04 and have followed the README.md in the > micropython git > > latest and on "yt build" I get the following > > ------------------------------------ > > info: generate for target: bbc-microbit-classic-gcc-nosd 0.2.3 at > > > /home/tom/Programming/microbit/micropython/yotta_targets/bbc-microbit-classic-gcc-nosd > > GCC version is: 4.9.3 > > suppressing warnings from ble-nrf51822 > > suppressing warnings from nrf51-sdk > > suppressing ALL warnings from mbed-classic, ble, ble-nrf51822 & > nrf51-sdk > > -- Configuring done > > -- Generating done > > -- Build files have been written to: > > > /home/tom/Programming/microbit/micropython/build/bbc-microbit-classic-gcc-nosd > > [101/291] Building CXX object > > ym/ble-n...les/ble-nrf51822/source/nRF5xGap.cpp.o > > FAILED: /usr/bin/arm-none-eabi-g++ -DYOTTA_MODULE_NAME=ble-nrf51822 > > -Igenerated/include -I/home/tom/Programming/microbit/micropython > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/microbit-dal > > -I/home/tom/Programming/microbit/micropython/yotta_modules/ble > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822 > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/btle > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/btle/custom > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/common > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/ble_radio_notification > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/ble_services/ble_dfu > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/common > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/device_manager > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/device_manager/config > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/peer_manager > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/device > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/ble_flash > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/delay > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/hal > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/pstorage > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/pstorage/config > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/bootloader_dfu > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/bootloader_dfu/hci_transport > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/crc16 > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/hci > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/scheduler > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/timer > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/util > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/fds > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/fstorage > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/experimental_section_vars > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/softdevice/common/softdevice_handler > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/softdevice/s130/headers > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/toolchain > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/api > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/hal > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/cmsis > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/cmsis/TARGET_NORDIC > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/cmsis/TARGET_NORDIC/TARGET_MCU_NRF51822 > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/cmsis/TARGET_NORDIC/TARGET_MCU_NRF51822/TOOLCHAIN_GCC_ARM > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/cmsis/TARGET_NORDIC/TARGET_MCU_NRF51822/TOOLCHAIN_GCC_ARM/TARGET_MCU_NRF51_16K_S110 > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822 > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/TARGET_NRF51_MICROBIT > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/s110_nrf51822_8_0_0 > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components/libraries > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components/libraries/util > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components/libraries/scheduler > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components/libraries/crc16 > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/s130_nrf51822_1_0_0 > > > -I/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source > > -fno-exceptions -fno-unwind-tables -ffunction-sections > -fdata-sections -Wall > > -Wextra -fno-rtti -fno-threadsafe-statics -mcpu=cortex-m0 -mthumb > > -D__thumb2__ -Os -g -gdwarf-3 -DNDEBUG -DTOOLCHAIN_GCC > -DTOOLCHAIN_GCC_ARM > > -DMBED_OPERATORS -DNRF51 -DTARGET_NORDIC -DTARGET_M0 -D__MBED__=1 > > -DMCU_NORDIC_16K -DTARGET_NRF51_MICROBIT -DTARGET_MCU_NORDIC_16K > > -DTARGET_MCU_NRF51_16K_S110 -DTARGET_NRF_LFCLK_RC > -DTARGET_MCU_NORDIC_16K > > -D__CORTEX_M0 -DARM_MATH_CM0 -DNO_BLE -include > > > "/home/tom/Programming/microbit/micropython/build/bbc-microbit-classic-gcc-nosd/yotta_config.h" > > -Wno-sign-compare -Wno-unused-variable -Wno-unused-parameter > > -Wno-unused-function -Wno-missing-field-initializers -w -MMD -MT > > > ym/ble-nrf51822/source/CMakeFiles/ble-nrf51822.dir/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp.o > > -MF > > > ym/ble-nrf51822/source/CMakeFiles/ble-nrf51822.dir/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp.o.d > > -o > > > ym/ble-nrf51822/source/CMakeFiles/ble-nrf51822.dir/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp.o > > -c > > > /home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp > > > /home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp: > > In member function 'virtual ble_error_t nRF5xGap::setWhitelist(const > > Gap::Whitelist_t&)': > > > /home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp:689:59: > > error: 'BLEProtocol::AddressType_t' is not a class or namespace > > if (whitelistIn.addresses[i].type == > > BLEProtocol::AddressType_t::RANDOM_PRIVATE_NON_RESOLVABLE) { > > ^ > > > /home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp: > > In member function 'ble_error_t > > nRF5xGap::generateStackWhitelist(ble_gap_whitelist_t&)': > > > /home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp:906:61: > > error: 'BLEProtocol::AddressType_t' is not a class or namespace > > if (whitelistAddresses[i].addr_type == > > BLEProtocol::AddressType_t::RANDOM_PRIVATE_RESOLVABLE) { > > ^ > > [101/291] Building CXX object > > ym/ble-n...dules/ble-nrf51822/source/nRF5xn.cpp.o > > ninja: build stopped: subcommand failed. > > error: command ['ninja'] failed > > ----------------------------------------------------------- > > Where have I gone wrong? > > Tom > > > > _______________________________________________ > > 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 joe.t.glancy at gmail.com Mon Aug 8 11:55:49 2016 From: joe.t.glancy at gmail.com (Joe Glancy) Date: Mon, 08 Aug 2016 15:55:49 +0000 Subject: [Microbit-Python] Build micropython problem In-Reply-To: References: <85efc26e-3186-8ae8-1bf6-647c234fceaa@googlemail.com> Message-ID: Ah, of course there isn't. Would rm -r *.o be a safe alternative? On Mon, 8 Aug 2016 at 16:12 Tom via Microbit wrote: > > There is no "make clean" alas! > > Tom > > On 08/08/16 15:52, Joe Glancy wrote: > > Always try rebuilding from scratch. I've had two makefiles (for completely > different things) recently which resulted in an error, but where a `make > clean` and `make` seemed to fix the issue. At any rate, strange it should > be an issue with Nordic's BLE driver. > > On Mon, 8 Aug 2016, 14:09 Damien George, > wrote: > >> I don't know what is wrong here. I tried checking out a clean copy of >> the project and building from scratch, and it went fine (on Arch Linux >> with arm-none-eabi-gcc v 6.1.1). >> >> >> On 8 August 2016 at 19:02, Tom via Microbit wrote: >> > I'm on Xubuntu 16.04 and have followed the README.md in the micropython >> git >> > latest and on "yt build" I get the following >> > ------------------------------------ >> > info: generate for target: bbc-microbit-classic-gcc-nosd 0.2.3 at >> > >> /home/tom/Programming/microbit/micropython/yotta_targets/bbc-microbit-classic-gcc-nosd >> > GCC version is: 4.9.3 >> > suppressing warnings from ble-nrf51822 >> > suppressing warnings from nrf51-sdk >> > suppressing ALL warnings from mbed-classic, ble, ble-nrf51822 & >> nrf51-sdk >> > -- Configuring done >> > -- Generating done >> > -- Build files have been written to: >> > >> /home/tom/Programming/microbit/micropython/build/bbc-microbit-classic-gcc-nosd >> > [101/291] Building CXX object >> > ym/ble-n...les/ble-nrf51822/source/nRF5xGap.cpp.o >> > FAILED: /usr/bin/arm-none-eabi-g++ -DYOTTA_MODULE_NAME=ble-nrf51822 >> > -Igenerated/include -I/home/tom/Programming/microbit/micropython >> > -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic >> > -I/home/tom/Programming/microbit/micropython/yotta_modules/microbit-dal >> > -I/home/tom/Programming/microbit/micropython/yotta_modules/ble >> > -I/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822 >> > -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/btle >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/btle/custom >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/common >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/ble_radio_notification >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/ble_services/ble_dfu >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/common >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/device_manager >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/device_manager/config >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/ble/peer_manager >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/device >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/ble_flash >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/delay >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/hal >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/pstorage >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/drivers_nrf/pstorage/config >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/bootloader_dfu >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/bootloader_dfu/hci_transport >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/crc16 >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/hci >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/scheduler >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/timer >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/util >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/fds >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/fstorage >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/libraries/experimental_section_vars >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/softdevice/common/softdevice_handler >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/softdevice/s130/headers >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/nrf51-sdk/source/nordic_sdk/components/toolchain >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/api >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/hal >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/cmsis >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/cmsis/TARGET_NORDIC >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/cmsis/TARGET_NORDIC/TARGET_MCU_NRF51822 >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/cmsis/TARGET_NORDIC/TARGET_MCU_NRF51822/TOOLCHAIN_GCC_ARM >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/cmsis/TARGET_NORDIC/TARGET_MCU_NRF51822/TOOLCHAIN_GCC_ARM/TARGET_MCU_NRF51_16K_S110 >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822 >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/TARGET_NRF51_MICROBIT >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/s110_nrf51822_8_0_0 >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components/libraries >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components/libraries/util >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components/libraries/scheduler >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nordic_sdk/components/libraries/crc16 >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/mbed-classic/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/s130_nrf51822_1_0_0 >> > >> -I/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source >> > -fno-exceptions -fno-unwind-tables -ffunction-sections -fdata-sections >> -Wall >> > -Wextra -fno-rtti -fno-threadsafe-statics -mcpu=cortex-m0 -mthumb >> > -D__thumb2__ -Os -g -gdwarf-3 -DNDEBUG -DTOOLCHAIN_GCC >> -DTOOLCHAIN_GCC_ARM >> > -DMBED_OPERATORS -DNRF51 -DTARGET_NORDIC -DTARGET_M0 -D__MBED__=1 >> > -DMCU_NORDIC_16K -DTARGET_NRF51_MICROBIT -DTARGET_MCU_NORDIC_16K >> > -DTARGET_MCU_NRF51_16K_S110 -DTARGET_NRF_LFCLK_RC >> -DTARGET_MCU_NORDIC_16K >> > -D__CORTEX_M0 -DARM_MATH_CM0 -DNO_BLE -include >> > >> "/home/tom/Programming/microbit/micropython/build/bbc-microbit-classic-gcc-nosd/yotta_config.h" >> > -Wno-sign-compare -Wno-unused-variable -Wno-unused-parameter >> > -Wno-unused-function -Wno-missing-field-initializers -w -MMD -MT >> > >> ym/ble-nrf51822/source/CMakeFiles/ble-nrf51822.dir/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp.o >> > -MF >> > >> ym/ble-nrf51822/source/CMakeFiles/ble-nrf51822.dir/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp.o.d >> > -o >> > >> ym/ble-nrf51822/source/CMakeFiles/ble-nrf51822.dir/home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp.o >> > -c >> > >> /home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp >> > >> /home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp: >> > In member function 'virtual ble_error_t nRF5xGap::setWhitelist(const >> > Gap::Whitelist_t&)': >> > >> /home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp:689:59: >> > error: 'BLEProtocol::AddressType_t' is not a class or namespace >> > if (whitelistIn.addresses[i].type == >> > BLEProtocol::AddressType_t::RANDOM_PRIVATE_NON_RESOLVABLE) { >> > ^ >> > >> /home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp: >> > In member function 'ble_error_t >> > nRF5xGap::generateStackWhitelist(ble_gap_whitelist_t&)': >> > >> /home/tom/Programming/microbit/micropython/yotta_modules/ble-nrf51822/source/nRF5xGap.cpp:906:61: >> > error: 'BLEProtocol::AddressType_t' is not a class or namespace >> > if (whitelistAddresses[i].addr_type == >> > BLEProtocol::AddressType_t::RANDOM_PRIVATE_RESOLVABLE) { >> > ^ >> > [101/291] Building CXX object >> > ym/ble-n...dules/ble-nrf51822/source/nRF5xn.cpp.o >> > ninja: build stopped: subcommand failed. >> > error: command ['ninja'] failed >> > ----------------------------------------------------------- >> > Where have I gone wrong? >> > Tom >> > >> > _______________________________________________ >> > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hot.toast at yahoo.co.uk Mon Aug 8 15:44:47 2016 From: hot.toast at yahoo.co.uk (hot.toast) Date: Mon, 8 Aug 2016 20:44:47 +0100 Subject: [Microbit-Python] Build micropython problem In-Reply-To: <85efc26e-3186-8ae8-1bf6-647c234fceaa@googlemail.com> References: <85efc26e-3186-8ae8-1bf6-647c234fceaa@googlemail.com> Message-ID: I'm getting exactly the same failure with Linux Mint 17.3.. On 08/08/16 10:02, Tom via Microbit wrote: > I'm on Xubuntu 16.04 and have followed the README.md in the > micropython git latest and on "yt build" I get the following > ------------------------------------ > ....... > [101/291] Building CXX object > ym/ble-n...dules/ble-nrf51822/source/nRF5xn.cpp.o > ninja: build stopped: subcommand failed. > error: command ['ninja'] failed > ----------------------------------------------------------- > Where have I gone wrong? > Tom > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > From hot.toast at yahoo.co.uk Mon Aug 8 16:08:20 2016 From: hot.toast at yahoo.co.uk (hot.toast) Date: Mon, 8 Aug 2016 21:08:20 +0100 Subject: [Microbit-Python] Differences between BBC: microbit and pyboard In-Reply-To: References: Message-ID: On 07/08/16 13:41, Ben Mustill-Rose wrote: > Hi, > > Run > yt up > and then try > yt build > again. I have no idea why you have to do this but I've received the > same error a few times & doing this always solved it. > Tried that, it didn't work for me (on Linux Mint 17.3) From hot.toast at yahoo.co.uk Mon Aug 8 16:23:56 2016 From: hot.toast at yahoo.co.uk (hot.toast) Date: Mon, 8 Aug 2016 21:23:56 +0100 Subject: [Microbit-Python] Differences between BBC: microbit and pyboard In-Reply-To: References: Message-ID: <315d94f0-f619-3c6a-d35d-68c8ef3cefc8@yahoo.co.uk> This certainly does download something but I cannot get any kind of prompt in a terminal if I do screen /dev/ttyACM0 like I would with the pyboard On 07/08/16 13:58, Carlos P.A. wrote: > You can also run uflash without giving it any python file and it will copy > the runtime on its own. > From damien.p.george at gmail.com Mon Aug 8 19:55:58 2016 From: damien.p.george at gmail.com (Damien George) Date: Tue, 9 Aug 2016 09:55:58 +1000 Subject: [Microbit-Python] Differences between BBC: microbit and pyboard In-Reply-To: <315d94f0-f619-3c6a-d35d-68c8ef3cefc8@yahoo.co.uk> References: <315d94f0-f619-3c6a-d35d-68c8ef3cefc8@yahoo.co.uk> Message-ID: You need to specify the baudrate: screen /dev/ttyACM0 115200 On 9 August 2016 at 06:23, hot.toast via Microbit wrote: > This certainly does download something but I cannot get any kind of prompt > in a terminal if I do > > screen /dev/ttyACM0 > > like I would with the pyboard > > > > On 07/08/16 13:58, Carlos P.A. wrote: >> >> You can also run uflash without giving it any python file and it will copy >> the runtime on its own. >> > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit From hot.toast at yahoo.co.uk Tue Aug 9 01:50:19 2016 From: hot.toast at yahoo.co.uk (hot.toast) Date: Tue, 9 Aug 2016 06:50:19 +0100 Subject: [Microbit-Python] Differences between BBC: microbit and pyboard In-Reply-To: References: <315d94f0-f619-3c6a-d35d-68c8ef3cefc8@yahoo.co.uk> Message-ID: <8548447d-baf3-df6a-9b73-ae96238dcda1@yahoo.co.uk> Thanks! I can recall seeing that baud-rate option but didn't realise its significance I can now get what I was expecting! screen /dev/ttyACM0 115200 followed by Ctrl-D >>> soft reboot MicroPython v1.7-9-gbe020eb on 2016-04-18; micro:bit with nRF51822 Type "help()" for more information. >>> On 09/08/16 00:55, Damien George wrote: > You need to specify the baudrate: > > screen /dev/ttyACM0 115200 > > > On 9 August 2016 at 06:23, hot.toast via Microbit wrote: >> This certainly does download something but I cannot get any kind of prompt >> in a terminal if I do >> >> screen /dev/ttyACM0 >> >> like I would with the pyboard >> >> >> >> On 07/08/16 13:58, Carlos P.A. wrote: >>> You can also run uflash without giving it any python file and it will copy >>> the runtime on its own. >>> >> _______________________________________________ >> Microbit mailing list >> Microbit at python.org >> https://mail.python.org/mailman/listinfo/microbit From fresh.bread at yahoo.co.uk Mon Aug 8 15:41:58 2016 From: fresh.bread at yahoo.co.uk (fresh.bread) Date: Mon, 8 Aug 2016 20:41:58 +0100 Subject: [Microbit-Python] Build micropython problem In-Reply-To: <85efc26e-3186-8ae8-1bf6-647c234fceaa@googlemail.com> References: <85efc26e-3186-8ae8-1bf6-647c234fceaa@googlemail.com> Message-ID: I'm getting the same failure with Linux Mint 17.3.. On 08/08/16 10:02, Tom via Microbit wrote: > I'm on Xubuntu 16.04 and have followed the README.md in the > micropython git latest and on "yt build" I get the following > ------------------------------------ > ......... > ^ > [101/291] Building CXX object > ym/ble-n...dules/ble-nrf51822/source/nRF5xn.cpp.o > ninja: build stopped: subcommand failed. > error: command ['ninja'] failed > ----------------------------------------------------------- > Where have I gone wrong? > Tom > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > From fresh.bread at yahoo.co.uk Sat Aug 13 13:29:50 2016 From: fresh.bread at yahoo.co.uk (fresh.bread) Date: Sat, 13 Aug 2016 18:29:50 +0100 Subject: [Microbit-Python] Copying python scripts to the microbit. Message-ID: I'm figuring out how to program the microbit in python but am finding the differences between the pyboard and the microbit confusing. I was under the impression that I could use uflash to flash a python runtime system (what I understand to be a python interpreter) to the board. If I do this I can open a terminal on the board and execute lines of python,[ tick!] On the pyboard, if I copy a python script to the board as main.py and then reboot the board, it will run the script On a microbit, (that I have flashed the python runtime using uflash), if I copy the main.py and do a soft reboot (i.e ctrl-d or use the reset switch) the script does not run. More confusing, if I do a hard reset by disconnecting and reconnecting the microbit, the main.py on the microbit vanishes? Is this normal? [The differences won't stop me programming the microbit its just that I would like a similar approach for both boards if that is possible] From microbit at sheep.art.pl Sun Aug 14 14:42:30 2016 From: microbit at sheep.art.pl (Radomir Dopieralski) Date: Sun, 14 Aug 2016 20:42:30 +0200 Subject: [Microbit-Python] Copying python scripts to the microbit. In-Reply-To: References: Message-ID: <20160814204230.0425a40e@ghostwheel> The trick is that the fake USB mass storage that appears when you connect the micro:bit can only be used to flash the .hex file to it, and will not work for copying any other files onto the board -- micro:bit simply doesn't have such functionality, the USB on it is handled by a separate chip that is dedicated to re-flashing the main chip and doesn't do anything else. To actually copy a python script onto the micro:bit, you have two options: * combine it with the .hex file of the MicroPython interpreter, and flash that together. That's what uflash does when you pass it a python file, and that's also what the Mu editor does. * run some python code on the repl that creates the file internally and saves the data you need to it. That's what the Mu editor does when you use its "files" dialog to transfer files. On Sat, 13 Aug 2016 18:29:50 +0100 "fresh.bread via Microbit" wrote: > I'm figuring out how to program the microbit in python but am > finding the differences between the pyboard and the microbit > confusing. > > I was under the impression that I could use uflash to flash a python > runtime system (what I understand to be a python interpreter) to the > board. If I do this I can open a terminal on the board and execute > lines of python,[ tick!] > > On the pyboard, if I copy a python script to the board as main.py and > then reboot the board, it will run the script > > On a microbit, (that I have flashed the python runtime using uflash), > if I copy the main.py and do a soft reboot (i.e ctrl-d or use the > reset switch) the script does not run. More confusing, if I do a hard > reset by disconnecting and reconnecting the microbit, the main.py on > the microbit vanishes? Is this normal? > > [The differences won't stop me programming the microbit its just that > I would like a similar approach for both boards if that is possible] -- Radomir Dopieralski -- Radomir Dopieralski From carlosperate at gmail.com Sun Aug 14 15:00:21 2016 From: carlosperate at gmail.com (Carlos Pereira Atencio) Date: Sun, 14 Aug 2016 20:00:21 +0100 Subject: [Microbit-Python] Copying python scripts to the microbit. In-Reply-To: <20160814204230.0425a40e@ghostwheel> References: <20160814204230.0425a40e@ghostwheel> Message-ID: If you prefer to use the command line there is also the MicroFs utility which allows you to transfer files to a microbit with MicroPython. It's the same tool used internally by Mu. https://github.com/ntoll/microfs On 14 August 2016 at 19:42, Radomir Dopieralski wrote: > The trick is that the fake USB mass storage that appears when you > connect the micro:bit can only be used to flash the .hex file to it, > and will not work for copying any other files onto the board -- > micro:bit simply doesn't have such functionality, the USB on it is > handled by a separate chip that is dedicated to re-flashing the main > chip and doesn't do anything else. > > To actually copy a python script onto the micro:bit, you have two > options: > > * combine it with the .hex file of the MicroPython interpreter, and > flash that together. That's what uflash does when you pass it a > python file, and that's also what the Mu editor does. > * run some python code on the repl that creates the file internally and > saves the data you need to it. That's what the Mu editor does when you > use its "files" dialog to transfer files. > > > On Sat, 13 Aug 2016 18:29:50 +0100 > "fresh.bread via Microbit" wrote: > > > I'm figuring out how to program the microbit in python but am > > finding the differences between the pyboard and the microbit > > confusing. > > > > I was under the impression that I could use uflash to flash a python > > runtime system (what I understand to be a python interpreter) to the > > board. If I do this I can open a terminal on the board and execute > > lines of python,[ tick!] > > > > On the pyboard, if I copy a python script to the board as main.py and > > then reboot the board, it will run the script > > > > On a microbit, (that I have flashed the python runtime using uflash), > > if I copy the main.py and do a soft reboot (i.e ctrl-d or use the > > reset switch) the script does not run. More confusing, if I do a hard > > reset by disconnecting and reconnecting the microbit, the main.py on > > the microbit vanishes? Is this normal? > > > > [The differences won't stop me programming the microbit its just that > > I would like a similar approach for both boards if that is possible] > > -- > 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 damien.p.george at gmail.com Tue Aug 16 07:30:20 2016 From: damien.p.george at gmail.com (Damien George) Date: Tue, 16 Aug 2016 21:30:20 +1000 Subject: [Microbit-Python] Build micropython problem In-Reply-To: References: <85efc26e-3186-8ae8-1bf6-647c234fceaa@googlemail.com> Message-ID: There is now a github issue for this: https://github.com/bbcmicrobit/micropython/issues/338 On 9 August 2016 at 05:41, fresh.bread via Microbit wrote: > > I'm getting the same failure with Linux Mint 17.3.. > > > On 08/08/16 10:02, Tom via Microbit wrote: >> >> I'm on Xubuntu 16.04 and have followed the README.md in the micropython >> git latest and on "yt build" I get the following >> ------------------------------------ >> ......... >> ^ >> [101/291] Building CXX object >> ym/ble-n...dules/ble-nrf51822/source/nRF5xn.cpp.o >> ninja: build stopped: subcommand failed. >> error: command ['ninja'] failed >> ----------------------------------------------------------- >> Where have I gone wrong? >> Tom >> >> _______________________________________________ >> 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 Wed Aug 17 15:04:52 2016 From: andrewferguson500 at gmail.com (Andrew Ferguson 500) Date: Wed, 17 Aug 2016 20:04:52 +0100 Subject: [Microbit-Python] Who runs withcode.uk Message-ID: Does anyone know who runs the website withcode.uk? They have a fantastic microbit simulator there with python support, and I'd love to integrate it into a project I am working on. The site states that everything except noted otherwise is Creative Commons licensed, but I need something GPL compatible. I have tried the contact form on the website twice over the past few weeks, with no luck. (I get a Wordpress automated confirmation, but no reply.) Can anyone help me get in touch with the owner of the website? Andrew From ntoll at ntoll.org Wed Aug 17 15:15:31 2016 From: ntoll at ntoll.org (Nicholas H.Tollervey) Date: Wed, 17 Aug 2016 20:15:31 +0100 Subject: [Microbit-Python] Who runs withcode.uk In-Reply-To: References: Message-ID: <890e7136-414d-e721-298b-317fcca382d9@ntoll.org> On 17/08/16 20:04, Andrew Ferguson 500 wrote: > Does anyone know who runs the website withcode.uk? They have a > fantastic microbit simulator there with python support, and I'd love > to integrate it into a project I am working on. The site states that > everything except noted otherwise is Creative Commons licensed, but I > need something GPL compatible. > > I have tried the contact form on the website twice over the past few > weeks, with no luck. (I get a Wordpress automated confirmation, but > no reply.) > > Can anyone help me get in touch with the owner of the website? > > Andrew > > > _______________________________________________ Microbit mailing > list Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > I've tried to contact the same parties for the same reasons. Haven't heard a sausage back. :-( I guess they're rather shy..? Anyone know them so we can congratulate them on such great work and help them build a community around their website..? 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 nigel.kendrick at gmail.com Wed Aug 17 15:27:36 2016 From: nigel.kendrick at gmail.com (Nigel Kendrick) Date: Wed, 17 Aug 2016 20:27:36 +0100 Subject: [Microbit-Python] Who runs withcode.uk In-Reply-To: <890e7136-414d-e721-298b-317fcca382d9@ntoll.org> References: <890e7136-414d-e721-298b-317fcca382d9@ntoll.org> Message-ID: <00a001d1f8bd$6bf74690$43e5d3b0$@gmail.com> Domain name: withcode.uk Registrant: Pete Dring Registrant type: Unknown Registrant's address: 53 Burnholme Avenue York North Yorkshire YO31 0NA United Kingdom -----Original Message----- From: Microbit [mailto:microbit-bounces+nigel.kendrick=gmail.com at python.org] On Behalf Of Nicholas H.Tollervey Sent: 17 August 2016 20:16 To: microbit at python.org Subject: Re: [Microbit-Python] Who runs withcode.uk On 17/08/16 20:04, Andrew Ferguson 500 wrote: > Does anyone know who runs the website withcode.uk? They have a > fantastic microbit simulator there with python support, and I'd love > to integrate it into a project I am working on. The site states that > everything except noted otherwise is Creative Commons licensed, but I > need something GPL compatible. > > I have tried the contact form on the website twice over the past few > weeks, with no luck. (I get a Wordpress automated confirmation, but no > reply.) > > Can anyone help me get in touch with the owner of the website? > > Andrew > > > _______________________________________________ Microbit mailing list > Microbit at python.org https://mail.python.org/mailman/listinfo/microbit > I've tried to contact the same parties for the same reasons. Haven't heard a sausage back. :-( I guess they're rather shy..? Anyone know them so we can congratulate them on such great work and help them build a community around their website..? N. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus From andrewferguson500 at gmail.com Wed Aug 17 15:36:20 2016 From: andrewferguson500 at gmail.com (Andrew Ferguson 500) Date: Wed, 17 Aug 2016 20:36:20 +0100 Subject: [Microbit-Python] Who runs withcode.uk In-Reply-To: <00a001d1f8bd$6bf74690$43e5d3b0$@gmail.com> References: <890e7136-414d-e721-298b-317fcca382d9@ntoll.org> <00a001d1f8bd$6bf74690$43e5d3b0$@gmail.com> Message-ID: <0B8B08D0-9736-46DD-9038-C476ADE6E0F6@gmail.com> There aren't any similar projects, are there? The microbit simulator part I can recreate given time, but it's the online python editor with breakpoints and the ability to step through code that is the most important part for me. On 17 Aug 2016, at 20:27, "Nigel Kendrick" wrote: > Domain name: > withcode.uk > > Registrant: > Pete Dring > > Registrant type: > Unknown > > Registrant's address: > 53 Burnholme Avenue > York > North Yorkshire > YO31 0NA > United Kingdom > > -----Original Message----- > From: Microbit [mailto:microbit-bounces+nigel.kendrick=gmail.com at python.org] > On Behalf Of Nicholas H.Tollervey > Sent: 17 August 2016 20:16 > To: microbit at python.org > Subject: Re: [Microbit-Python] Who runs withcode.uk > > On 17/08/16 20:04, Andrew Ferguson 500 wrote: >> Does anyone know who runs the website withcode.uk? They have a >> fantastic microbit simulator there with python support, and I'd love >> to integrate it into a project I am working on. The site states that >> everything except noted otherwise is Creative Commons licensed, but I >> need something GPL compatible. >> >> I have tried the contact form on the website twice over the past few >> weeks, with no luck. (I get a Wordpress automated confirmation, but no >> reply.) >> >> Can anyone help me get in touch with the owner of the website? >> >> Andrew >> >> >> _______________________________________________ Microbit mailing list >> Microbit at python.org https://mail.python.org/mailman/listinfo/microbit >> > > I've tried to contact the same parties for the same reasons. Haven't heard a > sausage back. :-( > > I guess they're rather shy..? > > Anyone know them so we can congratulate them on such great work and help > them build a community around their website..? > > N. > > > > --- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit From ntoll at ntoll.org Wed Aug 17 15:39:07 2016 From: ntoll at ntoll.org (Nicholas H.Tollervey) Date: Wed, 17 Aug 2016 20:39:07 +0100 Subject: [Microbit-Python] Who runs withcode.uk In-Reply-To: <0B8B08D0-9736-46DD-9038-C476ADE6E0F6@gmail.com> References: <890e7136-414d-e721-298b-317fcca382d9@ntoll.org> <00a001d1f8bd$6bf74690$43e5d3b0$@gmail.com> <0B8B08D0-9736-46DD-9038-C476ADE6E0F6@gmail.com> Message-ID: <0a9fa44a-2503-a00e-c1a7-4e0c456d6ebf@ntoll.org> GrokLearning have one in the works that looks amazing (I've seen a sneak peak) although it's not publicly available. It simulates the actual hardware so the hex file is "flashed" to the virtualised micro:bit. Even plays tunes from the music module. Very cool. N. On 17/08/16 20:36, Andrew Ferguson 500 wrote: > There aren't any similar projects, are there? The microbit simulator > part I can recreate given time, but it's the online python editor > with breakpoints and the ability to step through code that is the > most important part for me. > > > > On 17 Aug 2016, at 20:27, "Nigel Kendrick" > wrote: > >> Domain name: withcode.uk >> >> Registrant: Pete Dring >> >> Registrant type: Unknown >> >> Registrant's address: 53 Burnholme Avenue York North Yorkshire YO31 >> 0NA United Kingdom >> >> -----Original Message----- From: Microbit >> [mailto:microbit-bounces+nigel.kendrick=gmail.com at python.org] On >> Behalf Of Nicholas H.Tollervey Sent: 17 August 2016 20:16 To: >> microbit at python.org Subject: Re: [Microbit-Python] Who runs >> withcode.uk >> >> On 17/08/16 20:04, Andrew Ferguson 500 wrote: >>> Does anyone know who runs the website withcode.uk? They have a >>> fantastic microbit simulator there with python support, and I'd >>> love to integrate it into a project I am working on. The site >>> states that everything except noted otherwise is Creative Commons >>> licensed, but I need something GPL compatible. >>> >>> I have tried the contact form on the website twice over the past >>> few weeks, with no luck. (I get a Wordpress automated >>> confirmation, but no reply.) >>> >>> Can anyone help me get in touch with the owner of the website? >>> >>> Andrew >>> >>> >>> _______________________________________________ Microbit mailing >>> list Microbit at python.org >>> https://mail.python.org/mailman/listinfo/microbit >>> >> >> I've tried to contact the same parties for the same reasons. >> Haven't heard a sausage back. :-( >> >> I guess they're rather shy..? >> >> Anyone know them so we can congratulate them on such great work and >> help them build a community around their website..? >> >> N. >> >> >> >> --- This email has been checked for viruses by Avast antivirus >> software. https://www.avast.com/antivirus >> >> _______________________________________________ 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 -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From nigel.kendrick at gmail.com Wed Aug 17 15:45:09 2016 From: nigel.kendrick at gmail.com (Nigel Kendrick) Date: Wed, 17 Aug 2016 20:45:09 +0100 Subject: [Microbit-Python] Micro:bit schematics Message-ID: <00a701d1f8bf$de32fae0$9a98f0a0$@gmail.com> Hi Nicholas, Did you hear any News at the IET about the schematics? Nigel Kendrick --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -------------- next part -------------- An HTML attachment was scrubbed... URL: From ntoll at ntoll.org Wed Aug 17 15:47:31 2016 From: ntoll at ntoll.org (Nicholas H.Tollervey) Date: Wed, 17 Aug 2016 20:47:31 +0100 Subject: [Microbit-Python] Micro:bit schematics In-Reply-To: <00a701d1f8bf$de32fae0$9a98f0a0$@gmail.com> References: <00a701d1f8bf$de32fae0$9a98f0a0$@gmail.com> Message-ID: Hi Nigel, Short answer: no. Long answer: it's coming and I don't know when. Jonny Austin (from ARM, perhaps a subscriber to this list) is in the best situation to explain when that's going to happen. It is, frustratingly, the final piece of the jigsaw to be open-sourced. Sorry I can't be more helpful. N. On 17/08/16 20:45, Nigel Kendrick wrote: > Hi Nicholas, > > > > Did you hear any News at the IET about the schematics? > > > > Nigel Kendrick > > > > Virus-free. www.avast.com > > > > > > _______________________________________________ > 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 fresh.bread at yahoo.co.uk Wed Aug 17 16:39:43 2016 From: fresh.bread at yahoo.co.uk (fresh.bread) Date: Wed, 17 Aug 2016 21:39:43 +0100 Subject: [Microbit-Python] Microbit operating voltage range In-Reply-To: <00a701d1f8bf$de32fae0$9a98f0a0$@gmail.com> References: <00a701d1f8bf$de32fae0$9a98f0a0$@gmail.com> Message-ID: <782da1a3-ef21-f9f4-0cec-101b1f339045@yahoo.co.uk> Perhaps a bit off topic, being a general hardware question, but I can't seem to find the appropriate forum to ask the question, but does anyone know what the Microbit's operating voltage range is. 1. I have seen it suggested that taking it above 3V isn't a good idea, is that true? 2. Has anyone measured the minimum operating, I coupled it to a pair of rechargeable NiMH cells, these were freshly charged and putting out 2.6V. My patience ran out before the cells.. Will it work off 2.4v (i.e a pair of tired NiMH cells) From mal at egenix.com Wed Aug 17 17:07:57 2016 From: mal at egenix.com (M.-A. Lemburg) Date: Wed, 17 Aug 2016 23:07:57 +0200 Subject: [Microbit-Python] Microbit operating voltage range In-Reply-To: <782da1a3-ef21-f9f4-0cec-101b1f339045@yahoo.co.uk> References: <00a701d1f8bf$de32fae0$9a98f0a0$@gmail.com> <782da1a3-ef21-f9f4-0cec-101b1f339045@yahoo.co.uk> Message-ID: <57B4D22D.6020400@egenix.com> On 17.08.2016 22:39, fresh.bread via Microbit wrote: > Perhaps a bit off topic, being a general hardware question, but I can't > seem to find the appropriate forum to ask the question, but does anyone > know what the Microbit's operating voltage range is. > > 1. I have seen it suggested that taking it above 3V isn't a good idea, > is that true? > 2. Has anyone measured the minimum operating, I coupled it to a pair of > rechargeable NiMH cells, these were freshly charged and putting out > 2.6V. My patience ran out before the cells.. Will it work off 2.4v (i.e > a pair of tired NiMH cells) You might find this test interesting: http://www.reuk.co.uk/wordpress/microbit-power-consumption/ Apparently, 1.83V is enough to get it working. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Experts >>> Python Projects, Coaching and Consulting ... http://www.egenix.com/ >>> Python Database Interfaces ... http://products.egenix.com/ >>> Plone/Zope Database Interfaces ... http://zope.egenix.com/ ________________________________________________________________________ ::::: Try our mxODBC.Connect Python Database Interface for free ! :::::: 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/ From jim at groklearning.com Wed Aug 17 22:30:08 2016 From: jim at groklearning.com (Jim Mussared) Date: Thu, 18 Aug 2016 12:30:08 +1000 Subject: [Microbit-Python] Microbit operating voltage range In-Reply-To: <57B4D22D.6020400@egenix.com> References: <00a701d1f8bf$de32fae0$9a98f0a0$@gmail.com> <782da1a3-ef21-f9f4-0cec-101b1f339045@yahoo.co.uk> <57B4D22D.6020400@egenix.com> Message-ID: The NRF51822 chip on the micro:bit is designed to run down to 1.8V -- internally it actually has built-in voltage conversion so even when you're supplying 3.3V it's still running at 1.8V. I haven't seen the schematics, so I'm not sure exactly which mode it's in though - I had a quick look under the microscope and it seems like it's probably not using the DC/DC converter mode and more likely the LDO. Either way - it's designed to run down to low voltages and in LDO mode it will work between 1.8 and 3.6V. However, the things you connect to it might not be happy with 1.8V. Also there's no LED driver on the board, and there's 5 resistors that look fairly likely to be current limiting for the matrix, so they'll be pretty dim at 1.8V. In general though - powering devices from batteries --one easy way around this problem is a DC/DC converter - this module looks like a great option (price, size, etc): https://www.pololu.com/product/2561 (acts as a boost converter for 0.5 - 3.3v, linear regulator for 3.3 - 5.5v input). There's a slightly cheaper option without the auto-shutdown (https://www.pololu.com/ product/2563). This will let you use anything from 0.5 to 5.5V. Also another option if you want to use a bigger battery pack (e.g. 4xAA) is a buck/boost converter so you can drive it at any voltage from 2.7-12V. https://www.pololu.com/product/2122 I'm sure cheaper modules exist too. The other good thing about the boost converter is that as the battery discharges and drops voltage, the device will continue to operate at 3.3V. On 18 August 2016 at 07:07, M.-A. Lemburg wrote: > On 17.08.2016 22:39, fresh.bread via Microbit wrote: > > Perhaps a bit off topic, being a general hardware question, but I can't > > seem to find the appropriate forum to ask the question, but does anyone > > know what the Microbit's operating voltage range is. > > > > 1. I have seen it suggested that taking it above 3V isn't a good idea, > > is that true? > > 2. Has anyone measured the minimum operating, I coupled it to a pair of > > rechargeable NiMH cells, these were freshly charged and putting out > > 2.6V. My patience ran out before the cells.. Will it work off 2.4v (i.e > > a pair of tired NiMH cells) > > You might find this test interesting: > > http://www.reuk.co.uk/wordpress/microbit-power-consumption/ > > Apparently, 1.83V is enough to get it working. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Experts > >>> Python Projects, Coaching and Consulting ... http://www.egenix.com/ > >>> Python Database Interfaces ... http://products.egenix.com/ > >>> Plone/Zope Database Interfaces ... http://zope.egenix.com/ > ________________________________________________________________________ > > ::::: Try our mxODBC.Connect Python Database Interface for free ! :::::: > > 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/ > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sparks.m at gmail.com Thu Aug 18 03:24:03 2016 From: sparks.m at gmail.com (Michael) Date: Thu, 18 Aug 2016 08:24:03 +0100 Subject: [Microbit-Python] Micro:bit schematics In-Reply-To: References: <00a701d1f8bf$de32fae0$9a98f0a0$@gmail.com> Message-ID: On Wednesday, 17 August 2016, Nicholas H.Tollervey wrote: >. It is, > frustratingly, the final piece of the jigsaw to be open-sourced. I'm also still waiting in the release of the reference/prototype implementation to be released as open source. So there's more than one piece to be released. I'm assured that also will be released but I don't have any say/control in the matter... :-( > Sorry I can't be more helpful. Likewise... :-( Michael -------------- next part -------------- An HTML attachment was scrubbed... URL: From carlosperate at gmail.com Thu Aug 18 07:16:37 2016 From: carlosperate at gmail.com (Carlos Pereira Atencio) Date: Thu, 18 Aug 2016 12:16:37 +0100 Subject: [Microbit-Python] Who runs withcode.uk In-Reply-To: <0a9fa44a-2503-a00e-c1a7-4e0c456d6ebf@ntoll.org> References: <890e7136-414d-e721-298b-317fcca382d9@ntoll.org> <00a001d1f8bd$6bf74690$43e5d3b0$@gmail.com> <0B8B08D0-9736-46DD-9038-C476ADE6E0F6@gmail.com> <0a9fa44a-2503-a00e-c1a7-4e0c456d6ebf@ntoll.org> Message-ID: Yes, GrokLearning definitely seem to be doing some interesting work as well. Do you know how open will it be once it is eventually resealed? On 17 August 2016 at 20:39, Nicholas H.Tollervey wrote: > GrokLearning have one in the works that looks amazing (I've seen a sneak > peak) although it's not publicly available. > > It simulates the actual hardware so the hex file is "flashed" to the > virtualised micro:bit. Even plays tunes from the music module. > > Very cool. > > N. > > On 17/08/16 20:36, Andrew Ferguson 500 wrote: > > There aren't any similar projects, are there? The microbit simulator > > part I can recreate given time, but it's the online python editor > > with breakpoints and the ability to step through code that is the > > most important part for me. > > > > > > > > On 17 Aug 2016, at 20:27, "Nigel Kendrick" > > wrote: > > > >> Domain name: withcode.uk > >> > >> Registrant: Pete Dring > >> > >> Registrant type: Unknown > >> > >> Registrant's address: 53 Burnholme Avenue York North Yorkshire YO31 > >> 0NA United Kingdom > >> > >> -----Original Message----- From: Microbit > >> [mailto:microbit-bounces+nigel.kendrick=gmail.com at python.org] On > >> Behalf Of Nicholas H.Tollervey Sent: 17 August 2016 20:16 To: > >> microbit at python.org Subject: Re: [Microbit-Python] Who runs > >> withcode.uk > >> > >> On 17/08/16 20:04, Andrew Ferguson 500 wrote: > >>> Does anyone know who runs the website withcode.uk? They have a > >>> fantastic microbit simulator there with python support, and I'd > >>> love to integrate it into a project I am working on. The site > >>> states that everything except noted otherwise is Creative Commons > >>> licensed, but I need something GPL compatible. > >>> > >>> I have tried the contact form on the website twice over the past > >>> few weeks, with no luck. (I get a Wordpress automated > >>> confirmation, but no reply.) > >>> > >>> Can anyone help me get in touch with the owner of the website? > >>> > >>> Andrew > >>> > >>> > >>> _______________________________________________ Microbit mailing > >>> list Microbit at python.org > >>> https://mail.python.org/mailman/listinfo/microbit > >>> > >> > >> I've tried to contact the same parties for the same reasons. > >> Haven't heard a sausage back. :-( > >> > >> I guess they're rather shy..? > >> > >> Anyone know them so we can congratulate them on such great work and > >> help them build a community around their website..? > >> > >> N. > >> > >> > >> > >> --- This email has been checked for viruses by Avast antivirus > >> software. https://www.avast.com/antivirus > >> > >> _______________________________________________ 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From carlosperate at gmail.com Thu Aug 18 07:22:17 2016 From: carlosperate at gmail.com (Carlos Pereira Atencio) Date: Thu, 18 Aug 2016 12:22:17 +0100 Subject: [Microbit-Python] Who runs withcode.uk In-Reply-To: <0B8B08D0-9736-46DD-9038-C476ADE6E0F6@gmail.com> References: <890e7136-414d-e721-298b-317fcca382d9@ntoll.org> <00a001d1f8bd$6bf74690$43e5d3b0$@gmail.com> <0B8B08D0-9736-46DD-9038-C476ADE6E0F6@gmail.com> Message-ID: I think a CAS hug has already publish a command line simulator. For the online python editor I will assume they are using skulpt (as it is the only js implementation that does sleep() properly), which also offers debugger hooks that could be used for step through and breakpoints. On 17 August 2016 at 20:36, Andrew Ferguson 500 wrote: > There aren't any similar projects, are there? The microbit simulator part > I can recreate given time, but it's the online python editor with > breakpoints and the ability to step through code that is the most important > part for me. > > > > On 17 Aug 2016, at 20:27, "Nigel Kendrick" > wrote: > > > Domain name: > > withcode.uk > > > > Registrant: > > Pete Dring > > > > Registrant type: > > Unknown > > > > Registrant's address: > > 53 Burnholme Avenue > > York > > North Yorkshire > > YO31 0NA > > United Kingdom > > > > -----Original Message----- > > From: Microbit [mailto:microbit-bounces+nigel.kendrick=gmail.com@ > python.org] > > On Behalf Of Nicholas H.Tollervey > > Sent: 17 August 2016 20:16 > > To: microbit at python.org > > Subject: Re: [Microbit-Python] Who runs withcode.uk > > > > On 17/08/16 20:04, Andrew Ferguson 500 wrote: > >> Does anyone know who runs the website withcode.uk? They have a > >> fantastic microbit simulator there with python support, and I'd love > >> to integrate it into a project I am working on. The site states that > >> everything except noted otherwise is Creative Commons licensed, but I > >> need something GPL compatible. > >> > >> I have tried the contact form on the website twice over the past few > >> weeks, with no luck. (I get a Wordpress automated confirmation, but no > >> reply.) > >> > >> Can anyone help me get in touch with the owner of the website? > >> > >> Andrew > >> > >> > >> _______________________________________________ Microbit mailing list > >> Microbit at python.org https://mail.python.org/mailman/listinfo/microbit > >> > > > > I've tried to contact the same parties for the same reasons. Haven't > heard a > > sausage back. :-( > > > > I guess they're rather shy..? > > > > Anyone know them so we can congratulate them on such great work and help > > them build a community around their website..? > > > > N. > > > > > > > > --- > > This email has been checked for viruses by Avast antivirus software. > > https://www.avast.com/antivirus > > > > _______________________________________________ > > 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 jim at groklearning.com Thu Aug 18 08:41:26 2016 From: jim at groklearning.com (Jim Mussared) Date: Thu, 18 Aug 2016 22:41:26 +1000 Subject: [Microbit-Python] Who runs withcode.uk In-Reply-To: <0a9fa44a-2503-a00e-c1a7-4e0c456d6ebf@ntoll.org> References: <890e7136-414d-e721-298b-317fcca382d9@ntoll.org> <00a001d1f8bd$6bf74690$43e5d3b0$@gmail.com> <0B8B08D0-9736-46DD-9038-C476ADE6E0F6@gmail.com> <0a9fa44a-2503-a00e-c1a7-4e0c456d6ebf@ntoll.org> Message-ID: Thanks Nicholas! We're just putting the finishing touches on our freely-available 'taster' course, and expect to have some announcements in the next few days! We're running a 5-week full course starting October 31 - the "Grok Code Quest" -- https://groklearning.com/codequest/ The taster course will include browser-based access to the full simulator (as well as ability to download code via .hex files, like the BBC site). We're also including simulated external components (buttons, LEDs, servos, speakers, etc and very soon, motors and cars). I gave a very brief demo of this at PyCon Australia last weekend in a talk about MicroPython in education (microbit, esp8266, etc). The relevant bit to this thread starts at 17:15. https://youtu.be/oCEZyJqkMrE?t=17m15s On 18 August 2016 at 05:39, Nicholas H.Tollervey wrote: > GrokLearning have one in the works that looks amazing (I've seen a sneak > peak) although it's not publicly available. > > It simulates the actual hardware so the hex file is "flashed" to the > virtualised micro:bit. Even plays tunes from the music module. > > Very cool. > > N. > > On 17/08/16 20:36, Andrew Ferguson 500 wrote: > > There aren't any similar projects, are there? The microbit simulator > > part I can recreate given time, but it's the online python editor > > with breakpoints and the ability to step through code that is the > > most important part for me. > > > > > > > > On 17 Aug 2016, at 20:27, "Nigel Kendrick" > > wrote: > > > >> Domain name: withcode.uk > >> > >> Registrant: Pete Dring > >> > >> Registrant type: Unknown > >> > >> Registrant's address: 53 Burnholme Avenue York North Yorkshire YO31 > >> 0NA United Kingdom > >> > >> -----Original Message----- From: Microbit > >> [mailto:microbit-bounces+nigel.kendrick=gmail.com at python.org] On > >> Behalf Of Nicholas H.Tollervey Sent: 17 August 2016 20:16 To: > >> microbit at python.org Subject: Re: [Microbit-Python] Who runs > >> withcode.uk > >> > >> On 17/08/16 20:04, Andrew Ferguson 500 wrote: > >>> Does anyone know who runs the website withcode.uk? They have a > >>> fantastic microbit simulator there with python support, and I'd > >>> love to integrate it into a project I am working on. The site > >>> states that everything except noted otherwise is Creative Commons > >>> licensed, but I need something GPL compatible. > >>> > >>> I have tried the contact form on the website twice over the past > >>> few weeks, with no luck. (I get a Wordpress automated > >>> confirmation, but no reply.) > >>> > >>> Can anyone help me get in touch with the owner of the website? > >>> > >>> Andrew > >>> > >>> > >>> _______________________________________________ Microbit mailing > >>> list Microbit at python.org > >>> https://mail.python.org/mailman/listinfo/microbit > >>> > >> > >> I've tried to contact the same parties for the same reasons. > >> Haven't heard a sausage back. :-( > >> > >> I guess they're rather shy..? > >> > >> Anyone know them so we can congratulate them on such great work and > >> help them build a community around their website..? > >> > >> N. > >> > >> > >> > >> --- This email has been checked for viruses by Avast antivirus > >> software. https://www.avast.com/antivirus > >> > >> _______________________________________________ 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrewferguson500 at gmail.com Thu Aug 18 09:45:45 2016 From: andrewferguson500 at gmail.com (Andrew Ferguson 500) Date: Thu, 18 Aug 2016 14:45:45 +0100 Subject: [Microbit-Python] Who runs withcode.uk In-Reply-To: References: <890e7136-414d-e721-298b-317fcca382d9@ntoll.org> <00a001d1f8bd$6bf74690$43e5d3b0$@gmail.com> <0B8B08D0-9736-46DD-9038-C476ADE6E0F6@gmail.com> <0a9fa44a-2503-a00e-c1a7-4e0c456d6ebf@ntoll.org> Message-ID: Wow Jim! That looks amazing! A quick note to Nicholas and others: I have just received a reply from Pete Dring (coincidence?) saying that the contact form on the website was setup incorrectly and so he didn't realize he had messages. But the upshot is that his code is available on github.com/pddring/createwithcode . And it is Free and Open Source (GPLv3)!!! On 18 Aug 2016, at 13:41, Jim Mussared via Microbit wrote: > Thanks Nicholas! We're just putting the finishing touches on our freely-available 'taster' course, and expect to have some announcements in the next few days! We're running a 5-week full course starting October 31 - the "Grok Code Quest" -- https://groklearning.com/codequest/ > > The taster course will include browser-based access to the full simulator (as well as ability to download code via .hex files, like the BBC site). We're also including simulated external components (buttons, LEDs, servos, speakers, etc and very soon, motors and cars). > > I gave a very brief demo of this at PyCon Australia last weekend in a talk about MicroPython in education (microbit, esp8266, etc). The relevant bit to this thread starts at 17:15. https://youtu.be/oCEZyJqkMrE?t=17m15s > > On 18 August 2016 at 05:39, Nicholas H.Tollervey wrote: > GrokLearning have one in the works that looks amazing (I've seen a sneak > peak) although it's not publicly available. > > It simulates the actual hardware so the hex file is "flashed" to the > virtualised micro:bit. Even plays tunes from the music module. > > Very cool. > > N. > > On 17/08/16 20:36, Andrew Ferguson 500 wrote: > > There aren't any similar projects, are there? The microbit simulator > > part I can recreate given time, but it's the online python editor > > with breakpoints and the ability to step through code that is the > > most important part for me. > > > > > > > > On 17 Aug 2016, at 20:27, "Nigel Kendrick" > > wrote: > > > >> Domain name: withcode.uk > >> > >> Registrant: Pete Dring > >> > >> Registrant type: Unknown > >> > >> Registrant's address: 53 Burnholme Avenue York North Yorkshire YO31 > >> 0NA United Kingdom > >> > >> -----Original Message----- From: Microbit > >> [mailto:microbit-bounces+nigel.kendrick=gmail.com at python.org] On > >> Behalf Of Nicholas H.Tollervey Sent: 17 August 2016 20:16 To: > >> microbit at python.org Subject: Re: [Microbit-Python] Who runs > >> withcode.uk > >> > >> On 17/08/16 20:04, Andrew Ferguson 500 wrote: > >>> Does anyone know who runs the website withcode.uk? They have a > >>> fantastic microbit simulator there with python support, and I'd > >>> love to integrate it into a project I am working on. The site > >>> states that everything except noted otherwise is Creative Commons > >>> licensed, but I need something GPL compatible. > >>> > >>> I have tried the contact form on the website twice over the past > >>> few weeks, with no luck. (I get a Wordpress automated > >>> confirmation, but no reply.) > >>> > >>> Can anyone help me get in touch with the owner of the website? > >>> > >>> Andrew > >>> > >>> > >>> _______________________________________________ Microbit mailing > >>> list Microbit at python.org > >>> https://mail.python.org/mailman/listinfo/microbit > >>> > >> > >> I've tried to contact the same parties for the same reasons. > >> Haven't heard a sausage back. :-( > >> > >> I guess they're rather shy..? > >> > >> Anyone know them so we can congratulate them on such great work and > >> help them build a community around their website..? > >> > >> N. > >> > >> > >> > >> --- This email has been checked for viruses by Avast antivirus > >> software. https://www.avast.com/antivirus > >> > >> _______________________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jonathan.Austin at arm.com Fri Aug 19 11:15:45 2016 From: Jonathan.Austin at arm.com (Jonathan Austin) Date: Fri, 19 Aug 2016 15:15:45 +0000 Subject: [Microbit-Python] Micro:bit schematics In-Reply-To: References: <00a701d1f8bf$de32fae0$9a98f0a0$@gmail.com> Message-ID: <6484EA2F-61E0-406C-8589-E559449FE855@arm.com> Hi all, > On 17 Aug 2016, at 20:47, Nicholas H.Tollervey wrote: > > Long answer: it's coming and I don't know when.e: > > Jonny Austin (from ARM, perhaps a subscriber to this list) Just to clarify - this isn?t ARM?s design to release - it?s a BBC and micro:bit partnership thing but I?m continuing to work on the project at ARM and so have visibility of some of this. > is in the > best situation to explain when that's going to happen. Longer answer: Nicholas already gave the best answer anyone can give at the moment - there are a number of things that need to happen, both from a legal and technical point of view before the design can go out the door. But maybe we can take some of those things out of the loop for certain uses and certain components. For example I?m currently looking to see whether the schematic could be made available open source sooner than other parts, say the gerbers which might be more complicated to get out. Overall, I think it?s really important to provide these so that people can take the micro:bit designs and embed them into their own projects - I?d like to see a clear path from: ?I built this with a micro:bit? to ?I use the open source micro:bit and extended the design and now I?ve got my own board? So - what are you trying achieve? Would the schematic help? Would more data about the design help? Pin allocation data? As you?ll see, there are a good number of parts of the micro:bit ecosystem already open source, so you might be able to get what you need elsewhere for now - for example the micro:bit is based on the mbed HDK for nRF51822, which is in turn based on a Nordic reference design. The HDK can be found in source control here: https://developer.mbed.org/teams/mbed/code/mbed-HDK/ > > It is, > frustratingly, the final piece of the jigsaw to be open-sourced. > > Sorry I can't be more helpful. > It?s absolutely not forgotten, it will happen, hopefully soon but committing to times isn?t the right thing for anyone in the project to do at the moment, sorry. Jonny > N. > > On 17/08/16 20:45, Nigel Kendrick wrote: >> Hi Nicholas, >> >> >> >> Did you hear any News at the IET about the schematics? >> >> >> >> Nigel Kendrick >> >> >> >> Virus-free. www.avast.com >> >> >> >> >> >> _______________________________________________ >> 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 IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. From linker3000 at gmail.com Wed Aug 17 15:25:38 2016 From: linker3000 at gmail.com (Linker3000) Date: Wed, 17 Aug 2016 20:25:38 +0100 Subject: [Microbit-Python] Who runs withcode.uk In-Reply-To: References: Message-ID: <009e01d1f8bd$24f1aa60$6ed4ff20$@gmail.com> Domain name: withcode.uk Registrant: Pete Dring Registrant type: Unknown Registrant's address: 53 Burnholme Avenue York North Yorkshire YO31 0NA United Kingdom -----Original Message----- From: Microbit [mailto:microbit-bounces+nigel.kendrick=gmail.com at python.org] On Behalf Of Andrew Ferguson 500 Sent: 17 August 2016 20:05 To: For Pythonic MicroBit related discussions Subject: [Microbit-Python] Who runs withcode.uk Does anyone know who runs the website withcode.uk? They have a fantastic microbit simulator there with python support, and I'd love to integrate it into a project I am working on. The site states that everything except noted otherwise is Creative Commons licensed, but I need something GPL compatible. I have tried the contact form on the website twice over the past few weeks, with no luck. (I get a Wordpress automated confirmation, but no reply.) Can anyone help me get in touch with the owner of the website? Andrew _______________________________________________ Microbit mailing list Microbit at python.org https://mail.python.org/mailman/listinfo/microbit --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus From osmarks at icloud.com Mon Aug 22 13:40:12 2016 From: osmarks at icloud.com (Oliver S Marks) Date: Mon, 22 Aug 2016 18:40:12 +0100 Subject: [Microbit-Python] JSON-parsing module? Message-ID: <253ec07b-a533-15e1-31fb-c9ea7f6c814a@icloud.com> I'm working on MicroBit programming, using MicroPython. However, I've noticed that there's nothing at all for dealing with JSON, which prevents practically all complex networked/persistent things from working. So, it would be helpful if you added a JSON parsing implementation in here somewhere. From garybake at gmail.com Tue Aug 23 08:28:36 2016 From: garybake at gmail.com (Gary Bake) Date: Tue, 23 Aug 2016 13:28:36 +0100 Subject: [Microbit-Python] JSON-parsing module? In-Reply-To: <253ec07b-a533-15e1-31fb-c9ea7f6c814a@icloud.com> References: <253ec07b-a533-15e1-31fb-c9ea7f6c814a@icloud.com> Message-ID: Hi Oliver, You can use the library in the micropython lib https://github.com/micropython/micropython-lib/tree/master/json On 22 August 2016 at 18:40, Oliver S Marks wrote: > I'm working on MicroBit programming, using MicroPython. However, I've > noticed that there's nothing at all for dealing with JSON, which prevents > practically all complex networked/persistent things from working. So, it > would be helpful if you added a JSON parsing implementation in here > somewhere. > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > -- Regards Gary Bake -------------- next part -------------- An HTML attachment was scrubbed... URL: From ntoll at ntoll.org Tue Aug 23 08:31:25 2016 From: ntoll at ntoll.org (Nicholas H.Tollervey) Date: Tue, 23 Aug 2016 13:31:25 +0100 Subject: [Microbit-Python] JSON-parsing module? In-Reply-To: References: <253ec07b-a533-15e1-31fb-c9ea7f6c814a@icloud.com> Message-ID: <2c65189b-1f92-a2e8-9437-c7046bffd253@ntoll.org> Alternatively, for "it's not quite JSON but close enough" you could just serialise you dicts with repr(). To de-serialise do eval(). Hope this makes sense. N. On 23/08/16 13:28, Gary Bake wrote: > Hi Oliver, > > You can use the library in the micropython lib > > https://github.com/micropython/micropython-lib/tree/master/json > > On 22 August 2016 at 18:40, Oliver S Marks > wrote: > > I'm working on MicroBit programming, using MicroPython. However, > I've noticed that there's nothing at all for dealing with JSON, > which prevents practically all complex networked/persistent things > from working. So, it would be helpful if you added a JSON parsing > implementation in here somewhere. > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > > > > > > -- > Regards > Gary Bake > > > _______________________________________________ > 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 Tue Aug 23 08:43:57 2016 From: david at thinkingbinaries.com (David Whale) Date: Tue, 23 Aug 2016 13:43:57 +0100 Subject: [Microbit-Python] JSON-parsing module? In-Reply-To: <253ec07b-a533-15e1-31fb-c9ea7f6c814a@icloud.com> References: <253ec07b-a533-15e1-31fb-c9ea7f6c814a@icloud.com> Message-ID: The Lancaster runtime has a tiny native json parser built into it, you could expose that via a python interface perhaps? On 22 Aug 2016 6:40 pm, "Oliver S Marks" wrote: > I'm working on MicroBit programming, using MicroPython. However, I've > noticed that there's nothing at all for dealing with JSON, which prevents > practically all complex networked/persistent things from working. So, it > would be helpful if you added a JSON parsing implementation in here > somewhere. > _______________________________________________ > 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 Tue Aug 23 08:55:30 2016 From: damien.p.george at gmail.com (Damien George) Date: Tue, 23 Aug 2016 22:55:30 +1000 Subject: [Microbit-Python] JSON-parsing module? In-Reply-To: References: <253ec07b-a533-15e1-31fb-c9ea7f6c814a@icloud.com> Message-ID: MicroPython upstream has a json parser and render built-in, but we did not add it to the microbit port because of space limitation. What kind of "complex network" opretions do you need to do? For such things you probably need a lot more RAM anyway, so better to use a more capable microcontroller. On 23 August 2016 at 22:43, David Whale wrote: > The Lancaster runtime has a tiny native json parser built into it, you could > expose that via a python interface perhaps? > > > On 22 Aug 2016 6:40 pm, "Oliver S Marks" wrote: >> >> I'm working on MicroBit programming, using MicroPython. However, I've >> noticed that there's nothing at all for dealing with JSON, which prevents >> practically all complex networked/persistent things from working. So, it >> would be helpful if you added a JSON parsing implementation in here >> somewhere. >> _______________________________________________ >> 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 mark at hotpy.org Tue Aug 23 13:14:06 2016 From: mark at hotpy.org (mark at hotpy.org) Date: Tue, 23 Aug 2016 18:14:06 +0100 Subject: [Microbit-Python] JSON-parsing module? In-Reply-To: Message-ID: <1e57ce66-565f-4b6a-b66d-dfaa9148adc4@email.android.com> An HTML attachment was scrubbed... URL: From larry at hastings.org Tue Aug 23 22:48:11 2016 From: larry at hastings.org (Larry Hastings) Date: Tue, 23 Aug 2016 22:48:11 -0400 Subject: [Microbit-Python] JSON-parsing module? In-Reply-To: <1e57ce66-565f-4b6a-b66d-dfaa9148adc4@email.android.com> References: <1e57ce66-565f-4b6a-b66d-dfaa9148adc4@email.android.com> Message-ID: <305381b5-6d05-b3a0-bb01-c06c9002ce43@hastings.org> On 08/23/2016 01:14 PM, mark at hotpy.org wrote: > > If you just need to decode json then, with a complete disregard for > safety, try this: > json_decode = eval > And with a complete disregard for the keyword "null" and the capitalization of True and False? //arry/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From dhylands at gmail.com Wed Aug 24 00:12:55 2016 From: dhylands at gmail.com (Dave Hylands) Date: Tue, 23 Aug 2016 21:12:55 -0700 Subject: [Microbit-Python] JSON-parsing module? In-Reply-To: <305381b5-6d05-b3a0-bb01-c06c9002ce43@hastings.org> References: <1e57ce66-565f-4b6a-b66d-dfaa9148adc4@email.android.com> <305381b5-6d05-b3a0-bb01-c06c9002ce43@hastings.org> Message-ID: Couldn't you just define those? null = None true = True false = False and then do the eval? On Tue, Aug 23, 2016 at 7:48 PM, Larry Hastings wrote: > > > On 08/23/2016 01:14 PM, mark at hotpy.org wrote: > > If you just need to decode json then, with a complete disregard for > safety, try this: > json_decode = eval > > > And with a complete disregard for the keyword "null" and the > capitalization of True and False? > > > */arry* > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > > -- Dave Hylands Shuswap, BC, Canada http://www.davehylands.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From barrachri at gmail.com Wed Aug 24 05:17:31 2016 From: barrachri at gmail.com (Christian Barra) Date: Wed, 24 Aug 2016 11:17:31 +0200 Subject: [Microbit-Python] Poland:Microbit Message-ID: Hello MicroPythonistas ! I had the pleasure to talk during an event of the KOED - COALITION FOR OPEN EDUCATION (http://koed.org.pl/) in Katowice about doing something similar to what BBC have done in UK. *Give away for free BBC:Microbit and organise courses for teachers and students.* The feedback was more than awesome :D You can find the slide of the presentation here: https://docs.google.com/presentation/d/1ewDlUExB91BKuDcSS2Tj6TnImp1FwHgnu2lW9IPs2bg/edit?usp=sharing I would like to receive some feedback, maybe someone also from this ML is already doing something similar and it would be nice to share as many idea as we can. -- With Gravitational Cheers, Christian EuroPython Society board member -------------- next part -------------- An HTML attachment was scrubbed... URL: From garybake at gmail.com Wed Aug 24 05:45:56 2016 From: garybake at gmail.com (Gary Bake) Date: Wed, 24 Aug 2016 10:45:56 +0100 Subject: [Microbit-Python] Poland:Microbit In-Reply-To: References: Message-ID: I'm liking the word 'MicroPythonistas' On 24 August 2016 at 10:17, Christian Barra wrote: > Hello MicroPythonistas ! > > I had the pleasure to talk during an event of the KOED - COALITION FOR > OPEN EDUCATION (http://koed.org.pl/) in Katowice about doing something > similar to what BBC have done in UK. > > > *Give away for free BBC:Microbit and organise courses for teachers and > students.* > The feedback was more than awesome :D > > You can find the slide of the presentation here: > https://docs.google.com/presentation/d/1ewDlUExB91BKuDcSS2Tj6TnImp1Fw > Hgnu2lW9IPs2bg/edit?usp=sharing > > I would like to receive some feedback, maybe someone also from this ML is > already doing something similar and it would be nice to share as many idea > as we can. > > -- > With Gravitational Cheers, > > Christian > EuroPython Society board member > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > > -- Regards Gary Bake -------------- next part -------------- An HTML attachment was scrubbed... URL: From carlosperate at gmail.com Wed Aug 24 07:13:41 2016 From: carlosperate at gmail.com (Carlos Pereira Atencio) Date: Wed, 24 Aug 2016 12:13:41 +0100 Subject: [Microbit-Python] Poland:Microbit In-Reply-To: References: Message-ID: That sounds fantastic! A great and exiting initiative, this is one of the reason why I love this community so much. It would interesting to know the type of resources you are planning to use or create? Including things like their formatting, distribution methods and stuff like that? Is there any specific goal in addition to teach programming? I've got the impression from the slides you might only be preparing a single 3-4 hours workshop, is that correct? And then as a personal interest I was wondering if you had, and didn't mind sharing, a general breakdown of the listed cost, as it seems quite tight. I don't have any experience organising this type of "remote workshops", just smaller local ones and there has always been a significant cost not associated with the hardware itself. Regards, Carlos On 24 August 2016 at 10:45, Gary Bake wrote: > I'm liking the word 'MicroPythonistas' > > On 24 August 2016 at 10:17, Christian Barra wrote: > >> Hello MicroPythonistas ! >> >> I had the pleasure to talk during an event of the KOED - COALITION FOR >> OPEN EDUCATION (http://koed.org.pl/) in Katowice about doing something >> similar to what BBC have done in UK. >> >> >> *Give away for free BBC:Microbit and organise courses for teachers and >> students.* >> The feedback was more than awesome :D >> >> You can find the slide of the presentation here: >> https://docs.google.com/presentation/d/1ewDlUExB91BKuDcSS2Tj >> 6TnImp1FwHgnu2lW9IPs2bg/edit?usp=sharing >> >> I would like to receive some feedback, maybe someone also from this ML is >> already doing something similar and it would be nice to share as many idea >> as we can. >> >> -- >> With Gravitational Cheers, >> >> Christian >> EuroPython Society board member >> >> _______________________________________________ >> Microbit mailing list >> Microbit at python.org >> https://mail.python.org/mailman/listinfo/microbit >> >> > > > -- > Regards > Gary Bake > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From joakim.pettersson at join.se Wed Aug 24 07:23:24 2016 From: joakim.pettersson at join.se (Joakim Pettersson) Date: Wed, 24 Aug 2016 11:23:24 +0000 Subject: [Microbit-Python] Poland:Microbit In-Reply-To: Message-ID: Great idea, I forwarded to the Swedish education ministry also! Hope it doesn't feel like a steal Chistian? BR/Joakim (Micropythonista:) ------ Originalmeddelande ------ Fr?n: "Carlos Pereira Atencio" Till: "For Pythonic MicroBit related discussions" Skickat: 2016-08-24 13:13:41 ?mne: Re: [Microbit-Python] Poland:Microbit >That sounds fantastic! A great and exiting initiative, this is one of >the reason why I love this community so much. > >It would interesting to know the type of resources you are planning to >use or create? Including things like their formatting, distribution >methods and stuff like that? Is there any specific goal in addition to >teach programming? I've got the impression from the slides you might >only be preparing a single 3-4 hours workshop, is that correct? > >And then as a personal interest I was wondering if you had, and didn't >mind sharing, a general breakdown of the listed cost, as it seems quite >tight. I don't have any experience organising this type of "remote >workshops", just smaller local ones and there has always been a >significant cost not associated with the hardware itself. > > >Regards, >Carlos > > >On 24 August 2016 at 10:45, Gary Bake wrote: >>I'm liking the word 'MicroPythonistas' >> >>On 24 August 2016 at 10:17, Christian Barra >>wrote: >>>Hello MicroPythonistas ! >>> >>>I had the pleasure to talk during an event of the KOED - COALITION >>>FOR OPEN EDUCATION (http://koed.org.pl/) in Katowice about doing >>>something similar to what BBC have done in UK. >>> >>>Give away for free BBC:Microbit and organise courses for teachers and >>>students. >>> >>>The feedback was more than awesome :D >>> >>>You can find the slide of the presentation here: >>>https://docs.google.com/presentation/d/1ewDlUExB91BKuDcSS2Tj6TnImp1FwHgnu2lW9IPs2bg/edit?usp=sharing >>> >>>I would like to receive some feedback, maybe someone also from this >>>ML is already doing something similar and it would be nice to share >>>as many idea as we can. >>> >>>-- >>>With Gravitational Cheers, >>> >>>Christian >>>EuroPython Society board member >>> >>>_______________________________________________ >>>Microbit mailing list >>>Microbit at python.org >>>https://mail.python.org/mailman/listinfo/microbit >>> >> >> >> >>-- >>Regards >>Gary Bake >> >>_______________________________________________ >>Microbit mailing list >>Microbit at python.org >>https://mail.python.org/mailman/listinfo/microbit >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hot.toast at yahoo.co.uk Wed Aug 24 17:14:47 2016 From: hot.toast at yahoo.co.uk (hot.toast) Date: Wed, 24 Aug 2016 22:14:47 +0100 Subject: [Microbit-Python] setting the range of the accelerometer Message-ID: <6d4a1968-6004-505a-c947-6149c323cf8b@yahoo.co.uk> Is there a Python function to select the maximum range of the Microbit's accelerometer (i.e 2g 4g or 8g)? I think the accelerometer hardware has this functionality but cannot find a python command to do the selection? From ntoll at ntoll.org Thu Aug 25 09:20:58 2016 From: ntoll at ntoll.org (Nicholas H.Tollervey) Date: Thu, 25 Aug 2016 14:20:58 +0100 Subject: [Microbit-Python] Poland:Microbit In-Reply-To: References: Message-ID: <553bb6f6-1f1f-302e-6820-cd5eb0d93a3c@ntoll.org> On 24/08/16 10:17, Christian Barra wrote: > Hello MicroPythonistas ! > > I had the pleasure to talk during an event of the KOED - COALITION FOR > OPEN EDUCATION (http://koed.org.pl/) in Katowice about doing something > similar to what BBC have done in UK. > > *Give away for free BBC:Microbit and organise courses for teachers and > students. > * > The feedback was more than awesome :D > > You can find the slide of the presentation here: > https://docs.google.com/presentation/d/1ewDlUExB91BKuDcSS2Tj6TnImp1FwHgnu2lW9IPs2bg/edit?usp=sharing > > I would like to receive some feedback, maybe someone also from this ML > is already doing something similar and it would be nice to share as many > idea as we can. > > -- > With Gravitational Cheers, > > Christian > EuroPython Society board member > > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > Hi Christian, That is totally wonderful. If there's anything I can do to help, please don't hesitate to ask. Will you be at PyCon PL..? You'll never guess who's giving a keynote that'll feature MicroPython on the BBC micro:bit..? (Hint: https://pl.pycon.org/2016/speakers_en.html) I'm also working on the pythonineducation.org (aliased to pyedu.io) website for the PSF. I'm writing it in such a way that it'll be easy to adopt / adapt the content for other locales. I should be ready to "announce" it for collaboration in about a fortnight. IN the meantime, the URL will direct you to a holding page containing a working-sh version of the landing page. 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 barrachri at gmail.com Thu Aug 25 15:24:22 2016 From: barrachri at gmail.com (Christian Barra) Date: Thu, 25 Aug 2016 21:24:22 +0200 Subject: [Microbit-Python] Poland:Microbit In-Reply-To: References: Message-ID: 2016-08-24 13:23 GMT+02:00 Joakim Pettersson : > Great idea, I forwarded to the Swedish education ministry also! Hope it > doesn't feel like a steal Chistian? BR/Joakim (Micropythonista:) > Thanks Joakim, I feel honored :) > ------ Originalmeddelande ------ > Fr?n: "Carlos Pereira Atencio" > Till: "For Pythonic MicroBit related discussions" > Skickat: 2016-08-24 13:13:41 > ?mne: Re: [Microbit-Python] Poland:Microbit > > > That sounds fantastic! A great and exiting initiative, this is one of the > reason why I love this community so much. > > It would interesting to know the type of resources you are planning to use > or create? Including things like their formatting, distribution methods and > stuff like that? Is there any specific goal in addition to teach > programming? I've got the impression from the slides you might only be > preparing a single 3-4 hours workshop, is that correct? > > Hi Carlos ! I really appreciate your enthusiasm :) The idea is to prepare the materials for a laboratory of 3-4 hours (maybe split in more days) This materials will be available on github, I will probably create a repo called Poland:Microbit. After this the plan is to organise local courses for the teachers and then organise the courses for the students, probably outside the schools. The workshop/laboratory will be around that duration, but the plan is to have more than one, I would like to have this kind of ratio 10 students/1 teacher and also to spread this around Poland. As I said the feedback was very good and a lot of associations are already doing something. For example them: http://www.superbelfrzy.edu.pl/ (Super Teachers) > And then as a personal interest I was wondering if you had, and didn't > mind sharing, a general breakdown of the listed cost, as it seems quite > tight. I don't have any experience organising this type of "remote > workshops", just smaller local ones and there has always been a significant > cost not associated with the hardware itself. > > The main cost will be for the Microbit, probably there will be the need to cover some expenses but I really hope to have some companies interested in joining this project. At least for now I'm pretty sure to have the spaces for the courses for free :D But it will not be a "remote workshop", apart from having a github repository for the material, everything will be "local". -- With Gravitational Cheers, Christian EuroPython Society board member -------------- next part -------------- An HTML attachment was scrubbed... URL: From barrachri at gmail.com Thu Aug 25 15:31:07 2016 From: barrachri at gmail.com (Christian Barra) Date: Thu, 25 Aug 2016 21:31:07 +0200 Subject: [Microbit-Python] Poland:Microbit In-Reply-To: <553bb6f6-1f1f-302e-6820-cd5eb0d93a3c@ntoll.org> References: <553bb6f6-1f1f-302e-6820-cd5eb0d93a3c@ntoll.org> Message-ID: 2016-08-25 15:20 GMT+02:00 Nicholas H.Tollervey : > > > Hi Christian, > > That is totally wonderful. If there's anything I can do to help, please > don't hesitate to ask. > Thanks Nicholas ! > > Will you be at PyCon PL..? You'll never guess who's giving a keynote > that'll feature MicroPython on the BBC micro:bit..? > > (Hint: https://pl.pycon.org/2016/speakers_en.html) > Sure, we are on the same page https://pl.pycon.org/2016/ambassadors.html :D Filip Klebczyk said to me he was waiting to be sure about your participation, glad to know you'll be there ! > > I'm also working on the pythonineducation.org (aliased to pyedu.io) > website for the PSF. I'm writing it in such a way that it'll be easy to > adopt / adapt the content for other locales. > > I should be ready to "announce" it for collaboration in about a > fortnight. IN the meantime, the URL will direct you to a holding page > containing a working-sh version of the landing page. > Awesome ! I'll wait to know how to contribute. -- With Gravitational Cheers, Christian EuroPython Society board member -------------- next part -------------- An HTML attachment was scrubbed... URL: From ntoll at ntoll.org Thu Aug 25 15:36:03 2016 From: ntoll at ntoll.org (Nicholas H.Tollervey) Date: Thu, 25 Aug 2016 20:36:03 +0100 Subject: [Microbit-Python] Poland:Microbit In-Reply-To: References: <553bb6f6-1f1f-302e-6820-cd5eb0d93a3c@ntoll.org> Message-ID: <597d3998-5185-3e02-422f-ba8cbf81e0fa@ntoll.org> On 25/08/16 20:31, Christian Barra wrote: > Sure, we are on the same page https://pl.pycon.org/2016/ambassadors.html :D Doh... I'd forgotten I'd agreed to be an "ambassador" and didn't realise that page existed. Hah! :-) Looking forward to catching up in Poland. I may have questions about your Polish contacts so I can use them in my talk. If you're doing things then the Polish Python community should know about it! 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 barrachri at gmail.com Tue Aug 30 04:53:35 2016 From: barrachri at gmail.com (Christian Barra) Date: Tue, 30 Aug 2016 10:53:35 +0200 Subject: [Microbit-Python] Poland:Microbit In-Reply-To: <597d3998-5185-3e02-422f-ba8cbf81e0fa@ntoll.org> References: <553bb6f6-1f1f-302e-6820-cd5eb0d93a3c@ntoll.org> <597d3998-5185-3e02-422f-ba8cbf81e0fa@ntoll.org> Message-ID: 2016-08-25 21:36 GMT+02:00 Nicholas H.Tollervey : > > > Looking forward to catching up in Poland. I may have questions about > your Polish contacts so I can use them in my talk. If you're doing > things then the Polish Python community should know about it! > > I'll keep you and the ML updated about this project ! -- With Gravitational Cheers, Christian EuroPython Society board member -------------- next part -------------- An HTML attachment was scrubbed... URL: From fresh.bread at yahoo.co.uk Wed Aug 31 01:48:17 2016 From: fresh.bread at yahoo.co.uk (fresh.bread) Date: Wed, 31 Aug 2016 06:48:17 +0100 Subject: [Microbit-Python] micro bit pin drive current Message-ID: <212d867d-7dfc-ba8f-41c4-5ea7a87580e7@yahoo.co.uk> I'm a bit worried by the diagram on the documentation for the micropython speech module showing a loudspeaker connected directly to pins 0 and 1 (see http://microbit-micropython.readthedocs.io/en/latest/tutorials/speech.html) What is the maximum drive current for the pins. The processor chip only seems to be able to sink/source 0.5ma (or 5ma in high current drive mode) .Are there additional buffers connected to pins 0,1,2 that allow a higher current? Jim From damien.p.george at gmail.com Wed Aug 31 02:23:18 2016 From: damien.p.george at gmail.com (Damien George) Date: Wed, 31 Aug 2016 16:23:18 +1000 Subject: [Microbit-Python] micro bit pin drive current In-Reply-To: <212d867d-7dfc-ba8f-41c4-5ea7a87580e7@yahoo.co.uk> References: <212d867d-7dfc-ba8f-41c4-5ea7a87580e7@yahoo.co.uk> Message-ID: There are no additional buffers on the pins. The microcontroller will source/sink its maximum current and then the output voltage will begin to drop to keep the current at that maximum (and so act like a current regulator/limiter). On 31 August 2016 at 15:48, fresh.bread via Microbit wrote: > I'm a bit worried by the diagram on the documentation for the micropython > speech module showing a loudspeaker connected directly to pins 0 and 1 (see > http://microbit-micropython.readthedocs.io/en/latest/tutorials/speech.html) > > What is the maximum drive current for the pins. The processor chip only > seems to be able to sink/source 0.5ma (or 5ma in high current drive mode) > .Are there additional buffers connected to pins 0,1,2 that allow a higher > current? > > Jim > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit From nevil.hunt at hotmail.co.uk Wed Aug 31 03:43:02 2016 From: nevil.hunt at hotmail.co.uk (Nevil Hunt) Date: Wed, 31 Aug 2016 07:43:02 +0000 Subject: [Microbit-Python] PyCon UK zbit:connect proposal Message-ID: Hi, In June I put forward a proposal to demonstrate my prototype "zbit:connect" boards for the BBC micro:bit on the Friday at this years PyCon UK. At the time I got an email acknowledging receipt of the proposal but since then I've not heard anything. Last week I sent another email but I've still not heard anything. Does anyone know who else I could contact? The "zbit:connect" boards make it easier to attach more sophisticated electronics to the micro:bit such as boards using the I2C and/or SPI busses and the only one of the 4 main micro:bit languages which supports driving these busses is micro python, hence it would be good to demonstrate them at PyCon UK to showcase some of the things micro python can do! I was looking to have space for a couple of tables for people to drop by during the day for a demo. Cheers, Nevil -------------- next part -------------- An HTML attachment was scrubbed... URL: From ntoll at ntoll.org Wed Aug 31 03:52:23 2016 From: ntoll at ntoll.org (Nicholas H.Tollervey) Date: Wed, 31 Aug 2016 08:52:23 +0100 Subject: [Microbit-Python] PyCon UK zbit:connect proposal In-Reply-To: References: Message-ID: Hi Nevil, I'm sorry to hear PyCon UK have not got back to you. I was one of the organisers last year and so I know those running this year's conference. I know from experience that volunteer led conferences are logistical nightmares that take up a huge amount of personal time and effort and I can only but surmise that they're a bit snowed under. I'll ping some of the people I know and hopefully you'll get some sort of a response soon. I look forward to catching up at PyCon UK! N. On 31/08/16 08:43, Nevil Hunt wrote: > Hi, > > > In June I put forward a proposal to demonstrate my prototype > "zbit:connect" boards for the BBC micro:bit on the Friday at this years > PyCon UK. At the time I got an email acknowledging receipt of the > proposal but since then I've not heard anything. Last week I sent > another email but I've still not heard anything. Does anyone know who > else I could contact? > > > The "zbit:connect" boards make it easier to attach more sophisticated > electronics to the micro:bit such as boards using the I2C and/or SPI > busses and the only one of the 4 main micro:bit languages which supports > driving these busses is micro python, hence it would be good to > demonstrate them at PyCon UK to showcase some of the things micro python > can do! I was looking to have space for a couple of tables for people to > drop by during the day for a demo. > > > Cheers, > > > Nevil > > > > _______________________________________________ > 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 Wed Aug 31 04:27:10 2016 From: nevil.hunt at hotmail.co.uk (Nevil Hunt) Date: Wed, 31 Aug 2016 08:27:10 +0000 Subject: [Microbit-Python] PyCon UK zbit:connect proposal In-Reply-To: References: , Message-ID: Thanks Nicholas, I suspect you are right that they are probably snowed under. Hopefully they can find me some space and if so I look forward to seeing you again in a couple of weeks! Nevil ________________________________ From: Microbit on behalf of Nicholas H.Tollervey Sent: 31 August 2016 08:52 To: microbit at python.org Subject: Re: [Microbit-Python] PyCon UK zbit:connect proposal Hi Nevil, I'm sorry to hear PyCon UK have not got back to you. I was one of the organisers last year and so I know those running this year's conference. I know from experience that volunteer led conferences are logistical nightmares that take up a huge amount of personal time and effort and I can only but surmise that they're a bit snowed under. I'll ping some of the people I know and hopefully you'll get some sort of a response soon. I look forward to catching up at PyCon UK! N. On 31/08/16 08:43, Nevil Hunt wrote: > Hi, > > > In June I put forward a proposal to demonstrate my prototype > "zbit:connect" boards for the BBC micro:bit on the Friday at this years > PyCon UK. At the time I got an email acknowledging receipt of the > proposal but since then I've not heard anything. Last week I sent > another email but I've still not heard anything. Does anyone know who > else I could contact? > > > The "zbit:connect" boards make it easier to attach more sophisticated > electronics to the micro:bit such as boards using the I2C and/or SPI > busses and the only one of the 4 main micro:bit languages which supports > driving these busses is micro python, hence it would be good to > demonstrate them at PyCon UK to showcase some of the things micro python > can do! I was looking to have space for a couple of tables for people to > drop by during the day for a demo. > > > Cheers, > > > Nevil > > > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit Microbit Info Page - Python mail.python.org The MicroBit is a small programmable device for children created by the BBC (in partnership with various other organisations, such as the PSF). > -------------- next part -------------- An HTML attachment was scrubbed... URL: From peter.inglesby at gmail.com Wed Aug 31 04:33:02 2016 From: peter.inglesby at gmail.com (Peter Inglesby) Date: Wed, 31 Aug 2016 09:33:02 +0100 Subject: [Microbit-Python] PyCon UK zbit:connect proposal In-Reply-To: References: Message-ID: Hi Nevil, I'm the chair of PyCon UK this year, and I'm really sorry that there's been a lack of communication here. I'll look into this today. Thanks for being understanding, Peter. On 31 August 2016 at 08:43, Nevil Hunt wrote: > Hi, > > > In June I put forward a proposal to demonstrate my prototype > "zbit:connect" boards for the BBC micro:bit on the Friday at this years > PyCon UK. At the time I got an email acknowledging receipt of the proposal > but since then I've not heard anything. Last week I sent another email but > I've still not heard anything. Does anyone know who else I could contact? > > > The "zbit:connect" boards make it easier to attach more sophisticated > electronics to the micro:bit such as boards using the I2C and/or SPI busses > and the only one of the 4 main micro:bit languages which supports driving > these busses is micro python, hence it would be good to demonstrate them at > PyCon UK to showcase some of the things micro python can do! I was looking > to have space for a couple of tables for people to drop by during the day > for a demo. > > > Cheers, > > > Nevil > > _______________________________________________ > Microbit mailing list > Microbit at python.org > https://mail.python.org/mailman/listinfo/microbit > > -------------- next part -------------- An HTML attachment was scrubbed... URL: