@dbrgn WiFi can always be enabled afterwards. The wifi on boot API only affects the behaviour during start up. If you call that specific sequence nothing will happen (calling WLAN() without params just returns the object). Cheers, Daniel

Just released 1.7.9.b3 which solves the ABP issue. Apologies for this bug, we'll investigate why it was not picked up by our automatic tests.

I don't know of any alternative, but have you tried it on another computer?

@athtest800 While the flash chip is rated for 100,000 program/erase cycles the Non-volatile storage library used to store these value does it's own kind of wear levelling so I'd expect a lot more, well into the millions.

USB issues SOLVED The problem was the baud rate being used by Putty. The default baud rate in Putty is 9600 but the rate that should be used is 115200. This is mentioned in the documentation section for using Linux . After I changed the baud rate to 115200 did that Serial USB was working.

@Paco88 Yes it is

Why doesn't the update tool support OTA updates, or at least make the firmware binaries available directly?

Issue solved by doing a complete download of all sources then re-doing all steps again.

@jmarcelino It turned out when I used a different computer it worked first time. Thanks for the help anyway I think it may have been a motherboard issue. thanks, Chris

@jmarcelino yes, of course. It's the part where I'm using the socket that is commented out right now: import machine from machine import UART from network import WLAN #from network import LoRa #lora = LoRa(mode=LoRa.LORAWAN) #from machine import SD import socket #import ssl #import time import os import pycom print('starting up..') #sd = SD() #os.mount(sd, '/sd') #time.sleep(5) #os.listdir('/sd') #time.sleep(5) uart = UART(0, 115200) os.dupterm(uart) pycom.heartbeat(False) pycom.rgbled(0x7f0000) # red wlan = WLAN() #print('SD mounted!') if machine.reset_cause() != machine.SOFT_RESET: print('setting wlan config...') wlan.init(mode=WLAN.STA) wlan.ifconfig(config=('10.0.0.88', '255.255.255.0', '10.0.0.1', '8.8.8.8')) if not wlan.isconnected(): print('looking for network...') wlan.connect('NETGEAR64', auth=(WLAN.WPA2, 'oddchair195'), timeout=5000) while not wlan.isconnected(): machine.idle() print('connected to wifi!') #s = socket.socket() #ss = ssl.wrap_socket(s) #ss.connect(socket.getaddrinfo('www.google.com', 443)[0][-1]) #print('connected to internet!') space = os.getfree('/flash') print('free flash mem: ', space) pycom.rgbled(0x007f00) # green

@jcaron said in First steps with LoPy & PySense and feedback: The cases (probably) fit the expansion board, but not the PySense. Wouldn't hurt being a bit more explicit about it on the site. Are there any cases that would fit the PySense? +1 for the cases issue. I bought a PySense and a PyTrack and a case for each. Pretty frustrating that there aren't the appropriate mounting points in the case for those boards.

@robert-Thank you, worked perfectly

@ssmith said in New firmware release 1.7.5.b2: When updating FW breaks what was previously working, that is a huge issue. Especially if a breaking change is not listed in any changelog, as far as I can tell :)

@jmarcelino I had high hopes and was rather pleased you pointed out the variant using a controlled stop. Sady it doesn't work for me. Here is my code. Changing the string I try to write doesn't change anything. I hadsome concern in my Python noobishness that my assignments to the addressing array may not be correct but a print(str(addressing)) of it showed it was correct (not in th below code). Oh. I saw you mention an older I2C eeprom you had. I checked it out - it may be a 5v only part. ---- begin ---- from machine import I2C import time # configure the I2C bus # i2c = I2C(0, I2C.MASTER, baudrate=100000, pins=('P9', 'P10')) i2c = I2C(0, I2C.MASTER, baudrate=100000) print('scanning') print(i2c.scan()) # returns list of slave addresses, tells me chip is on the bus loops = 0 addressing = bytearray(3) addressing[0] = 0xA0 # Write command, chip 0 on bus addressing[1] = 0x00 # MSB address addressing[2] = 0x00 # LSB address i2c.writeto(80, addressing, stop=False) # setup chip, no stop means more to follow i2c.writeto(80, '123hello world456') # this should be a "page write" (assume) time.sleep(1) # crazy long. 5mS should be enough addressing[0] = 0xA1 # make it a read command, chip 0 on bus while 1: i2c.writeto(80, addressing, stop=False) # setup chip, no stop means more to follow time.sleep(0.1) # not necessary. "try anything" result = i2c.readfrom(80, 32) # clock out 32 bytes in page mode (assume) print(str(loops) + ' ' + str(result)) time.sleep(1.0) loops = loops + 1 ---- it returns ---- scanning                                                                                                                 [80]                                                                                                                     0 b'\x0f\x0c\x08\x12\x13,\x01Y\x02C\x04\x07\n\x10\x00\xff\x0f\x0c\x08\x12\x18,\x01I\x03\xfb\x04\x1e\n\x11\x00\xff'       1 b'\x0f\x0c\x08\x12\x13,\x01Y\x02C\x04\x07\n\x10\x00\xff\x0f\x0c\x08\x12\x18,\x01I\x03\xfb\x04\x1e\n\x11\x00\xff'

@this.wiederkehr @peekay123 @daniel It seems, as if with release 1.7.7.b1 this issue is gone. I ran the loop&write test three times up to 2 million passes = 2048000000 Bytes successfully, at which time it stopped intentionally to avoid writing more than 2 GB into a file.

@daniel - any chance of getting this anytime soon ?

Refer to this thread for details on how Pycom builds the libraries: https://forum.pycom.io/topic/2835/is-it-possible-to-recompile-pycom-s-esp-idf-with-different-settings

@peekay123 I am having the same issue, although only for certain networks. When I connect to my "802.11n" network at 2.4GHz, it works no problem. However, when I try to connect to a "802.11ac" network which is using 5GHz, the wlan.isconnected() method never returns true. My other board which still has 1.6.7 firmware does not have this issue. It connects to both networks.

@jmarcelino s/n is "1713000002" @Pajarraco sorry I should have said that I already used those drivers... but strangely, I had to manually select the drivers as the device appeared as "unknown device" and windows 10 didn't ask me to choose what to do automatically