Another New Chip, BBC Micro:Bit Go
erco
Posts: 20,256
Just saw this in a Fry's ad, know nothing about it. It's getting hard to keep up with every new STEM item that promises "learn to code". I'm neither endorsing nor planning to buy, just pointing out.
http://www.frys.com/product/9204099#detailed
http://www.frys.com/product/9204099#detailed
Comments
Give me a Propeller and a Pi. That covers most things I want to do. At least non-professionally.
The BBC Micro Bit seems to be a thing back home in Blighty as they have some kind of plan to make them available to all school kids there.
From the UK, and earliest candidate versions had an AVR in them, but that morphed to a couple of ARM's.
I like the large holes for banana plugs and the edge connector hybrid. Nicely covers a couple of IO choices bases there.
There are multiple editor options including a MS Blocky type and a Python Editor that can be used to code the Micro:Bit.
this should answer your question (starting at 12:47):
This was in the days of only four TV channels (two of which were BBC) and it took seriously its (unstated) remit for education (it was a nationalised company then, perceived as a benevolent partner to other
organisations such as the Department for Education). Lots more channels and the need to show a profit and so anything to do with science / technology took a back seat in favour of lowbrow shows that got the ratings.
And of course the Raspberry Pi and Micro Bit are ARM based. The circle is complete. The Pi has shipped 13 million units. Far more than the BBC micro ever did.
I would not say it did not amount to much!
It's a bit limited compared to other Espruino running micro-controllers. But I guess Micro Python is as well.
As far as I can tell this has 256 kbytes of FLASH and 16 kbytes of RAM.
From this thread https://github.com/bbcmicrobit/micropython/issues/71 :
"We've been working with the Nordic BLE stack for sometime now to help support the other languages, and it really is a VERY memory intensive (and a rather invasive beast). The stack needs about 100k of FLASH, statically allocated... and that's for the smallest version of the 'soft device' stack currnently available chip. In addition, the stack also statically reserves 8K of SRAM before it starts. It also need another 1.5K SRAM to support its SDKs, and consumes up to 2K more on the stack when any deep interrupts fire."
"Even with enough RAM (eg on a 32k device) it's still going to be hard to support BLE because of the flash requirements: the soft device needs 112k, leaving 144k for application."
If you find out that some progress has been made please post. The radio API could be fun to play with though - looks very simple. But I was hoping for BLE.
Edited to add: too bad they didn't use the Nordic nRF52832 with 64 kbytes RAM and 512 kbytes FLASH instead of the nRF51822, but I guess it would have driven the cost up. (Some comparisons here - https://devzone.nordicsemi.com/blogs/792/new-features-in-nrf52/)
Espruino discusses what they had to cut here - http://www.espruino.com/MicroBit
https://makecode.microbit.org/#
I was in Fry's so I had to pick up a pair of these. I've attached some images so you can see how the "Go" version is packaged. This just adds a AAAx2 battery pack and a pathetically short USB cable.
On my old HP chromebook getting it to mount as a drive seems to be a bit flakey, but I was able to get it to work. It works better with OS X Yosemite.
I was curious what goes on behind the scenes, so I tried looking through the generated hex file to see what javascript engine is being used but couldn't figure it out. (Using srec_cat and strings. I can find the names of some .c files, but they don't look javascript related.)
Edited to add: I guess this is what is used? "MakeCode’s underlying programming language is a subset of TypeScript, omitting JavaScript dynamic features."
https://makecode.com/about
All this effort has to be good news for P2, as those languages and flows and code sizes are right in P2 ballpark.
Better than RaspPi, which lets developers be much lazier in coding.
I was thinking a PiZero form factor made sense for a P2 compact Module, but maybe there is room for a micro:bit format too ?
You got it, pal! With twins, I need two of everything!
One possible demo for these boards would be to remote control robots of course. For example as far as I can tell, this should be trivial to accomplish - http://learn.parallax.com/tutorials/xbee-wireless-sumobot-tilt-controller
There is a Connector Breakout board for the MocroBit, and I have seen folks just bolt on a header using the holes on the board to gain access to the other pins.
https://kitronik.co.uk/5601-edge-connector-breakout-board.html
However, such a board would be interesting with a Propeller 44-Pin QFP on it.
...but doesn't Mrs. Erco have three kids???
I went to my local Micro Center to buy a "Raspberry Pi 3 kit" that contained a Raspberry Pi3, a 7" LCD display (800 x 480 pixels) with a driver board (The driver board takes in Composite Video, VGA, and HDMI as inputs). The kit also included a bunch of other accessories. I can also use the display with my "Propeller Hydra" and "Propeller Demo" boards.
I saw the "BBC Micro:Bit Go version kit" on the shelf, so I picked one up. I have not powered it up yet.
There was not very much Parallax stuff in the store, so sad :frown:, but I did buy a Parallax 4 x 20 Serial LCD (Backlit) (#27979-RT) on closeout for $17.91.
I wish the "Propeller 2" chip was complete, so I could be using it in my projects. But, the P2 development seems to be like the "Eveready Energizer Bunny", it just keeps on going, and going, and going.
I am active in a local Hackerspace and often direct "Newbies" visiting our Hackerspace to the local Micro Center store, so they can get started with robots and micros. But it is very hard to get them started with Parallax products if they are not available in the local store.
During my visit to Micro Center, I was also happy to see more electronic components and related items in the hobby electronics section. Since, all the local RadioShack(s) have now closed, Micro Center seems to be expanding their selection.
You got that right!
It's the new math! Common core! No child left behind!
Interesting idea. Micro:bit is not much more $ than a WiFi module, but IO limited.
Any ideas on connector prices ?
https://www.adafruit.com/product/3342
I'm thinking that both should display the radio group number on their LEDs. One button could be used to change groups. And maybe the other button on the transmitter could enable/disable the servos. So you can easily control starting/stopping the beast.
Anyways - one way to demonstrate that Parallax and Micro:bit can coexist. I always thought that anyone doing Sumobot should spend some time controlling the bot to get a feel for it. And maybe kids would enjoy kids versus robot. I had put on an ESP8266 board into a sumobot before and used Roboremo, but this Micro:bit approach seems much easier and doesn't require a smartphone/tablet.
Edited to add: Also for anyone who's interested in what Fry's think "Makers" want: http://images.frys.com/art/email/071317_thu973grx_Maker/Maker_web.html