Powering the dev kit from the spotter

Dev Kit Support
21

image
image1920×2560 274 KB

After we triple checked the commands to turn off the power controller and enable providing continuous power, and ensuring the battery is charged, this is what we’re seeing from the probes. I can confirm that we have been using a wall-wart to usbc charger for the spotter and the dashboard as well as the LED colors indicate full charge.

22

Ah dang okay. Can you copy the text you see on the CLI when you boot up the Spotter or the SD card from a fresh card? I’ll take a look and see if I can see anything.

Thanks!

23

Here are the results on a boot on a brand new fresh SD card, hopefully theres something useful in here!

2024-04-27T21:04:31.695Z [SYS] [INFO] Switch toggled to ON. Continuing boot process.
2024-04-27T21:04:31.695Z [SYS] [INFO] GpsPowerManager disabled, starting up GPS normally.
2024-04-27T21:04:31.695Z [GPS] [WARNING] Initializing GPS. Tries remaining 3
2024-04-27T21:04:31.921Z [GPS] [WARNING] TXT: u-blox AG - www.u-blox.com
2024-04-27T21:04:31.964Z [GPS] [WARNING] TXT: HW UBX-M8030 00080000
2024-04-27T21:04:32.011Z [GPS] [WARNING] TXT: EXT CORE 3.01 (107900)
2024-04-27T21:04:32.054Z [GPS] [WARNING] TXT: ROM BASE 3.01 (107888)
2024-04-27T21:04:32.089Z [GPS] [WARNING] TXT: FWVER=SPG 3.01
2024-04-27T21:04:32.125Z [GPS] [WARNING] TXT: PROTVER=18.00
2024-04-27T21:04:32.164Z [GPS] [WARNING] TXT: MOD=NEO-M8N-0
2024-04-27T21:04:32.207Z [GPS] [WARNING] TXT: FIS=0xEF4015 (100111)
2024-04-27T21:04:32.242Z [GPS] [WARNING] TXT: GPS;GLO;GAL;BDS
2024-04-27T21:04:32.281Z [GPS] [WARNING] TXT: SBAS;IMES;QZSS
2024-04-27T21:04:32.320Z [GPS] [WARNING] TXT: GNSS OTP=GPS;GLO
2024-04-27T21:04:32.390Z [GPS] [WARNING] TXT: LLC=FFFFFFFF-FFFFFFED-FFFFFFFF-FFFFFFFF-FFFFFF69
2024-04-27T21:04:32.437Z [GPS] [WARNING] TXT: ANTSUPERV=AC SD PDoS SR
2024-04-27T21:04:32.476Z [GPS] [WARNING] TXT: ANTSTATUS=DONTKNOW
2024-04-27T21:04:32.503Z [GPS] [WARNING] TXT: PF=3FF
2024-04-27T21:04:32.695Z [UBX] [WARNING] Packet RX timeout
2024-04-27T21:04:33.128Z [GPS] [WARNING] TXT: ANTSTATUS=INIT
2024-04-27T21:04:33.437Z [GPS] [WARNING] TXT: Resetting GNSS
2024-04-27T21:04:33.871Z [GPS] [WARNING] TXT: Resetting GNSS
2024-04-27T21:04:33.929Z [GPS] [WARNING] TXT: ANTSUPERV=AC SD OD PDoS SR
2024-04-27T21:04:34.437Z [UBX] [INFO] Requesting TP5 Data
2024-04-27T21:04:34.632Z [UBX] [WARNING] Packet RX timeout
2024-04-27T21:04:34.695Z [ERR] [INFO] GpsErrorState changed from N/A to NO_SIGNAL
2024-04-27T21:04:34.695Z [GPS] [WARNING] Successfully initialized GPS!
2024-04-27T21:04:34.699Z [ORC] [INFO] Standard Mode Enabled
2024-04-27T21:04:34.699Z [ERR] [INFO] OrchErrorState changed from N/A to OK
2024-04-27T21:04:34.699Z [SYS] [INFO] Initialize sensors
2024-04-27T21:04:34.769Z [ERR] [INFO] HtuErrorState changed from N/A to OK
2024-04-27T21:04:34.769Z [SYS] [INFO] Starting barometer filter with parameters:
size: 200
percentile: 10.00
downsamplingRate: 50
alpha: 1.0000387
2024-04-27T21:04:34.777Z [ERR] [INFO] BaroErrorState changed from N/A to OK
2024-04-27T21:04:34.781Z [SYS] [INFO] /bm directory not present. Creating!
2024-04-27T21:04:34.796Z [SYS] [INFO] APP_NAME: spotter_bm-dbg
2024-04-27T21:04:34.796Z [SYS] [INFO] UID: 203630325847500700350025
2024-04-27T21:04:34.796Z [SYS] [INFO] FW Version: v2.9.0
2024-04-27T21:04:34.796Z [SYS] [INFO] GIT SHA: 76CCEBA3
2024-04-27T21:04:34.796Z [SYS] [INFO] Build ID: 5f75a8a37902a2578706dd3426140b8ce72c329d
2024-04-27T21:04:34.796Z [SYS] [INFO] BSP: sunflower_v3.3
2024-04-27T21:04:34.796Z [SYS] [INFO] Reset Reason: SD card insertion reset
2024-04-27T21:04:34.796Z [SYS] [INFO] Main Deck HW Version: 02
2024-04-27T21:04:34.800Z [SYS] [INFO] Upper Deck HW Version: 02
2024-04-27T21:04:34.800Z [SYS] [INFO] Bootloader Information:
  Version: v2.9.0
  SHA: 76CCEBA3
  Signature support: 1
  Encrytion support: 0
  Swap Type: NONE
Bm bridge dfu init complete
Transitioning to state: idle
2024-04-27T21:04:34.812Z [BRIDGE] [INFO] Bridge Enabled
2024-04-27T21:04:34.886Z [GPS] [WARNING] TXT: ANTSTATUS=OK
2024-04-27T21:04:35.113Z [ORC] [INFO] Iridium modem enabled
2024-04-27T21:04:35.136Z [SYS] [INFO] Iridium IMEI: 300534064524640
2024-04-27T21:04:35.152Z [IRI] [INFO] ATI0 - 2400
2024-04-27T21:04:35.167Z [IRI] [INFO] ATI1 - 0000
2024-04-27T21:04:35.179Z [IRI] [INFO] ATI2 - OK
2024-04-27T21:04:35.195Z [IRI] [INFO] ATI3 - TA21004
2024-04-27T21:04:35.218Z [IRI] [INFO] ATI4 - IRIDIUM 9600 Family
2024-04-27T21:04:35.234Z [IRI] [INFO] ATI5 - 8816
2024-04-27T21:04:35.246Z [IRI] [INFO] ATI6 - 1QD
2024-04-27T21:04:35.273Z [IRI] [INFO] ATI7 - BOOT07d4/9602NrvA-D/04/RAW0d
2024-04-27T21:04:35.292Z [IRI] [INFO] AT+CGMI - Iridium
2024-04-27T21:04:35.328Z [IRI] [INFO] AT+CGMM - IRIDIUM 9600 Family SBD Transceiver
2024-04-27T21:04:35.351Z [IRI] [INFO] AT+CGSN - 300534064524640
2024-04-27T21:04:35.398Z [IRI] [INFO] AT+CGMR - Modem DSP Version: 1.7 svn: 2358
2024-04-27T21:04:35.414Z [IRI] [INFO] AT+CGMR - DBB Version: 0x0001 (ASIC)
2024-04-27T21:04:35.433Z [IRI] [INFO] AT+CGMR - RFA Version: 0x0007 (SRFA2)
2024-04-27T21:04:35.441Z [IRI] [INFO] AT+CGMR - NVM Version: KVS
2024-04-27T21:04:35.468Z [IRI] [INFO] AT+CGMR - Hardware Version: BOOT07d4/9602NrvA-D/04/RAW0d
2024-04-27T21:04:35.492Z [IRI] [INFO] AT+CGMR - BOOT Version: 2004 TD2-BLB960X-27 R4710
2024-04-27T21:04:35.492Z [ERR] [INFO] IridiumErrorState changed from N/A to OK
2024-04-27T21:04:35.496Z [ORC] [INFO] Iridium modem disabled
2024-04-27T21:04:35.773Z [BRIDGE] [INFO] Reboot info received from 2db5abab0d4ac2e3 - Reason: 8 gitSHA: b557f3d0 Reboot cnt: 0
2024-04-27T21:04:37.773Z [BRIDGE_CFG] [INFO] Response msg -- Node Id:0,Partition:system, Commit Status:0
2024-04-27T21:04:37.773Z [BRIDGE_CFG] [INFO] Num Keys: 3
2024-04-27T21:04:37.773Z [BRIDGE_CFG] [INFO] Key 0: bridgePowerControllerEnabled
2024-04-27T21:04:37.773Z [BRIDGE_CFG] [INFO] Key 1: sampleIntervalMs
2024-04-27T21:04:37.777Z [BRIDGE_CFG] [INFO] Key 2: sampleDurationMs
2024-04-27T21:04:37.777Z [BRIDGE_CFG] [INFO] Response msg -- Node Id:0,Partition:user, Commit Status:0
2024-04-27T21:04:37.777Z [BRIDGE_CFG] [INFO] Num Keys: 0
2024-04-27T21:04:37.785Z [BRIDGE_CFG] [INFO] Response msg -- Node Id:0,Partition:hardware, Commit Status:0
2024-04-27T21:04:37.785Z [BRIDGE_CFG] [INFO] Num Keys: 1
2024-04-27T21:04:37.785Z [BRIDGE_CFG] [INFO] Key 0: smConfigurationCrc
2024-04-27T21:04:37.792Z [BRIDGE_CFG] [INFO] Node ID: 0 Partition: system Value: 0
2024-04-27T21:04:37.796Z [BRIDGE_CFG] [INFO] Node ID: 0 Partition: system Value: 360000
2024-04-27T21:04:37.804Z [BRIDGE_CFG] [INFO] Node ID: 0 Partition: system Value: 60500
2024-04-27T21:04:37.812Z [BRIDGE_CFG] [INFO] Node ID: 0 Partition: hardware Value: 1596212596
2024-04-27T21:04:39.812Z [BRIDGE] [INFO] Requesting self test
2024-04-27T21:04:39.820Z [BRIDGE] [INFO] Self test result from 2db5abab0d4ac2e3 - 1
2024-04-27T21:04:39.820Z [ERR] [INFO] bridgeErrorState changed from N/A to OK
2024-04-27T21:04:39.820Z [BRIDGE] [INFO] Self test successful
2024-04-27T21:04:40.773Z [BRIDGE_CFG] [INFO] Bridge network info CRC: 5f244574
2024-04-27T21:04:40.773Z [BRIDGE_CFG] [INFO] Bridge FW Version: Major: 0 Minor: 4 Revision: 0
2024-04-27T21:04:40.773Z [BRIDGE_CFG] [INFO] Bridge sys config partition CRC: 22c800b9
2024-04-27T21:04:40.773Z [BRIDGE_CFG] [INFO] Bridge toplogy: 2db5abab0d4ac2e3
2024-04-27T21:04:40.984Z [MS] [INFO] Notecard powered on!
2024-04-27T21:04:40.984Z [MS] [INFO] Notecard enabled successfully
2024-04-27T21:04:41.027Z [SYS] [INFO] Notecard IMEI: 860322068111795
2024-04-27T21:04:41.027Z [SYS] [INFO] Notecard sku: NOTE-WBNA-500
2024-04-27T21:04:41.027Z [SYS] [INFO] Notecard Board Version: 1.11
2024-04-27T21:04:41.031Z [SYS] [INFO] Notecard Firmware Version: notecard-4.2.1.4015688
2024-04-27T21:04:41.031Z [MS] [INFO] Removing old notecard tx messages
2024-04-27T21:04:43.964Z [MS] [INFO] Flushing old notecard rx messages
2024-04-27T21:04:43.988Z [MS] [INFO] Checking for update (and clearing successful one!)
2024-04-27T21:04:44.003Z [ERR] [INFO] CellularErrorState changed from N/A to OK
2024-04-27T21:04:45.332Z [MS] [INFO] Entering Transmit cellular state.
24

Dang okay I was hoping to spot something here but I see that:

There weren’t any low battery warnings
The bridge (which controls the smart mooring) looks OK
The bridgePowerControllerEnabled is set to 0 so that’s good…

Let’s get you a new electronics box. I’ll send you a quick email so we can discuss the details of the swap there.

Thanks
Z

25

Hi - We got the new ebox and it did fix the power issues! We are now able to run the dev board without using the wall wart.
Howeverrr…it’s caused some issues with our program that was working fine before. The spotter and dev kit don’t seem to be connecting properly.
This is the sort of messages that I see in the dev board console:

🏘📡 Updating neighbor info! 6b98ffbeb769bb5d
🏚  Neighbor offline :'( 6b98ffbeb769bb5d
Set RTC to 2024-05-14T00:42:37.511
hum_temp | tick: 682189, rtc: 2024-05-14T00:42:38.585, hum: 45.977570, temp: 23.847292
pressure | tick: 684198, rtc: 2024-05-14T00:42:40.593, temp: 23.846979, pressure: 1013.495544
power | tick: 684205, rtc: 2024-05-14T00:42:40.601, addr: 67, voltage: 23.942400, current: 0.000000
power | tick: 684207, rtc: 2024-05-14T00:42:40.601, addr: 65, voltage: 23.940800, current: -0.001500
🏚  Neighbor offline :'( 6b98ffbeb769bb5d
Set RTC to 2024-05-14T00:42:47.511
hum_temp | tick: 692189, rtc: 2024-05-14T00:42:48.585, hum: 46.016727, temp: 23.848543
pressure | tick: 694198, rtc: 2024-05-14T00:42:50.593, temp: 23.849169, pressure: 1013.531982
power | tick: 694205, rtc: 2024-05-14T00:42:50.601, addr: 67, voltage: 23.940800, current: 0.000000
power | tick: 694207, rtc: 2024-05-14T00:42:50.605, addr: 65, voltage: 23.940800, current: -0.001000
🏘📡 Updating neighbor info! 6b98ffbeb769bb5d
🏚  Neighbor offline :'( 6b98ffbeb769bb5d

And this is the sort of messages that turn up in the spotter console:

2024-05-14T00:42:47.289Z [BRIDGE_SYS] [INFO] Neighbor 29f5069863a2a349 lost
1715647369.128 29f5069863a2a349, hum_temp | tick: 692189, rtc: 2024-05-14T00:42:48.585, hum: 46.016727, temp: 23.848543
1715647371.140 29f5069863a2a349, pressure | tick: 694198, rtc: 2024-05-14T00:42:50.593, temp: 23.849169, pressure: 1013.531982
1715647371.164 29f5069863a2a349, power | tick: 694205, rtc: 2024-05-14T00:42:50.601, addr: 67, voltage: 23.940800, current: 0.000000
1715647371.191 29f5069863a2a349, power | tick: 694207, rtc: 2024-05-14T00:42:50.605, addr: 65, voltage: 23.940800, current: -0.001000
2024-05-14T00:42:57.289Z [BRIDGE_SYS] [INFO] Neighbor 29f5069863a2a349 lost
1715647379.128 29f5069863a2a349, hum_temp | tick: 702189, rtc: 2024-05-14T00:42:58.589, hum: 45.949619, temp: 23.847918
1715647381.140 29f5069863a2a349, pressure | tick: 704198, rtc: 2024-05-14T00:43:00.597, temp: 23.848543, pressure: 1013.544067
1715647381.164 29f5069863a2a349, power | tick: 704205, rtc: 2024-05-14T00:43:00.605, addr: 67, voltage: 23.942400, current: 0.000000
1715647381.191 29f5069863a2a349, power | tick: 704207, rtc: 2024-05-14T00:43:00.605, addr: 65, voltage: 23.940800, current: -0.000750
2024-05-14T00:43:07.289Z [BRIDGE_SYS] [INFO] Neighbor 29f5069863a2a349 lost

A lot of repeated messages about neighbor issues. And similar to my previous post about the dev board crapping out when it was receiving uart data, sometimes it just crashes, seemingly unexplanable. That issue had been fixed before and was working fine with the old ebox. A last thing, our dev board app also tries to fprintf to log files in the spotter sd card. We never used to have issues with that, but now I’m seeing repeated “failed to fprintf” in the spotter console.
For reference, here’s some bridge info it’s spitting out.

2024-05-13T23:52:27.070Z [BRIDGE_CFG] [INFO] Bridge network info CRC: 8bce8668
2024-05-13T23:52:27.070Z [BRIDGE_CFG] [INFO] Bridge FW Version: Major: 0 Minor: 11 Revision: 0
2024-05-13T23:52:27.070Z [BRIDGE_CFG] [INFO] Bridge sys config partition CRC: 137ed9b0
2024-05-13T23:52:27.070Z [BRIDGE_CFG] [INFO] Bridge toplogy: 6b98ffbeb769bb5d
No update available for 6b98ffbeb769bb5d

I’ve double checked all of the physical connections between the spotter and dev board, and set the power controller using “bridge cfg set 0 s u bridgePowerControllerEnabled 0, bridge cfg commit 0 s” Is there some other configuration for the new ebox that I could be missing?

26

Hi @elliepeauroi I see that the bridge we shipped you is on v0.11.0.

In release v0.10.0 we added variables to the header struct for some of the core bristlemouth messages(Those were the BCMP messages if you are curious). Anyways, this means that devices >= v0.10.0 are unable to process BCMP messages from devices on <v0.10.0 and vice versa.

I am assuming your code is using a release around v0.5.0, is that correct?

There are a couple options we can do here, but they will depend on how you are updating/flashing your devkit. Are you using the SD card method, an ST-LINK + make flash, or dfu-util?

Your options are:

Option 1. Downgrade your Bridge + Spotter to be compatible with your devkit.

  • Note: If you choose this option, before you begin, please let me know the version of your devkit. This will allow me to direct you to the correct Spotter version for your needs.

Steps:

  1. Find the Firmware version/release that your devkit is using by typing info in your devkits serial terminal.
  2. Then go over to the Bristlemouth release page and find the same release. Download the bridge zip file and extract the contents. Find the file that ends with .elf.dfu.bin. The release page may just have the .elf.dfu.bin file. If so download it.
  3. Put the bridges .elf.dfu.bin file onto the Spotter SD card.
  4. Update the bridge just like how you would do a devkit SD card update:
bridge dfu bridge_v1_0-bridge-dbg.elf.dfu.bin 0x<NODE ID> 120000
  1. Wait for the update to complete and you should see a success like:
73891t [BM_DFU] [INFO] Node 0ba390a73fe8ea4f update status: 1, 0
  1. Now it is time to downgrade the Spotter to v2.X.X (TBD). I will link to you a release for you to use and you can use the installer script to downgrade the Spotter.

Option 2. Update your code base to the v0.11.0 release and update your devkit

  • Note: This requires that you use dfu-util or make flash. (You could do this by first downgrading your bridge, then updating your devkit, then re-updating your bridge, but thats a lot of extra steps.).
  • Note 2: I haven’t tested this yet, so I would suggest making sure your code changes are saved/commited/pushed before attempting.
  1. Rebase your committed code onto v0.11.0, that can look like:
(bristlemouth-m1) ➜  bm_protocol git:(victor/testing_updating_my_code) ✗ git add README.md
(bristlemouth-m1) ➜  bm_protocol git:(victor/testing_updating_my_code) ✗ git commit -m "made changes to readme, then I will rebase on v0.11.0"
[victor/testing_updating_my_code 7177699] made changes to readme, then I will rebase on v0.11.0
 1 file changed, 2 insertions(+)
(bristlemouth-m1) ➜  bm_protocol git:(victor/testing_updating_my_code) git rebase v0.11.0
Successfully rebased and updated refs/heads/victor/testing_updating_my_code.
  1. re-build your app
  2. Flash your app to your devkit using the ST-LINK or dfu-util.
  3. Check the info in your devkits serial terminal.
  4. See if the neighbor lost messages go away.
  5. If all that worked, now you have some stability improvements to the bristlemouth code base - brislemouth dfu updates - and more commands on Spotter to poll you devkits. For example you can now change configs on your devkit from the Spotter terminal.

Hope this helps! Let me know if I can clarify anything or if you have any other questions. Also if you go with option 1, let me know what version your devkit is using and I will get you the most compatible Spotter version to go with it!

Victor

27

Hello!

That’s some really useful information, we really appreciate it! For now we would like to push forward with Option 1, and our devkit is on version 0.5.0 right now.

Side note, when I went to update the bridge I got this error:

Update finished: 29f5069863a2a349 success: 0 err:c

Any thoughts as to what the error c means and how to address it?

Thank you,
Kaitlyn + Team

28

Hi @Kaitlynyau!

Here is a link to the Spotter Firmware - it is for v2.9.0. This link should automatically download the zip file.
https://5311899.fs1.hubspotusercontent-na1.net/hubfs/5311899/Spotter%20firmware%20updates%20page/v2.9.0/Spotter_BM_Firmware_Update_v2.9.0.zip
This is the installer script and here is a link on how to use it.

I am assuming you also saw something like: 235660t [BM_DFU] [INFO] Node 0000123456789876 update status: 0, 12. c(or really 0xc) and 12 are referring to an enum in bm_dfu.h called bm_dfu_err_t. These are the different error codes for bristlemouth dfu. On v0.11.0 this error 12 is BM_DFU_ERR_UNKNOWN_NODE_ID meaning the node id was unknown. I would double check that the node id you have for your bridge is correct. On this version of Spotter/bridge you can check that in the Spotter terminal using bm topo. The first node id will be the bridges.

Best

Victor

29

Hey!
So we followed your instructions and on the Spotter’s end of things, the neighbor issue seemed to be completely fixed, we’re seeing the dev kit data and everything. However, the dev kit console is still consistently outputting “:houses::satellite: Updating neighbor info! 6b98ffbeb769bb5d”. Another thing to note is that I tried very many times to push the bridge update through to no avail. I keep getting error messages every time with 0 successful updates. I triple checked the Node ID with bm topo and am still getting this:

Transfer complete!
Transitioning to state: update
File transferred, entering update phase.
Opening bm_mote_v1.0-remora-dbg.elf.dfu.bin
Node 29f5069863a2a349 update status: 0, 12
Update finished: 29f5069863a2a349 success: 0 err:c
Transitioning to state: idle

Not sure what’s going on here but hopefully theres a simple fix!

Thanks!
Kaitlyn

30

Hello!

Could you paste the command you are using to try and update the bridge? That will help me better understand the starting state of the attempted updates.

These should go away once the bridge is downgraded. Hopefully we can get there soon :sweat_smile:.

Thanks
Victor

31

Yep of course,
The latest one i was trying was:

bridge dfu bm_mote_v1.0-remora-dbg.elf.dfu.bin 0x29f5069863a2a349 300000 force

which I had altered the time-out period after getting a time-out error on the 120000 increment. We had thought that if we were able to sucessfully push a firmware we had been working on through it would solve our problems. I also put a few attempts on the exact command you laid out above:

I also tried:

bridge dfu bridge_v1_0-bridge-dbg.elf.dfu.bin 0x29f5069863a2a349 120000 force

The Node ID is the exact one copied off of the (root)29f5069863a2a349 value after issuing a bm topo command in the CLI. All of these have resulted in that error I copied above

Hope this helps!
-Kaitlyn

32

Ah! I think I should have clarified this better in my instructions, but to which device did you issue the bm topo command?

If you did it on your devkit, the root is going to be the devkit.

This is the part that I should have clarified. On Spotter, before it was downgraded to v2.9.0, you could also use the bm topo command when connected to its terminal. It would have output a list of node id’s, with the first one being the bridge. However, it does not output the (root). If your are using a node id that has (root) next to it that is telling me that the node id you copied is coming from somewhere else.

Regardless, you can double check that your bridge’s Node ID is correct by looking on the Spotters SD card. Go into the log directory and look for a file named ####_BRIDGE_CFG.log (the #'s will be a number like 0001). In that file look for some log lines like:

[BRIDGE_CFG] [INFO] Bridge network info CRC: ce670533
10583t [BRIDGE_CFG] [INFO] Bridge FW Version: Major: 0 Minor: 4 Revision: 0
10583t [BRIDGE_CFG] [INFO] Bridge sys config partition CRC: ffffffff
10583t [BRIDGE_CFG] [INFO] Bridge toplogy: ba390a73fe8ea4f | 48d57401250b4d7c | 9569d11677cf7bda

In the line starting with Bridge toplogy: the first node id will be the bridges. I think that in your case there will be only one node id.

If the node id is different, try the update command with that one.

Best
Victor

33

Hey! Kora here from the pioneer program, popping in this thread really quick. I’m having a similar issue over here in that I can’t get the spotter to power the devkit. I can connect to the devkit just fine when it’s powered from the wall charger but when powered from the spotter all I see is one red flash on the devkit then radio silence despite a fully charged spotter. Advice?

34

Ok, so this time i grabbed the Node ID from the Spotter’s SD card, it was indeed different so I popped that into the command but im currently getting a time-out error at 300000 ms. Should I just keep increasing this value? The ACK numbers stop sending pretty quickly then it just keeps pulling info from the dev-kit per usual until the time-out error shows up.

...
Sending 143360:1024
ACK 23000
Sending 144384:1024
ACK 23400
Sending 145408:1024
ACK 23800
Sending 146432:1024
2024-05-21T21:39:09.578Z [BRIDGE_SYS] [INFO] ␄ 1716327551.386 29f5069863a2a349, hum_temp | tick: 462188, rtc: 2024-05-21T21:39:10.832, hum: 44.804893, temp: 23.101759
1716327553.394 29f5069863a2a349, pressure | tick: 464197, rtc: 2024-05-21T21:39:12.839, temp: 23.102697, pressure: 1015.095581
1716327553.421 29f5069863a2a349, power | tick: 464204, rtc: 2024-05-21T21:39:12.847, addr: 67, voltage: 23.937599, current: 0.000000
1716327553.445 29f5069863a2a349, power | tick: 464206, rtc: 2024-05-21T21:39:12.847, addr: 65, voltage: 23.936001, current: -0.001000
2024-05-21T21:39:19.550Z [BRIDGE_SYS] [INFO] ␄ 1716327561.386 29f5069863a2a349, hum_temp | tick: 472188, rtc: 2024-05-21T21:39:20.984, hum: 44.547932, temp: 23.097696
1716327563.394 29f5069863a2a349, pressure | tick: 474197, rtc: 2024-05-21T21:39:22.996, temp: 23.097383, pressure: 1015.035767
1716327563.417 29f5069863a2a349, power | tick: 474204, rtc: 2024-05-21T21:39:23.003, addr: 67, voltage: 23.937599, current: 0.000000
1716327563.445 29f5069863a2a349, power | tick: 474206, rtc: 2024-05-21T21:39:23.003, addr: 65, voltage: 23.936001, current: -0.001000
2024-05-21T21:39:27.113Z [GPS] [INFO] Max CNO changed from 31 to 34
FFT begin.
FFT complete.
sample analysis complete
2024-05-21T21:39:29.550Z [BRIDGE_SYS] [INFO] ␄ 1716327571.386 29f5069863a2a349, hum_temp | tick: 482188, rtc: 2024-05-21T21:39:30.988, hum: 44.832882, temp: 23.107073
1716327573.394 29f5069863a2a349, pressure | tick: 484197, rtc: 2024-05-21T21:39:32.996, temp: 23.107073, pressure: 1015.041199
1716327573.421 29f5069863a2a349, power | tick: 484204, rtc: 2024-05-21T21:39:33.003, addr: 67, voltage: 23.937599, current: 0.000000
1716327573.445 29f5069863a2a349, power | tick: 484206, rtc: 2024-05-21T21:39:33.007, addr: 65, voltage: 23.936001, current: -0.001000
2024-05-21T21:39:33.464Z [BRIDGE_SYS] [INFO] ␄ 2024-05-21T21:39:34.468Z [BRIDGE_SYS] [INFO] ␄!2024-05-21T21:39:34.476Z [BRIDGE_SYS] [INFO] ␄#2024-05-21T21:39:34.480Z [BRIDGE_SYS] [INFO] ␄␚1716327581.386 29f5069863a2a349, hum_temp | tick: 492188, rtc: 2024-05-21T21:39:40.992, hum: 44.832951, temp: 23.112387
1716327583.394 29f5069863a2a349, pressure | tick: 494197, rtc: 2024-05-21T21:39:43.000, temp: 23.115200, pressure: 1015.051819
1716327583.421 29f5069863a2a349, power | tick: 494204, rtc: 2024-05-21T21:39:43.007, addr: 67, voltage: 23.937599, current: 0.000000
1716327583.445 29f5069863a2a349, power | tick: 494206, rtc: 2024-05-21T21:39:43.007, addr: 65, voltage: 23.936001, current: -0.001000
2024-05-21T21:39:49.550Z [BRIDGE_SYS] [INFO] ␄ 1716327591.386 29f5069863a2a349, hum_temp | tick: 502188, rtc: 2024-05-21T21:39:50.992, hum: 44.827442, temp: 23.118326
1716327593.394 29f5069863a2a349, pressure | tick: 504197, rtc: 2024-05-21T21:39:53.000, temp: 23.121765, pressure: 1015.061646
1716327593.421 29f5069863a2a349, power | tick: 504204, rtc: 2024-05-21T21:39:53.007, addr: 67, voltage: 23.937599, current: 0.000000
1716327593.445 29f5069863a2a349, power | tick: 504206, rtc: 2024-05-21T21:39:53.011, addr: 65, voltage: 23.936001, current: -0.001000
2024-05-21T21:39:59.550Z [BRIDGE_SYS] [INFO] ␄ 1716327601.386 29f5069863a2a349, hum_temp | tick: 512188, rtc: 2024-05-21T21:40:00.996, hum: 44.805199, temp: 23.125828
1716327603.398 29f5069863a2a349, pressure | tick: 514197, rtc: 2024-05-21T21:40:03.003, temp: 23.126453, pressure: 1015.055054
1716327603.421 29f5069863a2a349, power | tick: 514204, rtc: 2024-05-21T21:40:03.011, addr: 67, voltage: 23.937599, current: 0.000000
1716327603.445 29f5069863a2a349, power | tick: 514206, rtc: 2024-05-21T21:40:03.011, addr: 65, voltage: 23.936001, current: -0.001000
2024-05-21T21:40:09.550Z [BRIDGE_SYS] [INFO] ␄ 1716327611.386 29f5069863a2a349, hum_temp | tick: 522188, rtc: 2024-05-21T21:40:10.996, hum: 44.794117, temp: 23.132706
1716327613.398 29f5069863a2a349, pressure | tick: 524197, rtc: 2024-05-21T21:40:13.007, temp: 23.124266, pressure: 1015.061157
1716327613.421 29f5069863a2a349, power | tick: 524204, rtc: 2024-05-21T21:40:13.011, addr: 67, voltage: 23.936001, current: 0.000000
1716327613.445 29f5069863a2a349, power | tick: 524206, rtc: 2024-05-21T21:40:13.015, addr: 65, voltage: 23.936001, current: -0.001000
FFT begin.
FFT complete.
sample analysis complete
2024-05-21T21:40:19.550Z [BRIDGE_SYS] [INFO] ␄ 1716327621.386 29f5069863a2a349, hum_temp | tick: 532188, rtc: 2024-05-21T21:40:21.000, hum: 44.777477, temp: 23.141771
1716327623.398 29f5069863a2a349, pressure | tick: 534197, rtc: 2024-05-21T21:40:23.007, temp: 23.137707, pressure: 1015.120483
1716327623.421 29f5069863a2a349, power | tick: 534204, rtc: 2024-05-21T21:40:23.015, addr: 67, voltage: 23.937599, current: 0.000000
1716327623.449 29f5069863a2a349, power | tick: 534206, rtc: 2024-05-21T21:40:23.015, addr: 65, voltage: 23.936001, current: -0.001000
2024-05-21T21:40:29.550Z [BRIDGE_SYS] [INFO] ␄ 1716327631.386 29f5069863a2a349, hum_temp | tick: 542188, rtc: 2024-05-21T21:40:31.000, hum: 44.744068, temp: 23.149586
1716327633.402 29f5069863a2a349, pressure | tick: 544197, rtc: 2024-05-21T21:40:33.011, temp: 23.149273, pressure: 1015.066772
1716327633.421 29f5069863a2a349, power | tick: 544204, rtc: 2024-05-21T21:40:33.019, addr: 67, voltage: 23.937599, current: 0.000000
1716327633.449 29f5069863a2a349, power | tick: 544206, rtc: 2024-05-21T21:40:33.019, addr: 65, voltage: 23.936001, current: -0.001000
2024-05-21T21:40:33.460Z [BRIDGE_SYS] [INFO] ␄ 2024-05-21T21:40:34.468Z [BRIDGE_SYS] [INFO] ␄!2024-05-21T21:40:34.476Z [BRIDGE_SYS] [INFO] ␄#2024-05-21T21:40:34.480Z [BRIDGE_SYS] [INFO] ␄␚Node ffbeb769bb5d0132 file transfer timed out
Transitioning to state: error
Update finished: ffbeb769bb5d0132 success: 0 err:ffffffff
Error updating -4
Transitioning to state: idle

and to clarify, the exact command was

bridge dfu bridge_v1_0-bridge-dbg.elf.dfu.bin 0xffbeb769bb5d0132 300000 force

Another lil update: we seem to be back on the error: c message when I try pasting in that update command again, even though I changed the node id to the one from the spotter’s log file.

35

Hello!

I looked back at previous posts and I see that the Bridges node id was reported as 6b98ffbeb769bb5d. Have you tried it using this one?

The ack’s stopping can happen sometimes when the Spotter sends a packet and doesn’t get an ACK back. We have since added more robustness to the bristlemouth dfu system, but the v0.5.0 and Spotter v2.9.0 releases don’t have this.

Also what version is your Spotter on currently? The reason I ask is, if you already downgraded you Spotter to v2.9.0, then that may imapct its ability to work with the bridge while it is still on v0.11.0. So we may need to first update your Spotter, then downgrade the bridge, then downgrade the Spotter.

Victor

36

Hi Kora!

Have you tried using a multimeter to measure the output from the ebox?

This post has an example of where you can measure it: Powering the dev kit from the spotter - #19 by zack_j

Victor

37

Hi!

So we indeed downgraded the Spotter already :grimacing: If we could get the spotter upgrade so we can downgrade the bridge that would be very helpful!

38

No worries! Here is the link for v2.15.1 https://5311899.fs1.hubspotusercontent-na1.net/hubfs/5311899/Spotter%20firmware%20updates%20page/v2.15.1/Spotter_BM_Firmware_Update_v2.15.1.zip

So update the Spotter with this, then try to downgrade your bridge. Then if that succeeds, downgrade the Spotter like you did before.

Let me know how it goes!

Victor

39

So the good news: The spotter is updated back to where it was before!
bad news: im getting a bad crc error?

2024-05-22T20:50:30.312Z [BM_DFU] [INFO] Transfer complete!

2024-05-22T20:50:30.312Z [BM_DFU] [INFO] Transitioning to state: update

2024-05-22T20:50:30.312Z [BM_DFU] [INFO] File transferred, entering update phase.

2024-05-22T20:50:30.312Z [BM_DFU] [INFO] Opening bm_mote_v1.0-remora-dbg.elf.dfu.bin

2024-05-22T20:50:30.566Z [BM_DFU] [INFO] Node 6b98ffbeb769bb5d update status: 0, 4

Update finished: 6b98ffbeb769bb5d success: 0 err:4

I checked via SD card and bm topo that the node id is correct but Im not sure what this error is indicating. If possible, would we be able to schedule a quick zoom call to maybe sort this out with less back and forth?

We appreciate all the thoughtful and quick responses to our problems!

-Kaitlyn + team

40

The bad CRC is likely from a missed ACK between the Spotter/Bridge. I would try again, and if possible, unplug the devkit from the bridge so limit the amount of traffic between Spotter/bridge.

Victor