Well, first the good news:
notaz got the rotation with the SSD working! We now have a stable, nonshifted and proper picture rotated by the SSD on the LCD.
One issue remains: The LCD has some tearing right now, be we haven't setup the AntiTearing system, so that was to be expected. It'll be the next thing - and then that's it for the LCD part.
In case you were wondering why it took so long:
It was a mixture of hardware and software issues.
As mentioned, the hardware had power issues, so even with the correct software setup, the SSD didn't work - so we poked around with the software for a while, but it could've never worked.
Once Nikolaus fixed the power issues, the SSD started to work with proper timing setups, and then rotation REALLY was easy (compared to the rest).
notaz did all the testing via remote connection on my dev setup.
Many of you have asked how this worked and wanted to see a picture of it - well, here it is, picture and explanation:
As you can clearly see from the background, the setup is standing around in my gaming room
First, let's list the parts we have here:
The device above the Pandora (where the webcam is clipped on) is simply a cheap old DVD player, only there to keep the webcam in place.
The RaspberryPi2 box is just there to keep the LCD in place
Now what's connected with what and why?
The Pandora
The Pandora is setup so notaz can access it externally via SSH and VNC.
The webcam plays back the video stream using mplayer on Pandoras display which can be accessed by notaz via VNC.
The Pandora is also connected to the serial output debug port of the OMAP5 devboard for low-level terminal access (without network). He can also reset the devboard with that in case it crashes.
Another USB cable connects the Pandora to the devboard and features a direct network connection (g_ether). This is simply because using Wifi on the Pandora is not that good for VNC and SSH, so he can also connect to the Pandora from the devboard and cable ethernet.
So: If the Devboard runs, he can connect to the Pandora from there, if the devboard has crashed, he can connect to the Pandora via Wifi and restart the Devboard, debugging it using the serial out connection.
The Devboard
The devboard also is setup so that notaz can access it via SSH.
It has a normal ethernet cable which connects it to the internet, and it also provides internet access to the Pandora using a USB cable (as mentioned above).
The second USB-Cable (MicroUSB) is the debug / serial out port connected to the Pandora.
We have a special adaptor attached which connects the devboard with Pyras Main PCB (so the devboard is a replacement for Pyras CPU PCB right now), and Pyras Display PCB is connected to the Main PCB the same way it will be connected in the final device.
Finally, on the Display PCB, the LCD is connected.
That's a pretty neat setup, isn't it?
It shows how versatile the Pandora is (and the Pyra will be).
Let me know if you have further questions
notaz got the rotation with the SSD working! We now have a stable, nonshifted and proper picture rotated by the SSD on the LCD.
One issue remains: The LCD has some tearing right now, be we haven't setup the AntiTearing system, so that was to be expected. It'll be the next thing - and then that's it for the LCD part.
In case you were wondering why it took so long:
It was a mixture of hardware and software issues.
As mentioned, the hardware had power issues, so even with the correct software setup, the SSD didn't work - so we poked around with the software for a while, but it could've never worked.
Once Nikolaus fixed the power issues, the SSD started to work with proper timing setups, and then rotation REALLY was easy (compared to the rest).
notaz did all the testing via remote connection on my dev setup.
Many of you have asked how this worked and wanted to see a picture of it - well, here it is, picture and explanation:
As you can clearly see from the background, the setup is standing around in my gaming room
First, let's list the parts we have here:
- Pandora
- Webcam
- OMAP5 EVM
- LCD
- Pyra Main PCB
- Pyra Display PCB
The device above the Pandora (where the webcam is clipped on) is simply a cheap old DVD player, only there to keep the webcam in place.
The RaspberryPi2 box is just there to keep the LCD in place
Now what's connected with what and why?
The Pandora
The Pandora is setup so notaz can access it externally via SSH and VNC.
The webcam plays back the video stream using mplayer on Pandoras display which can be accessed by notaz via VNC.
The Pandora is also connected to the serial output debug port of the OMAP5 devboard for low-level terminal access (without network). He can also reset the devboard with that in case it crashes.
Another USB cable connects the Pandora to the devboard and features a direct network connection (g_ether). This is simply because using Wifi on the Pandora is not that good for VNC and SSH, so he can also connect to the Pandora from the devboard and cable ethernet.
So: If the Devboard runs, he can connect to the Pandora from there, if the devboard has crashed, he can connect to the Pandora via Wifi and restart the Devboard, debugging it using the serial out connection.
The Devboard
The devboard also is setup so that notaz can access it via SSH.
It has a normal ethernet cable which connects it to the internet, and it also provides internet access to the Pandora using a USB cable (as mentioned above).
The second USB-Cable (MicroUSB) is the debug / serial out port connected to the Pandora.
We have a special adaptor attached which connects the devboard with Pyras Main PCB (so the devboard is a replacement for Pyras CPU PCB right now), and Pyras Display PCB is connected to the Main PCB the same way it will be connected in the final device.
Finally, on the Display PCB, the LCD is connected.
That's a pretty neat setup, isn't it?
It shows how versatile the Pandora is (and the Pyra will be).
Let me know if you have further questions
