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

AT Messages Debug #23

Open
yldzmuhammed opened this issue Jan 2, 2020 · 3 comments
Open

AT Messages Debug #23

yldzmuhammed opened this issue Jan 2, 2020 · 3 comments

Comments

@yldzmuhammed
Copy link

Hello,

Is it possible to see sended and received at messages between mcu and module?

I enabled all the debug modes but no luck.

I dont want to make any changes on the library functions. But i think it could add on the received data process function. Am i correct?

@MaJerle
Copy link
Owner

MaJerle commented Jan 2, 2020

Library does not support this feature as not all commands are processed through same internal channel.
if this is necessary, low-level driver shall implement this debug, part where you have to make your port for your architecture.

@yldzmuhammed
Copy link
Author

yldzmuhammed commented Jan 2, 2020

Hi @MaJerle

In fact, it would be perfect if it could be possible.

Can you guide me how should i do this?

Using STM32F7 with keil and freertos (with CMSIS V2).

Edit: For transmitting commands from mcu, it is easy. just call debugger tx function. But what about for receive response from module? How it would be done?

If i am not wrong, you are receiving data via DMA. So i have to wait for all data come in.

Do i miss anything?

@MaJerle
Copy link
Owner

MaJerle commented Jan 2, 2020

Well, there is a function gsm_input_process which accepts received characters for processing. You can call your debugger rx function afterwards with same data to send these to your PC (or wherever you want).

Port for win32 supports this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants