I didn't realise there was an LED - no sign of it on the schematic http://www.wemos.cc/Products/images/d1_mini.pdf. Yet experimentation has revealed an active low blue LED on pin 2. For what it's worth the LED's on the Huzzah are both active low (pins 0 and 2).torwag wrote:...However, for my boards, it seems the heartbeat LED is reversed. a Pin.low() will enable the LED and vice versa...
v1.8 works on a WeMos D1 Mini
- pythoncoder
- Posts: 5956
- Joined: Fri Jul 18, 2014 8:01 am
- Location: UK
- Contact:
Re: v1.8 works on a WeMos D1 Mini
It works here too (Linux Mint), with WiFi in station mode.
Peter Hinch
Index to my micropython libraries.
Index to my micropython libraries.
Re: v1.8 works on a WeMos D1 Mini
I think there is an active-low LED on all ESP-12 modules.
The reason why it is active-low is that it's tied to the TX pins, which are pulled high when the serial has nothing to send. So to make them normally off, and blink when data is being transmitted, they have to be active-low.
The reason why it is active-low is that it's tied to the TX pins, which are pulled high when the serial has nothing to send. So to make them normally off, and blink when data is being transmitted, they have to be active-low.
Re: v1.8 works on a WeMos D1 Mini
Sorry for the LED stuff... I had somehow in mind that people used the WeMOS-boards and demonstrated the functionality on, what looked like, an active-high LED. However, I might have mixed this up with other boards.
Thus, it seems to be pretty normal that the LED on the board is active-low.
Next to get is the Relay-board and we are one step further towards a Micropython based home-automation system
Thus, it seems to be pretty normal that the LED on the board is active-low.
Next to get is the Relay-board and we are one step further towards a Micropython based home-automation system
-
- Posts: 2
- Joined: Tue Sep 20, 2016 5:07 pm
Re: v1.8 works on a WeMos D1 Mini
I'm wondering if v1.8.4 is working for anyone with the Wemos D1 Mini? I've tried flashing with:
esptool.py --port /dev/tty.wchusbserial1410 --baud 115200 write_flash --verify --flash_mode=dio --flash_size=32m -ff 40m 0x00000 esp8266-20160909-v1.8.4.bin
However, it seems to crash at boot. I can't access the REPL from the serial port (at 115200 baud, or any other for that matter), and the only hint of life is the following at 74880 baud at boot:
ets Jan 8 2013,rst cause:2, boot mode:(3,6)
Additionally, after flashing with micropython, I need to use a 10 Ohm resistor between GND and D3 to clear it/reflash it with another firmware. Any ideas?
esptool.py --port /dev/tty.wchusbserial1410 --baud 115200 write_flash --verify --flash_mode=dio --flash_size=32m -ff 40m 0x00000 esp8266-20160909-v1.8.4.bin
However, it seems to crash at boot. I can't access the REPL from the serial port (at 115200 baud, or any other for that matter), and the only hint of life is the following at 74880 baud at boot:
ets Jan 8 2013,rst cause:2, boot mode:(3,6)
Additionally, after flashing with micropython, I need to use a 10 Ohm resistor between GND and D3 to clear it/reflash it with another firmware. Any ideas?
Re: v1.8 works on a WeMos D1 Mini
Works fine for me on several d1 minis (and a d1 mini pro), no resistors are necessary.
Re: v1.8 works on a WeMos D1 Mini
Instead of DIO use QIO...
-
- Posts: 2
- Joined: Tue Sep 20, 2016 5:07 pm
Re: v1.8 works on a WeMos D1 Mini
@deshipu, are you using the micropython-supplied esp8266-20160909-v1.8.4.bin (https://micropython.org/download/#esp8266)?
I was able to get it running with a pull-up resistor from D3 to 5V. Odd thing is I don't need the pull-down/up or to deal with any of this when reflashing firmwares through the Arduino IDE. Very strange.
$ esptool.py --port /dev/tty.wchusbserial1410 erase_flash
esptool.py v1.1
Connecting...
Erasing flash (this may take a while)...
$ esptool.py --port /dev/tty.wchusbserial1410 --baud 115200 write_flash --verify --flash_mode=dio --flash_size=32m -ff 40m 0x00000 esp8266-20160909-v1.8.4.bin
esptool.py v1.1
Connecting...
Running Cesanta flasher stub...
Flash params set to 0x0240
Writing 507904 @ 0x0... 507904 (100 %)
Wrote 507904 bytes at 0x0 in 44.0 seconds (92.4 kbit/s)...
Leaving...
Verifying just-written flash...
Verifying 0x7bec8 (507592) bytes @ 0x00000000 in flash against esp8266-20160710-v1.8.2.bin...
-- verify OK (digest matched)
$ screen /dev/tty.wchusbserial1410 115200
^�C��ORqc�*��a]BPBij9EH�@nqa���,�!��ʽb֖���B�������sll��|�l�|�$�b|����s�b�c��no�doo���c8��l{lsdx�o��d#g�<���#��gn�l��l`�g�do;���o�l p�g�{�����cn�|d��c��no��l`�nl`gs���g���`x�n�;�������#o�|�c��og�l �gd`o;���o{;l ;��o{{l ��$��|��s{oc��l�b�lc쌜���#�l{ldl��|��{;g#��l��p�c�c쌜���c��l{l�d��|��r'c��d����c�c서���#�lcl��r�d�l��d`��{�l�d�l ��r�d���dd`{l��r$���cl�#{|�#p��#bb��'�'�dl��d쇄l��dl���l��d�n����#d�x���bd�#xsd{ls�g�����o����csc��c䇜��l���bbd��l'�8{d�l��|���#4 ets_task(40100390, 3, 3fff6300, 4)
WebREPL daemon started on ws://192.168.4.1:8266
Started webrepl in setup mode
could not open file 'main.py' for reading
MicroPython v1.8.4-10-gbc28ac8 on 2016-09-09; ESP module with ESP8266
Type "help()" for more information.
>>>
I was able to get it running with a pull-up resistor from D3 to 5V. Odd thing is I don't need the pull-down/up or to deal with any of this when reflashing firmwares through the Arduino IDE. Very strange.
$ esptool.py --port /dev/tty.wchusbserial1410 erase_flash
esptool.py v1.1
Connecting...
Erasing flash (this may take a while)...
$ esptool.py --port /dev/tty.wchusbserial1410 --baud 115200 write_flash --verify --flash_mode=dio --flash_size=32m -ff 40m 0x00000 esp8266-20160909-v1.8.4.bin
esptool.py v1.1
Connecting...
Running Cesanta flasher stub...
Flash params set to 0x0240
Writing 507904 @ 0x0... 507904 (100 %)
Wrote 507904 bytes at 0x0 in 44.0 seconds (92.4 kbit/s)...
Leaving...
Verifying just-written flash...
Verifying 0x7bec8 (507592) bytes @ 0x00000000 in flash against esp8266-20160710-v1.8.2.bin...
-- verify OK (digest matched)
$ screen /dev/tty.wchusbserial1410 115200
^�C��ORqc�*��a]BPBij9EH�@nqa���,�!��ʽb֖���B�������sll��|�l�|�$�b|����s�b�c��no�doo���c8��l{lsdx�o��d#g�<���#��gn�l��l`�g�do;���o�l p�g�{�����cn�|d��c��no��l`�nl`gs���g���`x�n�;�������#o�|�c��og�l �gd`o;���o{;l ;��o{{l ��$��|��s{oc��l�b�lc쌜���#�l{ldl��|��{;g#��l��p�c�c쌜���c��l{l�d��|��r'c��d����c�c서���#�lcl��r�d�l��d`��{�l�d�l ��r�d���dd`{l��r$���cl�#{|�#p��#bb��'�'�dl��d쇄l��dl���l��d�n����#d�x���bd�#xsd{ls�g�����o����csc��c䇜��l���bbd��l'�8{d�l��|���#4 ets_task(40100390, 3, 3fff6300, 4)
WebREPL daemon started on ws://192.168.4.1:8266
Started webrepl in setup mode
could not open file 'main.py' for reading
MicroPython v1.8.4-10-gbc28ac8 on 2016-09-09; ESP module with ESP8266
Type "help()" for more information.
>>>
Re: v1.8 works on a WeMos D1 Mini
The pullup resistor shouldn't be necessary, and certainly not to 5V (esp8266 works at 3.3V internally, you shouldn't give it 5V as input), unless you have something connected to that pin that pulls it down at startup and negates the internal pullup.
Re: v1.8 works on a WeMos D1 Mini
What library are you using for LCD with HD44780, can you give me the tutorial please..!?mcauser wrote:@platforma I found the little OLED shield a little too tiny at only 64x48. Beautiful display, but doesn't fit many words.
If you are considering ordering the DHT11/22 shield, get the Dual Base shield to avoid the ESP8266 warming up the sensor and skewing the results.
There are not any WeMos shields for it, but you can connect 128x32 and 128x64 OLEDs with a SSD1306.
I found cheap Nokia 5110 LCDs work great: https://github.com/mcauser/WeMos-D1-min ... 10-PCD8544
Low power consumption, 84x48 resolution, fast refresh rate, readable in daylight without the backlight, nice and cheap.
I also have these displays working:
1.44" 128x128 TFT with ST7735 (green tab)
2.2" 320x240 TFT with ILI9341 (green tab and red tab, not touchscreen, but does have a sd card slot)
08x2, 16x2 and 20x4 Character LCDs with HD44780 and PCF8574T