MicroPython Forum (Archive)

On a V1 micro:bit I had some success with this for driving directly one physical row (2nd one from top). MicroPython v1.9.2-34-gd64154c73 on 2017-09-01; micro:bit v1.0.1 with nRF51822 Type "help()" for more information. >>> >>> import machine >>> import microbit >>> display.off() >>> OUTSET = 0x5000...

It would also be useful to be able to change the playback rate. I ended up duplicating the samples to play a file at half speed for Halloween laughing skeleton using Cytron EDU:BIT and BBC micro:bit (YouTube). For anyone interested, more detail on that in Instructables: Halloween Spooky Ghost With B...

I squashed as much as I could into the 30k: Instructables: PIR Movement Alarm With BBC Micro:bit and External Speaker - YouTube video in step 5 with the sample playback. Would be nice to see this raised and perhaps with a marker/warning showing when you go above 30k for projects developed on the V2 ...

The micro:bit V2 has 512kB flash (double that of the V1) but it appears to still have the same ~30kB reserved for files? I wanted to do a bit of audio sample playback and I can't fit it all into 30k. Is there an easy way to change/extend this?

I have some audio playing (unsigned 8bit raw files) on a V2 as I type this. from microbit import * import audio import math def frames_from_file(sfile, frame): # 32 is length of AudioFrame while(sfile.readinto(frame, 32) > 0): yield frame def play_file(filename): frame = audio.AudioFrame() with open...

I've had a few troublesome MemoryError exceptions in CircuitPython recently and from what I've seen on MicroPython on micro:bit the issue is the same. The tricky ones for me fall into four categories: feels like there's enough memory around but still fails, sometimes explicity gc.mem_free() "profili...

I can't find the documentation for the BBC micro:bit MicroPython's get_mode() method on the pins. It appears to be set all the time to a useful value apart from for read_analog() where it returns unused for some reason? MicroPython v1.9.2-34-gd64154c73 on 2017-09-01; micro:bit v1.0.1 with nRF51822 T...

I noticed this in CircuitPython but just tested a micro:bit and it does the same thing. bytes() makes a new copy of an object even if it's bytes() already. MicroPython v1.9.2-34-gd64154c73 on 2017-09-01; micro:bit v1.0.1 with nRF51822 Type "help()" for more information. >>> >>> a = b"Original" >>> b...

Thanks for the info. It reminds me of the days of peek and poke!

Is it possible to access the pins for the rows of the LED display to allow direct, low-level control of the LED screen after a display_off(), of course? The columns appear to be available as microbit.pinX but I've not worked out how to access the rows.