Skip to content

Support Seeed Tracker-T1000-E-Pro#10067

Open
SeeedZhangyh wants to merge 8 commits intomeshtastic:developfrom
Seeed-Studio:tracker-t1000-e-pro
Open

Support Seeed Tracker-T1000-E-Pro#10067
SeeedZhangyh wants to merge 8 commits intomeshtastic:developfrom
Seeed-Studio:tracker-t1000-e-pro

Conversation

@SeeedZhangyh
Copy link
Copy Markdown

Support for the T1000-E-Pro Development Board

Summary

Building upon the previous release, this PR extends support to the Pro version of the Tracker-T1000-E, incorporating the necessary hardware adaptations and software implementations.

Key updates in this release include: upgrading the LoRa module to the LR2021, maintaining support for existing GNSS functionality with enhanced dual-frequency positioning via the AG3335, and adding integrated support for the DRV2605 haptic feedback motor. The specific changes are detailed below:

Board Support: T1000-E-Pro

Added support for the T1000-E-Pro development board: New configuration files and associated settings specific to the T1000-E-Pro have been added to ensure full compatibility and proper operation within the Meshtastic ecosystem.

LoRa Module Update: LR2021

The LoRa subsystem has been updated to support the LR20x0 series modules. Since the Pro version utilizes the LR2021 to replace the LoRa hardware found in the previous iteration, this update introduces the corresponding software adaptations required to ensure the LR2021 module communicates correctly and functions properly on the T1000-E-Pro board.

GNSS Enhancement: AG3335 (Dual-Frequency Support)

While maintaining compatibility with the existing GPS framework, the Pro version leverages the AG3335’s dual-frequency capability to provide improved positioning accuracy and reliability.

This PR represents a further extension of the support provided in the previous release. While the current implementation may still contain areas open to optimization, the community is warmly invited to provide suggestions and feedback to assist in the ongoing refinement of these features.

Thank you for considering this PR and for any help or guidance you can provide.

Best regards,

@github-actions github-actions bot added the hardware-support Hardware related: new devices or modules, problems specific to hardware label Apr 3, 2026
@fifieldt
Copy link
Copy Markdown
Member

fifieldt commented Apr 3, 2026

Thank you for this exciting news and substantial patch!

/* Heltec Mesh Node T096 board features an nRF52840 CPU and a TFT screen. */
meshtastic_HardwareModel_HELTEC_MESH_NODE_T096 = 127,
/* Seeed studio T1000-E Pro tracker card. NRF52840 w/ LR2021 radio, GPS, button, buzzer, and sensors. */
meshtastic_HardwareModel_TRACKER_T1000_E_PRO = 128,
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For this value we should make a patch to https://github.com/meshtastic/protobufs

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, i have done it.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you! I have approved and waiting for another collaborator to merge.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@SeeedZhangyh , the protobufs have been updated. You can probably update the submodule and the changes should disappear from this patch since they are already in the repository...

Comment thread platformio.ini Outdated
@CLAassistant
Copy link
Copy Markdown

CLAassistant commented Apr 3, 2026

CLA assistant check
All committers have signed the CLA.

@lyusupov
Copy link
Copy Markdown

lyusupov commented Apr 4, 2026

@SeeedZhangyh

These GPIO numbers do not match with port/pin mapping

image


No any of LR2021 DIO pins are defined as RF switch one(s)

image


No QSPI flash memory anymore ?

Comment thread platformio.ini
lib_deps =
# renovate: datasource=github-tags depName=RadioLib packageName=jgromes/RadioLib
https://github.com/jgromes/RadioLib/archive/refs/tags/7.6.0.zip
https://github.com/jgromes/RadioLib/archive/7971af87a2087e295586ec78ced73da3d6474765.zip
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FYI, there was another radiolib patch for the LR2021 that went in yesterday:

https://github.com/jgromes/RadioLib/commits/master/

9e8713fbe8812caf92380a9e577fb7442d8b29a5

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, a minor bug has been fixed. We will be using the latest dependency packages from now on. Thank you.

@fifieldt
Copy link
Copy Markdown
Member

fifieldt commented Apr 4, 2026

@SeeedZhangyh , firstly: thank you very much for adding LR2021 support! It's a big effort and we're super happy you've done it in a way that other devices can benefit. Very appreciated.

If possible, I would like to split this PR into two PRs -

  1. LR2021 support
  2. Tracker-T1000E-Pro support

Simply because smaller pieces of code generally make it easier/faster for the meshtastic code reviewers to complete their work. It's just a style preference, but I think it will help get this support merged faster.

If that is acceptable for you, let me know whether you might like to make the PRs, or whether you want me to try and manipulate git on your behalf :)

@SeeedZhangyh
Copy link
Copy Markdown
Author

@SeeedZhangyh

These GPIO numbers do not match with port/pin mapping

image


No any of LR2021 DIO pins are defined as RF switch one(s)

image


No QSPI flash memory anymore ?

Thanks for pointing it out, it was my oversight to modify the pin description.I will make changes in a later commit.

Regarding the issue of using the LR2021 pins as an RF switch, we haven't used it yet. If it's needed in the future, or if others need to use it, they can modify it here to maintain compatibility.

The QSPI flash memory is still retained in the hardware.

Thank you again.

@lyusupov
Copy link
Copy Markdown

lyusupov commented Apr 5, 2026

@SeeedZhangyh

The QSPI flash memory is still retained in the hardware.

Does the T1000-E-Pro flash use the same GPIOs as a regular T1000-E one ?

Does Meshtastic LR2021 node receive LoRa signal from SX127x based nodes or
the issue #4775 for LR11xx radio still remains valid for LR2021 as well ?

@SeeedZhangyh
Copy link
Copy Markdown
Author

@SeeedZhangyh

The QSPI flash memory is still retained in the hardware.

Does the T1000-E-Pro flash use the same GPIOs as a regular T1000-E one ?

Does Meshtastic LR2021 node receive LoRa signal from SX127x based nodes or
the issue #4775 for LR11xx radio still remains valid for LR2021 as well ?

The QSPI Flash pin assignments do not appear to have changed, though this still requires further verification.

Regarding the issues concerning the SX127x, I am currently unable to provide a precise response. I sincerely apologize for the delay; We will get back to you in a few days.

@SeeedZhangyh
Copy link
Copy Markdown
Author

@SeeedZhangyh , firstly: thank you very much for adding LR2021 support! It's a big effort and we're super happy you've done it in a way that other devices can benefit. Very appreciated.

If possible, I would like to split this PR into two PRs -

  1. LR2021 support
  2. Tracker-T1000E-Pro support

Simply because smaller pieces of code generally make it easier/faster for the meshtastic code reviewers to complete their work. It's just a style preference, but I think it will help get this support merged faster.

If that is acceptable for you, let me know whether you might like to make the PRs, or whether you want me to try and manipulate git on your behalf :)

It would also be fine if you could handle this on my behalf. Thank you very much.

@lyusupov
Copy link
Copy Markdown

lyusupov commented Apr 5, 2026

The QSPI Flash pin assignments do not appear to have changed, though this still requires further verification.

Thanks' !

yes, I can see that most GPIOs associated with QSPI flash remain vacant in your variant.h except P1.13

P1.13 in T1000-E is in use as QSPI flash ENABLE signal (active HIGH).
In T1000-E-PRO the P1.13 is occupied by GNSS VRTC:

image

@Lorondos
Copy link
Copy Markdown

Lorondos commented Apr 6, 2026

Hmm, I am curious about this board, is it in relation to this one?

https://www.seeedstudio.com/LR2021-LoRa-Plus-Evaluation-kit-868Mhz-EU-V2-0-p-6697.html

@SeeedZhangyh
Copy link
Copy Markdown
Author

The QSPI Flash pin assignments do not appear to have changed, though this still requires further verification.

Thanks' !

yes, I can see that most GPIOs associated with QSPI flash remain vacant in your variant.h except P1.13

P1.13 in T1000-E is in use as QSPI flash ENABLE signal (active HIGH). In T1000-E-PRO the P1.13 is occupied by GNSS VRTC:

image

Regarding the QSPI-related pins, the signal pins remain consistent with the Tracker-T1000-E;
only the power enable pin has been modified.
T1000-e VCC_FLASH_EN: P1.13
T1000-e-pro VCC_FLASH_EN: P0.15

@SeeedZhangyh
Copy link
Copy Markdown
Author

Hmm, I am curious about this board, is it in relation to this one?

https://www.seeedstudio.com/LR2021-LoRa-Plus-Evaluation-kit-868Mhz-EU-V2-0-p-6697.html

The board you mentioned utilizes the same LoRa module—the LR2021—as this board.
Essentially, it serves as an LR2021 development board, allowing you to swap in compatible microcontrollers or sensors to engage in DIY design and debugging activities.
The Tracker-T1000-E-Pro, on the other hand, is a LoRa-based tracker card that supports the Meshtastic protocol; it is a complete, ready-to-use product that works right out of the box.

@lyusupov
Copy link
Copy Markdown

lyusupov commented Apr 8, 2026

@SeeedZhangyh

Unlike regular T1000-E, the PRO has RTC, right ?

image
  1. What is make & model of the RTC ?

  2. The PRO has DRV2605 haptic IC but does NO longer have QMA6100P accelerometer IC, is that correct ?

@SeeedZhangyh
Copy link
Copy Markdown
Author

@SeeedZhangyh

Unlike regular T1000-E, the PRO has RTC, right ?

image 1. What is make & model of the RTC ? 2. The PRO has **DRV2605** haptic IC but does **NO** longer have **QMA6100P** accelerometer IC, is that correct ?
  1. The Pro model does indeed feature an RTC; however, we have not yet enabled it. In future updates, it can be used to provide time synchronization to the GNSS module, thereby accelerating satellite acquisition speeds.
  2. The Pro model no longer supports the QMA6100P sensor; however, we have reserved hardware interfaces for three types of sensors—an accelerometer, a magnetometer, and a air pressure sensor—for use in future versions (such as the PLUS).

@SeeedZhangyh SeeedZhangyh mentioned this pull request Apr 9, 2026
@SeeedZhangyh
Copy link
Copy Markdown
Author

@fifieldt I have split the submission into two parts. This PR contains only the tracker component, while the support updates for the lora2021 component are included in a separate PR #10111.

@fifieldt
Copy link
Copy Markdown
Member

fifieldt commented Apr 9, 2026

Thank you very much!

@Lorondos
Copy link
Copy Markdown

Lorondos commented Apr 9, 2026

Hmm, I am curious about this board, is it in relation to this one?
https://www.seeedstudio.com/LR2021-LoRa-Plus-Evaluation-kit-868Mhz-EU-V2-0-p-6697.html

The board you mentioned utilizes the same LoRa module—the LR2021—as this board. Essentially, it serves as an LR2021 development board, allowing you to swap in compatible microcontrollers or sensors to engage in DIY design and debugging activities. The Tracker-T1000-E-Pro, on the other hand, is a LoRa-based tracker card that supports the Meshtastic protocol; it is a complete, ready-to-use product that works right out of the box.

Ah so this is a new product! Nice! Thanks for coming back to me 🙂

@lyusupov
Copy link
Copy Markdown

lyusupov commented Apr 10, 2026

@SeeedZhangyh
Does the Pro come with Adafruit bootloader for nRF52840 ?
Regular bootloader for T1000-E uses "T1000-E" as a UF2 disk volume name. What is the UF2 volume name for T1000-E Pro bootloader ?

@SeeedZhangyh
Copy link
Copy Markdown
Author

@SeeedZhangyh Does the Pro come with Adafruit bootloader for nRF52840 ? Regular bootloader for T1000-E uses "T1000-E" as a UF2 disk volume name. What is the UF2 volume name for T1000-E Pro bootloader ?

Yes, Adafruit bootloader for nRF52840 will be pre-installed, and the UF2 disk volume name will be: T1000-E Pro.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds Meshtastic firmware support scaffolding for the Seeed SenseCAP Tracker T1000-E-Pro (nRF52840), including board/variant definitions and related platform integration.

Changes:

  • Introduces a new nRF52840 variant folder for tracker-t1000-e-pro (pins, peripherals, and PlatformIO env).
  • Extends deep-sleep handling to cover TRACKER_T1000_E_PRO and adjusts environmental telemetry sensor registration gating.
  • Updates the RadioLib dependency pin and adds the hardware model mapping in the nRF52 architecture layer.

Reviewed changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated 5 comments.

Show a summary per file
File Description
variants/nrf52840/tracker-t1000-e-pro/variant.h New pin/peripheral definitions (LR2021, GNSS, haptics, power pins, ADC config).
variants/nrf52840/tracker-t1000-e-pro/variant.cpp New initVariant() power/IO initialization for the board.
variants/nrf52840/tracker-t1000-e-pro/rfswitch.h Adds an LR2021 RF switch table stub for the variant.
variants/nrf52840/tracker-t1000-e-pro/platformio.ini Adds a new PlatformIO environment for the T1000-E-Pro build.
boards/tracker-t1000-e-pro.json Adds a new PlatformIO board definition JSON.
src/sleep.cpp Includes TRACKER_T1000_E_PRO in deep sleep GPIO/power-down handling and disables haptic power.
src/platform/nrf52/architecture.h Maps TRACKER_T1000_E_PRO to the protobuf hardware model enum.
src/modules/Telemetry/EnvironmentTelemetry.cpp Moves certain I2C sensor registration under the correct compile-time gating.
src/mesh/InterfacesTemplates.cpp Adds a new file header comment block.
platformio.ini Pins RadioLib to a specific commit ZIP instead of a tagged release.

extends = nrf52840_base
board = tracker-t1000-e-pro
board_level = pr
custom_meshtastic_hw_model = 71
Copy link

Copilot AI Apr 11, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

custom_meshtastic_hw_model is set to 71 (same as TRACKER_T1000_E), but the protobuf hardware model enum for TRACKER_T1000_E_PRO is 128 (see src/mesh/generated/meshtastic/mesh.pb.h). This mismatch will cause incorrect hwModel metadata/identification for this target.

Update custom_meshtastic_hw_model to 128 to match meshtastic_HardwareModel_TRACKER_T1000_E_PRO and keep custom_meshtastic_hw_model_slug consistent.

Suggested change
custom_meshtastic_hw_model = 71
custom_meshtastic_hw_model = 128

Copilot uses AI. Check for mistakes.
Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, that was my oversight.

Comment thread variants/nrf52840/tracker-t1000-e-pro/variant.h
Comment thread variants/nrf52840/tracker-t1000-e-pro/variant.h Outdated
Comment thread platformio.ini
* Arduino objects - C++ only
*----------------------------------------------------------------------------*/

#endif // _VARIANT_TRACKER_T1000_E_
Copy link

Copilot AI Apr 11, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Header guard end-comment refers to _VARIANT_TRACKER_T1000_E_, but the guard is _VARIANT_TRACKER_T1000_E_PRO. Update the comment to avoid confusion during maintenance.

Suggested change
#endif // _VARIANT_TRACKER_T1000_E_
#endif // _VARIANT_TRACKER_T1000_E_PRO

Copilot uses AI. Check for mistakes.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@lyusupov
Copy link
Copy Markdown

lyusupov commented Apr 14, 2026

@SeeedZhangyh

Is there an actual or 3D rendered picture of how the Pro Tracker will look like ?

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

Labels

hardware-support Hardware related: new devices or modules, problems specific to hardware

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants