Before I purchase the low.js Professional IDE, I want to verify the board I have meets the minimum hardware requirments.
Overview: I had onhand a generic ESP32-WROVER that provided the opportunity to quick test the functionality that NeoniousOne provides. Beyond the standard 'Hello World' and external 'Blinky' LED test, I've reached a reasonable limit of productivity and now time to explore more. Reading over the low.js Professional debugger IDE has generated
some curisoity questions.
From the opening paragraph at:
'If you have a generic ESP32-WROVER based board with a minimum of 16 MB Flash, you can flash low.js Professional'
indicates that a board requires 16MB of flash, to install the IDE,
beneath heading 'INTRODUCING NEONIOUS ONE The reference board for low.js Professional':
'240 Mhz, 4 MB RAM, 4 MB Flash dedicated to your application, with all files being compressed on the fly'
yet the NeoniousOne board itself only has 4MB.
According to the Espressif documentation, boards are 4MB flash
p.7 'ESP32-WROVER integrates a 4 MB of external SPI flash and an 8 MB PSRAM for more memory space'
Q1) Is the 16MB notation a documentation error? or, how does the NeoniousOne board differ such that the IDE runs with 4MB there?
'To flash, call lowsync flash --init --port=theport --pro --pro-key=thekey'
'THE ON-BOARD IDE Develop from any PC'
'Full file manager'
The IDE appears to be that of a MAC browser instance image, and the verbage 'Develop from any PC' is present along with a 'File Manager'
It is quite possible I haven't grasped how this environment works, but as the IDE seems to be installed onto the board, it is a bit puzzling how the IDE manages files. Are they the files on the PC, or files that are written to the board itself?
Q3) How is the IDE launched, once the key has been entered? From the Node.js Cmd Window perhaps or maybe the 'Key' somehow ties a PC based browser to the board the 'Key' pair has, only allowing comm between those specific devices. In which case launched from PC as a browser instance app and the 'File Manager' only accesses those files in the local Node development folder on the PC and no access to files on the device.
Should the later be the case, this seems problematic as:
A port need be specified to provide the key, but on Windows10, Com Ports are (can be) reassigned. I'm constantly blowing away the assignments in order to continue development, each time a new (any variety) device is connected, as when jumping between Arduino and other USB devices that retain previous overlapping Com port values.
Q4) Would this mean I might have to (when Com port assignments overlap) re-install (lowsync flash) the key each time I fire up the PC then?
With a better understanding, I may push forward to the IDE purchase.