T1000E Meshtastic / Lorawan

Products & Technology
1

I got a pair of T1000Es for Meshtastic, but I seem to have gotten the LoraWan version instead. Can I reflash them to use them with Meshtastic?

2

I got one Meshtastic and converted to Lorawan following these instructions:

# From Meshtastic to LoRaWAN

1.Enter Adafruit bootloader UF2 mode

2.Drap the t1000_e_bootloader_1th_ota_uf2.uf2 to USB disk

3.Wait for update to new bootloader

The u2fs and readme were found in this file: Seeed_T1000_E_Dev_Board_Alpha-main.zip . It is in files dot seeedstudio dot com/ wiki/ SenseCAP /Meshtastic
3

How did you get the firmware to work?

I have a T1000-E meshtastic, followed your steps to flash the bootloader (DFU mode, usb drive shows up, drag/drop UF2 file into USB drive)

GitHub .com/Seeed-Studio/Seeed-Tracker-T1000-E-for-LoRaWAN-dev-board/tree/main/firmware

Bootloader t1000_e_bootloader_1th_ota_uf2.uf2

After flashing, the drive now says “UF2 Bootloader, Model: Seeed T1000-E for LoraWAN”.

I flashed 02_buzzer, it worked (buzzed constantly). I tried flashing 11_lorawsn_tracker - the led lights just flashed on/off, sensecap app or my phone cannot see any available Bluetooth connection

4

Fyi, I removed fds_init_write from #11 lorawan tracker example per this, and had updated keys in lorawan_key_config.h

github .com/Seeed-Studio/Seeed-Tracker-T1000-E-for-LoRaWAN-dev-board/issues/4

After flashing, it seemed better (the led was breathing aka waiting for LoraWAN handshaking). I haven’t figured out exactly the serial console params (using 12000 rate, I do see some initial messages. And luckily I saw one message that says AppKey: 000000000)

I had changed keys lorawan_key_config.h but #11 example actually uses keys(and active region) from t1000_e/tracker/src/app_config_param.c based on what I saw on console.

Once app_config_param.c is updated, my tracker registers and shows up on Helium public LNS (Chirpstack v4) now and the led stopped breathing as expected. When message is sent, it beeps

The Bluetooth app connectivity still is not working, and I haven’t gotten the Chirpstack codec decoder to work yet (I see binary/base64 data only inside Chirpstack)

5

I guess, the original question was how to re flash LoraWan bootloader to Meshtastic?
I have the same question. Has any one done it?
It seems the Lorawan bootloader is locked.
It doesn’t present COM port when in DFU mode.
And also droping a converted hex to uf2 S140 7.3.0 bootloader to MSB doesn’t get accepted.
My goal is to flash S140 6.1.1 for SoftRF.

6

Hi there,

And welcome here…
So you are correct the Bootloader is signed and locked.
I don’t believe it’s open source and possible to convert it.

HTH
GL :slight_smile: PJ :v:

7

Which is strange because it says the T1000-E lorawan is open source firmware… So firmware is open source, stock bootloader can load unsigned firmware, but you cannot replace stock bootloader? And the meshtastic version is more open?

wiki.seeedstudio. com/get_started_with_lorawan_tracker/

My T1000-E meshtastic - with the GitHub bootloader and custom firmware, accelerator/temp(Celsius)/light sensor, wifi/BE scan , all this seem to work.

Gps doesn’t seem to work though, need to invest more time with this

1 Like
8

Hi there,

I know, It is seems to me it’s in between open and closed , LOL.
The signed Bootloader maybe is why it’s locked or something, I just don’t get the proprietary of it, Same with the "AT " command set, Although I did see an open source version of that at some point in the research. We really need a full OPEN source Dev platform, NONE of the current offerings are that, IMO sux and slows the development of the total TECH.

I hope for more GOOD stuff in this area. :crossed_fingers:

GL :slight_smile: PJ :v: