Dragino TrackerD Support

Support
1

Sorry I’m fairly new to all this but I noticed that in Firmware release 2.2.12.092e6f2
(Release Meshtastic Firmware 2.2.12.092e6f2 Beta · meshtastic/firmware · GitHub) that there was a mention of initial support for the TrackerD device (TrackerD -- LoRaWAN Tracker)

My question is how do I get the meshtastic firmware onto the TrackerD device? I don’t see a specific hardware firmware listed in the zip file. Will one of the Esp32 based devices work for the TrackerD or is there another way to work this?

Thanks in advance for any insight and I apologize for the newbie question.

2

Anyone able to assist?

3

You’ll have to build the firmware yourself, since it’s not an officially supported device. See the instructions here: Building Meshtastic Firmware | Meshtastic

4

Ok you got me on the right track until I actually went to build the firmware. After attempting to build it I got the following error:

src/Power.cpp:40:43: error: ‘ADC_CHANNEL’ was not declared in this scope
static const adc1_channel_t adc_channel = ADC_CHANNEL;
^~~~~~~~~~~
src/Power.cpp:40:43: note: suggested alternative: ‘ADC_CHANNEL_9’
static const adc1_channel_t adc_channel = ADC_CHANNEL;
^~~~~~~~~~~
ADC_CHANNEL_9
*** [.pio\build\trackerd\src\Power.cpp.o] Error 1

checking in the Power.cpp.o file I see this line as the problem where the ADC_CHANNEL was not declared:

#ifndef BAT_MEASURE_ADC_UNIT // ADC1 is default

static const adc1_channel_t adc_channel = ADC_CHANNEL;

static const adc_unit_t unit = ADC_UNIT_1;

#else // ADC2

static const adc2_channel_t adc_channel = ADC_CHANNEL;

static const adc_unit_t unit = ADC_UNIT_2;

RTC_NOINIT_ATTR uint64_t RTC_reg_b;

anyone able to help with this??

Thanks in advance!

5

You’ll have to add a #define ADC_CHANNEL <enter_the_correct_channel_here> in the variant file for the Tracker D.

Or if you don’t want to deal with compilation issues, you could use the release where pull request for this device was merged.

6

I got dragino working with meshtastic

869×407 406 KB

Check my pull request.

1 Like
7

checked on my device: worked @fzellini Thanks

1 Like
8

Hi
I am not very skilled in programming but I have programmed several devices with meshtastic, but I need to enable some Dragino TrackerD devices. Could you tell me how to do it, since I cannot find the appropriate firmware on the flasherweb.
Can you give any directions please?
Regards

9

there are no Dragino TrackerD firmware on CI/CD. waiting for [Feature Request]: add trackerd to CI/CD compilation · Issue #4024 · meshtastic/firmware · GitHub
you can start from this instruction build Building Meshtastic Firmware | Meshtastic
but this is long way for you…
I can provide firmware build by myself - but you still need some pyhon staf and so
Flashing with the CLI | Meshtastic

1 Like
10

Hi Alexander
If you can provide me the firmware I can try with python CLI.

Thank you very much.

11
12

Thank you Alexander.
I flasshed it but It does not work. All is going well but finnaly I can not connect to it with the Meshtastic configuration web.

I did this:

C:\Users\YOGA\Documents\Meshtastic TrackerD>device-install.bat -f 2.4.2.59cc57fc.bin
Trying to flash update 2.4.2.59cc57fc.bin, but first erasing and writing system information"
esptool.py v4.7.0
Found 1 serial ports
Serial port COM4
Connecting…
Detecting chip type… Unsupported detection protocol, switching and trying again…
Connecting…
Detecting chip type… ESP32
Chip is ESP32-PICO-D4 (revision v1.0)
Features: WiFi, BT, Dual Core, 240MHz, Embedded Flash, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 4c:75:25:df:8c:08
Uploading stub…
Running stub…
Stub running…
Erasing flash (this may take a while)…
Chip erase completed successfully in 5.4s
Hard resetting via RTS pin…
esptool.py v4.7.0
Found 1 serial ports
Serial port COM4
Connecting…
Detecting chip type… Unsupported detection protocol, switching and trying again…
Connecting…
Detecting chip type… ESP32
Chip is ESP32-PICO-D4 (revision v1.0)
Features: WiFi, BT, Dual Core, 240MHz, Embedded Flash, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 4c:75:25:df:8c:08
Uploading stub…
Running stub…
Stub running…
Configuring flash size…
Flash will be erased from 0x00000000 to 0x001d9fff…
Compressed 1938496 bytes to 1205934…
Wrote 1938496 bytes (1205934 compressed) at 0x00000000 in 106.7 seconds (effective 145.3 kbit/s)…
Hash of data verified.

Leaving…
Hard resetting via RTS pin…
usage: esptool write_flash [-h] [–erase-all] [–flash_freq {keep,80m,60m,48m,40m,30m,26m,24m,20m,16m,15m,12m}]
[–flash_mode {keep,qio,qout,dio,dout}]
[–flash_size {detect,keep,256KB,512KB,1MB,2MB,2MB-c1,4MB,4MB-c1,8MB,16MB,32MB,64MB,128MB}]
[–spi-connection SPI_CONNECTION] [–no-progress] [–verify] [–encrypt]
[–encrypt-files [ …]]
[–ignore-flash-encryption-efuse-setting] [–force] [–compress | --no-compress]
[ …]
esptool write_flash: error: argument : [Errno 2] No such file or directory: ‘bleota.bin’

13

bleota.bin provided in standart zip archive. common module.
https://github.com/meshtastic/firmware/releases/download/v2.4.0.46d7b82/firmware-2.4.0.46d7b82.zip

14

image
trackerd included in official build

1 Like