No problem, thanks for taking the effort to help.
What can I expect to be the costs of the repair? And is it worth it?
What can I expect to be the costs of the repair? And is it worth it?
Etiquette, expectations, entitlement...
@autoexec_bin | #magiclantern | Discord | Reddit | Server issues
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: a1ex on June 01, 2015, 03:58:36 PM
I'm afraid the display circuit might be in trouble. The backlight turns on (it's just a LED), but either the LCD itself or the display driver appears to be faulty.
However, this appears not to be the only problem. Relevant lines from the log:
118: 115.603 [PROPAD] ERROR GetPropertyData ID = 0x010100A5
119: 115.684 [PROPAD] ERROR GetPropertyData ID = 0x010100A6
1511: 54243.424 [CAPD] ERROR Image Power Failure
1539: 54248.702 [STARTUP] startupErrorRequestChangeCBR (0x82218001)
1540: 54248.778 [STARTUP] startupErrorRequestChangeCBR : ErrorSend (120, SHUTDOWN)
1580: 54329.894 [SHTC] ERROR ERROR scsEventDispatch Current=8,dwEventID=12,dwParam=0x0
I can try to investigate those errors in QEMU, but I'm not confident I'll find anything useful.
What's strange is that I couldn't find property 0x010100A5/A6 in my 5D2 ROM and property logs (I could only find A2,A3 and A4).
I'd like two sets of ROM dumps (send them to me by PM):
- a ROM dump before the error appeared (you should be able to find one under ML/LOGS if you didn't format the card yet, or maybe on some older cards; no big deal if you no longer have it, but if you have it, it's nice to have)
- a ROM dump after the error (it should appear under ML/LOGS when you boot from a fresh ML card), so I can try to run it under QEMU.
Quote from: a1ex on May 30, 2015, 09:59:55 PM
What was the exact result?
Page created in 0.067 seconds with 13 queries.