Search results for:

Gordon. We appreciate VERY much your boards (I have two personally and since I gave one of them to my dad I'm going to get another one)

And we appreciate VERY much your answers and you allowing this board to talk about 8266.

I think it makes a LOT of sense for the json to only have official boards.

Thanks again for your amazing work!

@Robin I'd love to make a video or tutorials and plan to update the our nodebotdays github with a lot of espruino code and examples.

I want to give everyone on that day options, and for me BY FAR this espruino way of doing javascript of these amazing little devices is the way to go.

I'll post something here when I've updated everything.

I was setting out 50 ESP8266 for July's NodeBot Days (down here in south florida) and I want to make sure I know as much about these as possible. The particular combination of this one cable and this one computer seems to work with at least the 3 I've done so far, so I think we're good.

@AkosLukacs question: Can I then rely that all NodeMCU.* match what's printed on the boards?

if I see D3 on the board it's always NodeMCU.D3 right?

I have 20 x Geekcreit® NodeMcu Lua ESP8266 ESP-12E and 30 x WeMos D1 for this event.

and you're absolutely right: I had to create a js file (for johnny-five.js ) that matched each PIN so that people didn't have to guess. This is just silly.

Here's the file for anyone needed. but for Espruino this the same as this NodeMCU built in object in espruino.
https://github.com/bocajs/NodeBotDays/bl­ob/master/esp8266Pins.js

The blink script for the ESP8266 now looks like this

var  on = false;
let LED1 = NodeMCU.D4;
setInterval(function() {
  on = !on;
  LED1.write(on);
}, 500);

for anyone that needs it.

this successfully will blink any LED on D4 and of course all 8266 seem to have a little light on the board that will also blink this (so nothing but your board is needed)

The Espruino IDE is of course set to the suggest 115200 baud and I'm connecting to what ever the connection is for the device.
COM10 in my case for windows /dev/ttyUSB0 on my linux and I cannot remember which port is the one on my mac but it was the one that DIDN'T start with /dev/tty.*

As for the "new machine" and "new cable".
I was using a Chromebook Pixel that now has Ubuntu 19.04 Installed and it seemed to be the problem.
I have another Chromebook (the original CR48) with Ubuntu 18.04 and it doesn't seem to have any trouble.
The fix ended up being again with simply a newcable. Nothing special. And using a windows desktop computer without a hub. I can't figure out if there is a small change in the ESPTOOL.PY line that made the difference. but I was able to then run the script and build two esp8266 and that worked on the CR48 ubuntu machine, a Macbook Pro 2016 and a windows 10 machine all working now.

The Top of the linue Ubuntu box doesn't work and I frankly can't figure out why. It's able to use other arduino devices just fine and is my main computer for everythign else.

and of coruse my amazing Pixl.js device works on that perfectly but of course that's through bluetooth.

1) I know the 8266 has a lot of PINS that don't line up with arduino boards so it's not crazy or a problem (for me) to have to use the NodeMCU prefix. besides a lot of code talks about the B1 or B3 etc of the espruino but of coruse they're no B* in the 8266 or ESP32. so they're talking about the D1 or D3 in those examples. so predefining a
var B3 = NodeMCU.D3
means I have to fink of it only once.

Please ignore the $ at the end of that ESPTOOL.PY line. it's just me trying to copy and paste what was on my command line. It's the full name of the .bin full file.

AHHHHH!!!! Sheesh.
what you need is NodeMCU.D4
var LED = NodeMCU.D4; add that to the default blink script.

and this is the other BIG things. A new machine. (a 4th one) and ANOTHER usb cable.

AHHH!!! the editor on this forum is NOT hapy with anything I paste in.

OK. So WHAT was the solution? It was MORE than just those settings that came from the post that maze1980 suggested. and the key was also that the 8266 needs for you to refer to the not just D4 (for the default LED) but instead

sorry. I couldn't copy and paste and then write something.
IT'S NOW Solved.

And I don't like how!
The line above is how I did it. I swear to you I tried

esptool.py --port COM10 --baud 460800 write_flash --flash_freq 80m --flash_mode dio --flash_size 4MB 0x0000 espruino_2v03_esp8266_4mb_combi$

Please tell me what I'm doing wrong.

I have about 20 x Geekcreit® NodeMcu Lua ESP8266 ESP-12E
I even have a ESP32 with the same results.
I have tried it on a 1) Ubuntu 19.04 laptop 2) Macbook Pro 2016 3) Windows 10 desktop.
Always the same results.
I've changed the port to show you the ubuntu, but i've tried "erase_flash" first. and you can see from the commands below that It even VERIFIES! and it's dead. I show the "screen" line but the IDE and CLI both say there's no connection.

The device blinks when it's being written to and if I plug it and unplug it or press the "reset" button it will blink once and nothing. (As if it's ready) but nothing.

the ONLY success (and I'm calling it as success) was on an OLD chromebook in dev mode where it at least showed giberrish (you know random characters with no reply)

I've tried the originan version 1.4 and I've tried the latest (see below)

What I am doing wrong. I've tried it on 3 different laptops on 3 8266 devices. with 5 different cables.
THis is crazy. Why does no one ever get this resolved in any of the posts where I see this asked?

Please show me where I'm being a morron and correct my mistakes. I'm happy to say I'm sorry and I'll be thankful. but am I the only one that can't get this to work?

$ sudo esptool.py --port /dev/ttyUSB0 --baud 460800 write_flash   --flash_freq 80m --flash_mode qio --flash_size 4MB-c1  0x0000 espruino_2v03_esp8266_4mb_combined_4096.­bin 
esptool.py v2.6
Serial port /dev/ttyUSB0
Connecting....
Detecting chip type... ESP8266
Chip is ESP8266EX
Features: WiFi
MAC: 60:01:94:70:84:30
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...
Flash params set to 0x006f
Compressed 4194304 bytes to 351183...
Wrote 4194304 bytes (351183 compressed) at 0x00000000 in 8.0 seconds (effective 4190.3 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...


$ sudo esptool.py --port /dev/ttyUSB0 --baud 460800 verify_flash   --flash_freq 80m --flash_mode qio --flash_size 4MB-c1  0x0000 espruino_2v03_esp8266_4mb_combined_4096.­bin 
esptool.py v2.6
Serial port /dev/ttyUSB0
Connecting....
Detecting chip type... ESP8266
Chip is ESP8266EX
Features: WiFi
MAC: 60:01:94:70:84:30
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...
Flash params set to 0x006f
Verifying 0x400000 (4194304) bytes @ 0x00000000 in flash against espruino_2v03_esp8266_4mb_combined_4096.­bin...
-- verify OK (digest matched)
Hard resetting via RTS pin...

$ screen /dev/ttyUSB0 115200
[screen is terminating]

Javascript developer since I was in my 20's and that was a LOOOOONG time ago

Why was this mark solved without a solution. THat sucks!

EDIT wow. this was a very nasty version of me. As you can see from another post I made you guys helped and I now have v2.03 on a ESP8266 and ESP32.

Great job. and next time ignore the mean people (like myself) We'll be fine.
Thanks!