Hi!
1.) I wasn’t meaning the turning was related to Waveshare32 solution, or the solution to getting Waveshare35A Touch working. The turning I was referring to is that the 40-pin connector, facing down onto the RPi, expects 3.3V on the left (Pin 1) and 5V on the right (Pin 2). The Waveshare35A also expects this as it is a Hat.
The official ribbon cable for the kit V2 26-pin connector has 5V on the LEFT (where the Waveshare35A expects 3.3V, Pin 1, etc) and 3.3V on the RIGHT (also is not Male of course). Maybe would help others later if they happened to try this v2 cable with a Waveshare or other Hat display. Someone tell me if I’m crazy?
2.) I know you have recommended this before, but I don’t understand how I can apply the Waveshare32 wiring while using the newer Kit v2 All-In-One board.
Are you referring to this:
And also choosing PROTOTYPE-4-WS32 in the webconf? I couldn’t find what you meant by a line I should remove you mentioned earlier.
Can I accomplish this while using the Kit v2 All-In-One board?
Do I need to make a new ribbon cable with a 40-pin Male connector / custom wiring?
Or,
Would I need to re-organize the connections between the AudioInjector 40-pin and the All-In-One 40-pin?
Perhaps using the AudioInjector instead of the HiFiBerry is making this overly complicated as well?
If this is too much, and something I just need to figure out on my own, I understand. Maybe I should work on my own pin map also?
If this could help someone else later, maybe it would be worth it. But of course now I wish I had bought an already supported display - I’m learning! Maybe there are some simple basics about how Zynthian works that I don’t understand yet (such as how to arrive at the values for the zyncoder_pin lines, guessing it’s all in the wiki.)
Anyways, I don’t know if I’m actually contributing or just clogging up the forum, sorry! I’ve spent over two hours on this post and a lot more trying to get this display to work normally, maybe just not worth the time now.