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

[[ACL]]

Originally Posted by pts69666

Ok, RHOD400 here. I seem to be having a little problem. Flashing the NBH file goes perfectly according to plan, however when I boot up the device (after already having the modules, system.ext2, rootfs.img, rhod400.kb, and gralloc.msm7k.so files in my andboot folder) It starts to load, the text scrolls, I get the two vibrates and then the screen goes blank. I know that the device is still on, because it doesn't reboot when I hit the power button. It does nothing. I would just wait for it to finish booting and then just power on, however the screen calibration is supposed to happen at some point during the initial boot. The screen doesn't come back to allow me to do that.

Any Ideas?

EDIT:

ok, i decided to let it sit for a while and then i hit the power key and it randomly turned on. However it appeared to be frozen it said
mdp irq already on 4 4
ndp_dma: busy

and if i hit enter those two lines just keep repeating

Yep.. this happens to me as well. Our code calls the panel resume during boot and once it does that the panel simply goes blank. Its not till android takes over till it seems to come back to life.

Ignore the mdp irp .. those will eventually be commented out. They arent related to the panel .. hopefully next patch i will make sure the panel is always on

[pts69666]

Originally Posted by [ACL]

Yep.. this happens to me as well. Our code calls the panel resume during boot and once it does that the panel simply goes blank. Its not till android takes over till it seems to come back to life.

Ignore the mdp irp .. those will eventually be commented out. They arent related to the panel .. hopefully next patch i will make sure the panel is always on

How long should the initial boot take? For me, the screen doesn't come back on until I hit the power button, and it doesn't let me do that for a good 15 minuets or so. From there, it just sits and doesn't do anything...

I'll let it sit longer, to see what happens.

[[ACL]]

Originally Posted by pts69666

How long should the initial boot take? For me, the screen doesn't come back on until I hit the power button, and it doesn't let me do that for a good 15 minuets or so. From there, it just sits and doesn't do anything...

I'll let it sit longer, to see what happens.

It may be that you have a slightly diff panel.. i'm gathering all the panel info now so hopefuly the next update has that worked out.

[pts69666]

Originally Posted by [ACL]

It may be that you have a slightly diff panel.. i'm gathering all the panel info now so hopefuly the next update has that worked out.

Is there something I can do to see if my panel is different. I saw something about haret dumps. How hard is that to figure out. xD

[[ACL]]

more haret dumping needed.

ok so take a look at this table

Topaz LCDModule - Htc-linux

Like i said there are alot of panels for the rhod and topaz. Unfortunately i dont know how to tell what panel is what yet so i may need to ask Markinus who did this whole part for the topaz.

In the mean time i have another init seq for the guys who provided the haret dumps.

This struct needs to be changed

struct nov_regs nov_init_seq[] = {
/* EID es3 */
{0x5100, 0x00},
{0x1100, 0x01},
{REG_WAIT, 0x64},
{0x4e00, 0x00},
{0x180, 0x02},
{0x880, 0x00},
{0x2080, 0x33},
{0x2680, 0x78},
{0x2880, 0x3e},
{0x2980, 0x04},
{0x2c80, 0x22},
{0x2e80, 0x00},
{0xde80, 0x02},
{0x3a00, 0x55},
{0x3500, 0x00},
{0x4400, 0x00},
{0x4401, 0x00},
{0x5e00, 0x00},
{0x6a01, 0x00},
{0x6a02, 0x01},
{0x5301, 0x10},
{0x5500, 0x02},
{0x6a17, 0x01},
{0x6a18, 0xff},
{0x2900, 0x01},
{0x5300, 0x2c},
{0x5303, 0x01},
}

i'm going to try it on the rhod 400.. it may work for me so we can use this instead in the mean time until we figure out how to detect the panel