• Replies 2 replies
  • Subscribers 15 subscribers
  • Views 677 views
  • Users 0 members are here
Options
Related

FR235 crash & reboot loop

IMGrant
over 8 years ago
My FR235 crashed on me today during a run, first it stopped/paused the run, then froze for a few seconds before rebooting (displaying the Garmin logo), when it came back up, it went straight to the activity, still stopped/paused, then immediately crashed again and rebooted. After doing this about 6 times, it came back up, straight into the activity and stayed up. I was able to resume the run and complete it (obviously there was some missing data for the few minutes it was rebooting and I continued to walk).

I had two Connect IQ data fields running, and one of them (my own, Flexirunner) had been replaced with the native Timer field, suggesting it was this data field that caused the crash. I was running a release build, not debug, so there is no CIQ_LOG.TXT, but there is information in the device ERR_LOG.TXT. Since the Connect IQ page encourages developers to post such information here, suggesting a bug in Connect IQ or the watch firmware, rather than the app, per se, here it is:

2431 (Forerunner 235) SW ver: 710Build Type: RELEASE
Commit:1bcef5c212eb9f98292ccd1d9b7ff1dbf9457258
ESN: 3922968744
02/02/17 14:16:52
RTL
errnum: 0x002
r0: 0x20007f20
r1: 0x000000b6
r2: 0x000f8551
Stack frame PC, SP: 0x0011953d, 0x20007c30
Call Stack - SP at 0x20007c30:
0x000e0693
0x000f8551
0x000f05df
0x000f8551
0x000f8551
0x0000c001
0x000f11d7
0x001068e5
0x000f11d7
0x000f088d
0x001068e5
0x0010f97b
0x0000c001
0x000f11d7
0x000f088d
0x00112173
0x00106647
0x00111f55
0x001128e9
0x0010050d
0x0010057b
0x00106433
0x000f544d
0x0002c90d
0x00041b31
0x00041e11
0x000427e1
0x000eec31
0x00000000
0x00000000
0x00000000
0x00000000
Uptime: 5856084


2431 (Forerunner 235) SW ver: 710
Build Type: RELEASE
Commit:1bcef5c212eb9f98292ccd1d9b7ff1dbf9457258
ESN: 3922968744
02/02/17 14:17:07
AP
PWR RST CTRL: 0x00400028
POR


2431 (Forerunner 235) SW ver: 710
Build Type: RELEASE
Commit:1bcef5c212eb9f98292ccd1d9b7ff1dbf9457258
ESN: 3922968744
02/02/17 14:17:55
AP
PWR RST CTRL: 0x00400028
POR


2431 (Forerunner 235) SW ver: 710
Build Type: RELEASE
Commit:1bcef5c212eb9f98292ccd1d9b7ff1dbf9457258
ESN: 3922968744
02/02/17 14:18:28
AP
PWR RST CTRL: 0x00400028
POR


2431 (Forerunner 235) SW ver: 710
Build Type: RELEASE
Commit:1bcef5c212eb9f98292ccd1d9b7ff1dbf9457258
ESN: 3922968744
02/02/17 14:18:28
AP
PWR RST CTRL: 0x00400028
POR


2431 (Forerunner 235) SW ver: 710
Build Type: RELEASE
Commit:1bcef5c212eb9f98292ccd1d9b7ff1dbf9457258
ESN: 3922968744
02/02/17 14:19:34
AP
PWR RST CTRL: 0x00400028
POR

Can anyone from Garmin offer any insight as to what that log is telling me?
I'm at a loss how to replicate the situation, it seemed to be random (I've run many hours with this data field).
  • over 8 years ago
    Hey there,

    I'm not totally sure what's going on here, but I was able to parse you error log and I think you are right in saying that it is something with the way the watch is handling your use of the data fields. I've created a ticket to take a look at it. Would you be able to send up information about the two data fields you were using and perhaps email us the project for your data field to [email][email protected][/email]. As well, please be sure to read the Bug Reports Forum Rules for posting future bug reports as formatting them correctly helps us to more efficiently process the reports we receive.

    Thanks so much!
    -Coleman
  • over 8 years ago
    Hi, thanks for the reply. Sorry about not formatting the bug report correctly (although, to be fair, the bit about reporting the steps to reproduce it is problematic here).

    What information do you require about the data fields I was using?
    They were:
    1. Stryd Power (JanuaryUpdateV2, https://apps.garmin.com/en-US/apps/660a581e-5301-460c-8f2f-034c8b6dc90f)
    2. Flexirunner (6.0.0, built with SDK 2.2.3, https://apps.garmin.com/en-US/apps/ce1e0b46-7c83-4ddb-9d48-c93edadabe3d)

    When you say "email us the project for your data field", what do you mean? The source code can be found here, if that's what you mean: https://github.com/imgrant/FlexiRunner

    My watch: Forerunner 235, firmware version 7.10 (as you can see from the logs)

    I've run again today, with an updated version of Flexirunner (6.1.0, built with SDK 2.2.3) and did not observe the problem. But, as I say, it was a one-time occurrence with seemingly no trigger.
    Do you need an email to [email][email protected][/email] referencing this thread?