This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ClimbPro and navigation instructions overlap causes FW 5.50 to crash

Tried with the beta before 5.50, but today it happened with 5.50 as well.

Here is the sequence of the events:

- Starred a route in Strava, it appeared automatically on my 530 - all good here!

- As I was following the route, at one point it triggered the ClimbPro

- As ClimbPro was on my screen, navigation instructions came up telling me which way to turn 

- Once Nav instructions were followed, it went back to ClimbPro (so far so good)

- When the climb was completed, it said so "Climb completed" and trying to return to the Nav screen (with the map) it crashed....

- Auto-restarted, all good and continued from where it crashed, except that it had to recalculate the route - not much of a problem.

Other remarks:

- Strava segments work just fine

- ClimbPro works just fine IF it does not contain overlapping navigation instructions 

- basically everything works just great except for the above combination.

Anyone else with similar experiences?

Happy to supply whatever file is needed.

  • Indeed, I was also talking about navigation pop-ups during active ClimbPro screen. But good suggestion, I will try next time with a course, created on Garmin Connect, not Strava. 

  • here is my log as well:

    [
    {
    "unit_id":"3329188439",
    "product_name":"Edge 530",
    "software_part_number":"006-B3121-00",
    "ms_since_epoch":1592048700000,
    "system_version":"5.50",
    "build_type":"PRODUCTION",
    "backtrace":"
    Function Address: 0x6086F87E
       Call Address at Function: 0x6086F8F0
    
    Function Address: 0x60213E58
       Call Address at Function: 0x6021420A
    
    Function Address: 0x60214DD8
       Call Address at Function: 0x60214E04
    
    Function Address: 0x60248BE0
       Call Address at Function: 0x60248CC0
    
    Function Address: 0x605EB51C
       Call Address at Function: 0x605EC072
    
    Function Address: 0x6020CBDC
       Call Address at Function: 0x6020CFD6
    
    Function Address: 0x6020D67C
       Call Address at Function: 0x6020D6E8
    
    Function Address: 0x6020D70C
       Call Address at Function: 0x6020D79C
    
    ",
    "error_cause":"RTL Trap",
    "proprietary_info":{
        "Commit ID":"4969a4be8627c688bdcae819f7a0fa2ac1e46614",
        "Time":"2020-6-13 13:45:0",
        "Project Specific":"2020-6-13 13:45:0",
        "CDP_LOG":"05C3E0D,600E7291,600E7291,605B07CD,600E7291,605B07CD,605B07CD,605B07CD,600E7291,605B07CD,600E7291,605B07CD,600E7291,605B07CD,600E7291,605CCB29,605C4D49,605C4D99,605CCB29,605CBE4D,605CCB29,600E7291,605B07CD,600E7291,605C4C1D,600E7291,60202449,605D7B05,605E47F5,605D7B05,60202449,600E7291,605A6CDD,600E7291,605B07CD,600E7291,60202449,605D7B05,605E47F5,605D7B05,60202449,600E7291,60589DDD,60589DDD,605C3D6D,60589DDD,605EC1FD,605C3D8D,605EC1FD,60589DDD,605EC1FD,60589DDD,605EC1FD,605C3D7D,605EC1FD,600E7291,",
        "RTL Error Number":"6E5D8024",
        "Error Message":"D15EB174,00000000,0000000D,D15EB174,D15EB180,00000009,00000006,61EDB760,0000000D,0000000E,00000001,00000004,D15EB174,61EDB534,00000000,6086F8F0,8000001F",
        "Task Name":"CDP main",
        "Saved SP":"61EDB534",
        "Saved LR":"00000000",
        "Saved PC":"6086F8F0",
        "R[0]":"D15EB174",
        "R[1]":"00000000",
        "R[2]":"0000000D",
        "R[3]":"D15EB174",
        "R[4]":"D15EB180",
        "R[5]":"00000009",
        "R[6]":"00000006",
        "R[7]":"61EDB760",
        "R[8]":"0000000D",
        "R[9]":"0000000E",
        "R[10]":"00000001",
        "R[11]":"00000004",
        "R[12]":"D15EB174",
        "R[13]":"61EDB534",
        "R[14]":"00000000",
        "R[15]":"6086F8F0",
        "cpsr":"8000001F"
        }
    
    }
    ]

  • My error log looks almost identical to yours - that should be a good news from bug fixing point of view.

  • Thanks.

    I have passed the logs on to Garmin and they are looking at the issue.

  • Great, thanks a lot for your help!

  • In looking for an Error Log to send I noted a ramdumpC2.log file that may align with my crash (47 MB or so), but I don't have an error log with the same file time stamp either in Debugging or Saved folder.  I have something like 4 error logs per ride, although I've only witnessed a single crash/reboot in all my use that I can recall.

    "Saved" Folder:

    Most of the error logs I have seem to complain about an Assert for example -

    "product_name":"Edge 530",
    "software_part_number":"006-B3121-00",
    "ms_since_epoch":1592070749000,
    "system_version":"5.51",
    "build_type":"PRODUCTION",
    "backtrace":"CDP main - Error type ( 0 ) File( ..\\..\\..\\ANT\\connection-manager\\ant_connection_utl.c ) Line( 583 )",
    "error_cause":"Assert",
    "proprietary_info":{
    "Commit ID":"8496f54306a49ba55faed9506375fa45a1b4a9a5",
    "Time":"2020-6-13 12:52:29",
    "Ram Dump":"N/A",
    "ESht PC":"0x00000000",
    "ESht SP":"0x00000000",
    "Project Specific":"0x00000000",
    "Fatal":"NO",
    "Task ID":"61EDBD20",
    "Task Name":"CDP main",
    "File Name":"..\\..\\..\\ANT\\connection-manager\\ant_connection_utl.c",
    "Line Number":"583",
    "Message":"583"
    }

    Other examples that show frequently:

    "product_name":"Edge 530",
    "software_part_number":"006-B3121-00",
    "ms_since_epoch":1592323474000,
    "system_version":"5.51",
    "build_type":"PRODUCTION",
    "backtrace":"BTM main - Error type ( 0 ) File( ..\\..\\..\\BTF\\btf_incident_detect.c ) Line( 1325 )",
    "error_cause":"Assert",
    "proprietary_info":{
    "Commit ID":"8496f54306a49ba55faed9506375fa45a1b4a9a5",
    "Time":"2020-6-16 11:4:34",
    "Ram Dump":"N/A",
    "ESht PC":"0x00000000",
    "ESht SP":"0x00000000",
    "Project Specific":"0x00000000",
    "Fatal":"NO",
    "Task ID":"61EB9EE0",
    "Task Name":"BTM main",
    "File Name":"..\\..\\..\\BTF\\btf_incident_detect.c",
    "Line Number":"1325",
    "Message":"1325"
    }

    And...

    "product_name":"Edge 530",
    "software_part_number":"006-B3121-00",
    "ms_since_epoch":1592323071000,
    "system_version":"5.51",
    "build_type":"PRODUCTION",
    "backtrace":"ant_main - Error type ( 0 ) File( ..\\..\\..\\ANT\\ant_module_bike_light_controller.c ) Line( 4839 )",
    "error_cause":"Assert",
    "proprietary_info":{
    "Commit ID":"8496f54306a49ba55faed9506375fa45a1b4a9a5",
    "Time":"2020-6-16 10:57:51",
    "Ram Dump":"N/A",
    "ESht PC":"0x00000000",
    "ESht SP":"0x00000000",
    "Project Specific":"0x00000000",
    "Fatal":"NO",
    "Task ID":"61E5F5E8",
    "Task Name":"ant_main",
    "File Name":"..\\..\\..\\ANT\\ant_module_bike_light_controller.c",
    "Line Number":"4839",
    "Message":"8,15232960,15232960,1,1"
    }

    I'd be happy to zip my error logs and/or try to get the ram dump to someone if anyone wants a deeper look.  I'm on 5.51 beta as you see from the log snip above.

  • Build 5.51 has more logging enabled, including the ability for the unit to dump the RAM.

    If you could respond to the beta email  [email protected]. about the RAM dumps that would be the best place.

  • Former Member
    0 Former Member over 5 years ago

    I have exactly the same issue using my 830. Until this week no issues due to the fact we have no climbs around.

    Yesterday it crashed 3 times just after the climb was completed. I make my GPX files with judise.nl (so no strava).

    It is pretty annoying especially when you need the navigation at that point, the calculation takes some time and your navigation is not working at the that moment.

    Anything that I can do to convince Garmin to solve this asap or to have a work around for the time?

    Kind regards, Sjoerd

  • I think we did what we could - hope it will be solved soon. But I get your frustration, I live in the same country as you - so a bit of a bummer after we finally get to one of the very few "climbs" and then it crashes. 

    Good to know it is not Strava route that is causing it though.

  • I have hopes they are going to get it fixed up - at least the firmware and betas are still clearly active for the device.

    If you look at issues on the Forerunner 935 there hasn't really been a firmware or beta in a year (the right around the latest production release is when they made some aspects worse - open water swim, for example).

    I wonder if you turn off the turn guidance or turn notifications if it would help (clearly it wouldn't help your navigation, but at least the crashing?)

    FWIW, I sent my fit file and a link to my RAM dump to the beta email as well.