I2C Causes crashes on FiPy and WiPy

[noobiemcfoob]

I have a WiPy 2.0 and a FiPy, both updated to the most available firmware ("MicroPython v1.8.6-849-83e2f7f on 2018-03-19; FiPy with ESP32").

When I attempt to use any of the I2C functions, the device crashes. This happens with either device. I've attempted using the I2C features with nothing connected to the board, with it connected to an I2C slave and with SDA and SCL connected to a 4.7kohm pull-up resistor.

Regardless of what I do I see something like this:

>>> from machine import I2C
>>> i2c = I2C(0, I2C.MASTER)
>>> i2c.scan()
[]
>>> ets Jun  8 2016 00:22:57

rst:0x7 (TG0WDT_SYS_RESET),boot:0x33 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff8028,len:8
load:0x3fff8030,len:1728
load:0x4009fa00,len:0
load:0x4009fa00,len:14584
entry 0x400a059c
Attempting to connect to WiFi with stored configuration
Stored SSID:Password - SQUANCH:Pentair1
Connected to SQUANCH! Connection: ('192.168.1.22', '255.255.255.0', '192.168.1.1', '192.168.1.1')
Enabling NTP
NTP Enabled
MicroPython v1.8.6-849-83e2f7f on 2018-03-19; FiPy with ESP32
Type "help()" for more information.
>>> 

[noobiemcfoob]

I spoke too soon! >.<

From a fresh wipe and firmware upgrade, I was able to run the I2C library. However, once I loaded my own modules onto the device and used them to connect to my network, calling "init" on an I2C instance caused the WiPy to freeze (connected over serial, but I could no longer type into the console).

I built a bit-banged version of I2C yesterday and am able to use it on the same pins ("P8", "P9") without issue.

[noobiemcfoob]

heh, full erase fixed it. All better now!

[jmarcelino]

@noobiemcfoob
How is the board connected? Do you have a Pycom expansion board?

Can you try to do a full erase and firmware upgrade?