Most recent activity
-
also, . . . . should that search box not return what might be expected,
Launch a new Google page instance and type a concise request using the 'site:' keyword qualifier. Google search something like:
how to illuminate the onboard LED for Pico
site:espruino.com
New interpreter error: FIFO_FULLsite:forum.espruino.com
-
Mon 2021.04.12
Hi @coolio were you aware there is search dialog at the upper right of most Espruino site pages? A wealth of information may be obtained with use of this tool.
The full Javascript API may be obtained from the main page:
Menu >> Documentation >> API Reference
Which contains detail on all current functions to perform the task you are after.
Class JSON for data formatting'understand if there is a way to load an array'
See ARRAY class:
'but there's no file system on the espruino'
See the FILE class:
http://www.espruino.com/Reference#l_File_read
http://www.espruino.com/Reference#fs
ESP8266 Class'I need to be able to store, retrieve'
I have been successful at off board storage with the AT24 series chips:
http://www.espruino.com/EEPROMs
http://www.espruino.com/AT24
Optional to RAM, Flashhttp://www.espruino.com/Data+Collection#line=123
http://www.espruino.com/File+IO
See post #17 by @hungryforcodes that the above link may not have been tested using ESP8266 yet.
http://forum.espruino.com/comments/15912413/
Another useful linkand of course the Javascript topic within the forum
-
'ok I tried the version 2v07 and I am still stuck at booting...BTN1 = reboot'
So, it appears to be code other than that of the firmware itself.
Have all four scenarios been tried beneath this heading: 'Powering-off' and
especially heading: 'Resetting without loading any code'
https://www.espruino.com/Bangle.js#powering-off
https://www.espruino.com/Bangle.js#resetting-without-loading-any-code
It would be of great help to know what was being worked on just prior, that is different enough
to cause this anomaly. -
Sat 2021.04.10
post #1 'This has been probably mentioned somewhere. But I am not able to locate it'
There is a nice tidy table with limits for all the original Espruino Devices.
For Future referenceFrom the FAQ page:
which hyperlinks to:
https://www.espruino.com/FAQ#how-much-power-can-i-supply-from-espruino-s-pins-
-
Sat 2021.04.10
Seems to be similar issue to what was just reported:
stuck in reboot loop, after flashing using nRT Toolbox and newest FW
-
Sat 2021.04.10
Seems to be similar issue to what was reported yesterday (2021.04.09):
Temporarily switch back to a previous version?
https://www.espruino.com/Bangle.js#firmware-updates
https://www.espruino.com/Download#banglejs -
-
Thr 2021.04.08
Thanks much @Gordon for that relative path. Now for the 'Friday Funnies!' We'll all get a good laugh at my expense. . . .
Lack of familiarity with VSCode caused me to have blinders on when using the hyperlink to both function definitions and declarations. I couldn't get passed why there was no corresponding .c file anywhere in each of the visible views. While using the file explorer within Windows10 was time consuming, and experience has taught me that if an internal System Service hasn't completed indexing, it is quite possible that the desired file is never (reasonable time frame) found. So I went to Google to search GitHub. None there either. So, I falsely determined that the content I was after was somehow pre-compiled into one of the .bin files used to flash Espruino, having no other explanation. Using the relative path that you provided, I searched GitHub again, and this time a result. So, curiosity forced me to find the reason why a search yesterday didn't locate that file.
Drum Roll Please . . . . . the funny part . . . .
I went through Chrome History to locate the search string. Couldn't believe my eyes! While I had used the wildcard '*' to perform the recusive file search using File Explorer yesterday, when I jumped to using the Browser, I had only searched for 'hardware.c' without the wild card as not permitted, at GitHub. Looks legit when typed, but somehow never registered the omission. okay, . . . . stop laughing . . . please!! ;-b)
Lesson here: Enjoy your youth and quick thinking mind while you have it - I'll get the last laugh on the other side
Back to the project:'The RTC only runs at 32kHz so you may find it's not accurate enough for you'
Yes, it is around 100 times too slow. I may resort back to triggering external clocking hardware with Javascript, and make use of the setWatch() GPIOTE peripheral to detect pulse edges.
'One of the Timers might be better'
The issue I had here was that I couldn't get a narrow enough pulse, and a train of pulses in a narrow enough time interval. Back then, I shelved the project at that point, but would need to put some time in to determine the limitations.
'Some of the hardware is used by Bluetooth and we have only limited control/usage of it'
Thanks for that tid-bit. I may resort back to the WiFi, also having the extra memory benefit.
My goal was to create a nice tutorial with a specific goal of a pulse generator and counter using the under utilized MDBT42Q breakout board. During that development, I discovered the lack of products with a suitable use within the music industry. Using a schmitt trigger, I created a proof of concept while working through the PPI link in post #1 above. Filtering out harmonics was doable with Javascript and some math I found online, but the response, around 1/3 second was just too slow, and the ear picks that up. External hardware may be my only choice. The tutorial would have covered both, with the intent to market the super-duper version, however, should I scrap that pie-in-the-sky goal, I may complete the limited slower range version for others to tinker with.
Sun 2021.04.18
Now that is cool!!
@OmegaRogue you'll have the foundation to get we tinker'ers to solve the issues that Google Glass could not!
How long to the Kickstarter kick-off? . . . Glasspruino ;-)
Curious, how is data to projection done? Bitmapping a graphics array to the proprietary projection unit via I2C / USB or something of the sort?
Found this one much larger though, RGB LED Pico Projector using HDMI as input