Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GSM_PPP api keeps sending commands to muxed AT channel #48625

Closed
ivonalo opened this issue Aug 3, 2022 · 3 comments
Closed

GSM_PPP api keeps sending commands to muxed AT channel #48625

ivonalo opened this issue Aug 3, 2022 · 3 comments
Assignees
Labels
area: Modem bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug Stale
Milestone

Comments

@ivonalo
Copy link

ivonalo commented Aug 3, 2022

When enabling the CONFIG_MODEM_GSM_PPP=y and CONFIG_GSM_MUX=y options the gsm_ppp.c api keeps sending "AT+CSQ" command to the modem with the CONFIG_MODEM_GSM_RSSI_POLLING_PERIOD period.
Because of this, when I am sending some other AT commands in my custom api to the muxed AT channel, the response to my AT command interferes with the response to the AT+CSQ command and part of my command output gets lost.
Any idea how to solve this issue of responses interfering?

@ivonalo ivonalo added the bug The issue is a bug, or the PR is fixing a bug label Aug 3, 2022
@ivonalo
Copy link
Author

ivonalo commented Aug 8, 2022

My question is how to synchronize the access to the modem with the gsm_ppp.c file from the application code? The semaphore is initialized in the gsm_ppp.c file and I have no idea how to access it from my application code

@rerickson1
Copy link
Member

This should not be synchronized from the application code. The driver needs to change to have proper locking to account for this use case.

@github-actions
Copy link

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Modem bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug Stale
Projects
None yet
Development

No branches or pull requests

4 participants