Guide 2: No Data from Dev Kit to Spotter

Dev Kit Support
1

I’m working my way through the Bristlemouth Dev Kit Guide 2 using WSL. When I set up the Dev Kit independent of the Spotter, I get all the readings over serial as expected. I disconnected the Dev Kit from the wall and switched to the Spotter. I connect to the Spotter over serial and get the “SOFAR SPOTTER” message but then no data comes through.

Eventually, I get a message saying the timebase is not yet set and the bus is turned off.

68684t [MS] [DEBUG] Notecard is 65.000000 pct full.
68685t [MS] [INFO] All messages sent successfully!
68685t [MS] [DEBUG] Checking for Rx Messages
68720t [ERR] [INFO] Cellular SignalErrorState changed from N/A to OK
68721t [MS] [DEBUG] Messages sent/received successfully.
132320t [BRIDGE_SYS] [INFO] Sample enabled 1
Sample Duration: 310 s
Sample Interval: 1800 s
Subsample enabled: 0
Subsample Duration: 30 s
Subsample Interval: 60 s
Alignment Interval: 300 s
132327t [BRIDGE_SYS] [INFO] Using RTC timebase
132335t [BRIDGE_SYS] [INFO] Bridge State Init Complete
133313t [BRIDGE_SYS] [INFO] Bridge State Disabled - controller enabled, but timebase is not yet set - bus off
133320t [BRIDGE_SYS] [INFO] Bridge bus power: 0
143400t [BRIDGE_SYS] [INFO] Neighbor b9ffc4da6af0be83 lost

I tried:
a) Set the Dev Kit RTC before switching over to Spotter - No data comes through Spotter
2793574t [BRIDGE_CFG] [INFO] Bridge topology in topology sampler:
2793582t [BRIDGE_CFG] [INFO] 00937ea0b49fefb9
2793589t [BRIDGE_CFG] [INFO] b9ffc4da6af0be83
2793597t [BRIDGE_SYS] [INFO] Checking CRC in report builder!
2793606t [BRIDGE_SYS] [INFO] Got CRC 5c8af5d4 OLD CRC 5c8af5d4
2793613t [BRIDGE_SYS] [INFO] CRCs match, not updating

b) Step a) and then setup Spotter RTC - Same as Step a)

I’ve tried the bridge power commands and no luck. Getting messages about “Waiting for TX”. The System & Signal LED are green and the Go is always red. Any direction would be greatly appreciated as I continue to work through the Dev Kit.

2

Hi Mike — welcome, and I’m sorry you’re having trouble. We need some more information in order to help.

When you say:

What readings are you seeing over serial? Do you have a sensor? If you’re only printing them over serial that will never go to Spotter. You have to publish something on the Bristlemouth network to talk to Spotter. What do you expect to see at the Spotter?

Some helpful troubleshooting info:

  • What are the firmware versions of Spotter, Bridge, and the Dev Kit? Start here if you don’t know how to answer that question. Start with the Managing Spotter & Bristlemouth Firmware Versions Guide if you don’t know how to answer that question.
  • What’s the output on Spotter of the post command (which is an abbreviation for “power on self test”)?

Cheers,

Zachary

3

Hi Zachary,

I’m only using the Spotter and Dev Kit with no attached third party sensor. I received the dev kit and have just been trying to follow the instructions on Bristlemouth Dev Kit Guide 2. When my PC is directly connected to the Dev Kit, I’m seeing the output shown in Guide 1 with humidity, temp, etc. When connected to the Spotter, I’m expecting to see this same information to come through to the Spotter as shown in the Guide. I’m mainly getting messages related to CRC.

The Spotter post command is all OK except
N/A: baroErrorState, sstErrorState
LOW: solarErrorState
NO_SIGNAL: gpsErrorState

Spotter Info Command:

APP_NAME: spotter_bm
UID: 203630325847500A00420021
FW Version: v2.15.5
GIT SHA: 161EBED2
Build ID: 3e68da6ef525e0acce429fe78e6cc98a68affa23
BSP: sunflower_v3.3
Reset Reason: Enter charge mode reset
Main Deck HW Version: 02
Upper Deck HW Version: 02
Iridium IMEI: 300534064520560
Bootloader Information:
Version: v2.15.5
SHA: 161EBED2
Signature support: 1
Encrytion support: 0
Swap Type: NONE
Notecard Information:
Notecard IMEI: 868050040404077
Notecard sku: NOTE-WBNA-500
Notecard Board Version: 1.11
Notecard Firmware Version: notecard-3.5.2.15620
SD Card Information:
Type: SDHC/SDXC
CardVersion: 2.x
Class: 1461
Block Size: 512
Number of Blocks: 31116288
Size: 15.93GB
Current Partition: 15.92GB (15.90GB free)

Dev Kit Info Command:

APP_NAME: hello_world
UID: 2039364e55315013004f0030
MAC: 00:00:6a:f0:be:83
IP addresses:
Link Local: FE80::B9FF:C4DA:6AF0:BE83
Unicast: FD00::B9FF:C4DA:6AF0:BE83
FW Version: hello_world@v0.13.3
GIT SHA: 98B26CBB
Build ID: d8332b67e50d712a6b8c2a414820367fe06cc7e8
BSP: mote_v1_0
Reset Reason: Invalid reset or first power on since flashing
Node ID: b9ffc4da6af0be83
Bootloader Information:
Version: v0.12.2
SHA: FC385392
Signature support: 0
Encrytion support: 0
Swap Type: NONE

Spotter Start Up Messages (After the Spotter Graphic):

Charge mode enabled. Toggle power switch to turn on
106667t [SYS] [INFO] Switch toggled to ON. Continuing boot process.
106669t [SYS] [INFO] GpsPowerManager disabled, starting up GPS normally.
106669t [GPS] [WARNING] Initializing GPS. Tries remaining 3
106898t [GPS] [WARNING] TXT: u-blox AG - www.u-blox.com
106941t [GPS] [WARNING] TXT: HW UBX-M8030 00080000
106986t [GPS] [WARNING] TXT: EXT CORE 3.01 (107900)
107031t [GPS] [WARNING] TXT: ROM BASE 3.01 (107888)
107067t [GPS] [WARNING] TXT: FWVER=SPG 3.01
107103t [GPS] [WARNING] TXT: PROTVER=18.00
107138t [GPS] [WARNING] TXT: MOD=NEO-M8N-0
107182t [GPS] [WARNING] TXT: FIS=0xEF4015 (100111)
107220t [GPS] [WARNING] TXT: GPS;GLO;GAL;BDS
107256t [GPS] [WARNING] TXT: SBAS;IMES;QZSS
107294t [GPS] [WARNING] TXT: GNSS OTP=GPS;GLO
107366t [GPS] [WARNING] TXT: LLC=FFFFFFFF-FFFFFFED-FFFFFFFF-FFFFFFFF-FFFFFF69
107412t [GPS] [WARNING] TXT: ANTSUPERV=AC SD PDoS SR
107453t [GPS] [WARNING] TXT: ANTSTATUS=DONTKNOW
107481t [GPS] [WARNING] TXT: PF=3FF
107670t [UBX] [WARNING] Packet RX timeout
108103t [GPS] [WARNING] TXT: ANTSTATUS=INIT
108414t [GPS] [WARNING] TXT: Resetting GNSS
108845t [GPS] [WARNING] TXT: Resetting GNSS
108905t [GPS] [WARNING] TXT: ANTSUPERV=AC SD OD PDoS SR
109414t [UBX] [INFO] Requesting TP5 Data
109610t [UBX] [WARNING] Packet RX timeout
109670t [ERR] [INFO] GpsErrorState changed from N/A to NO_SIGNAL
109671t [GPS] [WARNING] Successfully initialized GPS!
109675t [ORC] [INFO] Standard Mode Enabled
109676t [ERR] [INFO] OrchErrorState changed from N/A to OK
109681t [SYS] [INFO] APP_NAME: spotter_bm
109681t [SYS] [INFO] UID: 203630325847500A00420021
109681t [SYS] [INFO] FW Version: v2.15.5
109681t [SYS] [INFO] GIT SHA: 161EBED2
109681t [SYS] [INFO] Build ID: 3e68da6ef525e0acce429fe78e6cc98a68affa23
109682t [SYS] [INFO] BSP: sunflower_v3.3
109682t [SYS] [INFO] Reset Reason: Enter charge mode reset
109683t [SYS] [INFO] Main Deck HW Version: 02
109684t [SYS] [INFO] Upper Deck HW Version: 02
109684t [SYS] [INFO] Bootloader Information:
Version: v2.15.5
SHA: 161EBED2
Signature support: 1
Encrytion support: 0
Swap Type: NONE
109690t [BRIDGE] [INFO] Bridge Enabled
109735t [ERR] [INFO] MicErrorState changed from N/A to OK
109756t [I2C] [WARNING] i2cTxRx Error [I2C2] - Unable to take mutex.
Output port differs 01E0 A5A5 A445
109865t [GPS] [WARNING] TXT: ANTSTATUS=OK
109991t [ORC] [INFO] Iridium modem enabled
110014t [SYS] [INFO] Iridium IMEI: 300534064520560
110029t [IRI] [INFO] ATI0 - 2400
110043t [IRI] [INFO] ATI1 - 0000
110057t [IRI] [INFO] ATI2 - OK
110074t [IRI] [INFO] ATI3 - TA21004
110096t [IRI] [INFO] ATI4 - IRIDIUM 9600 Family
110114t [IRI] [INFO] ATI5 - 8816
110128t [IRI] [INFO] ATI6 - 1QL
110155t [IRI] [INFO] ATI7 - BOOT07d4/9602NrvA-D/04/RAW0d
110174t [IRI] [INFO] AT+CGMI - Iridium
110208t [IRI] [INFO] AT+CGMM - IRIDIUM 9600 Family SBD Transceiver
110232t [IRI] [INFO] AT+CGSN - 300534064520560
110280t [IRI] [INFO] AT+CGMR - Modem DSP Version: 1.7 svn: 2358
110295t [IRI] [INFO] AT+CGMR - DBB Version: 0x0001 (ASIC)
110311t [IRI] [INFO] AT+CGMR - RFA Version: 0x0007 (SRFA2)
110322t [IRI] [INFO] AT+CGMR - NVM Version: KVS
110348t [IRI] [INFO] AT+CGMR - Hardware Version: BOOT07d4/9602NrvA-D/04/RAW0d
110370t [IRI] [INFO] AT+CGMR - BOOT Version: 2004 TD2-BLB960X-27 R4710
110373t [ERR] [INFO] IridiumErrorState changed from N/A to OK
110374t [ORC] [INFO] Iridium modem disabled
110467t [ERR] [INFO] Visibility LEDErrorState changed from N/A to OK
111012t [BRIDGE_SYS] [INFO] Bridge bus power: 1
111048t [BRIDGE] [INFO] Reboot info received from 00937ea0b49fefb9 - Reason: 8 gitSHA: 98b26cbb Reboot cnt: 0 PC: 0x0 LR: 0x0
113051t [BRIDGE_CFG] [INFO] Response msg – Node Id: 0000000000000000, Partition: user, Commit Status: 0
113051t [BRIDGE_CFG] [INFO] Num Keys: 0
113061t [BRIDGE_CFG] [INFO] Response msg – Node Id: 0000000000000000, Partition: hardware, Commit Status: 0
113061t [BRIDGE_CFG] [INFO] Num Keys: 1
113061t [BRIDGE_CFG] [INFO] Key 0: smConfigurationCrc
113074t [BRIDGE_CFG] [INFO] Node ID: 0000000000000000 Partition: hardware - Failed to decode value
116053t [BRIDGE_CFG] [INFO] Bridge topology in topology sampler:
116061t [BRIDGE_CFG] [INFO] 00937ea0b49fefb9
116068t [BRIDGE_CFG] [INFO] b9ffc4da6af0be83
116079t [BRIDGE_CFG] [INFO] Network configuration change detected! crc: 0x5c8af5d4 at UTC:0
116087t [BRIDGE_CFG] [INFO] Stored CRCs:
0xaba03e7
0x5c8af5d4
0x61a2fdcc
0xe6c6ee46
116116t [MS] [INFO] Notecard powered on!
116116t [MS] [INFO] Notecard enabled successfully
0x3b77b611
0x1b67b4c7
0x30622beb
0xfe3c39de
116160t [SYS] [INFO] Notecard IMEI: 868050040404077
116160t [SYS] [INFO] Notecard sku: NOTE-WBNA-500
116161t [SYS] [INFO] Notecard Board Version: 1.11
116161t [SYS] [INFO] Notecard Firmware Version: notecard-3.5.2.15620
116162t [MS] [INFO] Removing old notecard tx messages
116202t [BRIDGE_CFG] [INFO] Bridge network config: [[41516050266714041, “bridge”, 2561830075, 1794850585, {“sampleIntervalMs”: 1800000, “sampleDurationMs”: 310000, “subsampleIntervalMs”: 60000, “subsampleDurationMs”: 30000, “subsampleEnabled”: 0, “bridgePowerControllerEnabled”: 0, “alignmentInterval5Min”: 1, “ticksSamplingEnabled”: 0, “samplesPerReport”: 2, “transmitAggregations”: 1, “currentReadingPeriodMs”: 60000, “softReadingPeriodMs”: 500, “rbrCodaReadingPeriodMs”: 500, “turbidityReadingPeriodMs”: 1000, “disableUnusedPortsTimeMs”: 0}], [13402647458453962371, “hello_world”, 2561830075, 1030244400, {“disableUnusedPortsTimeMs”: 0}]]
116245t [BRIDGE_CFG] [INFO] Bridge network info CRC: 5c8af5d4
116245t [BRIDGE_CFG] [INFO] Bridge FW Version: Major: 0 Minor: 13 Revision: 3
116245t [BRIDGE_CFG] [INFO] Bridge sys config partition CRC: 6afb3f19
116246t [BRIDGE_CFG] [INFO] Bridge toplogy: 00937ea0b49fefb9 | b9ffc4da6af0be83
No update available for b9ffc4da6af0be83
No update available for 00937ea0b49fefb9
Current bit offset: 196
Rounded bit offset: 200
New bit offset: 2720
116627t [MS] [INFO] Added message(id: 0 len: 340) to queue MS_Q_LEGACY: (1)!
Message: DF 00 00 00 00 00 0D A0 0A C1 21 11 ED 80 00 6D 40 00 17 22 BD 75 00 1B C0 82 85 1B 00 93 7E A0 B4 9F EF B9 66 62 72 69 64 67 65 1A 98 B2 6C BB 1A 6A FB 3F 19 AF 70 73 61 6D 70 6C 65 49 6E 74 65 72 76 61 6C 4D 73 1A 00 1B 77 40 70 73 61 6D 70 6C 65 44 75 72 61 74 69 6F 6E 4D 73 1A 00 04 BA F0 73 73 75 62 73 61 6D 70 6C 65 49 6E 74 65 72 76 61 6C 4D 73 19 EA 60 73 73 75 62 73 61 6D 70 6C 65 44 75 72 61 74 69 6F 6E 4D 73 19 75 30 70 73 75 62 73 61 6D 70 6C 65 45 6E 61 62 6C 65 64 00 78 1C 62 72 69 64 67 65 50 6F 77 65 72 43 6F 6E 74 72 6F 6C 6C 65 72 45 6E 61 62 6C 65 64 00 75 61 6C 69 67 6E 6D 65 6E 74 49 6E 74 65 72 76 61 6C 35 4D 69 6E 01 74 74 69 63 6B 73 53 61 6D 70 6C 69 6E 67 45 6E 61 62 6C 65 64 00 70 73 61 6D 70 6C 65 73 50 65 72 52 65 70 6F 72 74 02 74 74 72 61 6E 73 6D 69 74 41 67 67 72 65 67 61 74 69 6F 6E 73 01 76 63 75 72 72 65 6E 74 52 65 61 64 69 6E 67 50 65 72 69 6F 64 4D 73 19 EA 60 73 73 6F 66 74 52 65 61 64 69 6E 67 50 65 72 69 6F 64 4D 73 19 01 F4 76 72 62 72 43 6F 64 61 52 65 61 64 69
Sent bytes: 315
Current bit offset: 20
Rounded bit offset: 24
New bit offset: 1056
116636t [MS] [INFO] Added message(id: 1 len: 132) to queue MS_Q_LEGACY: (2)!
Message: DF 00 10 6E 67 50 65 72 69 6F 64 4D 73 19 01 F4 78 18 74 75 72 62 69 64 69 74 79 52 65 61 64 69 6E 67 50 65 72 69 6F 64 4D 73 19 03 E8 78 18 64 69 73 61 62 6C 65 55 6E 75 73 65 64 50 6F 72 74 73 54 69 6D 65 4D 73 00 85 1B B9 FF C4 DA 6A F0 BE 83 6B 68 65 6C 6C 6F 5F 77 6F 72 6C 64 1A 98 B2 6C BB 1A 3D 68 48 30 A1 78 18 64 69 73 61 62 6C 65 55 6E 75 73 65 64 50 6F 72 74 73 54 69 6D 65 4D 73 00
Sent bytes: 444
116639t [BRIDGE_SYS] [INFO] Checking CRC in report builder!
116639t [BRIDGE_SYS] [INFO] Got CRC 5c8af5d4 OLD CRC 0
116639t [BRIDGE_SYS] [INFO] Getting topology in report builder!
116639t [BRIDGE_SYS] [INFO] Got topology in report builder!
116639t [BRIDGE_SYS] [INFO] Updating CRC and topology in report builder!
116640t [BRIDGE_SYS] [INFO] Updated reportBuilders max network configuration CBOR map
119388t [MS] [INFO] Checking for update (and clearing successful one!)
119402t [ERR] [INFO] CellularErrorState changed from N/A to OK
119690t [BRIDGE] [INFO] Requesting self test
119690t [BRIDGE] [DEBUG] Self test attempts remaining: 3
119690t [BRIDGE] [DEBUG] Self test request sent
119696t [BRIDGE] [INFO] Self test result from 00937ea0b49fefb9 - 1
119696t [ERR] [INFO] bridgeErrorState changed from N/A to OK
119697t [BRIDGE] [INFO] Self test successful
119785t [BM_DFU] [INFO] Bm bridge dfu init complete
119785t [BM_DFU] [INFO] Transitioning to state: idle
120558t [MS] [INFO] Entering Transmit cellular state.
120646t [MS] [DEBUG] Has message 0 expired? queuedTime: 116627, now64: 120646, remaining: 86395981
120646t [MS] [DEBUG] Sending legacy messages to Notecard.
120663t [MS] [DEBUG] Notecard is 65.000000 pct full.
120663t [MS] [INFO] Queuing message 0 20024160
Got bridge Node ID: 00937ea0b49fefb9
Running info request on bridge
Neighbor information:
Node ID: 00937ea0b49fefb9
VID: 0000 PID: 0000
Serial number 0000000000000000
GIT SHA: 98B26CBB
Version: 0.13.3
HW Version: 0
VersionStr: bridge@v0.13.3
Device Name: 203238484d3050010042003f
121281t [MS] [DEBUG] Has message 1 expired? queuedTime: 116636, now64: 121281, remaining: 86395355
121282t [MS] [INFO] Queuing message 1 20024370
121565t [MS] [DEBUG] Attempting to Sync.
121580t [MS] [DEBUG] Waiting for TX

4

Hey Mike,

Thanks for all that info.

Things mostly look as we expect. I think it’s possible that if you just waited for a while, you might eventually see the logging of power, pressure, and htu from the dev kit.

The main thing that jumps out at me is that Spotter’s firmware version v2.15.5 is not perfectly compatible with Bristlemouth v0.13.3, which is what both the bridge and the dev kit are running.

Check out the compatibility tables.

You should update Spotter to v2.16.2, which is available on the Sofar firmware releases and downloads page.

Once you update Spotter, if everything’s going well with guide 2, you should be ready to continue to further guides!

Cheers,
Zachary

5

Hi Zachary,

I updated the Spotter to v2.16.2 using the Mac instructions. I used the non-Bristlemouth version since my sticker has a Spotter Icon and not a Bristlemouth Icon. I initially tried the Windows instructions (on Windows 11) and that timed out, but switching to Mac was successful.

After rebooting, I got an error saying the bridge has a “FW_HW_MISTMATCH_ERR”. I thought maybe the Windows method messed something up. I followed the instructions of (Trouble with flashing firmware - Dev Kit Support - Bristlemouth) and updated the bridge FW to v0.13.4 using the file bridge_release-v0.13.4.zip. That was successful, but I encountered the same error after rebooting the Spotter.

I don’t have my dev kit attached to simplify things.

6

Oh no! Sorry about the lack of clarity — we changed the stickers at some point but early Pioneer Program systems were shipped without the Bristlemouth logo. This is the Bristlemouth forum, and all conversations here only apply to Bristlemouth systems. Please download the Bristlemouth firmware, and run the updater again. I think that should clear up the error.

7

Okay so running the Bristlemouth installer says it is unable to find any connected nodes (makes sense since wrong Spotter FW). I tell it to update, but it says the device is already up to date with v2.16.2 so it does not proceed.

I figure I need to load old firmware on the Spotter so I can run the v2.16.2 Bristlemouth installer. I can’t find any old installers, so I grabbed the “sunflower_v3.3-spotter_bm-v2.15.2.elf.dfu.bin” file and these instructions: Guide: Updating Firmware In A Spotter & Bristlemouth System

I’m assuming I should be following Section 3: Update Bristlemouth Spotter Main Processor? Except in Step 1, my System LED never went green after 5 min. I decided to proceed, and all three LEDs flashed amber for ~30sec then the System & Go LED just went red. The Spotter then replied like normal and the post command still indicates same bridge error. The only things on the SD are: README.txt, log, and update.bin.

How do I get the proper firmware on the spotter?

8

Normally those instructions should work, but the hardware-firmware mismatch is now blocking them.

Can you run dfu-util in the WSL terminal? If so, I can send a binary and some instructions.

9

I can use my old Mac and run dfu-util. Looking forward to trying the binary & instructions.

10

I’ve followed up by direct message. Good luck! :crossed_fingers: