I encounter a major bug where i think the SPIFFS filesystem isn't properly created, or something.
When I look at the debug port(DBG, GPIO2) I am getting garbage. And The esp doesn't do any AP transmission.
I did mention before that the second part of the flashing procedure doesn't work.
"make htmlflash"
When i flash another program that contains a SPIFFS file system (using the arduino SPIFFS file system uploader, and then if I reflash my chip with the parallax-esp program,
The parallaxesp program works fine. AND SO DOES THE DBG(GPIO2) output at 115200.
To test this, I went through this procedure many times with multiple different esp devices.
You can test it by issuing the command: esptool.py --port /dev/ttyUSB0 --baud 115200 erase_flash
Then try to reflash with parallaxESP, if you monitor GPIO2 at 115200 baud, it should then throw out garbage.
Can anyone confirm this problem?
Or is it possible that my make htmlflash not working is the problem?
Another possible bug, is the renaming feature of the module, it does not save to flash, and doesn't show up as the new name in the ap list or its network hostname.
How big is your flash chip? The firmware assumes a 2MB flash at present. Also, I never use "make flash". I always use the shell scripts that are in the "release" directory of the source tree. Try the "flash-all.sh" script to make sure everything gets reflashed and the settings areas get cleared.
:~/Parallax-ESP/release/release $ sh flash-all.sh
Using port /dev/ttyUSB0
Uploading 3856 bytes from boot_v1.6.bin to flash at 0x00000000
.... [ 100% ]
Uploading 307732 bytes from httpd.user1.bin to flash at 0x00001000
................................................................................ [ 26% ]
................................................................................ [ 53% ]
................................................................................ [ 79% ]
............................................................. [ 100% ]
Uploading 4096 bytes from blank.bin to flash at 0x0007E000
.... [ 100% ]
Uploading 4096 bytes from blank.bin to flash at 0x0007F000
.... [ 100% ]
Uploading 128 bytes from esp_init_data_default.bin to flash at 0x003FC000
. [ 100% ]
Uploading 4096 bytes from blank.bin to flash at 0x003FE000
.... [ 100% ]
Uploading 4096 bytes from blank.bin to flash at 0x003FA000
.... [ 100% ]
Uploading 4096 bytes from blank.bin to flash at 0x00100000
.... [ 100% ]
Garbage issue still happening, im looking into it more... by trying different things.
So I ran these:
pi@Pie:~/Parallax-ESP/release/release $ sh clear.sh
Using port /dev/ttyUSB0
Uploading 4096 bytes from blank.bin to flash at 0x0007E000
.... [ 100% ]
Uploading 4096 bytes from blank.bin to flash at 0x0007F000
.... [ 100% ]
Uploading 128 bytes from esp_init_data_default.bin to flash at 0x001FC000
. [ 100% ]
Uploading 4096 bytes from blank.bin to flash at 0x001FE000
.... [ 100% ]
Uploading 4096 bytes from blank.bin to flash at 0x001FA000
.... [ 100% ]
Uploading 4096 bytes from blank.bin to flash at 0x00100000
.... [ 100% ]
pi@Pie:~/Parallax-ESP/release/release $ sh clear-ffs.sh
Using port /dev/ttyUSB0
Uploading 4096 bytes from blank.bin to flash at 0x00100000
.... [ 100% ]
pi@Pie:~/Parallax-ESP/release/release $ sh flash-all.sh
Using port /dev/ttyUSB0
Uploading 3856 bytes from boot_v1.6.bin to flash at 0x00000000
.... [ 100% ]
Uploading 307732 bytes from httpd.user1.bin to flash at 0x00001000
................................................................................ [ 26% ]
................................................................................ [ 53% ]
................................................................................ [ 79% ]
............................................................. [ 100% ]
Uploading 4096 bytes from blank.bin to flash at 0x0007E000
.... [ 100% ]
Uploading 4096 bytes from blank.bin to flash at 0x0007F000
.... [ 100% ]
Uploading 128 bytes from esp_init_data_default.bin to flash at 0x003FC000
. [ 100% ]
Uploading 4096 bytes from blank.bin to flash at 0x003FE000
.... [ 100% ]
Uploading 4096 bytes from blank.bin to flash at 0x003FA000
.... [ 100% ]
Uploading 4096 bytes from blank.bin to flash at 0x00100000
.... [ 100% ]
Now the debug port (dbg gpio2) shows proper info, and the esp's AP shows in the wireless devices.
So I had to run clear.sh and clear-ffs.sh
This was after desoldering a 2MB flash chip on my ESP to a 16MB flash chip.
I am guessing the new-unused 16MB flash chip contained some seriously random garbage, that caused issues.
The ESP now preserves my MODULENAME that I changed it to, AND the MODULENAME I changed it to shows up as the AP broadcast name. (when I search for wireless networks, it shows there)
I noticed that when connected to an AP, the original module name shows up as its hostname still. (which is part of its mac)
Also the DBG (gpio2) port is much more verbose than before.
Dang, i should have used the sh script to begin with.
Perhaps all this trial and error im going through will help create a newbie help file, hehehe...
I am new to most of this and github...
I never realized that most github code repositories have a "releases" tab.
This would save me some time, I have been going about github the hard way. https://github.com/parallaxinc/Parallax-ESP/releases
Now I understand why most of the things I am going aren't documented, because its not something a new user needs to do, they just need to look at the releases tab, and use all that.
It doesn't make sense that you had to run clear.sh and clear-ffs.sh before running flash-all.sh. The flash-all.sh script does the same thing as both of those combined plus it flashes the bootloader and the firmware. Just that should have been enough. Also, there really shouldn't be a problem with random junk in the flash chip. The esptool always erases a sector before trying to write it. I wish we could figure out what was causing this problem so I could fix it. Anyway, Parallax will be writing documentation on how to set these things up. You have to realize that you're trying to use software that hasn't yet been released so it isn't in finished form. Also, it's designed to work with a Parallax module. It's just luck that you are able to use it on your module.
Anyway, Parallax will be writing documentation on how to set these things up. You have to realize that you're trying to use software that hasn't yet been released so it isn't in finished form. Also, it's designed to work with a Parallax module. It's just luck that you are able to use it on your module.
I appreciate that this is not released, and unfinished, I like to be able to help test/debug it if i get to the point that my problems aren't user error...
It doesn't make sense that you had to run clear.sh and clear-ffs.sh before running flash-all.sh. The flash-all.sh script does the same thing as both of those combined plus it flashes the bootloader and the firmware. Just that should have been enough. Also, there really shouldn't be a problem with random junk in the flash chip. The esptool always erases a sector before trying to write it. I wish we could figure out what was causing this problem so I could fix it.
I am able to recreate the junk problem by doing this.
:~/Parallax-ESP $ esptool.py --port /dev/ttyUSB0 --baud 115200 erase_flash
esptool.py v1.2
Connecting...
Running Cesanta flasher stub...
Erasing flash (this may take a while)...
Erase took 48.1 seconds
AT this point, when I power cycle the esp, i get junk out of DBG, and the unit will not produce an AP.
BUT
You said don't use the 'make flash' method, use the 'script.sh' method, so that might be the problem.
I cannot reproduce my first attempt at using 'flash-all.sh', I just tried after getting garbage from using 'make flash', and the script method DID fix the issue with out needing to run 'clear.sh' or 'clear-ffs.sh' No idea why my first attempt failed.
Just about 1 hour ago I re-downloaded the parallax-esp.git and updated the entire esp toolchain and recompiled it.
(this made my pi3 overheat, lol)
Perhaps i messed up a parallax-esp git file, I WAS using odd permissions (sudo) and I fixed that.
I'll keep monitoring if i can recreate it using some repeatable method.
Right. Don't use "make flash". I should add a note to that effect to the README file or figure out why it doesn't work and fix it. We moved to using esptool-ck because Parallax didn't want to have to require that the user have Python installed to flash the ESP.
Pretty nifty, I can upload a propeller binary file via my browser, wireless.
I had one over 2k, so I just.... do a few HttpRequester POST commands... to first write it to the flash file system, and then load it onto the propeller from the flash file system...
http://192.168.4.1/userfs/write?file=blink.binary
and then
http://192.168.4.1/propeller/load-file?file=blink.binary
Then I open telnet port 23 in PUTTY on ip 192.168.4.1, and BAM, im getting my propeller debug output, WIRELESS
This is really excellent.
Do you guys have any plans for this module to make our coffee too, tha'd be great.
I've been sticking to RC-modelflying for a long time and did almost no prop-coding.
Now on this thread there is a lot of activity about this ESP8266.
Here in the thread you are talking about details. (Normal what a thread does of course)
But as I haven't been reading here for a long time it is above my head.
Where can I find an introductional description of this "Parallax-ESP-thing" that does exist in GitHub but seems to have no product in the parallax-online-store
Where can I find an introduction description of this "Parallax-ESP-thing" that does exist in GitHub but seems to have no product in the parallax-online-store
thank you very much for pointing me to the PDF-File. It is what it is called
a "Parallax Wi-Fi Module Firmware Guide"
Now things are a bit clearer. But only a bit.
But there is no information about the "Parallax-WiFi-Module" b]itself[/b].
I write what I believe I have understood about this parallax-ESP-module.
I guess my understanding is 80%-wrong. But maybe If I write that you get a picture
of where my problems of understanding are.
Please read and correct if something is wrong:
The "Parallax-ESP-Module" is a WiFi-Module.
It is based on the ESP8266-Chip.
There is one wired interface and the WiFi-interface.
WiFi can be set to client-mode or AP-mode. Ap-mode is insecure because it's not encrypted.
I hope the client-mode can use WPA2-encryption?
The different wireless modes seem to be related to low-level http-stuff
I don't know anything about http and things like "path:handle-id" etc.
Do I have to learn http-protocol on this low level to use this module?
Where can I find a introductional description of the functionality?
I mean a description like
"With this module you can upload html-code to the memory of the module and it acts like a small webserver"
or
"this module allows wireless communication on the ....-level"
or
"this module provides a script-language that makes it easy to create devices that can be accessed via http to show measured values or interaction via simple webpages"
From the variety of my descriptions (of what it might be) you can conclude I'm totally lost with this firmware-document mentioned above.
So again I ask:
does there exist an introctional description of the high-level functionality described similar to the examples above YES or NO?
And If yes can anybody provide a link to it?
a question to transparent-mode:
a longer time ago I used Wixel-modules as a wirelss programming-link for propeller-chips.
worked most of the time except very big files. With big files the propeller-tools failed to transmit the whole code.
Will this modul be the one that allows wireless programming of the EEPROM-Chip?
Pretty nifty, I can upload a propeller binary file via my browser, wireless.
I had one over 2k, so I just.... do a few HttpRequester POST commands... to first write it to the flash file system, and then load it onto the propeller from the flash file system...
http://192.168.4.1/userfs/write?file=blink.binary
and then
http://192.168.4.1/propeller/load-file?file=blink.binary
Then I open telnet port 23 in PUTTY on ip 192.168.4.1, and BAM, im getting my propeller debug output, WIRELESS
This is really excellent.
Do you guys have any plans for this module to make our coffee too, tha'd be great.
You can certainly do that but it isn't the way proploader works. It uses the /propeller/load function to load a second-stage loader that then talks across a TCP connection to complete the load. It's much faster than using the /propeller/load-file function if you have large programs.
"You have to realize that you're trying to use software that hasn't yet been released so it isn't in finished form."
I have understood that it is a product in development and that the release-date is unknown.
Maybe I sound penetrant. (Sorry for that)
Anyway: are you still changing the capabilities (=functionality) of this parallax-ESP-module so much that it makes no sense to describe the funcionality on the high-level?
"You have to realize that you're trying to use software that hasn't yet been released so it isn't in finished form."
I have understood that it is a product in development and that the release-date is unknown.
Maybe I sound penetrant. (Sorry for that)
Anyway: are you still changing the capabilities (=functionality) of this parallax-ESP-module so much that it makes no sense to describe the funcionality on the high-level?
best regards
Stefan
I think that the functionality that is there will probably remain but more functionality is likely to be added in the future.
You can certainly do that but it isn't the way proploader works. It uses the /propeller/load function to load a second-stage loader that then talks across a TCP connection to complete the load. It's much faster than using the /propeller/load-file function if you have large programs.
I also noticed the HttpRequester doesn't have an eeprom load function yet, so proploader is how i must load a permanent change right now.
I like it allll...
It would be nice to know the estimated price and pinout of this new parallax module.
(i have a design in development, that needs an esp, and id like to support this, and i think, why not use the parallax one)
You can certainly do that but it isn't the way proploader works. It uses the /propeller/load function to load a second-stage loader that then talks across a TCP connection to complete the load. It's much faster than using the /propeller/load-file function if you have large programs.
I also noticed the HttpRequester doesn't have an eeprom load function yet, so proploader is how i must load a permanent change right now.
I like it allll...
It would be nice to know the estimated price and pinout of this new parallax module.
(i have a design in development, that needs an esp, and id like to support this, and i think, why not use the parallax one)
That's because it was only intended to load a second-stage loader.
I also noticed the HttpRequester doesn't have an eeprom load function
That's because it was only intended to load a second-stage loader.
Oh.
I gotta say, this code so far works 'excellent', I just loaded it on an esp, and connected it to a prop that is measuring water level using etape.
Which I am able to monitor the level using telnet and putty.
I am using ASCII control codes to make putty display color and organize the display output, and it works great through telnet.
I also noticed the HttpRequester doesn't have an eeprom load function
That's because it was only intended to load a second-stage loader.
Oh.
I gotta say, this code so far works 'excellent', I just loaded it on an esp, and connected it to a prop that is measuring water level using etape.
Which I am able to monitor the level using telnet and putty.
I am using ASCII control codes to make putty display color and organize the display output, and it works great through telnet.
Thanks for all your effort and the tech support!
I'm glad you're having good luck with it. Let me know if you decide to try the command interface from the Propeller. It's supposed to allow a program running on the Propeller to handle HTTP requests sent over the wi-fi connection.
I wish we could figure out what was causing this problem so I could fix it.
Is it possible that I was encountering the bootloop issue with SDK 2.0.0?
It seems to fit my scenario of using blank flash, or newly wiped flash, and SDK 2.0.0
Switch to SDK 2.0.0 by default.
Firmware built with SDK 2.0.0 can't be programmed to blank flash (will
lead to bootloop), so affected parties should be prepared to flash
esp_init_data_default.bin manually, or update their firmware to detect
blank flash and initialize default data automatically (what previous
versions of vendor SDK did themselves).
Ok, nevermind, I see you already DO flash esp_init_data_default.bin in the flash-all.sh file.
Why can't we delete posts anymore... it just leads to post bloat.
IS there anyway to set your mode to STA and your ssid/password without using the webinterface or the serial interface?
I have had a very difficult time getting STA/AP mode to display my AP.
In the serial diagnostic output, it says it found 1 ap, but no ap ever shows up on the networks list.
And it continually repeats the same message, found 1ap, but the webpage never shows the ap that it found.
Is there a way to force the firmware to start in STA mode and connect to a specific ap?
What file would i change?
I think I also might have found a bug.
If you change the module name in STA mode, and try to save to flash, it will not keep the name.
But if you change the module name in STA+AP mode and try to save to flash, it WILL keep the new name. (even if you then switch to STA mode)
Conn req from 192.168.4.2:44296, using pool slot 0
URL = /wifi/wifiscan.cgi
Is url index 0
Is url index 11
Starting scan...
Pool slot 0 is done. Closing.
Pool slot 0: socket closed.
Conn req from 192.168.4.2:44324, using pool slot 0
URL = /wifi/wifiscan.cgi
Is url index 0
Is url index 11
Pool slot 0 is done. Closing.
Pool slot 0: socket closed.
Conn req from 192.168.4.2:44323, using pool slot 0
URL = /wifi/wifiscan.cgi
Is url index 0
Is url index 11
Pool slot 0 is done. Closing.
Pool slot 0: socket closed.
scandone
wifiScanDoneCb 0
Scan done: found 1 APs
Conn req from 192.168.4.2:44325, using pool slot 0
URL = /wifi/wifiscan.cgi
Is url index 0
Is url index 11
Starting scan...
Pool slot 0 is done. Closing.
Pool slot 0: socket closed.
Conn req from 192.168.4.2:44326, using pool slot 0
URL = /wifi/wifiscan.cgi
Is url index 0
Is url index 11
Pool slot 0 is done. Closing.
Pool slot 0: socket closed.
scandone
wifiScanDoneCb 0
Scan done: found 1 APs
Conn req from 192.168.4.2:44328, using pool slot 0
URL = /wifi/wifiscan.cgi
Is url index 0
Is url index 11
Starting scan...
Pool slot 0 is done. Closing.
Pool slot 0: socket closed.
Conn req from 192.168.4.2:44329, using pool slot 0
URL = /wifi/wifiscan.cgi
Is url index 0
Is url index 11
Pool slot 0 is done. Closing.
Pool slot 0: socket closed.
Conn req from 192.168.4.2:44322, using pool slot 0
URL = /wifi/wifiscan.cgi
Is url index 0
Is url index 11
Pool slot 0 is done. Closing.
Pool slot 0: socket closed.
scandone
wifiScanDoneCb 0
Scan done: found 1 APs
Conn req from 192.168.4.2:44327, using pool slot 0
URL = /wifi/wifiscan.cgi
Is url index 0
Is url index 11
Starting scan...
Pool slot 0 is done. Closing.
Pool slot 0: socket closed.
Conn req from 192.168.4.2:44330, using pool slot 0
URL = /wifi/wifiscan.cgi
Is url index 0
Is url index 11
Pool slot 0 is done. Closing.
Pool slot 0: socket closed.
scandone
wifiScanDoneCb 0
Scan done: found 1 APs
Conn req from 192.168.4.2:44332, using pool slot 0
URL = /wifi/wifiscan.cgi
Is url index 0
Is url index 11
Starting scan...
Pool slot 0 is done. Closing.
Pool slot 0: socket closed.
Conn req from 192.168.4.2:44333, using pool slot 0
URL = /wifi/wifiscan.cgi
Is url index 0
Is url index 11
Pool slot 0 is done. Closing.
Pool slot 0: socket closed.
Conn req from 192.168.4.2:44334, using pool slot 0
URL = /wifi/wifiscan.cgi
Is url index 0
Is url index 11
Pool slot 0 is done. Closing.
Pool slot 0: socket closed.
scandone
wifiScanDoneCb 0
Scan done: found 1 APs
IS there anyway to set your mode to STA and your ssid/password without using the webinterface or the serial interface?
I have had a very difficult time getting STA/AP mode to display my AP.
In the serial diagnostic output, it says it found 1 ap, but no ap ever shows up on the networks list.
And it continually repeats the same message, found 1ap, but the webpage never shows the ap that it found.
That's odd. I haven't seen that. I'm not sure why that would happen.
Is there a way to force the firmware to start in STA mode and connect to a specific ap?
What file would i change?
It should already do that. Once you've connected to an AP it remembers the SSID and password and connects automatically the next time if the AP is visible.
I think I also might have found a bug.
If you change the module name in STA mode, and try to save to flash, it will not keep the name.
But if you change the module name in STA+AP mode and try to save to flash, it WILL keep the new name. (even if you then switch to STA mode)
Again, I'm not sure what's going on here. I haven't seen that behavior. The settings code really has nothing to do with what wi-fi mode you're in.
That's odd. I haven't seen that. I'm not sure why that would happen.
Is it possible that all the background apps and programs that are trying to connect to the internet are causing the esp to timeout for the original webinterface config page?
(a.k.a. too many DNS connection attempts)?
I see in the diagnostic output, that my tablet and pc try to repeatedly connect to multiple websites for all kinds of background communications..
I know the esp has a limited about of connections it can handle...
It should already do that. Once you've connected to an AP it remembers the SSID and password and connects automatically the next time if the AP is visible.
not sure what's going on here. I haven't seen that behavior. The settings code really has nothing to do with what wi-fi mode you're in.
Yea, im saying i want to change the firmware settings so when i run flash-all.sh, my esp is already programmed with its ssid and password.
It should already do that. Once you've connected to an AP it remembers the SSID and password and connects automatically the next time if the AP is visible.
not sure what's going on here. I haven't seen that behavior. The settings code really has nothing to do with what wi-fi mode you're in.
Yea, im saying i want to change the firmware settings so when i run flash-all.sh, my esp is already programmed with its ssid and password.
Use the flash-fw.sh script and it won't overwrite your settings or the flash filesystem.
It should already do that. Once you've connected to an AP it remembers the SSID and password and connects automatically the next time if the AP is visible.
not sure what's going on here. I haven't seen that behavior. The settings code really has nothing to do with what wi-fi mode you're in.
Yea, im saying i want to change the firmware settings so when i run flash-all.sh, my esp is already programmed with its ssid and password.
Use the flash-fw.sh script and it won't overwrite your settings or the flash filesystem.
In fact, why not just use OTA firmware updating? I never use the batch files unless I flash firmware that doesn't work for some reason. It's much easier to just use an OTA firmware update.
It seems I have major issues with an esp that doesn't have an antenna built in.
I have 8 of these, and they seem to be a bad design.
I seem to have nothing but problems with this particular version:
Comments
When I use an esp device that has a brand new flash chip (blank data)
OR if I run this command:
And then I immediately try to flash my chip with parallaxESP
I encounter a major bug where i think the SPIFFS filesystem isn't properly created, or something.
When I look at the debug port(DBG, GPIO2) I am getting garbage. And The esp doesn't do any AP transmission.
I did mention before that the second part of the flashing procedure doesn't work.
"make htmlflash"
When i flash another program that contains a SPIFFS file system (using the arduino SPIFFS file system uploader, and then if I reflash my chip with the parallax-esp program,
The parallaxesp program works fine. AND SO DOES THE DBG(GPIO2) output at 115200.
To test this, I went through this procedure many times with multiple different esp devices.
You can test it by issuing the command: esptool.py --port /dev/ttyUSB0 --baud 115200 erase_flash
Then try to reflash with parallaxESP, if you monitor GPIO2 at 115200 baud, it should then throw out garbage.
Can anyone confirm this problem?
Or is it possible that my make htmlflash not working is the problem?
Another possible bug, is the renaming feature of the module, it does not save to flash, and doesn't show up as the new name in the ap list or its network hostname.
The shell scripts are causing major issues with me.
I didn't have ZIP so i installed it.
The esptool.py copy i have is generating errors with the sh script.
:~/Parallax-ESP/release $ sh flash-all.sh Using port /dev/ttyUSB0 usage: esptool [-h] [--port PORT] [--baud BAUD] {load_ram,dump_mem,read_mem,write_mem,write_flash,run,image_info,make_image,elf2image,read_mac,chip_id,flash_id,read_flash,verify_flash,erase_flash,version} ... esptool: error: argument operation: invalid choice: '/dev/ttyUSB0' (choose from 'load_ram', 'dump_mem', 'read_mem', 'write_mem', 'write_flash', 'run', 'image_info', 'make_image', 'elf2image', 'read_mac', 'chip_id', 'flash_id', 'read_flash', 'verify_flash', 'erase_flash', 'version')I found out why, i need the esptool helper.
https://github.com/igrr/esptool-ck
I downloaded the arm release https://github.com/igrr/esptool-ck/releases/download/0.4.9/esptool-0.4.9-linux-armhf.tar.gz and put it in my /opt/parallax/bin folder.
IT works now.
Garbage issue still happening, im looking into it more... by trying different things.
So I ran these:
Now the debug port (dbg gpio2) shows proper info, and the esp's AP shows in the wireless devices.
So I had to run clear.sh and clear-ffs.sh
This was after desoldering a 2MB flash chip on my ESP to a 16MB flash chip.
I am guessing the new-unused 16MB flash chip contained some seriously random garbage, that caused issues.
The ESP now preserves my MODULENAME that I changed it to, AND the MODULENAME I changed it to shows up as the AP broadcast name. (when I search for wireless networks, it shows there)
I noticed that when connected to an AP, the original module name shows up as its hostname still. (which is part of its mac)
Also the DBG (gpio2) port is much more verbose than before.
Dang, i should have used the sh script to begin with.
Perhaps all this trial and error im going through will help create a newbie help file, hehehe...
I am new to most of this and github...
I never realized that most github code repositories have a "releases" tab.
This would save me some time, I have been going about github the hard way.
https://github.com/parallaxinc/Parallax-ESP/releases
Now I understand why most of the things I am going aren't documented, because its not something a new user needs to do, they just need to look at the releases tab, and use all that.
This pdf helps me immensely, i never realized this existed until about 5 minutes ago : https://github.com/parallaxinc/Parallax-ESP/releases/download/v1.0/Parallax_Wi-Fi_Module_API.pdf
I see the pdf has the info I need to communicate with my propeller chips tx/rx lines via telnet... excellent.
I appreciate that this is not released, and unfinished, I like to be able to help test/debug it if i get to the point that my problems aren't user error...
I am able to recreate the junk problem by doing this. Then AT this point, when I power cycle the esp, i get junk out of DBG, and the unit will not produce an AP.
BUT
You said don't use the 'make flash' method, use the 'script.sh' method, so that might be the problem.
I cannot reproduce my first attempt at using 'flash-all.sh', I just tried after getting garbage from using 'make flash', and the script method DID fix the issue with out needing to run 'clear.sh' or 'clear-ffs.sh' No idea why my first attempt failed.
Just about 1 hour ago I re-downloaded the parallax-esp.git and updated the entire esp toolchain and recompiled it.
(this made my pi3 overheat, lol)
Perhaps i messed up a parallax-esp git file, I WAS using odd permissions (sudo) and I fixed that.
I'll keep monitoring if i can recreate it using some repeatable method.
So I installed http requester for firefox... https://addons.mozilla.org/En-us/firefox/addon/httprequester/
Pretty nifty, I can upload a propeller binary file via my browser, wireless.
I had one over 2k, so I just.... do a few HttpRequester POST commands... to first write it to the flash file system, and then load it onto the propeller from the flash file system...
Then I open telnet port 23 in PUTTY on ip 192.168.4.1, and BAM, im getting my propeller debug output, WIRELESS
This is really excellent.
Do you guys have any plans for this module to make our coffee too, tha'd be great.
I've been sticking to RC-modelflying for a long time and did almost no prop-coding.
Now on this thread there is a lot of activity about this ESP8266.
Here in the thread you are talking about details. (Normal what a thread does of course)
But as I haven't been reading here for a long time it is above my head.
Where can I find an introductional description of this "Parallax-ESP-thing" that does exist in GitHub but seems to have no product in the parallax-online-store
best regards
Stefan
If you read the PDF https://github.com/parallaxinc/Parallax-ESP/releases/download/v1.0/Parallax_Wi-Fi_Module_API.pdf
You can see the item number will be 32420S or 32402D. The pdf documentation has a date of November-02-2016, so ALL this stuff is new.
Its nice that they let others in on the fun before its dun.
I don't think its for sale YET, the software isn't done, so the hardware probably isn't also.
thank you very much for pointing me to the PDF-File. It is what it is called
a "Parallax Wi-Fi Module Firmware Guide"
Now things are a bit clearer. But only a bit.
But there is no information about the "Parallax-WiFi-Module" b]itself[/b].
I write what I believe I have understood about this parallax-ESP-module.
I guess my understanding is 80%-wrong. But maybe If I write that you get a picture
of where my problems of understanding are.
Please read and correct if something is wrong:
The "Parallax-ESP-Module" is a WiFi-Module.
It is based on the ESP8266-Chip.
There is one wired interface and the WiFi-interface.
WiFi can be set to client-mode or AP-mode. Ap-mode is insecure because it's not encrypted.
I hope the client-mode can use WPA2-encryption?
The different wireless modes seem to be related to low-level http-stuff
I don't know anything about http and things like "path:handle-id" etc.
Do I have to learn http-protocol on this low level to use this module?
Where can I find a introductional description of the functionality?
I mean a description like
"With this module you can upload html-code to the memory of the module and it acts like a small webserver"
or
"this module allows wireless communication on the ....-level"
or
"this module provides a script-language that makes it easy to create devices that can be accessed via http to show measured values or interaction via simple webpages"
From the variety of my descriptions (of what it might be) you can conclude I'm totally lost with this firmware-document mentioned above.
So again I ask:
does there exist an introctional description of the high-level functionality described similar to the examples above YES or NO?
And If yes can anybody provide a link to it?
a question to transparent-mode:
a longer time ago I used Wixel-modules as a wirelss programming-link for propeller-chips.
worked most of the time except very big files. With big files the propeller-tools failed to transmit the whole code.
Will this modul be the one that allows wireless programming of the EEPROM-Chip?
best regards
Stefan
thank you very much for commenting
I have understood that it is a product in development and that the release-date is unknown.
Maybe I sound penetrant. (Sorry for that)
Anyway: are you still changing the capabilities (=functionality) of this parallax-ESP-module so much that it makes no sense to describe the funcionality on the high-level?
best regards
Stefan
OK. If you have enough of my re-asking for more details just drop a short line here or as PM and I will stop. This hasn't happened yet. So I ask:
What is the functionality that is already in the code?
best regards Stefan
I also noticed the HttpRequester doesn't have an eeprom load function yet, so proploader is how i must load a permanent change right now.
I like it allll...
It would be nice to know the estimated price and pinout of this new parallax module.
(i have a design in development, that needs an esp, and id like to support this, and i think, why not use the parallax one)
Oh.
I gotta say, this code so far works 'excellent', I just loaded it on an esp, and connected it to a prop that is measuring water level using etape.
Which I am able to monitor the level using telnet and putty.
I am using ASCII control codes to make putty display color and organize the display output, and it works great through telnet.
Thanks for all your effort and the tech support!
Need to put it back on my todo list
Is it possible that I was encountering the bootloop issue with SDK 2.0.0?
It seems to fit my scenario of using blank flash, or newly wiped flash, and SDK 2.0.0
https://github.com/pfalcon/esp-open-sdk/commit/24f10eb164947fdd38b6225f72e752d5eb785391
This was very recent also... Oct 17, 2016
Ok, nevermind, I see you already DO flash esp_init_data_default.bin in the flash-all.sh file.
Why can't we delete posts anymore... it just leads to post bloat.
I have had a very difficult time getting STA/AP mode to display my AP.
In the serial diagnostic output, it says it found 1 ap, but no ap ever shows up on the networks list.
And it continually repeats the same message, found 1ap, but the webpage never shows the ap that it found.
Is there a way to force the firmware to start in STA mode and connect to a specific ap?
What file would i change?
I think I also might have found a bug.
If you change the module name in STA mode, and try to save to flash, it will not keep the name.
But if you change the module name in STA+AP mode and try to save to flash, it WILL keep the new name. (even if you then switch to STA mode)
Is it possible that all the background apps and programs that are trying to connect to the internet are causing the esp to timeout for the original webinterface config page?
(a.k.a. too many DNS connection attempts)?
I see in the diagnostic output, that my tablet and pc try to repeatedly connect to multiple websites for all kinds of background communications..
I know the esp has a limited about of connections it can handle...
Yea, im saying i want to change the firmware settings so when i run flash-all.sh, my esp is already programmed with its ssid and password.
I have 8 of these, and they seem to be a bad design.
I seem to have nothing but problems with this particular version:
But this one below works great with your software. (i have two of these, and both work perfectly)
https://www.olimex.com/Products/IoT/MOD-WIFI-ESP8266-DEV/open-source-hardware
http://www.digikey.com/product-detail/en/olimex-ltd/MOD-WIFI-ESP8266-DEV/1188-1154-ND/5247121
The original modules typically need such action, more complex devboards don't...