-
-
There's an stm32 cryptographic library: http://www.st.com/web/en/catalog/tools/PF259409
It would be handy to have access to things like aes as a native module for performance reasons, but I guess it'd have to be an optional inclusion into the firmware add must people wouldn't use it.
-
@Gordon will you be making any other usb interfaces available? I'm asking because I was thinking it'd be cool to be able to present html files over mass storage to be able to talk to the Espruino without needing drivers. Kind of like how the Nucleo boards show an error file over mass storage when the st-link isn't connected to something.
-
-
Yeah, it would be a good one to compile in by default, if there's space for it. (Or maybe a candidate for implementing as an installable module, like the new ESP8266 module... but I suspect that's no easy task)
I tried the sd card functions on my Nucleo board yesterday and they were undefined. If I get a chance I'll try compiling firmware for it with USE_FILESYSTEM=1 and give it a go, I've got an sd module I've been meaning to try out...
-
I think you need to compile the firmware for it yourself, as filesystem isn't defined in the makefile for the pico. See this thread: http://forum.espruino.com/conversations/252934/
-
-
@Gordon Awesome. Freeing up flash was why I asked.
-
My code was minifying, just not completely. It's not a problem with the IDE, or even the compiler I suppose, just a quirk in the process.
Private constants was the main thing that wasn't minifying. One of the reasons was that in one of my functions I was referring to a value not listed in the array, which wouldn't normally be a problem until that function is called. It looks like closure compiler just skipped C and moved on without an error.
-
-
-
-
Okay, thanks, good to know. I suppose that once implemented, features can be ported to internal functions if they prove popular.
Btw, NVRAM/EEPROM is handy for storing things like network addresses for when you're running the same code on multiple devices. But I suppose with Espruino you can just set it into a variable and hit save(). :)
-
@Gordon - I wanted to ask about this but didn't want to take over that other thread...
Is it better to add on-chip low-level features to jshardware.c or as modules? For something like NVRAM I think that basic read/write, or at least the address would be great to have built in.
Also, I did not know about process.env, it looks quite handy.
-
-
-
-
-
-
@Gordon how did you attach the ESP8266 shim? It has a very low profile, are the espruino and the ESP8266 soldered straight to the shim?
-
-
It's good to get a closer look of the final pico board. You've done well to squeeze so much onto such a small space in a very usable layout.
It's good to see some pico specific tutorials for first-timers. A page about the adapter shims in general could be good, unless you just want to add to the relevant other tutorials.
-
Is there a link somewhere for sending money to @Gordon/Espruino? I know that getting any financial contributions hasn't gone well in the past, despite the awesomeness of the software, but it might change as popularity increases with the release of the Pico. I'm specifically asking because I'm thinking of running Espruino on a version of the sensor nodes that I'm building for use in my house, and if I do I'd like to be able to contribute back a bit.
-
@Gordon do you think you'd keep the same 0.05" header on any future espruino boards? Not necessarily the same pins, but maybe the same functions. It'd be great to build things knowing that they can be used on newer boards. Also, on this track, maybe an original espruino to nano adapter could be useful.
I use Dfrobot for my pcbs and they've been good and cheap. They've done a couple of snap apart boards for me and they worked well.
Half an hour in and you've already got 24 orders? I think there's some demand. :)