Repository navigation
WIP: Example of uProtocol and MQTT5 on NetX Duo - #82
Open
justinhrpr-cmi wants to merge 5 commits into
Open
justinhrpr-cmi wants to merge 5 commits into
justinhrpr-cmi wants to merge 5 commits into
Conversation
justinhrpr-cmi
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds a uprotocol-mqtt AZ3166 example using uProtocol 1.6 over MQTT 5. The original mqtt example remains a separate MQTT 3.1.1 target. The AZ3166 NetX Duo submodule is pinned to fork commit 0edae5f, which contains the MQTT 5 and uProtocol addons. This should updated if the forked NetX Duo commit is merged.
Board testing exposed issues in the shared WICED/NetX integration: DHCP could start before Wi-Fi joined, and NetX lacked the interface MAC, MTU, and Ethernet address mapping needed for reliable unicast traffic. This PR updates app/common and board library configuration to address those issues. These shared changes also apply to starter, mqtt, and arcade.
Validation: starter, telemetry, mqtt, arcade, and uprotocol-mqtt cross-build successfully. Board testing has confirmed network initialization for the new example, and we tested end-to-end MQTT 5/uProtocol publication and reception with an example broker application. The other examples have not been run on hardware with these shared changes.