herrmannc1899 Show full post »
Jon_B
NolanM for the win.  I just connected it up and it works with these code changes:

// Hardware pin-number labels
#define SCK_PIN 18
#define DIN_PIN 19
#define DOUT_PIN 23
#define CS_PIN 5
#define DR_PIN 4

#define SDA_PIN 18 // not used
#define SCL_PIN 19 // not used

#define LED_0 2
#define LED_1 27 // not used


With that I get:

Clipboard01.jpg 
The data streams to the terminal window just fine.
Quote
herrmannc1899
Hello!

Sorry, I have been quite busy with class work and etc. 


NolanM wrote:
Are you sure you have the right PinOut for your board?


 
I am aware that the image is not the pin out for my board. I was simply using it to illustrate and confirm the default SPI pinouts of the ESP32 module XD. 

Once I get the chance I will give it one last shot before I order a new board. Both boards use the ESP32-WROOM module so I was thinking that there really couldn't have been much difference; I didn't see much of a point in paying 10 extra dollars for features that I didn't need on the Adafruit Huzzah.

Regardless, I will give it a shot once more with my cheapo dev board and if that doesn't work then I will treat myself to a ESP32 Huzzah board. If the Huzzah board doesn't work, then I think maybe it will have to do with the fact that I had to compile the xtensa toolchain for ARM on the raspberry pi, but I doubt that is this case.

Regardless, I will make sure to update everyone as soon as I try it!
Quote
herrmannc1899
Jon_B wrote:
NolanM for the win.  I just connected it up and it works with these code 
The data streams to the terminal window just fine.



Awesome! I will make sure to let everyone know when I test it. I should have some time tomorrow to give it a whirl. I have been using those exact pinouts to no avail so I will give it one more shop before treating myself to Huzzah off of Prime. Although they the ESP32 modules are identical who knows what could have gone wrong in the cheap chinese version.

I will keep you all updated. Thanks again for this incredible dedication!
Quote
herrmannc1899
Well that didn't work 🙁 .

As soon as I powered it on the Assert LED simply stayed lit and there was no touch data printed to the terminal.



I am thinking that it has to be a hardware issue at this point then.

I will buy a Huzzah board and will try it once more in a few days once it gets here.

If that doesn't work then as one last final resort I will buy yet another TM0023023 XD. Maybe I shorted this one out by mistake.
Quote
Jon_B
Ahh, I forgot to mention: the LED is reversed (it is ON when there is no touch and OFF when there is a touch).  The LED must be tied to the opposite rail from what the demo code expected.

Also, those modules usually survive being connected up wrong.

You could try hacking the code a bit to send some SPI data. Then probe the lines to make sure they are connected correctly.
Quote
herrmannc1899
Well, 

A week later and I have my ESP32 Feather, and surprise surprise, it didn't work.

It still simply prints out the header with X, Y, Z, and then hangs up, even using the recommended pin out.

I double checked all of my connections and tested the continuity between each pin on the Huzzah and each test point on the TM023023 and everything checked out. Nonetheless I still whipped up a quick breakout board designed specifically for the ESP32 Feather and the touchpads, so I will post that when they arrive in a week or so.

So with that being said that ONLY thing that I can think that might be causing me issues is that I am doing all of this on a Raspberry Pi.

I did not want to compile the toolchain myself because it takes so long apparently, so I used one that someone else has compiled: here

I am hoping to the almighty technology gods that because this version of the tool chain is almost a year old now it might not have SPI working correctly for whatever reason. The next and final step now is to find a different computer to step up on and then see how it goes.

If EVEN THAT doesn't work....well, I guess I will just have to drink away my sorrows....
Quote
NolanM
How are you interfacing from the ESP to the touchpad? I have been using the ribbon cables to the Dev Kit board (https://www.cirque.com/circle-trackpad-dev-kit) From the dev board I have been remapping based on whatever micro I'm using (Adafruit 32u4 Bluefruit Feather and Teensy 3.2) Your statement ...  


I double checked all of my connections and tested the continuity between each pin on the Huzzah and each test point on the TM023023 and everything checked out. Nonetheless I still whipped up a quick breakout board designed specifically for the ESP32 Feather and the touchpads, so I will post that when they arrive in a week or so.


... makes me think that the interface between the ESP and the chip is where your problem lies, especially because you are getting the header data and nothing else. Could you post a picture of your setup and maybe a schematic-ish diagram of how you are connecting the touchpad to your controller?

Also, what version of Arduino are you using from your Rasberry Pi?  I can see if matching the same version I get the same issue. 

Hopefully soon we will be drinking to your success!
Quote
herrmannc1899

Guys. Guys. It WORKED.

and of course I knew that it was going to be something stupid. 
Basically the bodged together breakout board that I was using mas missing a connection. Here is a shitty picture of.
IMG_20180928_230223.jpg 


It's hard to see but it's the interface between that little tiny pin nub and that glob of solder on the second green wire. I had basically been checking the continuity between the wrong two point so this little problem went undiscovered.


So I am getting the ESP32 to talk to the trackpad now which is great news. The issue now is that it is giving somewhat garbage data. Sometimes half of the trackpad does not work and other times when it does work it doesn't seem to give consistent data.

I will post some screenshots of the data when I get the chance.

I have also received the breakout boards that I designed so I will post pictures of that too.

Quote