Ok,
So fresh news and summary.
Many many thanks to Sergio Costas for his work and assistance. He wrote and
published FW extractor. I suppose it will be useful for someone trying to
make it works GSL1680.
In my case, Chuwi Vi8 super (baytrail architecture) it looks that chinese
developers put
Ok,
So fresh news and summary.
Many many thanks to Sergio Costas for his work and assistance. He wrote and
published FW extractor. I suppose it will be useful for someone trying to
make it works GSL1680.
In my case, Chuwi Vi8 super (baytrail architecture) it looks that chinese
developers put
Hello,
On 20 May 2015 at 10:55, sergk.ad...@gmail.com wrote:
i2cdump -f -y 4 0x040 -r 0x00-0x7F b
PROBLEMS: Variant1: On the running Android with working touch screen very
often I could NOT read via i2cget data and more over repeating reading makes
NO RESULT. For example
i2cset -f -y 4
I would like to rise up topic into the following direction: Lets try to
dump currently loaded firmware for GSL1680 on Adroid.
From the theory on https://linux-sunxi.org/GSL1680
Chip is located on I2C bus on 0x040 address
Firmware is reading/writing from/into chip via set of chunks, each 128
Since there are no recently any practical replies just report current
status - loosing hope that I could get correct firmware I have just added
rescaling to ported Sergio Costa's userspace driver and it woks pretty good
if not taking into account absence of using INT line from chip.
One more
Thank you for make it clear.
;-) Lets transform this knowledge into practical result!
I have successfully compiled i2c-tools for x86 Android.
So, what is the exact command line to grab all loaded into GSL 1680 chip
firmware?
i2cbus or i2cget? and how to use it , How via this toolset I could
On 19 May 2015 at 11:39, sergk.ad...@gmail.com wrote:
Sorry but your post makes it more weird.
According https://linux-sunxi.org/GSL1680 page GSL1680 controller stores
Firmware in 0x00-0x7F: these registers are used to load portions of the
firmware
This is only 128 8bit = 1byte registers.
On Tuesday, May 19, 2015 at 12:53:43 PM UTC+3, Michal Suchanek wrote:
That's one page of the configuration which is 128 bytes or 32 integers.
Writing the page register gives access (read or write) to different pages.
So one blob might have multiple such pages or the firmware can be
composed of
On 19 May 2015 at 12:36, sergk.ad...@gmail.com wrote:
On Tuesday, May 19, 2015 at 12:53:43 PM UTC+3, Michal Suchanek wrote:
That's one page of the configuration which is 128 bytes or 32 integers.
Writing the page register gives access (read or write) to different pages.
So one blob might have
Hi,
You can do it with readelf and dd, it's not straight forward, you need to
find the symbol offset(table offset + symbol ofset) and size in the file
then you dump it with dd.
I made a graphical tool to make this easier:
https://hephaistos.lpp.polytechnique.fr/redmine/projects/execut/wiki
You
Could you please explain more detailed this portion by reading registers 00
to 7F for each 128-byte block.
Questions:
1) Does it enough only one 128-byte block?
2) How to determine how much such 128byte blocks should be read and where
is the finish?
On Monday, May 18, 2015 at 11:52:13 AM
On 18 May 2015 at 11:15, sergk.ad...@gmail.com wrote:
To ALL:
Could anyone share binary static linked i2c tools for Baytrail x86 (i386)
Android? If I understand right simply PC-i386/i686 i2c-tool package will not
work?
You can try but most likely you will have to rebuild i2c tools
Check if you have the i2c tools in your android system, and try to use them to
dump the firmware from the running chip. You should be able to do it by reading
registers 00 to 7F for each 128-byte block, and writting in register 0xF0 the
page you want to read.
--
You received this message
Thanks,
Am I understand right - all I need - it is just open .ko file, jumb to
symbols page and choose needed variable (4ex:
GSLX680_FW_I81_GSL3676B_8001280_OGS_SG) and choose export to binary and
as result I will get my firmware?
In that case = declarations exists in .rodata and .data.
I would read all the 256 pages, and dump all them to my chip.
On 18/05/15 11:00, sergk.ad...@gmail.com wrote:
Could you please explain more detailed this portion by reading
registers 00 to 7F for each 128-byte block.
Questions:
1) Does it enough only one 128-byte block?
2) How to determine
To ALL:
Could anyone share binary static linked i2c tools for Baytrail x86 (i386)
Android? If I understand right simply PC-i386/i686 i2c-tool package will
not work?
On Monday, May 18, 2015 at 11:52:13 AM UTC+3, raste...@gmail.com wrote:
Check if you have the i2c tools in your android system,
16 matches
Mail list logo
