Subcategories

• Discussion

  General firmware discussion

  154
  Topics
  685
  Posts

  A

  The Pass to IP Layer .... string is generated into lwip library. I've added that string into the ethernet.c file that is part of the lwip library. I've built the wifi/scan project and then substituted the lwip.a file into the pycom-micropython project. The code used to generate that strings is something like this LWIP_DEBUGF(ETHARP_DEBUG, ("Pass to IP Layer \n")); Of course i've changed the ETHARP_DEBUG value from LWIP_DBG_OFF to LWIP_DBG_ON into lwipopts.h header file in order to enable the ETHARP DEBUG. The TCP - _send_receive ... string is generated at level application. I'm using a TCP Modbus external python library. I've added the following code into the library print('TCP - _send_receive - Receive %s' % response) The application (and the modbus tcp library of course) is frozen into the final build and then uploaded through pycom firmware update tool. TCP Modbus messages are managed from a manager that runs as a python thread. The log output is got from USB interface.
• Enhancements

  Firmware wishlist & desired features

  52
  Topics
  236
  Posts

  J

  @Gijs I think it's a concern of many users that Pycom is spreading resources thin by working on too many new products which never see the light of day while not following up enough on the existing products. Let's just consider this list of Pycom vapourware: PyGo 1/2 + PyLife : first announced 25/09/2018 (soon to be 3 years ago). PyNode range: announced 25/06/2020 PyNode Touch: announced 06/07/2020 Expansion board V4: announced 14/10/2020 M.2 format boards: announced 17/11/2020 ESP32-S3-based boards: announced 01/02/2021 PyNode+ range: announced 08/02/2021 I know time-to-market can be essential in this industry but this is getting a bit out of hand...
• Issues & Bugs

  Anything related to firmware issues & bugs

  267
  Topics
  1518
  Posts

  G

  I am having the same problem. Is there a solution?