Search results for:

Yep, holding BTN1 works.

I haven't used Espruino (or my micro:bit) for a while, I downloaded the latest (1v90) for the microbit and flashed it, however save(); either isnt working or has severely changed since 1v86. @Gordon helped me with this before.

This is the code i have:

function m() {
  show(0b1);
}
function onInit(){
  m();
}
save();

on 1v86 this is the output:

on 1v90 this is the output:

2 Things
1) I don't know why on 1v90 it thinks its 4200 bytes and on 1v86 it is just 3720...
2) If i power my microbit with 1v86 after running that code it displays the first led (correct) on 1v90, nothing happens.

Quick question about bluetooth / nRF, I noticed in changelog it has been changed, however I am unsure of how to change the broadcast name from "ESPRUINO Microbit" it just says

options is an object, which can contain:

{
name: "Hello" // The name of the device
showName: true/false // include full name, or nothing
discoverable: true/false // general discoverable, or limited - default is limited
interval: 600 // Advertising interval in msec, between 20 and 10000
}

And i dont really understand it..

Yep, thanks!

I downloaded from the "cutting edge" builds espruino_1v86.206_microbit.hex and now it works fine, I can save code and run code on it. I see someone made a fix in github.

Yeah, I found these commands, it doesn't show flash.

Is there a way to show the amount of memory avaliable?

If I use espruino 1v86 on my microbit you get this error when calling save:

Erasing Flash...
Writing...
ERROR: Too big to save to flash (244 vs -4 bytes)
Deleting command history and trying again...
Erasing Flash...
Writing...
ERROR: Too big to save to flash (163 vs -4 bytes)

however if I use espruino 1v85 I can save files all day long. for 1v86 i even enabled the minification in the web IDE which said it minifed from 41bytes to 8, this still didnt allow the save in 1v86, only works in 1v85.

EDIT: If i use any form of minification with 1v86 it fails because it changes things like show(1); to ho(1);