<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>&amp;#39;cst816s: failed reading chip id&amp;#39; with Waveshare 1.69&amp;quot; Touch LCD</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/112255/cst816s-failed-reading-chip-id-with-waveshare-1-69-touch-lcd</link><description>I am getting an error message when trying to use a nRF5340 DK with a Waveshare 1.69inch Touch LCD Module on the Zephyr sample code with minimal modifications. When I flash/reset I get: 
 
 
 and when I touch the screen I get: 
 
 
 
 The pin settings</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 28 Jun 2024 11:11:01 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/112255/cst816s-failed-reading-chip-id-with-waveshare-1-69-touch-lcd" /><item><title>RE: 'cst816s: failed reading chip id' with Waveshare 1.69" Touch LCD</title><link>https://devzone.nordicsemi.com/thread/491294?ContentTypeID=1</link><pubDate>Fri, 28 Jun 2024 11:11:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:648d4fa9-7395-4aae-b09f-624e9ae88300</guid><dc:creator>lcj</dc:creator><description>&lt;p&gt;I had pins backwards!!!!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: 'cst816s: failed reading chip id' with Waveshare 1.69" Touch LCD</title><link>https://devzone.nordicsemi.com/thread/491191?ContentTypeID=1</link><pubDate>Thu, 27 Jun 2024 23:00:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7a47de13-c3a2-4443-a968-c0f8f302401d</guid><dc:creator>lcj</dc:creator><description>&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1719533916428v1.png" /&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1719534185965v1.png" /&gt;&lt;/p&gt;
&lt;p&gt;No idea what this means. Tried changing around the pins. They seem to be off.&lt;/p&gt;
&lt;p&gt;I moved the SCL wire from what I thought was for to what I thought was 5 and this is what it looked like:&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1719535395580v1.png" /&gt;&lt;/p&gt;
&lt;p&gt;So, I guess SCL was 4 in this last one and SDA was 5.&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1719540235750v1.png" alt=" " /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: 'cst816s: failed reading chip id' with Waveshare 1.69" Touch LCD</title><link>https://devzone.nordicsemi.com/thread/491087?ContentTypeID=1</link><pubDate>Thu, 27 Jun 2024 11:42:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:03da204c-0a83-4195-870c-67d944733d72</guid><dc:creator>lcj</dc:creator><description>&lt;p&gt;&lt;span&gt;All the demo source files for other platforms (Arduino, ESP32, Pico, Raspberry Pi, and STM32.) are here&amp;nbsp;&lt;/span&gt;&lt;a id="" href="https://files.waveshare.com/wiki/1.69inch-Touch-LCD-Module/1.69inch_Touch_LCD_Demo.zip" rel="nofollow"&gt;https://files.waveshare.com/wiki/1.69inch-Touch-LCD-Module/1.69inch_Touch_LCD_Demo.zip&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: 'cst816s: failed reading chip id' with Waveshare 1.69" Touch LCD</title><link>https://devzone.nordicsemi.com/thread/490288?ContentTypeID=1</link><pubDate>Mon, 24 Jun 2024 12:33:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:67f10e19-1cdb-4ac0-b1c7-f099f78738f8</guid><dc:creator>Sigurd Hellesvik</dc:creator><description>&lt;p&gt;Yes SCL and SDA.&lt;/p&gt;
[quote user="jakkra"]No, this means the interrupt pin is working and the touch chip, but not your i2c communication.&amp;nbsp;[/quote]
&lt;p&gt;Agreed, well reasoned&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: 'cst816s: failed reading chip id' with Waveshare 1.69" Touch LCD</title><link>https://devzone.nordicsemi.com/thread/490078?ContentTypeID=1</link><pubDate>Sat, 22 Jun 2024 10:49:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6d23aa2b-418e-4e38-ad69-66c08d878ada</guid><dc:creator>lcj</dc:creator><description>&lt;p&gt;Is there another way to debug this besides the oscilloscope? Out of curiosity, which lines would I probe? Are they the SCL/SDA?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: 'cst816s: failed reading chip id' with Waveshare 1.69" Touch LCD</title><link>https://devzone.nordicsemi.com/thread/490073?ContentTypeID=1</link><pubDate>Sat, 22 Jun 2024 08:59:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2c90fca0-e22d-4b23-80a8-75f6dca4690d</guid><dc:creator>jakkra</dc:creator><description>&lt;p&gt;No, this means the interrupt pin is working and the touch chip, but not your i2c communication.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: 'cst816s: failed reading chip id' with Waveshare 1.69" Touch LCD</title><link>https://devzone.nordicsemi.com/thread/489986?ContentTypeID=1</link><pubDate>Fri, 21 Jun 2024 13:30:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:11cd634e-5eab-4ead-80fc-ab3ef07ebb60</guid><dc:creator>lcj</dc:creator><description>&lt;p&gt;I&amp;#39;ve never done that before. I might be able to try it, but I do get this error:&lt;br /&gt;&lt;pre class="ui-code" data-mode="text"&gt;[00:37:04.562,744] &amp;lt;err&amp;gt; cst816s: Could not read x data&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;When I touch the screen so I would assume the lines are working, right?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: 'cst816s: failed reading chip id' with Waveshare 1.69" Touch LCD</title><link>https://devzone.nordicsemi.com/thread/489979?ContentTypeID=1</link><pubDate>Fri, 21 Jun 2024 13:15:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0de264c0-3821-4532-8900-ec7df90b8284</guid><dc:creator>Sigurd Hellesvik</dc:creator><description>&lt;p&gt;Something seems off with the I2C.&lt;br /&gt;Can you probe your I2C lines with a logic analyzer or oscilloscope and see if there is any activity?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: 'cst816s: failed reading chip id' with Waveshare 1.69" Touch LCD</title><link>https://devzone.nordicsemi.com/thread/489970?ContentTypeID=1</link><pubDate>Fri, 21 Jun 2024 12:53:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9f1c6452-8184-477a-a8a1-0e0a6eedf602</guid><dc:creator>lcj</dc:creator><description>&lt;p&gt;&lt;br /&gt;&lt;pre class="ui-code" data-mode="text"&gt;[00:00:00.441,375] &amp;lt;dbg&amp;gt; display_st7789v: st7789v_reset_display: Resetting display
[00:00:01.145,263] &amp;lt;err&amp;gt; cst816s: failed reading chip id
*** Booting nRF Connect SDK v3.5.99-ncs1-1 ***
[00:00:01.149,597] &amp;lt;inf&amp;gt; app: Starting...
[00:00:01.159,210] &amp;lt;dbg&amp;gt; display_st7789v: st7789v_write: Writing 240x28 (w,h) @ 0x0 (x,y)
[00:00:01.166,717] &amp;lt;dbg&amp;gt; display_st7789v: st7789v_write: Writing 240x28 (w,h) @ 0x28 (x,y)
[00:00:01.174,224] &amp;lt;dbg&amp;gt; display_st7789v: st7789v_write: Writing 240x28 (w,h) @ 0x56 (x,y)
[00:00:01.181,732] &amp;lt;dbg&amp;gt; display_st7789v: st7789v_write: Writing 240x28 (w,h) @ 0x84 (x,y)
[00:00:01.192,291] &amp;lt;dbg&amp;gt; display_st7789v: st7789v_write: Writing 240x28 (w,h) @ 0x112 (x,y)
[00:00:01.203,063] &amp;lt;dbg&amp;gt; display_st7789v: st7789v_write: Writing 240x28 (w,h) @ 0x140 (x,y)
[00:00:01.210,571] &amp;lt;dbg&amp;gt; display_st7789v: st7789v_write: Writing 240x28 (w,h) @ 0x168 (x,y)
[00:00:01.218,139] &amp;lt;dbg&amp;gt; display_st7789v: st7789v_write: Writing 240x28 (w,h) @ 0x196 (x,y)
[00:00:01.225,708] &amp;lt;dbg&amp;gt; display_st7789v: st7789v_write: Writing 240x28 (w,h) @ 0x224 (x,y)
[00:00:01.234,344] &amp;lt;dbg&amp;gt; display_st7789v: st7789v_write: Writing 240x28 (w,h) @ 0x252 (x,y)
[00:00:01.243,804] &amp;lt;dbg&amp;gt; display_st7789v: st7789v_write: Writing 53x27 (w,h) @ 94x253 (x,y)
[00:00:02.257,110] &amp;lt;dbg&amp;gt; display_st7789v: st7789v_write: Writing 29x27 (w,h) @ 106x253 (x,y)
[00:00:03.269,714] &amp;lt;dbg&amp;gt; display_st7789v: st7789v_write: Writing 28x27 (w,h) @ 107x253 (x,y)
[00:00:04.281,463] &amp;lt;dbg&amp;gt; display_st7789v: st7789v_write: Writing 27x27 (w,h) @ 107x253 (x,y)
[00:00:05.294,006] &amp;lt;dbg&amp;gt; display_st7789v: st7789v_write: Writing 30x27 (w,h) @ 106x253 (x,y)
[00:00:06.306,610] &amp;lt;dbg&amp;gt; display_st7789v: st7789v_write: Writing 29x27 (w,h) @ 106x253 (x,y)
[00:00:07.319,244] &amp;lt;dbg&amp;gt; display_st7789v: st7789v_write: Writing 29x27 (w,h) @ 106x253 (x,y)
[00:00:08.330,902] &amp;lt;dbg&amp;gt; display_st7789v: st7789v_write: Writing 28x27 (w,h) @ 106x253 (x,y)
[00:00:09.342,651] &amp;lt;dbg&amp;gt; display_st7789v: st7789v_write: Writing 28x27 (w,h) @ 106x253 (x,y)&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: 'cst816s: failed reading chip id' with Waveshare 1.69" Touch LCD</title><link>https://devzone.nordicsemi.com/thread/489962?ContentTypeID=1</link><pubDate>Fri, 21 Jun 2024 12:30:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6273b121-9379-4436-b121-6d6e9d022c9c</guid><dc:creator>Sigurd Hellesvik</dc:creator><description>&lt;p&gt;Try to increase CONFIG_DISPLAY_LOG_LEVEL and see if you get any logs from the display init driver.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: '</title><link>https://devzone.nordicsemi.com/thread/489799?ContentTypeID=1</link><pubDate>Thu, 20 Jun 2024 15:06:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7b571f4a-9cce-4490-8240-fe26ab6a9959</guid><dc:creator>lcj</dc:creator><description>&lt;p&gt;&lt;code&gt;&lt;span&gt; LOG_INF(&amp;quot;lv_btn_click_callback called&amp;quot;);&lt;/span&gt;&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;and&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;&lt;span&gt;CONFIG_LV_Z_POINTER_INPUT=y&lt;/span&gt;&lt;/code&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: '</title><link>https://devzone.nordicsemi.com/thread/489754?ContentTypeID=1</link><pubDate>Thu, 20 Jun 2024 12:58:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5fff980d-cabd-40dc-8245-39b20a5ac21c</guid><dc:creator>Sigurd Hellesvik</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
[quote user=""]with minimal modifications:[/quote]
&lt;p&gt;Could you explain which modifications?&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Sigurd Hellesvik&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>