Guru Mediation Error after changing access point #6

davidmoshal · 2017-01-20T19:58:24Z

Hi, I managed to connect to ESP32 Duktape, and change the access point.
However, the device appears to have crashed

There appears to be a 'Guru Mediation Error'

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
ets Jun  8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0x00
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3ffc0008,len:0
load:0x3ffc0008,len:1580
load:0x40078000,len:3648
ho 0 tail 12 room 4
load:0x40080000,len:256
entry 0x40080034
I (1005) heap_alloc_caps: Initializing heap allocator:
I (1005) heap_alloc_caps: Region 19: 3FFC1C34 len 0001E3CC tag 0
I (1006) heap_alloc_caps: Region 25: 3FFE8000 len 00018000 tag 1
I (1010) cpu_start: Pro cpu up.
I (1013) cpu_start: Single core mode
I (1016) cpu_start: Pro cpu start user code
I (1030) rtc: rtc v160 Nov 22 2016 19:00:05
I (1037) rtc: XTAL 26M
D (1048) nvs: nvs_flash_init_custom start=9 count=6
D (1084) phy_init: loading PHY init data from application binary
D (1085) nvs: nvs_open phy 0
D (1086) nvs: nvs_get cal_version 4
V (1100) phy_init: phy_get_rf_cal_version: 258

D (1140) nvs: nvs_get_str_or_blob cal_mac
D (1176) nvs: nvs_get_str_or_blob cal_data
D (1219) nvs: nvs_close 1
V (1231) phy_init: register_chipv7_phy, init_data=0x3f400fe8, cal_data=0x3ffc2d18, mode=0
I (1487) phy: phy_version: 258, Nov 29 2016, 15:51:07, 1, 0
D (1488) nvs: nvs_open phy 1
V (1488) phy_init: phy_get_rf_cal_version: 258

D (1497) nvs: nvs_set cal_version 4 258
D (1631) nvs: nvs_set_blob cal_mac 6
D (1635) nvs: nvs_set_blob cal_data 1904
D (2531) nvs: nvs_close 2
I (2532) cpu_start: Starting scheduler on PRO CPU.
D (2533) bootwifi: >> bootWiFi
tcpip_task_hdlxxx : 3ffc5810, prio:18,stack:2048
D (2535) nvs: nvs_open misc 1
D (2538) nvs: nvs_get_str_or_blob log
I (2541) wifi: frc2_timer_task_hdl:3ffc7270, prio:22, stack:2048

D (2547) nvs: nvs_open nvs.net80211 1
D (2551) nvs: nvs_get opmode 1
D (2553) nvs: nvs_get country 1
D (2556) nvs: nvs_get_str_or_blob sta.ssid
D (2560) nvs: nvs_get_str_or_blob sta.mac
D (2564) nvs: nvs_get sta.authmode 1
D (2567) nvs: nvs_get_str_or_blob sta.pswd
D (2571) nvs: nvs_get_str_or_blob sta.pmk
D (2575) nvs: nvs_get sta.chan 1
D (2578) nvs: nvs_get auto.conn 1
D (2581) nvs: nvs_get bssid.set 1
D (2584) nvs: nvs_get_str_or_blob sta.bssid
D (2588) nvs: nvs_get sta.phym 1
D (2591) nvs: nvs_get sta.phybw 1
D (2594) nvs: nvs_get_str_or_blob sta.apsw
D (2597) nvs: nvs_get_str_or_blob sta.apinfo
D (2602) nvs: nvs_get_str_or_blob ap.ssid
D (2605) nvs: nvs_get_str_or_blob ap.mac
D (2609) nvs: nvs_get_str_or_blob ap.passwd
D (2613) nvs: nvs_get_str_or_blob ap.pmk
D (2616) nvs: nvs_get ap.chan 1
D (2619) nvs: nvs_get ap.authmode 1
D (2622) nvs: nvs_get ap.hidden 1
D (2625) nvs: nvs_get ap.max.conn 1
D (2629) nvs: nvs_get bcn.interval 2
D (2632) nvs: nvs_get ap.phym 1
D (2635) nvs: nvs_get ap.phybw 1
D (2638) nvs: nvs_get ap.sndchan 1
D (2641) nvs: nvs_set_blob sta.mac 6
D (2645) nvs: nvs_set_blob ap.mac 6
I (2648) wifi: pp_task_hdl : 3ffc9ae0, prio:23, stack:8192
E (2653) wifi: timer:0x3ffb1124 cb is null

D (2657) bootwifi: >> bootWiFi2
D (2660) nvs: nvs_open bootwifi 1
D (2662) nvs: nvs_get version 4
D (2665) nvs: nvs_get_str_or_blob connectionInfo
D (2670) nvs: nvs_close 5
D (2672) bootwifi: - Connecting to access point "AU" ...
I (2678) wifi: mode : sta (24:0a:c4:04:b9:a0)
D (2681) event: SYSTEM_EVENT_STA_START
V (2685) event: enter default callback
V (2688) event: exit default callback
D (2692) bootwifi: << bootWiFi2
D (2694) bootwifi: << bootWiFi
I (4015) wifi: n:9 0, o:1 0, ap:255 255, sta:9 0, prof:1
I (4664) wifi: state: 0 -> 2 (b0)
I (4666) wifi: state: 2 -> 3 (0)
I (4671) wifi: state: 3 -> 5 (10)
I (4684) wifi: connected with AU, channel 9
D (4684) event: SYSTEM_EVENT_STA_CONNECTED, ssid:AU, ssid_len:2, bssid:00:1f:5b:87:f7:38, channel:9, authmode:3
V (4687) event: enter default callback
V (4692) event: exit default callback
D (8667) event: SYSTEM_EVENT_STA_GOTIP, ip:10.1.10.14, mask:255.255.255.0, gw:10.1.10.1
V (8667) event: enter default callback
I (8667) event: ip: 10.1.10.14, mask: 255.255.255.0, gw: 10.1.10.1
V (8673) event: exit default callback
D (8676) bootwifi: ********************************************
D (8682) bootwifi: * We are now connected and ready to do work!
D (8688) bootwifi: * - Our IP address is: 10.1.10.14
D (8692) bootwifi: ********************************************
D (8698) esp32_specific: >> setupVFS
D (8701) esp32_specific: << setupVFS
D (8705) esp32_mongoose: Mongoose task starting
D (8706) duktape_task: >> duktape_task
D (8706) duktape_main: >> telnetTask
D (8710) esp32_mongoose: Mongoose: Starting setup
mg_socketpair: 0x100007f 0x100007f
mg_socketpair debug A
D (8730) esp32_mongoose: Mongoose: Succesfully inited
D (8733) esp32_mongoose: Mongoose: Successfully bound to address ":80"
D (8784) duktape_utils: Console:
 ______  _____ _____ ____ ___
|  ____|/ ____|  __ \___ \__ \
| |__  | (___ | |__) |__) | ) |
|  __|  \___ \|  ___/|__ < / /
| |____ ____) | |    ___) / /_
|______|_____/|_|  _|____/____|
|  __ \      | |  | |
| |  | |_   _| | _| |_ __ _ _ __   ___
| |  | | | | | |/ / __/ _` | '_ \ / _ \
| |__| | |_| |   <| || (_| | |_) |  __/
|_____/ \__,_|_|\_\\__\__,_| .__/ \___|
                           | |
                           |_|
 http://duktape.org
 ESP32 port/framework: Neil Kolban


D (8819) duktape_utils: Console: esp32_duktape>
Guru Meditation Error of type InstrFetchProhibited occurred on core   0. Exception was unhandled.
Register dump:
PC      :  002c002c  PS      :  00060d30  A0      :  800ea862  A1      :  3ffc56f0
A2      :  00000001  A3      :  3ffcab40  A4      :  002c002c  A5      :  00000008
A6      :  00000000  A7      :  3ffbd5b8  A8      :  800e6ff4  A9      :  00000002
A10     :  3ffcab40  A11     :  00000001  A12     :  3ffbf87c  A13     :  00000000
A14     :  3ffc4ff4  A15     :  3ffbf660  SAR     :  00000013  EXCCAUSE:  00000014
EXCVADDR:  002c002c  LBEG    :  4000c2e0  LEND    :  4000c2f6  LCOUNT  :  ffffffff
Entering gdb stub now.
$T0b#e6

Some notes regarding changing the access point which you might want to incorporate back into your instructions.

I followed the instruction here:
https://github.com/nkolban/duktape-esp32/blob/master/docs/README.md

Your notes suggest typing "http://" in the url bar (without the quotes), which didn't work.
Eventually I figured out that the url has to be http://192.168.4.1 or whatever is reported from screen.

D (2662) bootwifi: **********************************************
D (2668) bootwifi: * We are now an access point and you can point
D (2674) bootwifi: * your browser to http://192.168.4.1
D (2679) bootwifi: **********************************************

You might want to make that more explicit...

Using the form to try and change the Access Point took a bit of trial and error, these were some of the issues:

I had the wrong password (there was no warning in screen about that)
I had to leave IP address, netmask and gateway blank
my laptop's wifi connection had a tendency to hop to another access point immediately following reset, probably correct behaviour on the part of the laptop, but worth reminding folks to make sure that they connect to the ESP32 access point as soon as screen says it's available.

So, now the ESP32 connects to the correct access point.
However, I was unable to ping the IP address 10.1.10.14, nor could I access it from a browser.

The text was updated successfully, but these errors were encountered:

nkolban · 2017-01-20T21:14:01Z

Howdy David,
I think the version you are using is old and tired ... I have uploaded the very freshest version and docs can be found here ... https://github.com/nkolban/duktape-esp32/blob/master/docs/installation.md

You will likely be the first person to be using it ... so I am all ears. Ping me live as needed if you need direct assistance... otherwise hoping to hear back from you ... Neil

davidmoshal · 2017-01-20T21:39:36Z

thanks, much appreciated.
I made a few notes above regarding the difficulties I faced.
All user error on my part, but probably worth noting in the docs.
I could make a few edits to your instructions and send a PR request if you like.
Dave
ps, what is a Guru Meditation Error ?

davidmoshal · 2017-01-20T21:41:55Z

oops, noticed that you incorporated the changes already!

davidmoshal · 2017-01-20T22:01:22Z

NICE!
Significantly smoother install than the Nov 30 build.
Rebooted by itself:

Notes:

there seems to be copious output on screen, lot's of low level debugging, initially I thought it was throwing errors, but I think it's all low-level debugging.
Clicking 'run' with the `console.log("Hello World") results in:

D (28745) log: selectResult: {"readfds":[0],"writefds":[],"exceptfds":[]}
D (28745) log: loop: working on ready to read of fd=0
D (28745) module_os: >> js_os_accept
D (28755) module_os:  About to call accept on 0
D (28755) module_os: << js_os_accept: new socketfd=1
D (28765) log: We accepted a new client connection: {"sockfd":1}
D (28775) log: IDE_WebServer: We have received a new HTTP client request!
D (28775) dukf_utils: requestHandler: heapSize=30532
D (28805) log: selectResult: {"readfds":[1],"writefds":[],"exceptfds":[]}
D (28805) log: loop: working on ready to read of fd=1
D (28805) module_os: >> js_os_recv
D (28815) module_os: -- js_os_recv: About to receive on fd=1 for a buffer of size 512
D (28815) module_os: << js_os_recv: length=480
D (28825) log: Length of data from recv: 480
D (28825) log: http parsing: POST /run HTTP/1.1
D (28835) log: http Method: POST, path: /run
D (28835) log: http parsing: Host: 10.1.10.14:8000
D (28845) log: http parsing: Connection: keep-alive
D (28845) log: http parsing: Content-Length: 29
D (28855) log: http parsing: Accept: */*
D (28855) log: http parsing: Origin: http://10.1.10.14:8000
D (28855) log: http parsing: X-Requested-With: XMLHttpRequest
D (28865) log: http parsing: User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36
D (28875) log: http parsing: Content-Type: application/javascript
D (28885) log: http parsing: Referer: http://10.1.10.14:8000/web/ide.html
D (28895) log: http parsing: Accept-Encoding: gzip, deflate
D (28895) log: http parsing: Accept-Language: en-US,en;q=0.8
D (28905) log: http parsing: 
D (28905) log: End of headers
{"Host":"10.1.10.14:8000","Connection":"keep-alive","Content-Length":"29","Accept":"*/*","Origin":"http://10.1.10.14:8000","X-Requested-With":"XMLHttpRequest","User-Agent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36","Content-Type":"application/javascript","Referer":"http://10.1.10.14:8000/web/ide.html","Accept-Encoding":"gzip, deflate","Accept-Language":"en-US,en;q=0.8"}
D (28945) log: HTTP Request on(data) passed: console.log("Hello World\n");
D (28955) log: HTTP Request on(end):
D (28955) log:  - method: POST
D (28955) log:  - path: /run
D (28965) log:  - headers: {"Host":"10.1.10.14:8000","Connection":"keep-alive","Content-Length":"29","Accept":"*/*","Origin":"http://10.1.10.14:8000","X-Requested-With":"XMLHttpRequest","User-Agent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36","Content-Type":"application/javascript","Referer":"http://10.1.10.14:8000/web/ide.html","Accept-Encoding":"gzip, deflate","Accept-Language":"en-US,en;q=0.8"}
D (29005) dukf_utils: ide_webserver: request.on(end): heapSize=22052
D (29005) log: We are about to run: console.log("Hello World\n");
D (29015) modules: >> js_console_log called
D (29015) log: Console: Hello World

D (29025) module_os: >> js_os_send
D (29025) module_os: About to send 17 bytes of data to sockfd=1
D (29025) module_os: - data: "HTTP/1.1 200 OK
"
D (29035) module_os: << js_os_send
D (29035) module_os: >> js_os_send
D (29045) module_os: About to send 2 bytes of data to sockfd=1
D (29045) module_os: - data: "
"
D (29055) module_os: << js_os_send
D (29055) module_os: >> js_os_shutdown
D (29055) module_os: About to shutdown fd=1
D (29055) module_os: << js_os_shutdown
D (29065) module_os: >> js_os_close
D (29065) module_os: About to close fd=1
D (29075) module_os: << js_os_close

but nothing in the Console at the bottom of the page.

nkolban · 2017-01-20T22:36:52Z

At this time, I had to disable the console output because we ran out of memory ... however ... that is hoped to be a temporary story. All appears to be working, if we look in your console log from the ESP32, we see the "Hello World" message.

davidmoshal · 2017-01-20T22:49:54Z

How are we dividing usage of processor memory vs spi memory?
According to the sparfun specs my board has 520k SRAM and 4m flash.
I recall the days of the parallax stamp where the interpreter was otp'd onto the chip, and user programs ran out of external memory.

nkolban · 2017-01-20T22:59:45Z

SPI memory (aka flash memory) is slow read/write memory ... that can only be written in 64K blocks but is permanent until it is re-written. Its content remains when power is removed. RAM (Random Access Memory) is very fast and readable/writable at the byte level but its content is lost when power is removed. The ESP32 modules have 4MBytes of flash and 512KBytes of RAM. The programs that the ESP32 runs written into flash and mapped to the address space of the ESP32 CPU. They are then executed from flash. Working storage (the storage that is used for variables) and some time critical functions are stored in RAM.

Currently, when a JS program is sent to the ESP32, it is sent as a text string (the source). This is transiently kept in RAM. The Duktape compiler then compiles the source to "bytecode" which is itself held in RAM and the original source released. The Duktape virtual machine (VM) then interprets the byte code to run the script. A goal is to have Duktape compile the JS to byte code and save that byte code in flash as opposed to RAM. This would free up the RAM currently held by the bytecode which (in principle) should be read-only. Unfortunately, I haven't been able to get that feature operational on the ESP32 and am working with the Duktape author to see what can be done. Its is NEW function in Duktape and all bets are still off on it. If you have time and inclination, have a good study of the docs of Duktape itself (www.duktape.org).

davidmoshal · 2017-01-20T23:26:24Z

A goal is to have Duktape compile the JS to byte code and save that byte code in flash as opposed to RAM.

Basically a JIT, no? I actually saw that in the Duktape docs a few weeks ago, just assumed you were doing that.

How are you debugging the ESP32? Is there a way to watch the memory allocation as you can in Java programs (or in Chrome)?

davidmoshal · 2017-01-20T23:32:51Z

btw- I'm not seeing anythin in the Chrome console, other than "Code sent for evaluation"

davidmoshal · 2017-01-20T23:46:48Z

Looking in the source of ide.html, I see that ide.js sends a post request with the script to execute.
So, using Postman, and sending: http://10.1.10.14:8000/run with body of:

console.log('hi')

I get nothing back other than 200 response code.

D (680179) log: selectResult: {"readfds":[0],"writefds":[],"exceptfds":[]}
D (680179) log: loop: working on ready to read of fd=0
D (680179) module_os: >> js_os_accept
D (680189) module_os:  About to call accept on 0
D (680189) module_os: << js_os_accept: new socketfd=2
D (680199) log: We accepted a new client connection: {"sockfd":2}
D (680209) log: IDE_WebServer: We have received a new HTTP client request!
D (680209) dukf_utils: requestHandler: heapSize=28872
D (680239) log: selectResult: {"readfds":[2],"writefds":[],"exceptfds":[]}
D (680239) log: loop: working on ready to read of fd=2
D (680239) module_os: >> js_os_recv
D (680249) module_os: -- js_os_recv: About to receive on fd=2 for a buffer of size 512
D (680249) module_os: << js_os_recv: length=497
D (680259) log: Length of data from recv: 497
D (680269) log: http parsing: POST /run HTTP/1.1
D (680269) log: http Method: POST, path: /run
D (680269) log: http parsing: Host: 10.1.10.14:8000
D (680279) log: http parsing: Connection: keep-alive
D (680279) log: http parsing: Content-Length: 17
D (680289) log: http parsing: Postman-Token: 858ba495-94ab-1643-6b62-316cccd86a65
D (680289) log: http parsing: Cache-Control: no-cache
D (680299) log: http parsing: Origin: chrome-extension://fhbjgbiflinjbdggehcddcbncdddomop
D (680309) log: http parsing: User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36
D (680319) log: http parsing: Content-Type: text/plain;charset=UTF-8
D (680329) log: http parsing: Accept: */*
D (680329) log: http parsing: Accept-Encoding: gzip, deflate
D (680339) log: http parsing: Accept-Language: en-US,en;q=0.8
D (680339) log: http parsing: 
D (680349) log: End of headers
{"Host":"10.1.10.14:8000","Connection":"keep-alive","Content-Length":"17","Postman-Token":"858ba495-94ab-1643-6b62-316cccd86a65","Cache-Control":"no-cache","Origin":"chrome-extension://fhbjgbiflinjbdggehcddcbncdddomop","User-Agent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36","Content-Type":"text/plain;charset=UTF-8","Accept":"*/*","Accept-Encoding":"gzip, deflate","Accept-Language":"en-US,en;q=0.8"}
D (680389) log: HTTP Request on(data) passed: console.log('hi')
D (680389) log: HTTP Request on(end):
D (680399) log:  - method: POST
D (680399) log:  - path: /run
D (680399) log:  - headers: {"Host":"10.1.10.14:8000","Connection":"keep-alive","Content-Length":"17","Postman-Token":"858ba495-94ab-1643-6b62-316cccd86a65","Cache-Control":"no-cache","Origin":"chrome-extension://fhbjgbiflinjbdggehcddcbncdddomop","User-Agent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36","Content-Type":"text/plain;charset=UTF-8","Accept":"*/*","Accept-Encoding":"gzip, deflate","Accept-Language":"en-US,en;q=0.8"}
D (680449) dukf_utils: ide_webserver: request.on(end): heapSize=20372
D (680449) log: We are about to run: console.log('hi')
D (680459) modules: >> js_console_log called
D (680459) log: Console: hi
D (680459) module_os: >> js_os_send
D (680469) module_os: About to send 17 bytes of data to sockfd=2
D (680469) module_os: - data: "HTTP/1.1 200 OK
"
D (680479) module_os: << js_os_send
D (680479) module_os: >> js_os_send
D (680479) module_os: About to send 2 bytes of data to sockfd=2
D (680489) module_os: - data: "
"
D (680489) module_os: << js_os_send
D (680499) module_os: >> js_os_shutdown
D (680499) module_os: About to shutdown fd=2
D (680499) module_os: << js_os_shutdown
D (680509) module_os: >> js_os_close
D (680509) module_os: About to close fd=2
D (680509) module_os: << js_os_close

so, in addition to WS being disabled, it's not returning anything after the script POST.

nkolban · 2017-01-20T23:47:13Z

Chrome is of course a browser that happens also to host a JavaScript runtime engine. The Chrome console is the console to the JS engine built into Chrome. For Duktape, we have a Duktape based debugging environment that is documented here ... https://github.com/nkolban/duktape-esp32/blob/master/docs/debugger.md

It seems to run as advertized on the ESP32 environment. For the majority of my debugging, I simply add "log()" statements in my JS code and watch the console.

nkolban · 2017-01-20T23:50:47Z

For your POST test ... if you look at the trace output at time stamp 680459 you will see the output of the script in the console. The POST request to ESP32-Duktape is posting the "JavaScript source program" that we are asking ESP32-Duktape to run. Given that the program could run and be done straight away or run for hours ... there is nothing to send back to the browser as a response to the POST request other than a "200" code saying "I got it and will process it". The use of WebSockets provides a "stream" of data back from ESP32-Duktape back to the browser ... and as mentioned, that has been deliberately switched off right now until we can reduce memory consumption. No use having the WebSockets and and able to stream data back to the browser if we fail because we are out of memory for the most simplest of programs.

The source for the ESP32-Duktape side of the processing of the Web IDE requests can be found here ... https://github.com/nkolban/duktape-esp32/blob/master/filesystem/ide_webserver.js

davidmoshal · 2017-01-21T00:00:59Z

Thanks, so we're sends via /run, and watching screen for the output, correct?
So the alternative would be to hook up an IDE via the serial port and watch for output, no?
I forked the project to play around, and am following your (excellent) book.
Page 66 talks about setting up a sample project - you're using MinGW GCC as the compiler.
As I'm on OSX, am wondering which one to choose, the options are:

Cross GCC
GNU Autotools Toolchain
MacOSX GCC

davidmoshal · 2017-01-21T00:04:55Z

My earlier question about debugging was whether we have a way to do something like this, which webstorm does:

https://www.jetbrains.com/help/webstorm/2016.3/debugging-javascript.html

nkolban · 2017-01-21T00:06:40Z

Ahhh ... driving the ESP32 through the serial port as an alternative ... weve already started on that. Although not yet fully publicized, we can place the ESP32-Duktape environment into a "serial processor" mode ... what that means is that when it starts up ... it doesn't NEED to start WiFi nor does it start an internal Web Server to process HTTP requests. The benefit of that is a LOT less memory needed and hence free for our own applications. The way that works is that there are scripts in ./tools which take JS files from your PC and sends them over serial line into the ESP32. Currently, because it is experimental, one needs to connect a second serial port to the ESP32 using a USB->Serial connector.

As for a development environment ... I'm a Windows man ... BUT ... I wouldn't dream of using Windows (or Mac OS) for ESP32 development. Instead I would strongly recommend running Linux ... if not natively then hosted by "VirtualBox".

nkolban · 2017-01-21T00:09:12Z

For debugging, we can indeed set breakpoints and examine variables ... its not nearly as attractive as a professional browser based environment ... its more like debugging Node.js (server side JS). We are reliant on the facilities provided by Duktape for debugging ... its not the easiest thing in the world ... see:

https://github.com/svaarala/duktape/blob/master/doc/debugger.rst

davidmoshal · 2017-01-21T00:20:47Z

thanks, comments below:

re Wifi: I'd MUCH prefer a good debugging experience than Wifi at this point, to learn about C, Duktape, FreeRTOS, and ESP. I mean, if I can't connect to any peripherals, then having a tiny webserver isn't much good. Additionally, in order to test your js peripheral libraries, and to work on a kid-friendly IDE, I don't need Wifi or a web server either.
re connecting a second port, I have FTDI serial boards, for use with the ESP8622-01, presumably anything that bridges between USB and UART would work, no? A digispark could do this, or even a Bluetooth serial chip, no? (or even and ESP8266).
re development environment: sounds like I should start with the espressif eclipse tutorial: https://github.com/espressif/esp-idf/blob/master/docs/eclipse-setup.rst

nkolban · 2017-01-21T00:30:56Z

I follow the crawl, walk, run approach when attacking a new technical area. First choose the platform in which you are going to do your development .. for me that is Linux. Then learn how to compile a simple program (a hello world) using the command line. From there you can work up. It isn't uncommon for getting boot-strapped like this to take some time depending on previous backgrounds. The ESP32 is a much lower level environment than desktop programming. Study all available materials ... including the ESP32 formal docs, my book of notes and relevant You Tube videos such as ...

https://www.youtube.com/watch?v=bYh2w0HzS7s

Realize that things take time. Should you get stuck, myself and the rest of the ESP32 community will be able to assist through the ESP32 forum and IRC chatroom. Becoming conversant with C, ESP-IDF, FreeRTOS and more will take weeks .... not hours ... be sure you know what you are getting into.

davidmoshal · 2017-01-21T00:40:11Z

:) thanks
Which forum and chatrooms are best?

nkolban · 2017-01-21T03:32:44Z

For a forum .... http://esp32.com/index.php

For a chatroom #ESP32 on IRC

davidmoshal · 2017-01-21T05:10:00Z

Thanks, am on the ESP32 forum.
Don't use IRC, will find a Mac client for it.

nkolban · 2017-02-24T04:48:25Z

Howdy David,
Is there anything further on this issue? If not, can we close it out and open new issues as needed?

davidmoshal · 2017-02-24T06:43:33Z

Hi Neil, I have to admit that I haven't had any bandwidth to explore this further.
Next step for me was to set up a Linux toolchain, but I haven't got round to that yet.
Am still using ESP8266 for teaching (though espruino v1.87 is the most stable build, that project seems to be getting less stable over time).
Going to be a few weeks before I can pick this up again.
Sorry.
David

nkolban · 2017-02-24T14:33:06Z

David,
Don't give it any thought my friend. My goal is to make sure everyone is happy. Pick it up when you can, I'm always going to be here.

davidmoshal · 2017-02-24T15:27:48Z

Thanks

paseaf · 2020-09-07T11:18:26Z

ps, what is a Guru Meditation Error ?

The meaning can be found here.
I also came across this error with duktape ver. 2.5.0 on ESP32. Trying to find a solution

paseaf · 2020-11-09T03:04:22Z

I found the solution for my problem.
My problem was I gave too less stack size to the main task. (the default size is small for using duktape) I found the problem by inserting printf("Stack Low Watermark: %d Bytes\n", uxTaskGetStackHighWaterMark(NULL));s in my code and found it goes to 0 after evaluating a small function.

I solved the problem by increasing sdkconfig -> Component config -> Common ESP-related -> Main task stack size.

davidmoshal closed this as completed Jan 20, 2017

davidmoshal reopened this Jan 20, 2017

davidmoshal changed the title ~~Unable to reconfigure access point~~ Guru Mediation Error after changing access point Jan 20, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Guru Mediation Error after changing access point #6

Guru Mediation Error after changing access point #6

davidmoshal commented Jan 20, 2017 •

edited

Loading

nkolban commented Jan 20, 2017

davidmoshal commented Jan 20, 2017 •

edited

Loading

davidmoshal commented Jan 20, 2017

davidmoshal commented Jan 20, 2017

nkolban commented Jan 20, 2017

davidmoshal commented Jan 20, 2017

nkolban commented Jan 20, 2017

davidmoshal commented Jan 20, 2017

davidmoshal commented Jan 20, 2017

davidmoshal commented Jan 20, 2017

nkolban commented Jan 20, 2017

nkolban commented Jan 20, 2017 •

edited

Loading

davidmoshal commented Jan 21, 2017

davidmoshal commented Jan 21, 2017

nkolban commented Jan 21, 2017

nkolban commented Jan 21, 2017

davidmoshal commented Jan 21, 2017

nkolban commented Jan 21, 2017

davidmoshal commented Jan 21, 2017

nkolban commented Jan 21, 2017

davidmoshal commented Jan 21, 2017

nkolban commented Feb 24, 2017

davidmoshal commented Feb 24, 2017

nkolban commented Feb 24, 2017

davidmoshal commented Feb 24, 2017

paseaf commented Sep 7, 2020

paseaf commented Nov 9, 2020

Guru Mediation Error after changing access point #6

Guru Mediation Error after changing access point #6

Comments

davidmoshal commented Jan 20, 2017 • edited Loading

nkolban commented Jan 20, 2017

davidmoshal commented Jan 20, 2017 • edited Loading

davidmoshal commented Jan 20, 2017

davidmoshal commented Jan 20, 2017

Notes:

nkolban commented Jan 20, 2017

davidmoshal commented Jan 20, 2017

nkolban commented Jan 20, 2017

davidmoshal commented Jan 20, 2017

davidmoshal commented Jan 20, 2017

davidmoshal commented Jan 20, 2017

nkolban commented Jan 20, 2017

nkolban commented Jan 20, 2017 • edited Loading

davidmoshal commented Jan 21, 2017

davidmoshal commented Jan 21, 2017

nkolban commented Jan 21, 2017

nkolban commented Jan 21, 2017

davidmoshal commented Jan 21, 2017

nkolban commented Jan 21, 2017

davidmoshal commented Jan 21, 2017

nkolban commented Jan 21, 2017

davidmoshal commented Jan 21, 2017

nkolban commented Feb 24, 2017

davidmoshal commented Feb 24, 2017

nkolban commented Feb 24, 2017

davidmoshal commented Feb 24, 2017

paseaf commented Sep 7, 2020

paseaf commented Nov 9, 2020

davidmoshal commented Jan 20, 2017 •

edited

Loading

davidmoshal commented Jan 20, 2017 •

edited

Loading

nkolban commented Jan 20, 2017 •

edited

Loading