[Pipo-Project] M7Pro kernel

[d33]

1.17

change:

uses VTL CT363 config file -> CT363LR2030D_1920x1200_V25130327FN.dat

[Slowry]

Some tips

The VTL driver try to update the firmware with .dat file each time the kernel boots.
So to make a test "fake" kernel simply comment/disable the update part in driver source (put bincksum = fwcksum in the right place !)
Now you have to flash the stock kernel (to update the vtl firmware) and flash the "fake" kernel et voilà, touchscreen should work as expected (at least you don't have to worry about .dat file !)

2 questions :

1. Why updating VTL firmware at boot time ? firmware could be lost or a kind of protection !?!
2. How to find the good firmware file ? in the binary stock kernel of course !

From the stock max M6 kernel, I have extracted the VTL 32K firmware file with success.
Perhaps I can try with the stock M7pro kernel.

I don't have your source files but I played a little with old JB sources and kernels.

[d33]

The VTL driver try to update the firmware with .dat file each time the kernel boots.
So to make a test "fake" kernel simply comment/disable the update part in driver source (put bincksum = fwcksum in the right place !)
Now you have to flash the stock kernel (to update the vtl firmware) and flash the "fake" kernel et voilà, touchscreen should work as expected (at least you don't have to worry about .dat file !)

2 questions :

1. Why updating VTL firmware at boot time ? firmware could be lost or a kind of protection !?!
2. How to find the good firmware file ? in the binary stock kernel of course !

From the stock max M6 kernel, I have extracted the VTL 32K firmware file with success.
Perhaps I can try with the stock M7pro kernel.

I don't have your source files but I played a little with old JB sources and kernels.

You are a very clever person!

That is definitely the correct solution! How did you extract the dat file? By decompilation? It would be great if you could do that. In the short term I will add a compile time switch to override update of firmware.

[Slowry]

You are a very clever person!

That is definitely the correct solution! How did you extract the dat file? By decompilation? It would be great if you could do that. In the short term I will add a compile time switch to override update of firmware.

Thanks ! I'm an old school dev !

To extract the ct36x firmware I used a more empirical approach than decompilation. Not very easy to explain : I spent lot of time with my hex editor, test and try as usual !

I have build a JB kernel with ct36x driver and a "dummy" dat file just to find it more easily with my hex editor.
Then I compare the result with a good JB kernel (offset change but not the struture).

Don't know if it's reproducible, post a functional M7pro kernel and I will make a second try.

For now I've spent time with JB (buggy sources!) not KK.

[d33]

first attempt to prevent firmware load - 1.18

SteveJC can you load stock kernel then this one?

[rrileypm]

Which one of these kernels to you need me to try on mine?

[rrileypm]

Darrell, I've flashed v1.7 and it works perfectly on mine. Do I need to flash 1.8?

[d33]

Darrell, I've flashed v1.7 and it works perfectly on mine. Do I need to flash 1.8?

No :-) I suspected that I had got a working 'standard' M7Pro kernel, you have confirmed this.

I think our problem is with 'rogue' VTL touchscreens!

I'm close now with M9Pro, just need to get the LCD right.

M8HD (tick)
M6Pro (tick)
M7Pro (tick) - Goodix
U30GT2 (tick)

M9Pro - just need a working LCD
M9 Max - awaiting test

We should do a generic ROM with a pack of all the kernels as a Freaktab release

[rrileypm]

Sounds like a plan.

Let me know if I can help.

[raxy]

Yes, it's a second hand tablet given by a nice Freaktab member

The tablet goes often to Mask Rom !
Then I Need to plug it, and flash loader and boot.img and it's ok !

So it might have been repaired and a vtl touchpad had replaced the goodix randy and me have in our stock hardware tablets.

Good to hear that the quest comes to an end!

[stevejc]

first attempt to prevent firmware load - 1.18

SteveJC can you load stock kernel then this one?

Hi, not booting, nothing on screen, just backlight no logo

[d33]

Hi, not booting, nothing on screen, just backlight no logo

I may have messed up the code adding m6pro support

does this work - 1.19 - same as 18 just with firmware loader switched back on

[stevejc]

I may have messed up the code adding m6pro support

does this work - 1.19 - same as 18 just with firmware loader switched back on

same problem : nothing on screen but the tablet seems working

[d33]

same problem : nothing on screen but the tablet seems working

Can you pull the DMESG?

[stevejc]

Can you pull the DMESG?

finaly after switching screen off, it comes up !

But same problem with touchscreen ; touch zone is smaller as usual
here dmesg :