Author Topic: Fatal exception  (Read 3336 times)

rwohleb

  • Newbie
  • *
  • Posts: 6
Fatal exception
« on: February 21, 2016, 12:37:55 am »
I've been working on a small sketch to read a DHT22 temperature sensor and post the data to the Adafruit IO service. I originally tried using their basic REST library and got HTTP 400 errors, but since AIO is beta I figured it might be on their end. I've definitely had a hell of a time with flashing failing quite often through Particle, so it's been hard to debug things.

I then switched over to the Adafruit MQTT library to see if that would be any better. Once again, repeated flashing failures, and nothing via the serial connection gives any hint why. To make sure it wasn't me I tried to push out the example blink sketch and it went through just fine. I switched back to trying to push my sketch and bam: I get a single exception message part way through my setup function, a stack dump, and then spammed with a repeating fatal exception message.
Code: [Select]
ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BP,0

Oak Temp Sensor
WiFi Connected!
IP address: 192.168.1.140

Exception (3):
epc1=0x4020dcd6 epc2=0x00000000 epc3=0x00000000 excvaddr=0x40237708 depc=0x00000000

ctx: cont
sp: 3fff2810 end: 3fff2a30 offset: 01a0

>>>stack>>>
3fff29b0:  40219797 3fff19fc 00000000 40209e6e 
3fff29c0:  3fff2a00 3ffe913d 00000001 3fff19fc 
3fff29d0:  3fffdc20 00000000 3fff2a84 4020de88 
3fff29e0:  40237708 0000000d 3fff2a84 4020df08 
3fff29f0:  3fffdc20 3fff2ab8 3fff2a84 40207cce 
3fff2a00:  3ffe8848 8c01a8c0 3fff19f4 40209f74 
3fff2a10:  3fffdc20 00000000 3fff19f4 40209653 
3fff2a20:  00000000 00000000 3fff1a10 40100114 
<<<stack<<<

 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - E,BC,8

Fatal exception (0):
epc1=0x402259b0, epc2=0x00000000, epc3=0x00000000, excvaddr=0x40237708, depc=0x00000000
Fatal exception (0):
epc1=0x402259b0, epc2=0x00000000, epc3=0x00000000, excvaddr=0x40237708, depc=0x00000000
Fatal exception (0):
epc1=0x402259b0, epc2=0x00000000, epc3=0x00000000, excvaddr=0x40237708, depc=0x00000000
Fatal exception (0):

Not sure if this means it's bricked or not, but seems like it's refusing to check particle.io any longer. Maybe the previous flashing failures are related, but then again it could just be the slow OTA flashing mode.

byronsalty

  • Newbie
  • *
  • Posts: 7
Re: Fatal exception
« Reply #1 on: February 21, 2016, 08:32:23 am »
An http 400 error would imply that it's not a server problem. It was 400 specifically? Not 401 or 404?

If so it's saying that you're not providing the right parameters or they are malformed.

rwohleb

  • Newbie
  • *
  • Posts: 6
Re: Fatal exception
« Reply #2 on: February 21, 2016, 01:36:19 pm »
Yeah, it was 400. As you said, it normally means a malformed request but I was using the library provided by Adafruit, so either it's having an odd interaction with the Oak stack or it is indeed on the AIO end. I know that a few people using MQTT on AIO have posted about issues this last week, so hard to say where the issue is in the chain without further debugging... and that has not come easy so far. I'm REALLY looking forward to fast and reliable OTA flashing.

rwohleb

  • Newbie
  • *
  • Posts: 6
Re: Fatal exception
« Reply #3 on: February 23, 2016, 03:35:15 pm »
The HTTP 400 error aside, the Oak is currently in a bad state. I would assume this is what other's are referring to as "bricked" in other discussions, but for all I know those units are much worse off.

In any case, I've left the unit in this condition in case Digistump needs any memory dumps or anything. My serial cable is standing by. Just let me know what you need.