Boron constantly in Listening Mode

Can you please provide additional details here? My Boron is blinking blue (listening mode) and I can’t get it out of this mode.

Dfu-util can’t find the device?

I now have 2 devices stuck in this mode.

@stevieb1, the solution that worked best for me with this issue was to pair the Boron with a different phone - my particular version of Android seemed not to be supported. I’ve found the best luck with an iPhone.

Unclaim the device and then claim again?Ahhh…

At first this solution (unclaim, re-claim) appeared to work but failed on bluetooth connect.

Still blinking blue.

When put into dfu mode (blinking yellow) device does NOT show up in the Windows device manager (at all) and will not connect when using dfu-util …

dfu-util indicates reports -
“No DFU capable USB device available”

Double check or replace your USB cable.

Plugged into a different USB port. New result …

I have downloaded and successfully flashed new firmware (from github)

particle flash --usb hybrid-0.9.0-boron.bin
particle flash --usb tinker-0.9.0-boron.bin
particle flash --usb system-part1-0.9.0-boron.bin

All producing the same result …

Now the device is blinking red.

Steve

What code is it blinking?

I'd download a more recent device OS version (e.g. 1.2.1: system part1, bootloader ) and run this sequence

particle flash --usb tinker -v
particle flash --usb boron-system-part1@1.2.1.bin -v
particle flash --usb tinker -v

Then put the device in Listening Mode and run

particle flash --serial boron-bootloader@1.2.1.bin -v

Then again in LM

particle serial inspect

and post the output here

Ran the first three command (tinker / boron-system / tinker) … all successful!

Result from “particle flash --serial boron-bootloader@1.2.1.bin -v”
C:\Projects\IoT\DeviceCode>particle flash --serial boron-bootloader@1.2.1.bin -v

! PROTIP: Hold the SETUP button on your device until it blinks blue!
? Press ENTER when your device is blinking BLUE
Error writing firmware: Opening COM18: File not found
VError: Error writing firmware: Opening COM18: File not found
at Promise.resolve.then.then.then.then.then.catch.err (C:\Users\steveburbrin
k\AppData\Local\particle\node_modules\particle-cli\dist\cmd\serial.js:485:13)
at
at process._tickCallback (internal/process/next_tick.js:189:7)
caused by: Error: Opening COM18: File not found

Result from “particle serial inspect” -
C:\Projects\IoT\DeviceCode>particle serial inspect
Serial err: Error: Opening COM18: File not found
Serial problems, please reconnect the device.
Could not get inspect device: Serial problems, please reconnect the device.

Device Manager shows Com18
image

You could try remove and reinstall CLI (including the driver set) and make sure to tick the “remove existing drivers” checkbox.

I run this code. Marks it as completed and wont bother you again.

#include "Particle.h"
#include "dct.h"

SYSTEM_MODE(SEMI_AUTOMATIC);

void setup() {
    // 0x01 = setup done
    // 0xff = setup not done (go into listening mode at boot)
    const uint8_t val = 0x01;
    dct_write_app_data(&val, DCT_SETUP_DONE_OFFSET, 1);

    // This is just so you know the operation is complete
    pinMode(D7, OUTPUT);
    digitalWrite(D7, HIGH);
}

void loop() {
}

@ric_hard Would you expect any issues from putting this code in setup and leaving it for the long term?

I wouldn’t do that. I would just run it once.

1 Like

Device shows online via com18

C:\Projects\IoT\DeviceCode>particle serial list
Found 1 device connected via serial:
COM18 - Boron

Fails to download

C:\Projects\IoT\DeviceCode>particle serial flash clearOutListening.ino
! PROTIP: Hold the SETUP button on your device until it blinks blue!
? Press ENTER when your device is blinking BLUE
sending file: clearOutListening.ino
Error writing firmware: timed out after 70000ms