Particle One Tracker always starts in listening mode

Edge Systems
1

I noticed the my Particle one tracker always goes to listening mode on power-up and upon battery connection.

I always need to issue particle usb stop-listening -v and that might be a challenge once the device is deployed to the field.

I looked at this thread and tried the particle usb setup done and that didnt works Argon always returns to listening mode

even putting on safe mode, and setup done, it just keeps on listening. I also tried doing cloud flash, and local flash.

I am using deviceOS 3.0.0.0.

2

@lanceseidman - would you mind looking into this one?

3

Hello,

May I ask you to run the Particle serial inspect tool and provide the results please. Also, the Argon is a little different than the Tracker and some steps may not be a one for one.

4

Hi here is the output of the particle serial inspect tool

Platform: 26 - Asset Tracker
Modules
  Bootloader module #0 - version 1005, main location, 49152 bytes max size
    Integrity: PASS
    Address Range: PASS
    Platform: PASS
    Dependencies: PASS
  System module #1 - version 3005, main location, 671744 bytes max size
    Integrity: PASS
    Address Range: PASS
    Platform: PASS
    Dependencies: PASS
      Bootloader module #0 - version 1005
      NCP module #0 - version 7
  User module #1 - version 6, main location, 131072 bytes max size
    UUID: 9F9B3EE8CBCD9A0CA063C7EAE070E7FD2CAAC621C0290CFDD72BD4C903DC4396
    Integrity: PASS
    Address Range: PASS
    Platform: PASS
    Dependencies: PASS
      System module #1 - version 3005
  NCP module #0 - version 7, main location, 1536000 bytes max size
    Integrity: PASS
    Address Range: PASS
    Platform: PASS
    Dependencies: PASS
  Radio stack module #0 - version 202, main location, 192512 bytes max size
    Integrity: PASS
    Address Range: PASS
    Platform: PASS
    Dependencies: PASS
1 Like
5

Hello,

May I ask you to please visit this tool: Particle Cloud Debug and perform the cloud debugging process? It may take a moment to initiate.

6

So, I have a weird situation, quite similar to the one referenced above.

We built a device based on the Tracker SoM, and it keeps going to blinking blue mode. If I press setup for a few seconds, it connects, does what it has to do, then goes back to blinking blue.

Code is based on the tracker-edge code and uses 3.1.0

I tried particle update, flashing the whole system + app (visual code studio) and whatever I do, it goes back to this listening mode. I even tried particle usb setup-done to no effect…

Am I doing anything wrong?

Thanks,
Phil.

7

Ok, I removed my device from development mode and flashed it with a version I uploaded to the console, and everything seems fine now… still a bit strange that in dev mode I couldn’t make it work…

8

Hi @cloud_nine,

Hope all is well! Can you confirm if you’ve seen this occur when your device is in or out of sleep mode?

9

Hi lance,

We still do have the problem. I tried placing it in development on Particle console and it still blinks blue. On bootup here is what i see:

0000006080 [system.nm] TRACE: Request to power on the interface
0000006090 [app] TRACE: evaluatePublish first
0000006098 [app] TRACE: waiting for stable GNSS lock for triggers
0000006092 [system.nm] INFO: State changed: DISABLED -> IFACE_DOWN
0000006410 [hal] ERROR: Not found response
0000006430 [hal] ERROR: CMD0 response error, expect 0x1, response 0
0000006431 [hal] ERROR: Please restart slave and test again,error code:264
0000007558 [app] TRACE: evaluatePublish first
0000007559 [app] TRACE: waiting for stable GNSS lock for triggers
0000008089 [app] TRACE: evaluatePublish first
0000008089 [app] TRACE: waiting for stable GNSS lock for triggers
0000008089 [app] TRACE: waiting for stable GNSS lock for triggers
0000008502 [ncp.esp32.at] TRACE: > AT
0000008504 [ncp.esp32.at] TRACE: < OK
0000009089 [app] TRACE: evaluatePublish first
0000009089 [app] TRACE: waiting for stable GNSS lock for triggers
0000009505 [ncp.esp32.client] TRACE: NCP ready to accept AT commands
0000009507 [ncp.esp32.at] TRACE: > AT+MVER
0000009509 [ncp.esp32.at] TRACE: < 7
0000009512 [ncp.esp32.at] TRACE: < OK
0000009513 [ncp.esp32.at] TRACE: > AT+CMUX=0
0000009518 [ncp.esp32.at] TRACE: < OK
0000009523 [ncp.esp32.mux] INFO: Starting GSM07.10 muxer
0000009527 [ncp.esp32.mux] INFO: Openning mux channel 0
0000009534 [ncp.esp32.mux] INFO: GSM07.10 muxer thread started
0000009544 [ncp.esp32.mux] INFO: Openning mux channel 1
0000009554 [ncp.esp32.at] TRACE: > AT
0000009560 [ncp.esp32.at] TRACE: < OK
0000009564 [ncp.esp32.at] TRACE: > AT+CWDHCP=0,3
0000009571 [ncp.esp32.at] TRACE: < OK
0000009571 [ncp.esp32.client] TRACE: NCP state changed: 1
0000009572 [system.nm] TRACE: Interface 5 power state changed: 2
0000010089 [app] TRACE: evaluatePublish first

And it will start blinking blue. I waited for it to blink green but it never does. What I will do next is to run the command to exit out of listening mode “particle usb stop-listening -v”

0000031109 [app] TRACE: evaluatePublish first
0000031109 [app] TRACE: publishing from triggers
0000031868 [system.nm] INFO: State changed: IFACE_DOWN -> IFACE_REQUEST_UP
0000031876 [net.pppncp] TRACE: NCP event 3
0000031877 [net.pppncp] TRACE: NCP power state changed: IF_POWER_STATE_POWERING_UP
0000031877 [system.nm] INFO: State changed: IFACE_REQUEST_UP -> IFACE_UP
0000031893 [system.nm] TRACE: Interface 4 power state changed: 4
0000031893 [ncp.client] TRACE: Powering modem on
0000032109 [app] TRACE: evaluatePublish first

I see that it powers up the modem when I run the command. I also marked the device out of development mode as what peergum did, but it didn’t do anything. I might try next to flash the device via console.