Arduino Client - Exception thrown when parsing beacon message #1

New issue

Closed

opened 2016-10-16 14:12:47 +00:00 by sbrl · 1 comment

sbrl commented

2016-10-16 14:12:47 +00:00

Owner

We've got UDP datagram receiving online, but the parser seems to be throwing an exception! Here's the full output:

Hello, world!
Beginning connection sequence.
Attempting to connect to evenstar-2.4 - success!
IP Address: 192.168.0.11
Initialising PixelHub auto detection system - success!
Listening for PixelHub beacon pings.
Received datagram #23 bytes in size from 192.168.0.3:5050.
Content as hex: 73 65 72 76 65 72 40 31 39 32 2E 31 36 38 2E 30 2E 33 3A 35 30 35 30 
Raw content: server@192.168.0.3:5050
Parsing datagram - 
Exception (29):
epc1=0x4000c118 epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000

ctx: cont 
sp: 3ffef2e0 end: 3ffef600 offset: 01a0

>>>stack>>>
3ffef480:  3ffef490 00000017 3ffee5a4 40201f9a  
3ffef490:  76726573 31407265 312e3239 302e3836  
3ffef4a0:  353a332e 00303530 3ffef50f 402034d0  
3ffef4b0:  3ffeff0c 40202368 3ffe8361 3ffee5a4  
3ffef4c0:  00000031 0000000a 3ffee5a4 40202e11  
3ffef4d0:  3ffef50e 72617473 342e322d efeffe00  
3ffef4e0:  efeffefe efeffefe 3ffef50d 40202efd  
3ffef4f0:  32354632 37363139 33373034 00000000  
3ffef500:  fee3ec00 1004d83f efeffe40 313131fe  
3ffef510:  fe85fd00 2028803f 00000040 00000b00  
3ffef520:  00000009 2028803f ffdad040 00001e3f  
3ffef530:  ffffff00 0000002d 3ffe8482 402034d0  
3ffef540:  3ffee5a4 0000000a 00000003 3ffef590  
3ffef550:  00002710 3ffee4b0 3ffee5a4 40202e11  
3ffef560:  3ffe8455 0000000b 3ffe8453 3ffee5d0  
3ffef570:  00002710 0000000c 3ffee5a4 40202e24  
3ffef580:  3ffe8784 3ffee4b0 3ffee5a4 40201e92  
3ffef590:  3ffe8780 0300a8c0 3ffe8780 0b00a8c0  
3ffef5a0:  3ffef490 3ffef490 0100a8c0 00000016  
3ffef5b0:  00000000 3ffee4b0 3ffee5a4 40201dd2  
3ffef5c0:  3ffe8780 0b00a8c0 3ffee5a4 3ffee5d0  
3ffef5d0:  00002710 3ffee4b0 3ffee5a4 402020e8  
3ffef5e0:  3fffdad0 00000000 3ffee5c8 40203144  
3ffef5f0:  feefeffe feefeffe 3ffee5e0 40100718  
<<<stack<<<

It doesn't appear to tell us what the problem was.

We've got UDP datagram receiving online, but the parser seems to be throwing an exception! Here's the full output: ``` Hello, world! Beginning connection sequence. Attempting to connect to evenstar-2.4 - success! IP Address: 192.168.0.11 Initialising PixelHub auto detection system - success! Listening for PixelHub beacon pings. Received datagram #23 bytes in size from 192.168.0.3:5050. Content as hex: 73 65 72 76 65 72 40 31 39 32 2E 31 36 38 2E 30 2E 33 3A 35 30 35 30 Raw content: server@192.168.0.3:5050 Parsing datagram - Exception (29): epc1=0x4000c118 epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000 ctx: cont sp: 3ffef2e0 end: 3ffef600 offset: 01a0 >>>stack>>> 3ffef480: 3ffef490 00000017 3ffee5a4 40201f9a 3ffef490: 76726573 31407265 312e3239 302e3836 3ffef4a0: 353a332e 00303530 3ffef50f 402034d0 3ffef4b0: 3ffeff0c 40202368 3ffe8361 3ffee5a4 3ffef4c0: 00000031 0000000a 3ffee5a4 40202e11 3ffef4d0: 3ffef50e 72617473 342e322d efeffe00 3ffef4e0: efeffefe efeffefe 3ffef50d 40202efd 3ffef4f0: 32354632 37363139 33373034 00000000 3ffef500: fee3ec00 1004d83f efeffe40 313131fe 3ffef510: fe85fd00 2028803f 00000040 00000b00 3ffef520: 00000009 2028803f ffdad040 00001e3f 3ffef530: ffffff00 0000002d 3ffe8482 402034d0 3ffef540: 3ffee5a4 0000000a 00000003 3ffef590 3ffef550: 00002710 3ffee4b0 3ffee5a4 40202e11 3ffef560: 3ffe8455 0000000b 3ffe8453 3ffee5d0 3ffef570: 00002710 0000000c 3ffee5a4 40202e24 3ffef580: 3ffe8784 3ffee4b0 3ffee5a4 40201e92 3ffef590: 3ffe8780 0300a8c0 3ffe8780 0b00a8c0 3ffef5a0: 3ffef490 3ffef490 0100a8c0 00000016 3ffef5b0: 00000000 3ffee4b0 3ffee5a4 40201dd2 3ffef5c0: 3ffe8780 0b00a8c0 3ffee5a4 3ffee5d0 3ffef5d0: 00002710 3ffee4b0 3ffee5a4 402020e8 3ffef5e0: 3fffdad0 00000000 3ffee5c8 40203144 3ffef5f0: feefeffe feefeffe 3ffee5e0 40100718 <<<stack<<< ``` It doesn't appear to tell us what the problem was.

sbrl commented

2016-12-11 20:27:29 +00:00

Author

Owner

After a long time debugging the dratted thing this its finally fixed - the TCP connect has finally been opened 😄

After a long time debugging the dratted thing this its finally fixed - the TCP connect has finally been opened :smile: