MaixPy-v1_scripts icon indicating copy to clipboard operation
MaixPy-v1_scripts copied to clipboard

touchscreen on GO

Open machinehistories opened this issue 5 years ago • 10 comments

When I run the touchscreen sample I just get a blank screen and in the terminal I get lines of 0 0 0 0 0 0 If I use the thumbwheel I get {"w":320, "h":240, "type"="rgb565", "size":153600} 0 0 0. I noticed in the FFT demo there are alternative pins called out. Might this also be the case for the touchscreen. Do you have any other suggestions. thanks

machinehistories avatar May 29 '19 07:05 machinehistories

Specify pins here: https://github.com/sipeed/MaixPy_scripts/blob/639e9dded8139b51f1e2457406462e8cde9e0bdc/hardware/demo_touchscreen.py#L11

if you use go, that should be like this:

2109762902 image

Neutree avatar May 29 '19 07:05 Neutree

Those are the pins I used but unfortunately the touchscreen is unresponsive. I was really excited to use it too. Do you have any other suggestions or is this something I should take up with Seeed where I purchased this product from. - jason

On Wed, May 29, 2019 at 12:48 AM Neucrack [email protected] wrote:

Specify pins here: https://github.com/sipeed/MaixPy_scripts/blob/639e9dded8139b51f1e2457406462e8cde9e0bdc/hardware/demo_touchscreen.py#L11

if you use go, that should be like this:

[image: 2109762902] https://user-images.githubusercontent.com/8625829/58538923-c6601880-8228-11e9-9ef3-7c6c8a7355cf.jpg [image: image] https://user-images.githubusercontent.com/8625829/58538959-e0016000-8228-11e9-9b6e-18d82b4d3fa9.png

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/sipeed/MaixPy_scripts/issues/6?email_source=notifications&email_token=AGMWUVAKG2YBVAW3GW7W6ALPXYYMJA5CNFSM4HQJ233KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWOPICA#issuecomment-496825352, or mute the thread https://github.com/notifications/unsubscribe-auth/AGMWUVG44A7QQ7GLRW37CHLPXYYMJANCNFSM4HQJ233A .

machinehistories avatar May 29 '19 23:05 machinehistories

the touchscreen device is ns2009, communicate with i2c, you can use i2c.scan() to find device:

from machine import I2C
i2c=  I2C(I2C.I2C0, freq=200000, scl=30, sda=31)
devices = i2c.scan()
print(devices)

output:

[38, 72]

if no device found, maybe the hardware broken or connection broken, maybe you have to check the connection by multimeter!

Neutree avatar May 30 '19 01:05 Neutree

When I run

from machine import I2C i2c= I2C(I2C.I2C0, freq=200000, scl=30, sda=31) devices = i2c.scan() print(devices)

I do get output:

[38, 72]

However it continues to only output 0 0 0 no matter how or where I touch it. I checked the continuity from pins 30,31 to the chip and they were ok. I also checked continuity from the lcd connector pins 30, 31 to the mainboard pins and those had continuity. The connection to the lcd board to the ribbon cable looks secure and I have reseated it but it didn't change anything. I think it is something in the touch sensor. Are there any documents for the lcd board and with pinouts for the flat cables and is there anything I should check on the lcd board to see if the sensor is broken. thanks

On Wed, May 29, 2019 at 6:32 PM Neucrack [email protected] wrote:

the touchscreen device is ns2009, communicate with i2c, you can use i2c.scan() to find device:

from machine import I2C i2c= I2C(I2C.I2C0, freq=200000, scl=30, sda=31) devices = i2c.scan() print(devices)

output:

[38, 72]

if no device found, maybe the hardware broken or connection broken, maybe you have to check the connection by multimeter!

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/sipeed/MaixPy_scripts/issues/6?email_source=notifications&email_token=AGMWUVDRYXZJWRPSN766KHTPX4VB5A5CNFSM4HQJ233KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWRCV3A#issuecomment-497167084, or mute the thread https://github.com/notifications/unsubscribe-auth/AGMWUVDGKMRYRXXFP2PJDZLPX4VB5ANCNFSM4HQJ233A .

machinehistories avatar May 31 '19 19:05 machinehistories

http://dl.sipeed.com/MAIX/HDK/Maix-GO/Maix-GO_2.20/Maix_GO_2.20%28Schematic%29.pdf http://dl.sipeed.com/MAIX/HDK/Maix-LCD/Maix_LCD_12.07/Maix_LCD_12.07%28Schematic%29.pdf

https://github.com/sipeed/LicheeDan_K210_examples/tree/master/src/lvgl

try this firmware, download it with kflash_gui: https://github.com/sipeed/LicheeDan_K210_examples/blob/master/src/lvgl/lvgl.bin

Neutree avatar Jun 01 '19 01:06 Neutree

Here is what I discovered. I also tried it using the arduino ide and I get the same result. The i2c address scans, the lcd works, however I get no feedback on the touchscreen. I appreciate your help. Do you suggest I get another screen, should I replace the entire GO kit, or are there other tests you can suggest. lcd

machinehistories avatar Jun 01 '19 04:06 machinehistories

you can replug the lcd module, maybe the connect is not so good.

xelll avatar Jun 20 '19 06:06 xelll

you can use this firmware to test touchscreen. ns2009.bin

xelll avatar Jun 20 '19 06:06 xelll

I appreciate your suggestions. Unfortunately it still doesn't respond to touch. I am going to get a replacement board and I look forward to using it.

On Wed, Jun 19, 2019 at 11:36 PM xel [email protected] wrote:

you can use this firmware to test touchscreen. ns2009.bin https://fdvad021asfd8q.oss-cn-hangzhou.aliyuncs.com/Sipeed_M1/firmware/ns2009.bin

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/sipeed/MaixPy_scripts/issues/6?email_source=notifications&email_token=AGMWUVG6HJIO47XU35S4GZ3P3MQO7A5CNFSM4HQJ233KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYENRLI#issuecomment-503896237, or mute the thread https://github.com/notifications/unsubscribe-auth/AGMWUVFVUZUFCOAIHSSZSSLP3MQO7ANCNFSM4HQJ233A .

machinehistories avatar Jun 21 '19 03:06 machinehistories

ok...

xelll avatar Jun 22 '19 08:06 xelll