Related

Mid-ride shutdown, had to turned on manually

Luko79
10 months ago

Any idea what can caused it?

[
{
"unit_id":"3445248299",
"product_name":"Edge 540",
"software_part_number":"006-B4061-00",
"ms_since_epoch":1685326454000,
"system_version":"9.29",
"build_type":"PRODUCTION",
"backtrace":"
Function Address: 0x608C1F14
Call Address at Function: 0x608C1F2C

Function Address: 0x608BCEE8
Call Address at Function: 0x608BD386

Function Address: 0x608BDD26
Call Address at Function: 0x608BDD50

Function Address: 0x604AF210
Call Address at Function: 0x604AF23C

Function Address: 0x6055DA00
Call Address at Function: 0x6055EB4A

Function Address: 0x605603F8
Call Address at Function: 0x605604F0

Function Address: 0x6056B17E
Call Address at Function: 0x6056B24A

Function Address: 0x6056DDD8
Call Address at Function: 0x6056E7E2

Function Address: 0x603D7D00
Call Address at Function: 0x603D7D24

Function Address: 0x608BFEB8
Call Address at Function: 0x608BFEE8

Function Address: 0x60562CE8
Call Address at Function: 0x60562EF2

",
"error_cause":"RTL Trap",
"proprietary_info":{
"Commit ID":"479d2de60dd046245db84d1845923a2bb438db5a",
"Time":"2023-5-29 4:14:14",
"RTL Error Number":"6E5D800F",
"Error Message":"62512550,604AF23D,0000A094,0005FCA6,03589FEC",
"Task Name":"MMP main",
"Saved SP":"62511EC8",
"Saved LR":"608BD387",
"Saved PC":"608C1F2D",
"R[0]":"62512550",
"R[1]":"604AF23D",
"R[2]":"0000A094",
"R[3]":"0005FCA6",
"R[4]":"03589FEC",
"R[5]":"00000000",
"R[6]":"00000000",
"R[7]":"00000000",
"R[8]":"00000000",
"R[9]":"00000000",
"R[10]":"00000000",
"R[11]":"00000000",
"R[12]":"00000000",
"R[13]":"00000000",
"R[14]":"00000000",
"R[15]":"00000000",
"cpsr":"00000000"
}
,
"Project Specific":{
"data" : {

}
}
}]

  • 0 10 months ago

    Have same problem today !!! After 2 hour device shutdown !! Very  sad I’m upgrade from 530 think that’s bug have fix on new generation but maybe not !!!

  • 0 10 months ago

    Any possible why if this ?

    can fix my fit file from ride, after that the first part of ride no account training status on my Garmin connect !!

    you have my clearance for check my files !  

  • 0 10 months ago in reply to DanielxcBR

    Daniel,

    did You follow a workout? (the guy who had the posted issue was running a guided workout during his ride, on a stock device, without any ConnectIQ app or similar)

  • 0 10 months ago in reply to Luko79

    Luko79,

    no,  I'm in free ride and after 90k paused for water refuel and 5 min after resume activity  device shutdown and restart. The only important change is big climate temperature spike from 8c  to  27c degree and altitude from 1000m to 11m -> meters, maybe have bug barometer or altimeter !

    ps: temperature and altitude change is correct, because I'm descent from mountain to sea level  and from initial ascent same mountain device have this problem ...

  • 0 9 months ago

    Any more info or solution on this? Started after firmware 13.75 I am consistently getting the same error - almost always in the afternoon along a certain route, never in the morning or the opposite direction (yet).

  • 0 9 months ago in reply to ScaryD

    Did anyone find out anything about this problem? I've had a similar experience. My Edge 540 dropped out 3 times at almost the same place. It was a race course with lots of ups and downs. This is so very disappointing. Needless to say that back home everything was fine again. And no, I have not been following a workout, no powersaving, not even another profile than what I use for everyday riding. :-(

  • 0 9 months ago in reply to 63a98ac27b774171bfca838b35f1c9f2

    Hi, after numerous resets, even FW13.9 beta update, map reload, kitchen sink, everything under the sun etc, my problem persisted. I chatted with a Garmin CS and was told that my Edge 1030 has an issue(s) that will not be fixable by future FW updates. The CS offered to replace my unit with another refurbished unit and I accepted the exchange. With the exchange and refurbished 1030, I no longer had location-based crash - even after the refurbished unit updated itself to FW13.75. So my problem was probably partly hardware or at least hardware-firmware related.

  • 0 8 months ago

    Same problem here. Bought this "high end" device and on my first ride reboot after like 45min in. Holy smokes. I am so disappointed, Garmin charges premium for everything and the most basic feature, simple tracking, results in shutdowns? Let's hope it's a simple bug that get's fixed soon.

  • 0 5 months ago in reply to npr77

    This has also happened to my 840 on numerous occasions. Does anyone have a fix yet?

  • 0 2 months ago

    I just bought the 540 about 2 weeks ago as my 510 finally packed up. Two hours into a 4 hour ride the device shuts down and I had to manually turn it back on. Seems like there was no loss in data collection from what I can see. Auto Sleep is turned off btw, so not that. Will test it next week on a long ride again.