Merge pull request #407 from david-cermak/bump/modem_1.0.4

bump(modem): 1.0.3 -> 1.0.4

components/esp_modem/.cz.yaml

@@ -3,6 +3,6 @@ commitizen:
   bump_message: 'bump(modem): $current_version -> $new_version'
   pre_bump_hooks: python ../../ci/changelog.py esp_modem
   tag_format: modem-v$version
-  version: 1.0.3
+  version: 1.0.4
   version_files:
   - idf_component.yml

components/esp_modem/CHANGELOG.md

@@ -1,5 +1,16 @@
 # Changelog
 
+## [1.0.4](https://github.com/espressif/esp-protocols/commits/modem-v1.0.4)
+
+### Bug Fixes
+
+- Added USB runner with ESP32S2 with A7670 ([edeb936](https://github.com/espressif/esp-protocols/commit/edeb936))
+- Extend docs on AT client example ([1f2ceed](https://github.com/espressif/esp-protocols/commit/1f2ceed))
+- Fix pytest exclusion, gitignore, and changelog checks ([2696221](https://github.com/espressif/esp-protocols/commit/2696221))
+- Fix DTE to post fragments to parsers for USB term ([1db1e15](https://github.com/espressif/esp-protocols/commit/1db1e15))
+- Fix DUAL_MODE regression from cb6e03ac ([2aada0f](https://github.com/espressif/esp-protocols/commit/2aada0f))
+- Fix AT client example to use custom AT processing ([1a5ba98](https://github.com/espressif/esp-protocols/commit/1a5ba98), [#352](https://github.com/espressif/esp-protocols/issues/352))
+
 ## [1.0.3](https://github.com/espressif/esp-protocols/commits/modem-v1.0.3)
 
 ### Bug Fixes

components/esp_modem/examples/modem_tcp_client/README.md

@@ -9,6 +9,20 @@ This example could be used in two different configurations:
 1) Custom TCP transport: Implements a TCP transport in form of AT commands and uses it as custom transport for mqtt client.
 2) Localhost listener: Uses standard transports to connect and forwards socket layer data from the client to the modem using AT commands.
 
+### Custom TCP transport
+
+This configuration expects that the network library, that is used to communicate with the endpoint uses `tcp_transport` component. In this example, we use `esp-mqtt` which supports custom transports so that we can implement a transport layer that communicate on TCP layer using AT commands. If we want to use TLS, we could add an SSL layer on top of this TCP layer.
+
+To enable this mode, please set `EXAMPLE_CUSTOM_TCP_TRANSPORT=y`
+
+![with custom tcp transport](at_client_tcp_transport.png)
+
+### Localhost listener
+
+This configuration could be used with any network library, which is connecting to a localhost endpoint instead of remote one. This example creates a localhost listener which basically mimics the remote endpoint by forwarding the traffic between the library and the TCP/socket layer of the modem (which is already secure if the TLS is used in the network library)
+
+![with localhost listener](at_client_localhost.png)
+
 ### Supported IDF versions
 
 This example is supported from IDF `v5.0`.

components/esp_modem/idf_component.yml

@@ -1,4 +1,4 @@
-version: "1.0.3"
+version: "1.0.4"
 description: esp modem
 url: https://github.com/espressif/esp-protocols/tree/master/components/esp_modem
 dependencies:

components/esp_modem/src/esp_modem_dte.cpp

@@ -313,6 +313,7 @@ void DTE::on_read(got_line_cb on_read_cb)
     if (on_read_cb == nullptr) {
         primary_term->set_read_cb(nullptr);
         internal_lock.unlock();
+        set_command_callbacks();
         return;
     }
     internal_lock.lock();