Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build ESP32-Duktape from source #34

Closed
njacot opened this issue Jun 6, 2018 · 1 comment
Closed

build ESP32-Duktape from source #34

njacot opened this issue Jun 6, 2018 · 1 comment

Comments

@njacot
Copy link

njacot commented Jun 6, 2018

Hi there,

I am trying to build ESP32-Duktape from source but I get an error.
I followed this doc https://github.com/nkolban/duktape-esp32/blob/master/docs/Building%20duktape%20from%20github.md
what I did:

  1. Download/extract the latest duktape release
  2. Create component.mk with all the modifications listed in the doc
  3. I did not follow the optional section.
  4. Then make duktape_configure

Then I just do not know exactly what is the next step. I tried to launch
make ship command but I get the following error:
+--------------------+ | Building espfs.img | +--------------------+ /bin/sh: ../bin/mkespfsimage: cannot execute binary file make: *** [images] Error 126

Any ideas what I am missing or doing wrong?
I am on MacOs if that can help
Thanks a lot

@njacot
Copy link
Author

njacot commented Jun 8, 2018

So, I figured the issue.
I had to use the proper mkespfimage and mkspiffs.
I built mkespimage from here: https://github.com/Spritetm/libesphttpd/tree/master/espfs/mkespfsimage
and spiffs from here: https://github.com/igrr/mkspiffs/releases

Now I can build the all project and flash it to the esp32.

The access point web page works and I can connect the board to the local wifi.
The web IDE do not work for now. It is maybe an issue with the SPIFFS version since I took the latest one(0.2.3).

When I try to connect to the web IDE, I get this error:
D (58105) module_fs: - Path to open is "/spiffs/web/ide.html" and flags are "r" D (58115) module_fs: << js_fs_openSync fd: 3 D (58115) module_fs: >> js_fs_readSync D (58115) module_fs: Buffer pointer size returned as 128 D (58125) module_fs: js_fs_readSync: read() error: 5 I/O error

which seems to be the same issue as #24
so, this can be closed I think for now

@njacot njacot closed this as completed Jun 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant