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

GNSS Sample - Callbacks do not get called with PuTTY and nRF7002DK #73927

Closed
BlimbBoat opened this issue Jun 7, 2024 · 6 comments
Closed

GNSS Sample - Callbacks do not get called with PuTTY and nRF7002DK #73927

BlimbBoat opened this issue Jun 7, 2024 · 6 comments
Assignees

Comments

@BlimbBoat
Copy link

Describe the bug
I am using the nRF7002-DK with PuTTY to test the GNSS sample.

My problem is whenever I send a NMEA0183 sentence: $GPGGA,092750.000,5321.6802,N,00630.3372,W,1,8,1.03,61.7,M,55.2,M,,*76
Nothing seems to happen. After spamming the message the following can be seen:

[00:00:25.367,645] <wrn> modem_chat: argv buffer overrun
[00:00:27.525,207] <wrn> modem_chat: receive buffer overrun

in my boards/nrf7002dk_nrf5340_cpuapp.overlay I added:

/ {
	aliases {
		gnss = &gnssdev;
	};
};

&uart2{
    status = "okay";

    current-speed = <9600>;
    data-bits = <8>;
    stop-bits = "1";
    parity = "none";

    pinctrl-0 = <&uart2_default>;
    pinctrl-names = "default";
    gnssdev: gnss-nmea-generic{
        compatible = "gnss-nmea-generic";
    };
};

&pinctrl {
    uart2_default: uart2_default {
        group1{
            psels = <NRF_PSEL(UART_TX, 0, 6)>;
        };
        group2{
            psels = <NRF_PSEL(UART_RX, 0, 7)>;
			bias-pull-up;
        };
    };
};

Environment (please complete the following information):

  • OS: Windows
  • Toolchain: nRF Connect SDK Toolchain v2.6.0

In the GNSS sample, it does state that a GNSS device is present, I thought that before having a GNSS device I could test it with PuTTY first, so maybe that is the problem.

Copy link

github-actions bot commented Jun 7, 2024

Hi @BlimbBoat! We appreciate you submitting your first issue for our open-source project. 🌟

Even though I'm a bot, I can assure you that the whole community is genuinely grateful for your time and effort. 🤖💙

@bjarki-andreasen
Copy link
Collaborator

Can you enable this option CONFIG_MODEM_MODULES_LOG_LEVEL_DBG=y in your prj.conf or using west build -t menuconfig?

My initial suspicion is that you are not sending the expected end delimiters when sending via PuTTY, should be "\r\n" :)

@bjarki-andreasen
Copy link
Collaborator

Additionally, you need to send both RMC and GGA before the driver calls back, since it uses data from both of those messages to populate struct gnss_data

@bjarki-andreasen
Copy link
Collaborator

oh, nvm, you need to add status="okay" to the gnssdev node :)

    gnssdev: gnss-nmea-generic{
        compatible = "gnss-nmea-generic";
        status = "okay";
    };

@BlimbBoat
Copy link
Author

Thanks for your comments!

I did not manage to do it using PuTTY, but I managed to send a GGA and RMC with the Serial Monitor in the Arduino IDE.

@bjarki-andreasen
Copy link
Collaborator

Good to know you made it work :)

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

No branches or pull requests

3 participants