For instance, when I execute this code:
Code: Select all
>>> import time
>>> for i in range(10):
... print("Hello World!")
... time.sleep(1)
Code: Select all
ets Jan 8 2013,rst cause:2, boot mode:(3,0)
load 0x40100000, len 31488, room 16
tail 0
chksum 0xb1
load 0x3ffe8000, len 924, room 8
tail 4
chksum 0x87
load 0x3ffe83a0, len 25872, room 4
tail 12
chksum 0x9e
csum 0x9e
don't use rtc mem data
rl��rl���bl�br|�bll���lb��n�nn��l�|�l�l��l������l`�n����b��b���bl�b�,
>>>
MicroPython v1.6-137-gc70637b on 2016-03-05; ESP module with ESP8266
Type "help()" for more information.
I'm using code from the github repo downloaded this morning. I've successfully built and deployed the firmware both on my Ubuntu 15.04 box as well as my Rpi (Raspbian Jessie). The issue is exactly the same on both my Feather and breakout Huzzah's from AdaFruit. So highly repeatable. However, I haven't seen any bug-reports concerning something like this on Github, so I'm assuming I might be doing something wrong. However, the issue seems similar to the timing issues that plagued the WiPy until recently, but from the forum it seems there was some kind of cryptic solution, until it got fixed in a more permanent way.
Btw, I'm using 'screen' from my Linux boxes to connect at baud-rate 115200. Wondering whether frequency matters (assuming it will also use clock-functions?). I haven't tried compiling in this script with the firmware yet.
Any suggestion would be highly appreciated!