The netconn thread receives SNMP packets and processes them in the SNMP stack, nothing else. It never calls snmp_set_device_enterprise_oid(). Put a breakpoint in calls snmp_set_device_enterprise_oid() and check the call stack. I guess it's your application that makes this call from the wrong thread.
Ciao Dirk On Thu, Mar 12, 2020 at 10:57 AM Harrold Spier <harrold.sp...@gmail.com> wrote: > Hi, > > After enabling core locked check (LWIP_ASSERT_CORE_LOCKED > and LWIP_MARK_TCPIP_THREAD), I got a lot of asserts in SNMP functions. > > I use the SNMP netconn implementation (SNMP_USE_NETCONN = 1), so I assume > all SNMP functions should be called by the snmp_netconn thread, not by > the tcpip_thread. > So why does a function like snmp_set_device_enterprise_oid() does a core > check (LWIP_ASSERT_CORE_LOCKED())? > I assume this would only be valid for the snmp raw implementation. > > Or do I miss something? > > Best regards, > Harrold > _______________________________________________ > lwip-users mailing list > lwip-users@nongnu.org > https://lists.nongnu.org/mailman/listinfo/lwip-users
_______________________________________________ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
