FiPy Core Dump

[seb]

@robert-hh
Erasing the flash does not erase the registration details, these are kept in a database on our end and the firmware updater will automatically add them in with each update. If there is an issue with registration details we recommend customers email support@pycom.io and we will be able to reset the info in our database.

[adrien3d]

@seb Do you have any ETA for a firmware release that will fix this bug?

[seb]

@adrien3d
I can't provide an exact date but it will be included with the next firmware version which will be released within the next two weeks

[ssmith]

@seb Can you provide some more details on this? We've been fighting a crash like this for the past week on the LoPy4.

Thanks,
Steve

[seb]

@ssmith
Hi,
I've been informed it is caused by a race condition that occurs early in the boot process, I'm afraid that's all I know. It is actively being worked on as we speak and a fix will be released along with our next firmware update.

[adrien3d]

Does the 1.16.0b1 firmware solves the problem ?

[seb]

@adrien3d
Hi,

Unfortunately this issue is proving more elusive than we previously thought. It is being actively investigated, I will keep you updated with the progress.

[seb]

Can you please try the new firmware and report if this fixes the issue you are experiencing?

[adrien3d]

@seb Not fixing anything :/

[seb]

@adrien3d

If you can share the complete back trace generated by the latest firmware, I'll pass this on to the firmware team to look over again. With the back trace they can pinpoint where the error occurs.

[adrien3d]

I've merged what was comprehensible:

ets Jun  8 2016 00:22:57

rst:0xc (SW_CPU_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
coUMP END =================
Rebootin0,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mx17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x0:1060
load:0x4009fa00,len:0
ho 12 tail 0 room 4
load:0x4009fode:DIO, clock div:1
load:0x3fff9028,len:8
load:0x3fff9030,lenabort() was called at PC 0x4008dbb4 on core 1

Backtrace: 0x4a00,len:14096
entry 0x400a05e0
x40083c16:0x3ffd42f0 0x40083cb3:0x3ffd4320 0x4015ea88:0x3ffd437008e05f:0x3ffd4280 0x4008e090:0x3ffd42a0 0x4008dbb4:0x3ffd42c0 03f0 0x400dce42:0x3ffd4430

================= CORE DUMP START 0 0x4015d95b:0x3ffd4390 0x4014d4d1:0x3ffd43d0 0x400e8a2c:0x3ffd4T+JBAAALFP8PyxT/D+8RP0/JFP8PxQAAAAAAAAAAAAAALxE/T8AAAAA
BQAAAL=================

Connecting on /dev/cu.usbmodemPy343431...
/Users/danicampora/Code/Espressif/IDF/esp-idf-20180112/componena00,len:14096
entry 0x400a05e0
bort() was callea at PC 0xs008aaa8 on cor0x00

Backtrace: 0x40ts/freertos/./queue.c:718 (xQueueGenericSend)- assert failed!
a4015d282:0x3ffd3bb0 0x4015d41a:0x3ffd3bd0 0x40155916:0x3ffd3c00 0x4014e3ec:0x3ffd3c20

====x3ffd3b50 0x4008aaa8:0x3ffd3b70 0x=============
HC0AAA4AAABsAQAA
BFP9P3A6/T+wPP0/
oDn9P1A8/T+N 0x4014e3ec:0x3ffd3c20

================= CORE DUMP END =================
Rebooting...
ets Jun  8 2016 00:22:57

rst:0xc (SW_CPU_RESET),boot:0x12 (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:0x3fff9028,len:8
load:0x3fff9030,len:1060
load:0x4009fa00,len:0
ho 12 tail 0 room 4
load:0x4009fa00,len:14096
entry 0x400a05e0
abort() was called at PC 0x4008dbb4 on core 1

Backtrace: 0x4008e05f:0x3ffd4280 0x4008e090:0x3ffd42a0 0x4008dbb4:0x3ffd42c0 0x40083c16:0x3ffd42f0 0x40083cb3:0x3ffd4320 0x4015ea88:0x3ffd4370 0x4015d95b:0x3ffd4390 0x4014d4d1:0x3ffd43d0 0x400e8a2c:0x3ffd43f0 0x400dce42:0x3ffd4430

================= CORE DUMP START =================

Looks like this line will provide you more infos:

Backtrace: 0x40ts/freertos/./queue.c:718 (xQueueGenericSend)- assert failed!