MicroPython on the BBC micro:bit | Hacker News Reader

MicroPython on the BBC micro:bit

ntoll.org

154 pointsntoll32 comments

I'm the author of the linked article and involved in bringing Python to the BBC micro:bit. Happy to answer questions.

Can you talk about the hardware at all? Technical details seem really hard to come by.

e.g. Wikipedia suggests it's got two processors. That's application processor and a USB I/O processor, right? Which handles mass storage mode and bootstrapping the applications processor? Does it also provide a debugging interface, and can it be programmed? Have they exposed any JTAG pins for the applications processor? Are you required to use their toolchain or can I just womp something up with gcc and deploy it?

Unfortunately, I can't reveal any more about the hardware than is already in the public domain already. :-(

Happy to talk about MicroPython.

Sorry.

Is it a quantum computer? I am curious about the secret behind the device.

Can you talk about what kind of documentation will be released? Data sheet? programmer's manual? anything at all about the hardware?

Yes, you'll get all the digital assets needed to be able to re-create the hardware yourself as well as access to the software.

Obviously, we'll be documenting the MicroPython implementation. Other partners will do their own thing.

Oh, well, it was worth a try!

What was the porting experience like? I have a non-ARM low-end microprocessor it might be interesting to port MicroPython to.

I'm under NDA, but I believe we can talk about things that have already been disclosed.

If you do a google image search for large micro:bit images, you'll see there's a Nordic NRF51822 chip (Which is an ARM Cortex M0, with BLE), and a Kinetis ARM chip connected to USB. It's running an mbed-compatible bootloader that appears as a USB mass storage device. You just copy hex files onto it and it programs the NRF51822.

Does that google image show any markings on "Kinetis ARM chip"?

Ok, Wikipedia says it's KL26Z, also 16K RAM, good. I was concerned there may be some cheating with higher RAM available on it. But nope, folks now will really need to optimize stuff to do something useful in 16K ;-).

In your opinion was it best for BBC to develop their own device or should they have gone instead with the RPi (or Arduino or something else)?

Do you think Microsoft's involvement has enhanced the technical goals of the project, sounds like you really needed to shoe-horn MicroPython in there?

Do you think if MicroPython was a goal that they did the project right, anything major you'd have done differently?

Thanks.

The RPi has a different aim (to provide a full computer), whereas the micro:bit is to facilitate first steps with minimum effort. By using Python a child gets a sense of progression from one device to the next.

I can confidently say that all the partners are working very hard to fulfil the vision the BBC has of inspiring a new generation of digital makers, engineers and creatives. Each partner brings different skills, capabilities and expertise to the table. It's most certainly a case of the whole is bigger than the sum of its parts since we're all pulling together in the same direction.

Any idea when you're gonna be able to push the port of micropython to the kl26z onto your github?

Is this going to be an ongoing thing? I mean, after the device is distributed this coming year, will another batch will be sent to the students in the following year? I'm asking because my son will start secondary school at September 2016 and I would be very thrilled to have me, i mean - him, play with one.

I've heard that they will be available commercially next year through partners, but won't be distributed free to all students again.

The original launch said they'd go on sale by the end of 2015 to the general public, I don't know about the ongoing plans though.

The BBC and partners are working together to organise how the legacy will function. This could include a second drop next year. Others are correct, the device will be available for the general public to buy. Given the eventual openness of the plans and resources, you should also be able to order your own to be fabricated somewhere. ;-)

BTW... here's a playlist of MicroPython / micro:bit status videos made during development and at PyCon UK: https://www.youtube.com/playlist?list=PLzCYc445IVNQimtxAlPpa...

I tend to get fanboyish around MicroPython, because it dramatically lowers a lot of barriers between my rough web-plumbing skills and the world of embedded devices / IoT. Hopefully it will be the same for kids.

On related news, it's great to see the generation that grew up with the BBC Micro is now fully in charge and understands the power this sort of "social programs" can have.

As a web plumber, the Arduino (and Photon and all the other similar platforms) is very very easy to get started with. With minimal C experience, I made a mobile phone[1] and the software was, by far, the easy part.

I definitely recommend buying an Arduino or one of the clones that sell for $2 or so.

I'm very excited about MicroPython as well, though, can't wait to buy something that will run it. (EDIT: at almost $50 per pyboard, it turns out I can wait :( )

[1]: http://www.stavros.io/posts/irotary-saga/

The esp8266 runs it. With WiFi and costs 5 pounds with a USB interface. (Nodemcu)

Huh, that's very interesting, thanks! Does it come with MicroPython by default, or do you flash it?

I would have gone with Lua, personally, specifically eLua, but this is still pretty awesome.. for those who have the micro:bit already, whats it like? Do any of you guys have experience with giving one to kids and seeing what they do with it?

I'll get one for my kids eventually .. but for sure, I'd imagine eLua to be high on the list of things to get running on it.

EDIT: Lua would be better than Python, imho, because it doesn't require an editor for young minds to harness before they can get working code .. my experience with my 5 and 8 year old kids is that they absolutely are not interested in programming if everything has to line up right - as is the case with Python - but if there are less restrictions imposed on them by the language, the interest flourishes. To me, while Python is an easy language to learn, Lua is a better language to start with .. so if I were a micro:bit user, I'd be putting Lua/eLua on it ..

There is currently a version of Espruino for the Micro:bit too, so kids will have the ability to use JavaScript. You can even program/debug it over BLE as well :)

However there's been virtually no interest in it so I haven't spent as much time on it as I'd have liked. Hopefully that'll change when the boards start appearing though.

I'd be willing to help put Lua on the thing, if that's of any interest. I guess I'll start thinking about that when the boards ship and I have one available.

Am I right in understanding you put Espruino on the micro:bit - care to tell us more about that?

> Lua would be better than Python, imho, because it doesn't require an editor

Can you elaborate on this? How does Lua not require an editor? Is it spoken programming language or something?

> they absolutely are not interested in programming if everything has to line up right

Yeah, I was not quite coherent with that statement: I mean that Lua doesn't require that you learn to use an editor to line things up properly, a concept which my 5 and 8 year old kids definitely have an aversion to, since it seems like trivial nonsense (to them) to have to do formatting to make code work, having cut their teeth on the BASIC of our 8-bit battlestations set up for the task.

I just mean, to a new programmer - especially a young one - having to grasp alignment/editing concept is a stumbling block, and unnecessary when languages like Lua provide all the same degree of power as Python, and less to learn to get started..

Wow! Very nice to see how Damien saved the day with MicroPython!!

Damien is one of the most talented developers I've ever had the pleasure to collaborate with. Seriously amazing amounts of very clever work have gone into this.

I agree 100% :-)

Damien who? Github?

Reply on news.ycombinator.com