I compiled configuration demo for ESP8266 by using Xtensa-lx106 GNU
file demo_client
demo_client: ELF 32-bit LSB executable, Tensilica Xtensa, version 1 (SYSV), corrupted program header size, not stripped
Could you please tell me, how can i flash this application to ESP8266 by using espytoo.py and how to test it.
I also not able to get GPIO ESP8266 controll application in my sandbox image.
Could you please tell me how can i test gpio control application with nodemcu esp8266 and android app.
Thanks
Rurban
To create a binary from the ELF file:
esptool.py elf2image demo_client
After this, to flash the board with the application:
sudo esptool.py write_flash 0x00000 demo_client-0x00000.bin 0x40000 demo_client-0x40000.bin
If necessary, you can specify the serial port with --port argument.
Regarding GPIO demo for ESP8266, here is an example of GPIO slave application that works with Kaa 0.10.
Related
I have a NodeMCU dev board based on the ESP 12E chipset that does not want to flash. I've tried with both NodeMCU-PyFlasher-4.0 and exptool.py v2.7.
Here's the output from NodeMCU when attempting to flash a firmware:
Command: esptool.py --port /dev/cu.SLAB_USBtoUART --baud 115200 --after no_reset write_flash --flash_mode dout 0x00000 /Volumes/Users/troy/Downloads/tasmota.bin --erase-all
esptool.py v2.6
Serial port /dev/cu.SLAB_USBtoUART
Connecting........_____....._____....._____.....___
Connecting to the serial port using screen /dev/tty.SLAB_USBtoUART 115200 and resetting the device gives the following:
�#�p~�o�lNo���cp��l{l{lp�o��$��co�|l����#�|~�o�l��$`�2oN$`Ns���o��l r��n���l �N�
Connecting to HW-BELTLINE-01
...........................
The . continue on for ever.
The same results occur when using a discrete FTDI USB to UART device connected to the relevant TX/RX headers and powering the board via headers as well (so, taking the USB to UART chip out of the equation).
Video of flashing attempt and serial console output: https://youtu.be/83wZuDMUBXc
Any suggestions on how to get some firmware onto this device, or is it DOA with something not connected properly?
Default firmware tries to connect to the HW-BELTLINE-01 ssid wlan, open or protected with HKHK123HW password. If it succeeds, you can call /gpio/0 or /gpio/1 to test your device.
I've just recently got an NodeMCUv3 ESP8266 and I've been trying to use the Arduino IDE 1.8.8 to program it on my Mac.
I've successfully installed ch340* drivers and I can flash the ESP8266 using USB wire cable.
But after flashing the BasicOTA example (modified to connect to my WiFi), I am not seeing my NodeMCU listed as a network port. I only see a list of Serial ports even after restarting ArduinoIDE and NodeMCU.
I tried Bonjour Browser to discover my NodeMCU device and I cannot see it on the net as well.
Could you please suggest any ideas what could be the problem for appearing the network port for NodeMCU device in the ArduinoIDE?
The problem was solved by adding the line
MDNS.update();
into loop() function.
If you are using windows
1. Install Bonjour
2. Exit the IDE, Disable the network adapters, Enable & connect the network adapters, Start the IDE
3. Disable IPV6 on your network adapters
4. Open the INBOUND port for Python.exe (with the full path)
Hopefully if you do all this, you should be able to do OTA
hello everybody:) I built a firmware with cloud build service. The firmware is master and includes "adc, file, gpio, http, mqtt, net, node, ow, spi, tmr, uart, wifi" and also supports SSL.
Using ESP 07 and the previous version of firmware was nodeMCU 0.9.6 and that was correctly worked but didn't support some modules that i need.
To flash the firmware, i use NodeMCU flasher with these setting:
flasher setting
I upload the binary firmware file to address 0x00000 and esp_init_data_default.bin which is from ESP8266_NONOS_SDK_V1.5.4.1 (downloaded from nodemcu website) to address 0x7c000.
After finishing the upload, module very actively prints garbage on the console.
I uploaded nodeMCU 0.9.6 again to check if the problem is because of the way i flashed firmware, but it wasn't. The module worked with uploaded nodeMCU 0.9.6 well.
Thank you very much:)
ESP-07 is a 512KB module. Hence,
flash mode is qio
flash size is 512KB
All the required settings are documented at http://nodemcu.readthedocs.io/en/latest/en/flash/.
So, using esptool.py the command is as follows:
esptool.py --port <serial-port-of-ESP8266> write_flash -fm qio -fs 4m 0x00000 <nodemcu-firmware>.bin 0x7c000 esp_init_data_default.bin
The esp_init_data_default.bin is contained in http://bbs.espressif.com/download/file.php?id=1572 as the documentation linked above explains.
I was facing the same issue. I did the following steps, which solved my issue.
Before flashing a new firmware, make sure your chip is fully erased. You may use the command below where "serial-port-of-ESP8266" may vary:
esptool.py --port <serial-port-of-ESP8266> erase_flash
Then flash the firmware to the chip using the same technique you use for flashing nodeMCU 0.9.6. You can refer the command below, which is what I used for flashing.
esptool.py --port /dev/ttyACM0 write_flash -fm qio 0x00000 nodemcu-master-8-modules-2016-12-16-09-52-59-float.bin
You mentioned that garbage was printed to console. This can be an indication of mismatched serial port parameters. It's probably worth spending a couple of minutes playing around working through the speed/parity settings of the tool you are using to display the serial output. Try using Putty or Coolterm for "raw" output as these apps do not try and interpret the response.
I have written the flash on an ESP-12E, using a custom build with the base modules + OneWire and mDNS.
The build is from a website i've used before and the build have always worked.
The flash write was apparently successful, yet after the write the ESP started to send garbage data and it hasn't stopped yet.
The ESP8266 download tool from Espressif fails to program the flash, and so does esptool.
The fun part is: I can actually read the MAC for both the AP and the STATION.
GPIO0/2 changes have no effect whatsoever, garbage data still comes in.
Tried to read the data with ESPlorer, PuTTY (Serial) and Teraterm and the problem is the same.
Also tried all standard Baudrates from 9600 to 230400...
And now i'm completely out of ideas.
Here's an image about the error on the Espressif downloader:
You need to familiarize yourself with the upgrading section in the NodeMCU docs. More specifically you need to flash the esp_init_data_default.bin of the Espressif SDK your firmware builds upon to the correct memory address.
I don't know how to do that with the NodeMCU Flasher (project seems to have stalled btw) but with esptool.py the command is as follows:
esptool.py --port <serial-port-of-ESP8266> write_flash -fm dio -fs 32m 0x00000 <nodemcu-firmware>.bin 0x3fc000 esp_init_data_default.bin
I am using Android ICS 4.0.4 source code for enabling the Wi-Fi Direct and run on i.MX6 board with Wi-Fi module which supports marvell 8787 chipset.
I was able to make the wfd0 interface up for wifi direct but the other p2p operations such as device discovery was failing.
I was using WEXT as driver interface .After googling I came to know for the p2p operations nl80211 must be used.
I changed the configurations from WEXT to nl80211. But the wpa_supplicant stopped working.Even though I am starting the wpa_supplicant service from init.rc file the wpa_supplicant does not seems to be running.
Does Android ICS 4.0.4 provide a complete support for Wi-Fi Direct?
Could anyone help me with this issue. ?
The support for Wi-Fi Direct on Android has began for the 4.1 version (source).
Moreover, as you said, the WEXT drivers does not support P2P. So you have to use nl80211 drivers. But are you sure that your device have a valid nl80211 driver?
If you want to known why your wpa_supplicant is crashing, you can start it by hand in a shell without the -B option and with the -dd option and check the log.