[TG] [TG11] Axiom crash on upgrade and reset.

[KenA]

I've got a Raymarine Axiom 9 which has been working very well.

Back in April this year I updated to v3.4.66 with success via a SD Card.

Since then I have not been able to update to any of the new versions including the one just released v3.7.70.

I have tried the following since April to resolve this issue. Here are some things I and tried and observed.

1. Tried a Settings RESET - The Unit asked for Yes or No. When I hit YES it says rebooting and the screen goes black and it never comes back. 1 hour say, I had to turn electronics switch off and on and it comes back.
2. Tried a Factory RESET - The Unit asked for Yes or No. When I hit YES it says rebooting and the screen goes black and it never comes back. 1 hour say, I had to turn electronics switch off and on and it comes back.
3. Software Update. It finds the update for the Axiom and after I select the update it reboots and never comes back. When I power off and on at circuit is says Software Update Failed. No details as to why. I have crash logs so I know it is crashing on 1, 2 and 3.
4. Disconnected the transducers, disabled all transducers and tried 1,2,3 - Same results.
5. Disconnected nmea BUS and tried 1,2,3 - Same results
6. WIFI download update - same as 3.

I have managed to get the systemlog off the unit and had a look through it. The log has the following which doesn't look good. Maybe just a distraction.
Should I post the complete log? It is

10-26 10:24:51.310 748 1069 E ProcessMonitor: Processor Monitor timeout detected
10-26 10:24:51.312 748 1069 E MFDApplication: *----------------------------------------------------------------------------
10-26 10:24:51.312 748 1069 E MFDApplication: * Mutex Information
10-26 10:24:51.312 748 1069 E MFDApplication: *
10-26 10:24:51.312 748 1069 E MFDApplication: * OSSMutexId Name Thread OSSTaskId LWP Lck Cnt Nusers
10-26 10:24:51.312 748 1069 E MFDApplication: * ---------- ----------------------------------- ----------------------------------- ---------- ---------- --- --- ------
10-26 10:24:51.312 748 1069 E MFDApplication: * 0xB7BF5594 TCPSocketServer.cpp:46 LNetNavigationServer.cpp:54 0xB7BF55DC 1309 1 1 0
10-26 10:24:51.313 748 1069 E MFDApplication: * 0xB7BF4C5C TCPSocketServer.cpp:46 LNetTrackServer.cpp:44 0xB7BF4CAC 1307 1 1 0
10-26 10:24:51.313 748 1069 E MFDApplication: * 0xB7BD853C TCPSocketServer.cpp:46 LNetWaypointServer.cpp:51 0xB7BD8590 1305 1 1 0
10-26 10:24:51.313 748 1069 E MFDApplication: * 0xB7BD1264 TCPSocketServer.cpp:46 CLNetDataBaseServer::RxConnectionTask 0xB7BD12C0 1302 1 1 0
10-26 10:24:51.313 748 1069 E MFDApplication: * 0xB7BBC79C TCPSocketServer.cpp:46 LNetDiagnosticsServer.cpp:78 0xB7BBC5D4 1290 1 1 0
10-26 10:24:51.313 748 1069 E MFDApplication: *
10-26 10:24:51.313 748 1069 E MFDApplication: * Possible Deadlocks:-
10-26 10:24:51.313 748 1069 F MFDApplication: Watchdog timeout detected

Tombstone written to: /data/tombstones/tombstone_00

Does anyone have any suggestions? Should I log a ticket with Raymarine?

Cheers,
Ken