Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

esp32 - tcp_server_blink example #120

Closed
flbauer opened this issue Oct 23, 2019 · 2 comments
Closed

esp32 - tcp_server_blink example #120

flbauer opened this issue Oct 23, 2019 · 2 comments

Comments

@flbauer
Copy link

flbauer commented Oct 23, 2019

Hello,

Hooray, I observed that in the meantime tcp_server-Example is available.
Is it already operational? When connecting with browser Im getting a reboot:

`I (2071) NETWORK: SYSTEM_EVENT_STA_CONNECTED received.
I (4761) event: sta ip: 192.168.2.104, mask: 255.255.255.0, gw: 192.168.2.1
I (4761) NETWORK: SYSTEM_EVENT_STA_GOT_IP: 192.168.2.104
connected
{{192,168,2,104},{255,255,255,0},{192,168,2,1}}
Listening on port 44404.
Waiting to accept connection...
Accepted connection.
Waiting to receive data...
Waiting to accept connection...
<<71,69,84,32,47,32,72,84,84,80,47,49,46,49,13,10,72,111,115,116,58,32,49,57,50,46,49,54,56,46,50,46,49,48,52,58,52,52,52,48,52,13,10,85,115,101,114,45,65,103,101,110,116,58,32,77,111,122,105,108,108,97,47,53,46,48,32,40,88,49,49,59,32,85,98,117,110,116,117,59,32,76,105,110,117,120,32,120,56,54,95,54,52,59,32,114,118,58,54,56,46,48,41,32,71,101,99,107,111,47,50,48,49,48,48,49,48,49,32,70,105,114,101,102,111,120,47,54,56,46,48,13,10,65,99,99,101,112,116,58,32,116,101,120,116,47,104,116,109,108,44,97,112,112,108,105,99,97,116,105,111,110,47,120,104,116,109,108,43,120,109,108,44,97,112,112,108,105,99,97,116,105,111,110,47,120,109,108,59,113,61,48,46,57,44,42,47,42,59,113,61,48,46,56,13,10,65,99,99,101,112,116,45,76,97,110,103,117,97,103,101,58,32,100,101,44,101,110,45,85,83,59,113,61,48,46,55,44,101,110,59,113,61,48,46,51,13,10,65,99,99,101,112,116,45,69,110,99,111,100,105,110,103,58,32,103,122,105,112,44,32,100,101,102,108,97,116,101,13,10,68,78,84,58,32,49,13,10,67,111,110,110,101,99,116,105,111,110,58,32,107,101,101,112,45,97,108,105,118,101,13,10,85,112,103,114,97,100,101,45,73,110,115,101,99,117,114,101,45,82,101,113,117,101,115,116,115,58,32,49,13,10,80,114,97,103,109,97,58,32,110,111,45,99,97,99,104,101,13,10,67,97,99,104,101,45,67,111,110,116,114,111,108,58,32,110,111,45,99,97,99,104,101,13,10,13,10>>
Sending packet back to client...
Waiting to receive data...
warning: event descriptor not found
abort() was called at PC 0x4014ae2d on core 1
0x4014ae2d: socket_callback at /home/florian/AtomVM/src/platforms/esp32/main/socket_driver.c:90

Backtrace: 0x40091780:0x3ffbe500 0x400919ad:0x3ffbe520 0x4014ae2d:0x3ffbe540 0x40149ba1:0x3ffbe570 0x4013ab21:0x3ffbe590 0x40140ae3:0x3ffbe5b0 0x401455e5:0x3ffbe5d0 0x40135c77:0x3ffbe5f0 0x4008e841:0x3ffbe620
0x40091780: invoke_abort at /home/florian/esp/esp-idf/components/esp32/panic.c:707

0x400919ad: abort at /home/florian/esp/esp-idf/components/esp32/panic.c:707

0x4014ae2d: socket_callback at /home/florian/AtomVM/src/platforms/esp32/main/socket_driver.c:90

0x40149ba1: recv_tcp at /home/florian/esp/esp-idf/components/lwip/lwip/src/api/api_msg.c:1447 (discriminator 6)

0x4013ab21: tcp_input at /home/florian/esp/esp-idf/components/lwip/lwip/src/core/tcp_in.c:435 (discriminator 1)

0x40140ae3: ip4_input at /home/florian/esp/esp-idf/components/lwip/lwip/src/core/ipv4/ip4.c:746

0x401455e5: ethernet_input at /home/florian/esp/esp-idf/components/lwip/lwip/src/netif/ethernet.c:184

0x40135c77: tcpip_thread at /home/florian/esp/esp-idf/components/lwip/lwip/src/api/tcpip.c:483

0x4008e841: vPortTaskWrapper at /home/florian/esp/esp-idf/components/freertos/port.c:403

Rebooting...
ets Jun 8 2016 00:22:57
`

@flbauer
Copy link
Author

flbauer commented Oct 24, 2019

I enabled TRACE to see more: a new connection appears in the netconn callback for which no event descriptor is registered:

connected {{192,168,2,104},{255,255,255,0},{192,168,2,1}} socket: init socket: creating server tcp netconn socket: opened event descriptor 0 in init_server_tcp_socket for netconn 0x3ffc30a4 socket: binding to IP_ADDR_ANY on port 44404 socket: bound to port 44404 socket: listening on port 44404 Listening on port 44404. Waiting to accept connection... socket: accepting tcp netconn socket: Found event descriptor in socket_driver_do_accept for netconn 0x3ffc30a4 socket: accepting tcp netconn COMPLETE socket: netconn callback, netconn: 0x3ffc30a4, evt: 0, len: 0 event_descriptor[0]: 0x3ffc30a4 socket: accepting callback socket: Found event descriptor in accept_callback for netconn 0x3ffc30a4 socket: netconn callback, netconn: 0x3ffc2d90, evt: 0, len: 344 event_descriptor[0]: 0x3ffc30a4 warning: event descriptor not found socket: event descriptor not found in socket_callback for netconn 0x3ffc2d90 abort() was called at PC 0x4014af3c on core 0 0x4014af3c: socket_callback at /home/florian/AtomVM/src/platforms/esp32/main/socket_driver.c:90

@flbauer
Copy link
Author

flbauer commented Oct 24, 2019

The mentioned behaviour occurs with browser.
When I use nc 44404 it works nicely.
However when cancelling the nc command and issueing a new one a reboot occurs.

@flbauer flbauer closed this as completed Oct 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant