Espruino 1v88 released #117
Replies: 28 comments
-
Posted at 2016-11-10 by @yerpj great! |
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-11-10 by Frida Updated a Pico to 1v88, with the new editor. I had to put {} in the for loop, and it show faults in the right editor Attachments: |
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-11-10 by @gfwilliams Yes - the editor itself isn't expecting any ES6 functionality. That was updated on GitHub today (so wouldn't be in the version that you have to test with). Espruino itself should be fine though. |
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-11-10 by @yerpj Talking about promises, I just got this error message: |
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-11-10 by @gfwilliams @Jean-Philippe_Rey what code did you paste in? The character
|
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-11-10 by @yerpj @gordon I tried the method
|
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-11-10 by @gfwilliams It's because it got right to the end of Try Unfortunately the module gets minified, so what would have been a helpful variable name like |
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-11-10 by @yerpj ooooh that's totally true. I ever forget to give it the callback :-/ sorry for wasting your time with such beginners issues... |
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-11-10 by @gfwilliams No problem - you had me panicked for a while ;) |
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-11-11 by jlawson Flashed the 1v88 version onto several original Espruino 1.3 boards resulting in just the red LED on reset. I tried it with both the web IDE and command line. 1v87 works on all the boards. Jamie |
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-11-11 by @gfwilliams Ok, thanks for letting me know - I'd tested it quite recently, but obviously not with the release version! I'll see if I can get that sorted tonight. edit: That's a really odd bug- as you said, just tried here and my board worked great at first, even after a reset - but failed after a power off and on. It possibly explains why it passed the quick test I did before releasing. |
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-11-11 by @gfwilliams Ok, try again now. I've found the problem and updated the Original Espruino's image with the fix. Turns out it was to do with the Low Speed oscillator. The F1 behaves very slightly differently to the F4, and the startup code got stuck waiting for the RTC to initialise - unfortunately if you previously had a good firmware on the device then when you put the new one on everything will keep working until you power it off (as the RTC is already set up). |
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-11-11 by jlawson That did it. Excellent work. Thanks Gordon. |
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-11-12 by jlawson Further to this; after leaving the boards powered down for some time they again did not reset properly. As mentioned I have 32.768kHz crystals connected to these three boards but I do not have the 12pF caps mounted since they all worked fine without them. However, if I hold my finger over the 32.768kHz crystal leads they do reset properly and also reset properly if left powered after the initial successful boot. So it seems they may now require the capacitors. I will update this post when I dig up some appropriate caps. |
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-11-12 by @gfwilliams
...even with the new firmware? and it was fine on the older firmware? I've tried on the 1v4 boards and they seem fine (crystal + capacitors). It's possible that without capacitors the oscillator ran for a bit and then stopped, and it's causing that function to get stuck somewhere else waiting for the RTC to respond. |
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-11-12 by hilo90mhz Do you have any advice for building these on windows using Vagrant for the NRF52832DK? I have tried out the current vagrant setup but believe the version of arm-none-eabi-gcc it installs in the provision.sh script may not be compatible with the current master branch? https://github.com/espruino/Espruino/blob/master/scripts/provision.sh From what I can tell based on this link: you are building with the current version: Right now on gcc-arm-none-eabi-4_9-2015q1 it mostly works but fails at the end with this:
|
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-11-13 by jlawson @gordon Espruino 1v87 (using the binary from the website) has started up fine so far after numerous unpluggings etc. It reverts to start up problems when 1v88 is flashed on again. Also, with 1v88 loaded the web ide has trouble connecting: Edit: An Espruino 1.3 without a crystal works fine with 1v88. |
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-11-13 by jlawson With 1v87 it appears that holding my finger on the crystal leads actually STOPS the LSE from starting up, possibly because it does not detect the crystal. With 1v88 it seems to detect the crystal and attempts to use the LSE even though it hasn't started up. Checked with peek32(0x40021020), RCC_BDCR register, after reset. |
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-11-13 by hilo90mhz Okay I figured out my own problem :)
and line 2086 of makefile
I had to add the "python" preface which was missing before the call to hexmerge.py - this fixed the merging problem. Also to fix the vagrant setup problems I changed the provision.sh by adding the top three lines and commenting out the lower ones.
I also edited the vagrant_setup.sh to include the correct path to new version of gcc-arm-embedded
I am not sure this is all correct but when I upload hex files for the NRF52832DK they now show up as bluetooth devices and some basic commands work :) You can see the changes on my fork of Espruino here espruino/Espruino@master...clowrey:master |
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-11-14 by @gfwilliams @hilo90mhz Thanks for that - looks like vagrant probably hasn't been used in a while (I think most people just build directly on Linux) @jlawson strange - there was another change in there that I can remove as well. I'll give it a try on some 1v3 boards here. |
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-11-14 by @gfwilliams Ok, I've just produced a new build (It'll be at http://www.espruino.com/binaries/git/commits/b4edf13c51c825ca8ed032d7e31dec7a2759a20f within the hour). Could you try that? I've just removed all the RTC code changes that were there for the F1, so all being well it should behave exactly the same as 1v87. |
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-11-14 by jlawson @gordon - the link is broken but I have rebuilt the latest pulled version here. Works on three Espruino 1v3 with the LSE running and also with the finger stopped LSE. |
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-11-14 by @gfwilliams Ahh - thanks for letting me know - looks like after the server move my build machine stopped uploading the builds. Hopefully it'll be fixed soon. There's a regression in 1v88 I found today that I'd like to get fixed, so I'll push out a proper 1v89 build soon anyway I think. |
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-12-06 by CanyonCasa @gordon, for an original Espruino board (v1.4b) running 1v89, code entered right after a reset of an example right out of Mozilla Developer Network Arrow Function page ...
Hangs, and usually eventually generates an out of memory error message.
|
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-12-06 by @gfwilliams Can you try one of the cutting edge builds? I think this was fixed on those - unfortunately too late for the 1v89 build though |
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-12-06 by CanyonCasa I tried both the http://www.espruino.com/binaries/git/commits/master/espruino_1v89.964_espruino_1r3.bin and http://www.espruino.com/binaries/git/commits/master/espruino_1v89.964_espruino_1r3_wiznet.bin builds and PC does not recognize the USB port after either- not sure why that is. But the http://drazzy.com/espruino/bigram/espruino_1v89.7_1r3_bigram_wiznet.bin build does work and fixed the problem. Thanks. |
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-12-06 by CanyonCasa I tried both the http://www.espruino.com/binaries/git/commits/master/espruino_1v89.964_espruino_1r3.bin and http://www.espruino.com/binaries/git/commits/master/espruino_1v89.964_espruino_1r3_wiznet.bin builds and PC does not recognize the USB port after either- not sure why that is. But the http://drazzy.com/espruino/bigram/espruino_1v89.7_1r3_bigram_wiznet.bin build does work and fixed the problem. Thanks. |
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-12-06 by @gfwilliams Hmm - interesting - thanks... I'll take a look when I get a moment |
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-11-10 by @gfwilliams
This one's a massive release - containing a whole raft of improvements that were originally developed for Puck.js - which will be going into production early next week!
You can check out a full list of improvements here but in summary - and with a bit more info:
ES6 additions
(Sadly none of the above made it to the micro:bit, as it's just too short on Flash/RAM at the moment. They're in the Original Espruino, Pico, Wifi, and Puck.js though)
Improvements
opendrain_pullup
(so no resistor is needed for short runs on OneWire now)E.lockConsole()
for use withE.setPassword()
save()
anddump()
now keep track of whether pin mode had been forced or notfs.readFile
(andFile.read
) now use Flat Strings to allow more memory efficient readsnew Bob() => "Bob {}"
process.on(
uncaughtException, ...)
to catch exceptions along with the exact place in code that they happenedFixes
E.dumpLockedVars()
in non-release builds to help debug memory leaks in librariesSo loads of stuff... Sadly I had to remove the VGA/TV output from the Original Espruino to make room for it. It's still in Pico/WiFi boards though - let me know if you were using it on the Original board and I'll see what I can do to get it back in (however I don't think it has ever been used!).
There'll also be a new Web IDE release coming soon too.
Beta Was this translation helpful? Give feedback.
All reactions