Hello, On 20 May 2015 at 10:55, <[email protected]> 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 0x040 0xf0 0x05 b > > i2cread -f -y 4 0x040 0x00 b - OK > i2cread -f -y 4 0x040 0x01 b - error - repeat - OK > i2cread -f -y 4 0x040 0x02 b - error -repeat - OK > i2cread -f -y 4 0x040 0x03 b - error -repeat-eror - stuch with this! :( > > Variant 2: > On the running Android with working touch screen > on the step2 = i2cdump -f -y 4 0x040 -r 0x00-0x7F b > it returns portion of data but on the screen there are many XX bytes (byte > with value XX)- that I do not even know what it is - is it not able to read > or something like forced conversion non displayed hex value to displaying > symbols inside i2cdump during outputing to terminal? > > > So ASSUMING: Is these variants correct? May be it should be done in another > way? Why there are such problems and how to read existing loaded FW? - I > need to dump it all. > For some reason the values are set in 4byte chunks (32bit integers) so maybe try reading integers rather than bytes. Unfortunately, i2cget does not seem to support 32bit values. Thanks Michal -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
