NAND Testing - 05-25 Update: New LK, Recovery.img, Kernel Updates through Recovery

[[ACL]]

Originally Posted by mpannen

Hi:

I ran this command:

pdump 0x00081034 1 b

and it came back with a result of 00000014


And for those of you not at a computer, you can turn on the haret console and connect to it using Putty for Windows Mobile. Just telnet to 127.0.0.1 port 9999, and press enter once connected. You will then see the console.

This means you have the same panel i do. So i'm baffled why you were getting display errors before. I'll look into it tho so next release should detect properly. I'm waiting to see if anyone has anything besides 0x14

[natemcnutty]

Originally Posted by [ACL]

This means you have the same panel i do. So i'm baffled why you were getting display errors before. I'll look into it tho so next release should detect properly. I'm waiting to see if anyone has anything besides 0x14

Unfortunately, I also have 0x14 on that paddress. Did you disassemble a wince driver for that address?

HaRET(12)# pdump 0x00081034 128
00081034 | 00000014 efffffff fff7ffdf ffffbfff | ................
00081044 | fffefffb fffffdff ffffffff fffdffff | ................
00081054 | ffffff7f 00000000 52455354 55aaaa55 | ........TSERU..U
00081064 | 58899885 00480052 0044004f 00300035 | ...XR.H.O.D.5.0.
00081074 | 00300030 00000030 ffffffff ffffffff | 0.0.0...........
00081084 | ffffffff 5349424b 52454749 ffffffff | ....KBISIGER....
00081094 | ffffffff 3fffff00 fdfffffd ffffbfff | .......?........
000810a4 | 00000000 4e534543 00001000 00000080 | ....CESN........

[[ACL]]

Originally Posted by natemcnutty

Unfortunately, I also have 0x14 on that paddress. Did you disassemble a wince driver for that address?

HaRET(12)# pdump 0x00081034 128
00081034 | 00000014 efffffff fff7ffdf ffffbfff | ................
00081044 | fffefffb fffffdff ffffffff fffdffff | ................
00081054 | ffffff7f 00000000 52455354 55aaaa55 | ........TSERU..U
00081064 | 58899885 00480052 0044004f 00300035 | ...XR.H.O.D.5.0.
00081074 | 00300030 00000030 ffffffff ffffffff | 0.0.0...........
00081084 | ffffffff 5349424b 52454749 ffffffff | ....KBISIGER....
00081094 | ffffffff 3fffff00 fdfffffd ffffbfff | .......?........
000810a4 | 00000000 4e534543 00001000 00000080 | ....CESN........

Had Cotulla take a look at the dlls and he got the address. We verified because it matches the wince kernel log.

If you dump the kernel log from wince during boot you will see g_currentpaneltype=20. So we know 0x14 is what most of us use.

[mpannen]

Could different radio firmwares have any influence? I have a Verizon 2.37 on my device..What do you have on yours ACL?

[[ACL]]

Originally Posted by mpannen

Could different radio firmwares have any influence? I have a Verizon 2.37 on my device..What do you have on yours ACL?

No idea.. i have sprint 400. But panel init shouldn't change at all with radio changes.

[natemcnutty]

Wirelessly posted (Opera/9.80 (Windows Mobile; Opera Mini/5.1.21594/22.414; U; en) Presto/2.5.25 Version/10.54)

Originally Posted by [ACL

]

Had Cotulla take a look at the dlls and he got the address. We verified because it matches the wince kernel log.

If you dump the kernel log from wince during boot you will see g_currentpaneltype=20. So we know 0x14 is what most of us use.

ACL, do you need any other info at this point? I was messing around with addlist TRACE for headset detection and wondered if you had everything you needed for panel stuff.

[[ACL]]

Originally Posted by natemcnutty

Wirelessly posted (Opera/9.80 (Windows Mobile; Opera Mini/5.1.21594/22.414; U; en) Presto/2.5.25 Version/10.54)



ACL, do you need any other info at this point? I was messing around with addlist TRACE for headset detection and wondered if you had everything you needed for panel stuff.

i think im all good for now. Just baffled we all have reported using the same panel. What i will do is mod the code to just write an error to the logs in-case it finds a panel besides 0x14.

how is the headset thing going?

[natemcnutty]

Wirelessly posted (Opera/9.80 (Windows Mobile; Opera Mini/5.1.21594/22.414; U; en) Presto/2.5.25 Version/10.54)

Originally Posted by [ACL

]

i think im all good for now. Just baffled we all have reported using the same panel. What i will do is mod the code to just write an error to the logs in-case it finds a panel besides 0x14.

how is the headset thing going?

Had to head out for shopping, but I'm really just documenting what I can. I'll post my findings for you or someone who can do real programming

[mpannen]

ACL:

You are not going to believe this, but I flashed back to Sprint radio 2.32 from VZW 2.37 and the display is working for me now. I am using the autobuild from 12/15/2010, which had previously failed for me.

[mpannen]

Well it worked very well for a while, but now the back light just comes on again....