Edge 520 Crashing: Error Message: Bad memory handle, r0=task ID, r1=handle, r2=rtrn}

Having written similar embedded crash logging code before, I bet the problem is software not hardware (99% odds :p )

Edge 520 is running SW ver: 230.

The meaningful message in the err_log.txt is the following:
Error Message: Bad memory handle, r0=task ID, r1=handle, r2=rtrn}
Exception_Info: {}
Error_Cause: {1}

The unit powered off in the middle of a ride.

This happened on the first ride with the factory configuration.

I'm trying to determine if this error is hardware or software related.

Having owned a Garmin before, I bet the problem is software not hardware (99% odds :p )

fixed :p

My 520 has also crashed/powered off 2 of the 3 rides I have used the device. (Have not checked if there is a log file.. )

Bundle sensors and phone connected.

I have had it shut down once on my first ride but not since. Looks like a similar error...



2067 (Edge 520) SW ver: 230
ParserVersion 3
UnitId: {3907876505}
Product: {Edge 520}
SoftwarePartNumber: {006-B2067-00}
Time: {2015-8-26 13:40:53}
PackageVersion: {}
SystemVersion: {2.30}
PackageName: {RELEASE}
Build_Tag: {RELEASE}
build_type: {RELEASE}
Symbols Error: {Symbols File Not Found}
Backtrace: {
Function Address: 0x080043B0
Call Address at Function: 0x080043E8

Function Address: 0x08235840
Call Address at Function: 0x08235858

Function Address: 0x081E5076
Call Address at Function: 0x081E5108

Function Address: 0x081E51A8
Call Address at Function: 0x081E51BE

Function Address: 0x08250416
Call Address at Function: 0x0825052E

Function Address: 0x082506B4
Call Address at Function: 0x08250A5E

Function Address: 0x08250C44
Call Address at Function: 0x08250DE4

Function Address: 0x080BBA94
Call Address at Function: 0x080BBB5C

Function Address: 0x080BBE7E
Call Address at Function: 0x080BBFE4

Function Address: 0x08208FF4
Call Address at Function: 0x08209AEE

Function Address: 0x08099C9A
Call Address at Function: 0x08099CF0

}
Assert_Info: {}
RTL_Trap_Info: {
Task ID: 0x713A6FB0
Task Name: MPM main
Error Number: 0x6E5D8002

Uptime: 2987342
Registers:
0x713A6FB0
0x00000000
0x081E5109
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000

CPSR: 0x00000000
HFSR: 0x00000000
CFSR: 0x00000000
BFAR: 0x00000000
MMFAR: 0x00000000
AFSR: 0x00000000
PSP: 0x00000000
MSP: 0x00000000

Error Message: Bad memory handle, r0=task ID, r1=handle, r2=rtrn}
Exception_Info: {}
Error_Cause: {1}

I have had it shut down once on my first ride but not since. Looks like a similar error...


...snip...

build_type: {RELEASE}
Symbols Error: {Symbols File Not Found}
Backtrace: {
Function Address: 0x080043B0

...more snipping...


Error Message: Bad memory handle, r0=task ID, r1=handle, r2=rtrn}
Exception_Info: {}
Error_Cause: {1}

I think that might be the problem. I don't know what they symbol is, but maybe there is one missing? I have only had it happen to me once so far, after I went past the start point of about 4 or more segments. Though, I have gone that way before and after without a problem.

Symbols File Not Found - this is additional debugging information used during the development of the software that contains variable names that humans can understand to make it easier to track what is happening in the software. It wall have been removed for the release software build and will not be the cause of the problem. I'd be more worried if the symbols file was still included as this would suggest some problems with Garmin's software engineering release processes.

Symbols File Not Found - this is additional debugging information used during the development of the software that contains variable names that humans can understand to make it easier to track what is happening in the software. It wall have been removed for the release software build and will not be the cause of the problem. I'd be more worried if the symbols file was still included as this would suggest some problems with Garmin's software engineering release processes.

That may be. To me, it read more like "opps we forgot to include the icon for XYZ and the device freaked out."

That may be. To me, it read more like "opps we forgot to include the icon for XYZ and the device freaked out."

Ok, but..how do we fix it? I am still having this issue !?

Thanks