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

Firmware 6.2 & 6.3 problems

I have been having problems with my 820 ever since updating to 6.2 and then with 6.3. The problem is if i turn it on inside where there is no gps signal the 820 crashes after a few minutes. This also applies when the 820 is in indoor mode. I use it indoors for training with an old classic trainer and a newer smart trainer, or at least I would do if it would work.
I have rolled back the firmware on my 820 to 5.2 and this problem has gone away and it now works fine, so the problem is clearly with the update.
Anyone have any suggestions how to load 6.3 without this problem.
Regards
Dave

0 Former Member over 8 years ago

since 6.30 Update my 820 also crashes. It did so twice today on a 80km ride. Was displaying a course on the map.

0 The_Hunnymonster over 8 years ago

I had a random shutdown yesterday - not doing anything unusual, recording ride, tracking a buddy on GroupTrack when the unit simply faded to grey. It did restart cleanly. Checked this morning and in the error log - this:

2530 (Edge 820) SW ver: 630

ParserVersion 3

UnitId: {3xxxxxxxx}

Product: {Edge 820}

SoftwarePartNumber: {006-B2530-00}

Time: {2017-4-9 10:5:27}

PackageVersion: {}

SystemVersion: {630 / 100.630 %}

PackageName: {RELEASE}

Build_Tag: {RELEASE}

build_type: {RELEASE}

Symbols Error: {Symbols File Not Found}

Backtrace: {

Function Address: 0x0800201A

   Call Address at Function: 0x08002052



Function Address: 0x0828FEC2

   Call Address at Function: 0x0828FFC4



Function Address: 0x080500A0

   Call Address at Function: 0x080500E6



Function Address: 0x0805054A

   Call Address at Function: 0x08050622



Function Address: 0x0813BB72

   Call Address at Function: 0x0813BBD4



Function Address: 0x0813BDC2

   Call Address at Function: 0x0813BE2E



Function Address: 0x08143724

   Call Address at Function: 0x08144AA0



}

Assert_Info: {}

RTL_Trap_Info: {

Task ID: 0x7171FAE8

Task Name: MMP main

Error Number: 0x6E5D8001



Uptime: 1143432

Registers: 

0x7171FAE8

0x00004000

0x080500E7

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: Out of memory handles, r0=task ID, r1=limit, r2=rtrn}

Exception_Info: {}

Error_Cause: {1}

PC_SP: {0x00000000,0x00000000}

0 JedRunner over 8 years ago

You may not believe this, but there are many (the vast majority) people out there who have used 6.20 & 6.30 since they became available without issue. Including but not limited to indoor rides, outdoor rides, Bluetooth uploads & WiFi uploads. Odd times (1 time out of 15) the WiFi upload didn't happen immediately, but it had within an hour without any intervention from me.

Suggests the problems are sporadic, perhaps exposed by some specific constellation of factors that pertain only to you. I know that in your house 100% are failing, in mine 100% are acting exactly as expected.

For me 100% of wifi uploads fails with the same symptoms as described. Bluetooth works 8/10. I created a separate thread a while ago with wifi issues but received no answer.

0 accordnick over 8 years ago

Stopped syncing over wifi after 6.30 update. After a ride it finds the wifi network, then shows "Checking" and that's it, transferring never starts, no matter whether BLE is enabled or not. Though it's still possible to sync via bluetooth, but I get used to using wifi and now it's pretty annoying to look for the phone every time you need to upload data.
Btw, how to roll the firmware version back? Just to make sure that it really started with 6.30.

The rolling back to 6.20 fixed wifi sync for me. Tried a lot of other tricks with no effect.