Most recent activity
-
-
@Gordon: Take your time. Espruino is great, but having a son is so much more :-)
-
I've made a PR to discuss my code: https://github.com/espruino/Espruino/pull/1255
The large lib is not a problem of code size on the due. It's ~250 MBs of Code in the Espruino Repo.
-
-
-
We now have access to all pins (I counted 63 Pins - impressive) and the SystemTimer for setInterval() and setTimeout() is working - kind of. Not very accuracte. I'm on it.
If someone wants to have a go, here are the Bin-Files: https://www.thomaschristlieb.de/wp-content/uploads/2017/09/espruinoduebin.tar.gz
I think after getting a real accurate Time (better than one Second!) I'm trying to get save() to Work...
-
I've got a REPL, I've got Pin Functions (Config, Get, Set) for the first Pin (the onboard LED). I think we can call it Alpha Status :-)
Next would be to get the setTimeout running by implementing jshGetSystemTime with the build-in RTC. Then I need to enter all possible pins (all 54!) and make the Pin Functions for them.
Thats a lot of work, but not very complicated anymore.
Hello Forum,
this little test may neither be fair nor exact but i still wonder about the outcome...
The Leibniz Formula is a little float Problem for calculating Pi.
I wrote the code in Python and Javascript and let it run on the PyBoard and the Espruino Pico.
Here‘s the Python-Code:
And here‘s the „same“ in Javascript:
On the PyBoard the code took 26 seconds to execute, the Pico took 458 seconds.
I‘m a little puzzled of the outcome because I though both boards have floating point hardware, or am I wrong?
Can anyone explain the massive speed difference to me?
Thomas
PS: I know that this synthetic benchmark has nothing to do with overall speed, I just want to understand why these numbers are what they are in this particular case.