We've made some good progress - so time again to make another summary :)
1. The Rotator Chip
-------------------
The only issue left right now is that we got some tearing when using
the rotator chip. For those who don't know what that is: When writing
to and reading from the framebuffer is not properly synchronized, the
picture you can see of the LCD is from two different frames (i.e. top
half frame 1, bottom half frame 2). This gives an effect as if the
screen is torn into two halfs when you got videos or games with fast
movement.
To prevent this, you need to synchronize the OMAP5 with the SSD
(rotator chip) so that the framebuffer is not being overwritten while
it's being read.
This is a bit more software work than we thought. There's a special
signal line from the SSD to the OMAP that is being used to synchronize
both devices, but that only works in MIPI Command Mode, whereas we are
running the OMAP5 using MIPI Video Mode. So as a solution, we'd either
need to change the existing driver somehow so that the TE line can be
used in Video Mode as well OR try to use the OMAP5 in Command Mode
instead of Video Mode.
We don't know yet which one of those two will be easier to achieve, but
both of them might be a bit time consuming.
Nevertheless, the hardware itself is working fine, so Nikolaus now
concentrates on the remaining hardware - fixing the software can happen
while we're waiting for the mass production to start (or even
afterwards).
So the display including the rotator works fine, but we currently have
some tearing issues with fast moving content until we improved the
driver.
2. The case
-----------
Basically, the case is finished.
I've printed the last revision and am just waiting for some final
prototype boards to assemble everything - and once I confirm that
everything fits, the real mold is being created. I expect it to be
finished about October.
Of course, as soon as I assemble it, I'll create a video of it!
3. The keyboard
---------------
The keyboard design is basically finished.
The normal keys will be surrounded by a bit of transparent silicone mat
(but will be 0,1mm higher), which will give a nice feeling and also
light up the key surroundings as well as the characters.
The only exception will be the gaming buttons:
Here, the plastic of the buttons will be glued on top of the mat, so
they feel like standard gaming buttons (yes, this has changed within
the last few days).
Mold production here should start within the next week and will take
approximately one month.
The means: Yep, there's no way I can run away from reading the keyboard
layout threads anymore ;)
4. The hardware
---------------
Nikolaus was working on the rotator chip as well, to find out what was
hardware and software related. As you probably can imagine, fixing
hardware later will be hard, but fixing software is possible :)
A week ago, Nikolaus restarted the work on the hardware.
Within this week, he created 106 traces within 15 hours work (so about
7 traces per hour).
410 traces are left to be created - so if he continues in the same
pace, the CPU board will be finished in about 15 days. Could be a bit
faster as well though (some non-critical traces could be made using the
auto-router), but we'll see.
Our goal is to have the full hardware finished within July, so we
actually have real prototypes ready to show at the GamesCom in August.
Yep, if you're visiting there, you might be able to play on a real Pyra
prototype!
Shortly after that preorders will start (unless we find some major
issue with the prototype) - with a lot of videos following.
Well, that's what we're planning anyways - let's hope we can keep that
and it will work out!
Nikolaus also started to work on the e-SATA adaptor which plugs into
our USB port for those who want to connect a SATA device to the Pyra.
Some good progress, I'd say :)
Hopefully back with more good news soon.
As usual, if you want to comment on the post and see a few nice
pictures, follow this link to the boards:
http://boards.openpandora.org/topic/18225-finishing-up-the-hardware/
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.
You can see that one in the blog post on the internet.
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 :)
As usual, if you want to comment on the post or see the picture,
follow this link to the boards:
http://boards.openpandora.org/topic/18156-how-to-get-rotation-working/