Feather HUZZAH ESP32 Installs old firmware

[adafruitguy]

A fresh Wippersnapper install on a Feather HUZZAH ESP32 installs v1.0.0-beta.12 (not .13) and remains "Offline"...

Fresh Install via WebSerial_NVMGenerator

Screen Shot 2021-10-17 at 8.53.24 PM.png (219.2 KiB) Viewed 1827 times

Offline

Screen Shot 2021-10-17 at 8.53.40 PM.png (186.23 KiB) Viewed 1827 times

[brubell]

The NVMTool should be updated to beta.13 now, I just pulled in the new binary (https://github.com/adafruit/Adafruit_We ... or/pull/13)

[adafruitguy]

Was able to pick-up bata.14, thank you!

Still not able to get the Feather Huzzah to come online. Clearly it's initially connecting to Adafruit IO as it's reporting with v1.0.0-beta.14.

Stubborn Feather Huzzah

Screen Shot 2021-10-18 at 4.01.34 PM.png (611.7 KiB) Viewed 1801 times

[adafruitguy]

Here's the logging from the Feather Huzzah 32...

Code: Select all

11:53:08.418 -> 
11:53:08.418 -> rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
11:53:08.418 -> configsip: 0, SPIWP:0xee
11:53:08.418 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
11:53:08.418 -> mode:DIO, clock div:1
11:53:08.418 -> load:0x3fff0030,len:1252
11:53:08.418 -> load:0x40078000,len:12732
11:53:08.455 -> load:0x40080400,len:3100
11:53:08.455 -> entry 0x400805ec
11:53:08.784 -> Subscribing to MQTT topics...
11:53:08.784 -> Added sub 0
11:53:08.784 -> Added sub 1
11:53:08.784 -> Added sub 2
11:53:08.822 -> Added sub 3
11:53:08.822 -> Added sub 4
11:53:11.602 -> Connecting to: io.adafruit.com
11:53:12.947 -> Connect result: 1
11:53:12.947 -> MQTT connect packet:
11:53:12.947 -> 	  [i]REDACTED DECODE[/i]
11:53:13.020 -> Client sendPacket returned: 95
11:53:13.057 -> Read data:		  [0x20], 
11:53:13.057 -> Packet Type:		  [0x20], 
11:53:13.057 -> Read data:		  [0x02], 
11:53:13.057 -> Packet Length:	2
11:53:13.057 -> Read data:		  [0x00],   [0x00], 
11:53:13.057 -> MQTT subscription packet:
11:53:13.057 ->  	 [i] REDACTED DECODE[/i]
11:53:13.131 -> Client sendPacket returned: 76
11:53:13.646 -> MQTT subscription packet:
11:53:13.646 -> 	  [i]REDACTED DECODE[/i]
11:53:13.718 -> Client sendPacket returned: 76
11:53:13.756 -> Read data:		  [0x90], 
11:53:13.756 -> Packet Type:		  [0x90], 
11:53:13.756 -> Read data:		  [0x03], 
11:53:13.756 -> Packet Length:	3
11:53:13.756 -> Read data:		  [0x00],   [0x01],   [0x01], 
11:53:13.792 -> MQTT subscription packet:
11:53:13.792 -> 	  [i]REDACTED DECODE[/i]
11:53:13.829 -> Client sendPacket returned: 80
11:53:13.902 -> Read data:		  [0x90], 
11:53:13.902 -> Packet Type:		  [0x90], 
11:53:13.902 -> Read data:		  [0x03], 
11:53:13.902 -> Packet Length:	3
11:53:13.902 -> Read data:		  [0x00],   [0x02],   [0x01], 
11:53:13.902 -> MQTT subscription packet:
11:53:13.902 ->  	  [i]REDACTED DECODE[/i]
11:53:13.976 -> Client sendPacket returned: 80
11:53:14.009 -> Read data:		  [0x90], 
11:53:14.009 -> Packet Type:		  [0x90], 
11:53:14.009 -> Read data:		  [0x03], 
11:53:14.009 -> Packet Length:	3
11:53:14.009 -> Read data:		  [0x00],   [0x03],   [0x01], 
11:53:14.009 -> MQTT subscription packet:
11:53:14.009 ->  	  [i]REDACTED DECODE[/i]
11:53:14.045 -> 	  [0x00], 
11:53:14.045 -> Client sendPacket returned: 25
11:53:14.081 -> Read data:		  [0x90], 
11:53:14.081 -> Packet Type:		  [0x90], 
11:53:14.081 -> Read data:		  [0x03], 
11:53:14.081 -> Packet Length:	3
11:53:14.081 -> Read data:		  [0x00],   [0x04],   [0x00], 
11:53:14.081 -> MQTT subscription packet:
11:53:14.081 ->  	  [i]REDACTED DECODE[/i]
11:53:14.118 -> Client sendPacket returned: 27
11:53:14.156 -> Read data:		  [0x90], 
11:53:14.156 -> Packet Type:		  [0x90], 
11:53:14.156 -> Read data:		  [0x03], 
11:53:14.156 -> Packet Length:	3
11:53:14.156 -> Read data:		  [0x00],   [0x05],   [0x00], 
11:53:14.156 -> Registering hardware with WipperSnapper...
11:53:14.156 -> Registering hardware with IO...
11:53:14.156 -> Encoding registration request...Encoding registration msg...MQTT publish packet:
11:53:14.192 ->  	 [i] REDACTED DECODE[/i]
11:53:14.228 -> Client sendPacket returned: 75
11:53:14.265 -> Publishing across:	 	 [i] REDACTED DIRECTORY[/i]
11:53:14.302 -> Read data:		@ [0x40], 
11:53:14.302 -> Packet Type:		@ [0x40], 
11:53:14.302 -> Read data:		  [0x02], 
11:53:14.302 -> Packet Length:	2
11:53:14.302 -> Read data:		  [0x00],   [0x06], 
11:53:14.302 -> Publish QOS1+ reply:		@ [0x40],   [0x02],   [0x00],   [0x06], 
11:53:14.302 -> Published!
11:53:14.302 -> Polling for registration message response...2
11:53:14.338 -> Polling for registration message response...2
11:53:14.338 -> Polling for registration message response...2
11:53:14.376 -> Polling for registration message response...2
11:53:14.412 -> Polling for registration message response...2
11:53:14.448 -> Polling for registration message response...2
11:53:14.483 -> Polling for registration message response...2
11:53:14.520 -> Polling for registration message response...2
11:53:14.520 -> Polling for registration message response...2
11:53:14.555 -> Polling for registration message response...2
11:53:14.592 -> Polling for registration message response...2
11:53:14.630 -> Polling for registration message response...2

[brubell]

Thanks for the serial output, I was just going to ask for that. Could you submit the error log to http://io.adafruit.com/support without redacted information? I need that information in order to dive into this bug. It will only go to the inbox of the IO team.

Thank you.

[adafruitguy]

I will send that now.

Hopefully it's coming through, I'm just getting a blank page when I hit submit.

[brubell]

Are you attempting to connect to a 5GHz network?

[adafruitguy]

My network supports 802.11a/b/g/n/ac/ax (2.4GHz as well as 5GHz Lo & Hi). The HUZZAH32 is spec’ed @ 802.11b/g/n which makes it a 2.4GHz device, and that’s where my network is seeing it show up…

HUZZAH32 Connected via 2.4GHz

197669A9-5DD1-4352-8258-9B71E3FDCB64.jpeg (89.53 KiB) Viewed 1721 times

I have a Metro M4 w/ Airlift & PyPortal Titano both running WipperSnapper which also have an ESP32 successfully connected via 2.4GHz to the same network. My ESP32-S2 WipperSnapper devices (Funhouse, MagTag, and Metro ESP32-S2) are also connected via the 2.4GHz band to the same network.

[brubell]

I'm going to look into that serial log when work on I2C ramps down, and get back to you. I'm gathering data for this specific registration error, as I've seen it a few times but am unable to locally reproduce it so far.

[adafruitguy]

I successfully installed WipperSnapper on second HUZZAH ESP32...

Two HUZZAH32's

Screen Shot 2021-11-09 at 7.51.32 AM.png (765.01 KiB) Viewed 1688 times

The working HUZZAH32 (pink Micro-B cable, on the right) happens to have different (simpler) markings on the chip packaging...

Different Packaging

IMG_0629.jpeg (1018.56 KiB) Viewed 1688 times

And the working HUZZAH32 board has "1617" in a 7-segment font on the back, and additional markings under the "32"...

HUZZAH32 Backside

Screen Shot 2021-11-09 at 7.59.14 AM.jpeg (288.32 KiB) Viewed 1688 times

Code load, and everything else was the same.

Possibly Rev 0 vs Rev 1 of the ESP32 silicon?

[brubell]

Oh, this is indeed strange, thanks for investigating. I'm using a much older Adafruit Feather ESP32.

Could you connect both feathers to the Adafruit ESPWebtool, https://adafruit.github.io/Adafruit_WebSerial_ESPTool. Then, copy and paste the data it outputs here. That'll let me look at differences between the modules.

[adafruitguy]

Both have been updated to Beta.15

Beta 15

Screen Shot 2021-11-18 at 2.47.17 PM.png (212.93 KiB) Viewed 1656 times

Same behavior unit one initially connects, shares it's version number and stays "offline", the second unit... No problem.

Output from "Adafruit_WebSerial_ESPTool", as requested, (not NVMGenerator)...

Unit 1:

Code: Select all

Adafruit WebSerial ESPTool loaded.
Connecting...
Connected successfully.
Try to reset.
Timed out after 100 milliseconds
Timed out after 100 milliseconds
Timed out after 100 milliseconds
Timed out after 100 milliseconds
Timed out after 100 milliseconds
Timed out after 100 milliseconds
Timed out after 100 milliseconds
Timed out after 100 milliseconds
Timed out after 100 milliseconds
Connected to ESP32
MAC Address: 30:AE:A4:14:0B:00
Uploading stub...
Running stub...
Stub is now running...
WARNING: ESP32 is having issues working at speeds faster than 115200. Continuing at 115200 for now...

Unit 2:

Code: Select all

Adafruit WebSerial ESPTool loaded.
Connecting...
Connected successfully.
Try to reset.
Timed out after 100 milliseconds
Timed out after 100 milliseconds
Timed out after 100 milliseconds
Timed out after 100 milliseconds
Timed out after 100 milliseconds
Timed out after 100 milliseconds
Timed out after 100 milliseconds
Timed out after 100 milliseconds
Timed out after 100 milliseconds
Connected to ESP32
MAC Address: 24:0A:C4:00:16:3E
Uploading stub...
Running stub...
Stub is now running...
WARNING: ESP32 is having issues working at speeds faster than 115200. Continuing at 115200 for now...