Allow Device OS to initialize BG95-S5 modems #2842
Merged
Conversation
This file contains 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
technobly
approved these changes
Nov 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem
Device OS fails to init BG95-S5 modem due to failing
AT+CPIN?commands. See discussion hereSolution
Skip querying CPIN for BG95-S5 modems.
Note: At time of manufacture, the device will boot with no NCPID. So Quectel NCP client will be configured with
PLATFORM_NCP_UNKNOWN.After the NCPID has been programmed, and the client is turned on, we need to query OTP for the NCPID in order to know that the unit has a BG95S5 and should skip the
AT+CPIN?commands.Steps to Test
Run DVOS + msom provisioning firmware
Example App
Use provisioning firmware
References
Links to the Community, Docs, Other Issues, etc..
Completeness