Meshtastic

Failed to write to target RAM (result was 01070000)

I just bought another 10 TTGO Tbeam 1.1 (back side battery case, 915MHz, LORA32) and this batch seem to all have the same error. They boot up to Meshtastic 1.0.0, I powered them up with both USB only and USB/battery and when I run the install script I get this:
chayss-MacBook-Pro:firmware-1.2.45.b674054 chays$ ./device-install.sh firmware-tbeam-1.2.45.b674054.bin

Trying to flash firmware-tbeam-1.2.45.b674054.bin, but first erasing and writing system information

esptool.py v3.0

Found 5 serial ports

Serial port /dev/cu.usbmodem52D50037701

Connecting…

Detecting chip type… ESP32

Chip is ESP32-D0WDQ6-V3 (revision 3)

Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None

Crystal is 40MHz

MAC: 08:3a:f2:66:dc:88

Uploading stub…

A fatal error occurred: Failed to write to target RAM (result was 01070000)

chayss-MacBook-Pro:firmware-1.2.45.b674054 chays$

Here’s the other one:
chayss-MacBook-Pro:firmware-1.2.45.b674054 chays$ ./device-install.sh firmware-tbeam-1.2.45.b674054.bin

Trying to flash firmware-tbeam-1.2.45.b674054.bin, but first erasing and writing system information

esptool.py v3.0

Found 5 serial ports

Serial port /dev/cu.usbmodem52D50038471

Connecting…

Detecting chip type… ESP32

Chip is ESP32-D0WDQ6-V3 (revision 3)

Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None

Crystal is 40MHz

MAC: 08:3a:f2:66:db:94

Uploading stub…

A fatal error occurred: Failed to write to target RAM (result was 01070000)

not sure you had success flashing other tbeams with the same setup, but I would suggest trying different USB cables or maybe a different machine (VMs should work too). esptool can be picky about USB cables and running on some versions of MacOS (Big Sur?).

1 Like

I’ve used the same software/cable/laptop setup to upgrade 15 radios in the last 48 hours.

odds not looking very good then. are you able to install other firmware like: GitHub - Xinyuan-LilyGO/LilyGo-LoRa-Series: LilyGo LoRa Series examples

or if they work with the Android App via bluetooth, maybe try upgrading firmware from there.

Have you visually compared the problematic boards to known working boards?

I wonder if this could be related: T-Beam CH9201 drivers

1 Like

I see that there is a different chip. The originals have a:
ublox
NEO-6M-0-001
24248541055
2033
07800 8

The new shipment has:
ublox
NEO-6M-0-001
24248541031
2033
0700 22

Any idea what that means?

Also, old board has this chip: AXP192 M1067AB 61K1
New board has: AXP192 LA026AB 6AX1

@geeksville can you help?

This is the reply I get from my Chinese supplier (I’ve purchased and sold around 100 Tbeams from them)
“These two use different chips , because the old one no goods, so use this new chip to instead it”

Nope.

Sorry.

I mentioned looking at the boards because it is all to common for manufacturers to change things without updating the silk screen print on old stock pcb boards with different components.

A thought. Can you flash it manually with esptool at a lower baud rate? You can also tweak the value in device-install.sh – find 921600 and replace it with something like 115200, which should be supported by pretty much every USB UART bridge.

Great suggestion, but I get the same error after changing all of the speeds in the install script.

2 Likes

I got it to update to 1.2.5 using the Android app over Bluetooth. I can’t find meshtastic app in the google play store anymore though to upgrade it to the latest. I have been opted in to the beta for months and I go to meshtastic.letstalkthis.com and click on the play icon to get it, I search for meshtastic and meshtastic beta in the play store but it’s not there anymore. What am I missing?

The android app is currently only in the amazon App Store.

You can also get it from github:

Android noob here… how do I connect to the amazon app store? NM I got it

Have you tried flashing the spiffs binary to your t-beams? That fixed a whole batch I got that wouldn’t flash.