-
Notifications
You must be signed in to change notification settings - Fork 964
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
[Bug]: Gps not present/ GPS not working anymore on Faketec Node since firmware version 2.5.15 #5521
Comments
This was tested on 4 builds of the exact same kind and used hardware I made with the exact same outcome as described above. |
Can you please provide logs of the early startup, perhaps using the Serial Console on https://flasher.meshtastic.org ? |
Log output under 2.5.14 were everything is working normal:
|
after updating to 2.5.15 or daily 2.5.16 startup is laggy and button presses are ignored, like it always is when gps is enabled and cant find it. I just realized that once its done with the first gps search and "gives up" I actually can enable and disable gps but it still cant find it anymore for some reason.
Powered by ▲ Vercel | Meshtastic® is a registered trademark of Meshtastic LLC. | Legal Information. Connected |
its an ATGM336H |
Excellent! I have a ton of these (and some RAK's already wired up to them). One of my favorites. I can try to reproduce this locally. |
Same, they have a super small footprint, work great and are very inexpensive, I pretty much use them for all of my builds by now ;) |
Tried using my closest combination - T114 (NRF52) and ATGM332D. Was not able to reproduce - detection and GPS worked fine.
|
Oh, interesting. I just noticed that your ATGM336H is detected as an L76K when it is "working", rather than an ATGM336H. Can you make a firmware with GPS_DEBUG set to 1 in the variant.h and paste the log results here? |
sadly I never compiled my own firmware for my nodes, but I also have a ATGM336H running on my T114 V2 without a problem on 2.5.15............ could it be that TX and RX are swapped for some reason? one thing I noticed on the faketec build is that when you connect RX to RX and TX to TX it does not help to swap gpios in the meshtastic app, only when I physically swapped the cables it started working for me ( tx ->rx and rx ->tx) |
Not a problem. What I'm wondering is if your ATGM336H's on these new nodes reply slightly differently to other ATGM336Hs we've seen before. Easy to update once we get what it's saying. If it's not replying at all (RX/TX swap/connection problem), we'll be able to see that straight away with GPS_DEBUG. Which variant are you using from the flasher? I can make a GPS_DEBUG build for you :) |
That would be great: |
Tested out fine for me on the latest with RAK4631 connected to ATGM336H module over UART. Detected on startup (as L76K which is normal) and got a GPS lock shortly thereafter.
|
Could the Promicro NRF52 dev board be the "culprint"? I am not owning a RAK so no clue how it would behave there. I am having this problem on a FakeTec build. ( same GPS module works fine on 2.5.16 with a Heltec T114) |
Cheese............ I feel stupid right now, there is a new bootloader available for the Pro micro NRF52 dev board. 0.9.2 after updating it and flashing the most recent nightly build it works normal again........Sorry I had no clue that a bootloader is so critical for this to work?! |
4 boards now all working after updating to newest bootloader version. I tested all of them by just updating to recent firmware, all of them could not find gps after the update, but all work fine now. Interesting is that when I updated to most recent firmware first before updating the bootloader, it did not work flashing the same firmware after flashing the bootloader, I had to go one back and then forth to most recent again to make it finally work. Sorry and also Thanks for the effort from everyone involved. |
Category
Other
Hardware
Other
Firmware Version
2.5.15.79da236
Description
Faketec Node NRF52 dev board with HT RA-62 ( new variant that finally works flawless!) Gps is not recognized anymore ( GPS not present)
Reverting back to 2.5.14 and it works again.
Relevant log output
No response
The text was updated successfully, but these errors were encountered: