Particle tachyon setup failing

Tachyon
1

unboxed tachyon, followed guide, put it in system update, but cannot get past particle tachyon setup. My dev environment:

  • ubuntu 24.04
  • particle cli version: 3.47.1
  • tachyon version: V1.2
Before we get started, we need to power on your Tachyon board:

Plug the USB-C cable into your computer and the Tachyon board.
The red light should turn on!

Put the Tachyon device into system update mode:

Hold the button next to the red LED for 3 seconds.

When the light starts flashing yellow, release the button.

Your device is now in system update mode!

Starting Process. See logs at: /home/me/.particle/logs/tachyon_flash_422a06000000000045bb75ae_1773423753727.log

▌ Getting device infoTerminated

if i look at the log it only shows the command it ran, if i run it manually it succeeds

 /tmp/qdl2026213-12347-1logce5.9phw/qdl --storage ufs --serial 45BB75AE /tmp/tachyon-init-files2026213-12347-1g1h99.cz048/prog_firehose_ddr.elf /tmp/tachyon-init-files2026213-12347-1g1h99.cz048/read_gpt.xml --skip-reset
waiting for programmer...
0 patches applied
read "gpt_main0.bin" successfully at 24kB/s
read "gpt_main1.bin" successfully
read "gpt_main2.bin" successfully
read "gpt_main3.bin" successfully
read "gpt_main4.bin" successfully
read "gpt_main5.bin" successfully
read "gpt_main6.bin" successfully

i cannot setup the tachyon past Install and Setup | Particle Developer

lsusb shows

Bus 003 Device 016: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

extra info

Getting device infoError: Command failed with ETXTBSY: /tmp/qdl2026213-15225-6t5sod.3qcas/qdl --storage ufs --serial 45BB75AE /tmp/tachyon-init-files2026213-15225-m3v7p0.a7a4/prog_firehose_ddr.elf /tmp/tachyon-init-files2026213-15225-m3v7p0.a7a4/read_gpt.xml --skip-reset
spawn ETXTBSY
2

I chatted to engineering about this.

The last error is interesting - it’s not something we’ve seen before and should only happen if a file that’s already open is then tried for execution.

Do you have an anti-virus or something similar running that could be intercepting things? Have you tried this from another computer?

3

i don't believe so, however i was able to get around this via following the steps on a raspberry pi with raspbian instead of doing it on my local machine running ubuntu

1 Like