Resurrecting a Psion Series 5 PDA with modern innards

Similar projects worth following
Bringing a Psion Series 5 into this decade by replacing all the important bits.

The completed result will (hopefully) be a portable modern Linux system with all the connectivity options expected in a modern device.

The idea is to make a modern handheld computer fit into the classic Psion Series 5 enclosure. Being a really well-engineered piece of hardware to begin with, this is a real challenge! We'll see where it'll end up :)

PCB Original Outline.dxf

Outline drawing of the original PCB

AutoCAD DXF - 16.61 kB - 04/06/2019 at 11:22


  • 1 × Psion Series 5, Series 5mx or Ericsson MC218

  • Tindie Stock Clearance

    RasmusB12/14/2017 at 09:44 2 comments

    I'm moving and need to clear out my stock a bit.

    33% off on my keyboard adapter!

  • The future is here

    RasmusB12/04/2017 at 08:48 2 comments

    I really hope this makes it to market! This will of course be a much more polished product than I could ever hope to produce in my home lab. While I don't think this will lead to a renaissance of the palmtop computer, I'll definitely be getting one if they become available.

  • Black Friday and Cyber Monday sale

    RasmusB11/22/2017 at 09:51 1 comment

    If you have been holding off getting one of my keyboard adapters, now is your chance!

    There will be a sale starting the night before black friday, all through cyber monday. Keep an eye on my Tindie product page:

  • Keyboard adapter production - lessons learned

    RasmusB10/09/2017 at 05:17 1 comment

    This project has had a side effect I did not expect when I started this project - I actually started selling hardware on Tindie! While I really appreciate that other people around the world are genuinely interested in what I am doing, I realized that it does not make sense to spend my time doing small batch production in my home office.

    First of all, I seriously underestimated how much time it would take to build the adapters. I had built several similar designs by hand before, and I thought that I had a good process going. Basically, I just stencil printed the solder paste and placed all the components with tweezers. Also, I expected to be able to pick up the pace when building several boards at once. But I have to admit that I find it exhausting to place 0402 components by hand. One or two boards are fine, but after that my speed starts to drop seriously. In practice, the time spent on each board did not get any shorter when building 10 boards compared to building a single board at a time.

    Secondly, the yield was terrible. For my last batch, less then half of the boards I built worked correctly right after soldering! I had two main issues:

    1. Handling errors - the PCB panels I designed did not have sufficient handling clearance and I ended up accidentally shifting components and smearing solder paste on my boards. I should have added a handling frame to avoid this.
    2. Solder bridges - I did expect to see some solder bridges on the QFN package or the fine-pitch FFC connector, but that actually hasn't happened. But I did get short circuits below some 0402 components. This proved to be extremely time consuming to fix, especially since it mostly happened on the decoupling caps. I could not see the issue under my microscope, so I had to resort to desolder one component at a time, checking if the short disappeared, and then replacing the removed parts. Rinse and repeat. I'm not sure whythis happened. The amount of solder paste present was good, but I suspect that I accidentally spread / squished the solder paste when placing the components and trying to align them.

    I had to find a better solution. I looked into modifying the design to add electrical testing to help me troubleshoot bad boards, but I realized that was just a time consuming way of treating the symptoms instead of actually fixing the disease. Also, it would be an entire project in its own right to create a reliable test setup. I looked into building some kind of rig to help with component placing (kind of a manual pick and place machine), but that would also become its own project.

    Instead, I started looking into having the boards built for me. This was the easiest way forward, since I already had everything that was needed - a proved working layout and a BOM. I sent those to iTead, Seeed Studio and Elecrow for quotes. Elecrow came out on top of this comparison, since they had by far the lowest setup cost - in practice just a $20 component sourcing fee.

    When I started selling the adapters, I made a spreadsheet listing all the production costs for the hardware. When I updated the spreadsheet using the quote from Elecrow, I was surprised to see that my cost didn't increase. This is partly due to me being able to order a larger batch of PCBs and components, but also that Elecrow did a good job of picking components. Included in their quote, I got a list of requested vs. quoted components. The only part I was concerned about was the FFC connector, but they quickly provided the datasheet when I asked, and I could confirm that it would indeed work for me. I could also have requested that they used the exact component specified in my BOM if necessary, increasing the cost slightly.

    So where are we now? I just got a picture sent to me of the finished boards, to verify that they look as expected before shipping.

    I am a little amused by the "QC Pass" sticker - I have not provided any information on how to test the boards, so at best they have checked for misaligned and/or rotated components....

    Read more »

  • New keyboard adapters incoming

    RasmusB05/03/2017 at 22:02 0 comments

    If you are on the list to get a keyboard adapter, you'll soon have your chance again!

    The first batch had an issue with the alignment of the stencil, so I ordered new panels and stencils.

    This time the alignment was good, so I'll add some adapters to stock soon.

  • 3D scanning with a camera, part 1

    RasmusB05/02/2017 at 21:06 1 comment

    This time I'm back with an actual update!

    Since space is tight inside the Psion housing, I wanted to create 3D models of the plastic parts. This proved more difficult than I expected since I couldn't easily access all areas of the parts with my calipers. So what to do?

    I had tried photogrammetry a bit before. The idea is to take a lot of pictures of the object from as many different angles as possible, and then let a computer calculate the shape of the object. It's basically magic :)

    However, my previous experiments didn't produce any useful models. For example, mobile apps such as 123dCatch produce 3d models that _look_ very nice, but is seriously lacking in actual resolution of the mesh. This doesn't show much when you apply a texture, but it is not suitable for reverse engineering of detailed parts.

    But today I got a new camera, which inspired me to make a new, more serious attempt :)

    My victim for this experiment was a plastic part that had seen better days. The Psion it came from was in pretty poor shape when I got it - it had been dropped, battery goop had been leaking into it and the plastic was cracked.

    Last time I learned that both shadows and highlights mess up the 3D algorithms. Shadows are taken care of with soft lighting, but highlights require a different approach. The quickest and easiest way for me was to paint the part with matte spray paint. This removed almost all of the highlights! Note that there is special paint for this purpose that can be applied and wiped off, but I opted for the cheap and cheerful route since I couln't care less if this broken part gets ruined.

    But now I just created a different problem. The algorithm works by matching features that are visible in several pictures against each other. If a surface is entirely featureless, the algorithm won't have anything to work with! To combat this, I intentionally ruined my pristine surface by doing the worst spray can job I have ever done in my life. The goal was to cover the gray primer with lots of random black spots.

    This was the final result of my intentionally crappy paint job. This picture is taken in my cheap light box, but it shows a lot of promise! There are no hard shadows, no specular highlights, and it is easy to overexpose the white background. The less crap there is in the intial pictures, the less crap I hope to get in my model as well.

    There are several different open source photogrammetry programs out there. One thing they all have in common is that they are a proper pain to get up and running. Thankfully, I stumbled over a guy who had made binary packages of several different programs. Check out his video:

    I started out with MVE, using the instructions and default values from the wiki just to see if my pictures were good enough to get a nice mesh this time. It does take a few minutes to run through the entire flow, but in the end this was the result:

    ... and since I complained about how textures hides crappy meshes before, here is the same mesh without any texture applied:

    Obviously there is still some strange things going on around the edges - my part seems to have grown a beard! I assume this is from the drop shadow of the part itself. Now that I have a workflow to get from pictures to 3d mesh, I'm thinking of trying the opposite approach - underexposing the pictures against a black background. That might eliminate any problems with the drop shadow. Processing the 32 images I took was maybe 30 minutes of computer time. Taking the pictures was a breeze since I can tether my new camera to the computer and just leave it on the tripod.

    I'll get back with a part 2 pretty soon, these results were honestly a lot better than I had expected from a first attempt! Most of the time was spent wrestling with misbehaving software, so I should be able to pick up the pace dramatically from now on :)

  • Keyboard adapters available!

    RasmusB03/20/2017 at 20:14 4 comments

    Finally you can order your keyboard adapters ready to go from me!

    Order from my Tindie store. With your order you'll receive a keyboard adapter, programmed with the Arduino bootloader and a LED blink sketch (that is how I test the boards).

  • Quick update + keyboard adapter

    RasmusB05/02/2016 at 17:52 16 comments

    Hello all,

    I thought I'd write a quick update since there has been a lot of interest since this project was featured on (

    I'm really happy about that, having people showing interest in your work is always a boost :)

    Anyway - several people have asked me about making the keyboard adapter available. While everything you need to make one is on Github, I fully appreciate that my design is pretty challenging to put together for people with little or no experience of surface mount soldering.

    So I'd like to hear from you - are you interested in getting a pre-built and tested keyboard adapter? The adapter looks like an Arduino Leonardo to your computer, so think of it as a tiny Arduino board with a connector that fits the Psion keyboard. While I'll make sure it works properly before shipping, I won't be able to provide much support or any warranty. This is mainly meant to help a few more people getting their own projects off the ground.

    Comment below if you are interested!

  • Reverse engineering mechanical parts

    RasmusB01/13/2016 at 19:01 17 comments

    I have been able to spend a few hours on the project, and I thought I could share some of the progress so far.

    I was going crazy trying to figure out a solution to the screen and processor dilemma. I still haven't figured out a perfect solution, but I choose to focus on other parts in the meantime.

    One problem with upgrading a small, handheld device is that there are serious space constraints you have to work around. Finding out how much room (or rather how little room!) I have to work with inside the empty shell is very time consuming, but spending the time now makes things a lot easier later on.

    I have two goals with the mechanical design:

    1. Everything must fit inside the original enclosure
    2. Reuse as many mechanical features as possible (pushbuttons, battery compartment, connectors etc.)

    The easiest route towards these goals is to start out from what I already have, in my case that is a main board from one of my Psions that wouldn't boot. (Bonus points to anyone who can spot the problem, it's actually visible in the photo below)

    For my first attempt, I used my digital calipers to measure the outline of the board. While this worked OK for the most part, i ran into some trouble.

    • I wanted to reuse components like the battery spring, but the spring holder was obscuring how it mounts to the PCB
    • It was very difficult to accurately measure the location of the mounting holes since they are closer to the middle of the PCB, making it too easy to take crooked measurements
    • The most complex shape (the lower right part in the picture) was very difficult to measure accurately, and that is the area with I have the least space to spare.

    So I decided to take a more refined approach. I assaulted the PCB with my hot air soldering tools until only the board itself was left:

    I had planned to harvest some components that I want to reuse for my own PCB from this board anyway. Now that the PCB was flat again, I could use a flatbed scanner to digitize the board.

    At the left is a ruler I included in the scan. This was partly to help keep the PCB horizontal in the scanner, and partly to have a size reference to make sure that I got the scaling correct. This actually came back to bite me in the rear, but we'll get back to that.

    With my scanned image trimmed down to the very edges of the PCB, it was only a matter of importing the image in FreeCAD and drawing the outline on top of the image.

    I also did some fine adjustment of the rotation of the image to get it exactly horizontal. If you want to try this yourself, make sure that you place your reference picture slightly below your sketch plane, or it will be impossible to see the lines you are drawing.

    To verify that I got the outline correct, I printed the outline on my laser printer and laid the PCB on top. To my surprise, it almost, kinda matched. I measured my printout carefully and concluded that printing something in 1:1 scale on my printer actually made it just a tiny bit to small. Once I had figured that out, I could adjust the scale and print it again. But it still looked off! What was going on?

    After spending more than an hour backtracking all my work so far and taking lots of careful reference measurements from the actual PCB and comparing them to my printouts and CAD model, I realized what went wrong - the scanned image has a small difference in scale between the vertical and horizontal axis!

    I thought I was being clever when I included a ruler in my scan, but it turns out the proper thing to do would have been to place another ruler in the horizontal direction as well to verify that the scale was the same in both directions. I also realized that I had been bitten by this behavior from a scanner before, but apparently I didn't get bit hard enough that time since i forgot about it...

    Now that I knew what the problem was, it was easily fixed by adjusting the size of my reference picture in FreeCAD and tweaking my drawing. Now the printout and the PCB matched perfectly!

    Getting the outline into KiCad

    The next step is to...

    Read more »

  • Arduino compatible keyboard adapter

    RasmusB11/28/2015 at 17:26 15 comments

    I finally got around to assembling the dedicated keyboard adapter I made before. I have had the PCBs and components for a while now, but I haven't had the time to assemble it.

    When I made the board layout I took the opportunity to get some more experience working with 0402 components, and I also wanted to try to make a PCB edge USB connector. In the end I came up with a very compact design where the keyboard connector is the only thing keeping it as big as it is.

    All discrete components are 0402 size, and the MCU is a 7x7 mm QFN package. I also ordered a solder paste stencil from, which came out very nice as usual. The PCB was ordered from

    Assembly was relatively painless. I did battle a bit with the solder paste application because my solder paste had gone a bit dry. I tried using solder paste from the bottom of the container since that was less dry, but I still got "lumps" in the solder paste. On the third attempt I got it right, and I could place and reflow the components with my hot air rework station.

    After doing a quick visual inspection with my microscope and checking for shorts, I needed to program the bootloader into the AVR. Then I could program it with my keyboard software through the USB interface. To do this, you need some kind of AVR programmer. I used my AVR Dragon.

    I did mean to build a 1.27mm pitch pogo pin ISP adapter (which would go onto the pads marked "ISP1" on the PCB), but I haven't done that yet. I first attempted to just press a 1.27mm pin header onto the pads to flash the bootloader, but I couldn't get that to work. In the end I just soldered wires to the pads. This worked well enough, after I also realized that I had populated R3 with a capacitor...

    To do the actual programming of the firmware, I did two things:

    Add my AVR Dragon as an ISP programmer in the Arduino IDE

    This is really simple. In the Arduino installation folder, find and open "programmers.txt" and add the following: AVR Dragon in ISP mode

    The next time you start the Arduino IDE, it will show up under the "Tools" menu:

    Program the AVR with the correct bootloader

    I want to use the Arudino Leonardo bootloader, since that has the same MCU and clock speed as my board. It's as simple as setting the Arduino Leonardo as the active board:

    ... and then choose "Burn Bootloader".

    After that, I removed my soldered ISP cables since they are not needed anymore. Now my board looks just like a normal Arduino Leonardo to my computer, and I can upload new firmware through the USB interface.

View all 20 project logs

Enjoy this project?



Oliver Polden wrote 09/14/2022 at 15:53 point

Has anyone got the Psion 5 screen or touchscreen working with a PI?

  Are you sure? yes | no

codeman0512 wrote 03/05/2021 at 20:50 point

Does anyone have a 3d model of the top case? The spring hooks on mine have snapped off.

  Are you sure? yes | no

jackal123uk wrote 01/05/2021 at 20:52 point

Hi RasmusB, I see it's been a while since there have been any updates - are you still working on this one?  

With the release of the Compute Module 4 I've started working on a similar project myself and your work has been a great help in getting me going.  

I'll try to write up my progress so that others will hopefully find it equally useful.

Keep up the great work! 

  Are you sure? yes | no

ostropest wrote 12/29/2019 at 20:04 point

pine64 working on pine tablet
please read or joint to the project

  Are you sure? yes | no

seilerjacinda925 wrote 11/19/2019 at 16:20 point

Nice to meet you after viewing your profile i am Jacinda, from (jakarta) indonesia,

i have a project discussion with you please email me on: (

  Are you sure? yes | no

Andy wrote 12/10/2018 at 18:31 point

Hi, are you still working on this project or are there any updates? I really like the idea of this and would love to see where it goes

  Are you sure? yes | no

fabian wrote 07/25/2018 at 13:44 point

Psion have good keyboard,

replace screen and procesor (like Linux) and will be good

  Are you sure? yes | no

ExPLIT wrote 06/03/2018 at 11:06 point

Hello guys! Do someone have English UK QWERTY Keymap file for this keyboard? I have problem to change scandinavic Keymap to UK English, and many important keys don't work at all or have different assignment.

  Are you sure? yes | no

Ronald wrote 11/16/2017 at 21:48 point

Haha, very nice. The hackaday AI suggested your project, probably because you're doing something technically similar. Incredibly simple looks your keyboard code - I guess all my speed optimizing that I thought I would need isn't really necessary to get the keyboard working. I should look into your code and your experiences a bit further, since 'my' keyboard is still a bit unstable at sending the correct keys.

  Are you sure? yes | no

Torben Gundtofte-Bruun wrote 09/19/2017 at 22:39 point

The Series 5 was my most favorite gadget *EVER* and has been my trusty companion for well over a decade. I was very sad to let it go to a new home eventually but I wanted Internet connectivity on the go and smartphones finally got good enough. Seeing THIS project deeply warms my heart, and it would be magnificent to see it completed. Lacking Rasmus' skills, I must be content to follow and admire your work. I am cheering for you!

  Are you sure? yes | no

Bartosz wrote 08/27/2017 at 08:55 point

i need a good terminal and good keyboard (with PgUp Down, home etc NO Fn modificators)

long using battery

  Are you sure? yes | no

eugene wrote 08/22/2017 at 00:24 point

I picked up an HP200LX with failing display thinking I'd do a similar project.  I'm having a hard time locating a 5" x 2" display to use though, anyone have good sources for odd sizes?

  Are you sure? yes | no

RasmusB wrote 08/22/2017 at 07:56 point

This is very difficult. Try searching for a "bar type LCD" and you'll probably find something that comes close. The hardest part is actually buying them in small quantities.

  Are you sure? yes | no

Biktor wrote 07/24/2017 at 04:58 point

Hey, have been looking at this a bit more in depth lately (I'm almost there to pull the trigger and get myself one of these), I thought I would share some ideas in case they help you a bit with the project :)

My idea would be to use the Raspberry Pi compute module with a Psion, this is the info I gathered so far, maybe you've dismissed some of it, or maybe not, it would be great to know your hardware choices ;)

- Power: Have you looked at using 14500 / AA type 3.6v li-ion batteries? They don't have the biggest density, but they would fit in the original socket, and with a little rewiring, you could get 3.6v / 4400mAh for it. Adafruit sells the Powerboost 1000C, which is both a battery charger and a 5V booster. Maybe it's not too efficient to use a booster from 3.6/4.2v to 5v to put it back down to 3.3 / 2.5 / 1.8v, but having a stable output for all the needed power rails would make it a bit easier to manage maybe. Compute Module dev board's datasheet uses a PAM2306A to take the voltage down to 3.3v from 5v and an AP7115 to take it further down to 1.8v. To control poweron/off, I would use another microcontroller emulating some standard APC USB powersupply, and feed it to the Pi so it knows it has a battery connected and can make a safe shutdown without having to write kernel modules or scripts. The only downside is that your keyboard module has all the pins used, otherwise you could still use the soft ON/OFF key for it...

- Touchscreen: Are you sacrificing the original touchscreen? I don't really know how tight it is there. If you're not, it's a standard one, and by the looks of it (I can only see the photos), those buttons are just discarded coordinates in Epoc, but they are just some more XY points in the touchscreen. If connected to another controller, they would make great F1-FX buttons + mouse (it's a resistive touchscreen anyway), or at least, some nice key combos

- LCD: Have you decided which one to use? There's nothing on 5.6" with an 8:3 aspect, curious what's your final approach on this. My best candidate would be something like Adafruit's 5.0" 16:9 display with DPI input, and wire Pi's bank0 dpi ports directly to it. With a compute module, you get another SPI, I2C port in another bank so it's not that much of a loss, given that the other choices tend to involve energy hungry hdmi converters or poor resolution i2c displays.

-USB Hub: The CF bay looks like the perfect spot to hide 2 USB ports for any storage needs. I haven't figured out how this could coexist with the embedded eMMC of the compute module, since you need USB slave mode to program it and it would need some way to fully disconnect it before flashing something in there

- Wireless: Compute module has a second SD port, SDIO compatible. That's how the Pi Zero W has wifi connection available, though, if using an internal USB hub, you could get the cheapest usb wifi module and solder it directly to the mainboard

Just my two cents ;)

  Are you sure? yes | no

RasmusB wrote 07/24/2017 at 11:35 point

Hey Biktor,

thanks for your interest in my project! Always fun to see that other poeple also find this idea interesting :)

First of all - yes, the compute module was my first candidate for this project. (That's where the project name came from originally). There are a few issues that bothers me though. Most of those issues boil down to missing support for DSI interfaces. There are no drivers available for anything else than the official 7" screen from the RPi Foundation. New (open source) drivers are being developed, but there are not guarantees and no timeline. Another problem is the lack of power management features. Basically, the hardware support in the Linux kernel is not as well developed as I would like. Broadcom has not provided any official documentation for the community, everything is locket away behind NDAs which goes against the open source nature of my project :(

So right now I have switched my focus to the BeagleBone Black instead. The newest variants uses a SoC which can be routed on a 4-layer PCB and soldered in my home workshop. The upstream linux support is a lot better, all parts can be sourced from i.e. Mouser, and all documentation is easily available for all included components - including the power managment features.

The only downside for me is that it doesn't have a DSI interface either, but since I can't use the one on the RPi anyway, that isn't a dealbreaker.

The DSI issue leads us into the screen problem - as you know, there are no direct replacement screens available. The best (and cheapest) option is to use a smartphone screen, and they almost exclusively comes with an DSI interface only. An DPI interface could work in theory, but they have fallen out of use for portable devices due to power consumption and space limitations. Space is an issue as well - I'm not sure I could fit the 40-pin connector from the adafruit screen through the existing hinge design. If possible, I would also like to have a bit higher resolution, but nothing is set in stone. :) The current plan is to find a suitable 5" smartphone screen and build my own adapter for it. See for example the Kickstarter for the MangaScreen 2 for a similar solution.

The original TS will be scrapped, since it requires a pen to use efficiently (I might use the empty pen slot for a headphone jack instead). Since I won't fit my replacement screen anyway, I'll rather have some extra room for the screen. If my replacement screen has a touchscreen I'll implement that of course.

The power supply has given me a lot of headache to be honest :) Here's where I'm at currently:

With by current BBBW design, the only time 5V is actually needed is if I want to use the USB host features. I like the idea of being able to use either two 14500s in parallell, or two AA alkaline batteries in series, just like the original. I have an idea on how to make that work, but I'll need to test it out. I won't have an USB hub in my design, mostly to keep the average power consumption down but also lower the peak power needed. (For each USB port I make available to the end user, I need to be able to provide an additional 500mA@5V...) This also means that there is a redesigned keyboard adapter coming up using HID over I2C, which is what I'm currently hacking away on :)

I hope you'll keep following my progress, and thank you again for your input, really appriciate it! :)

  Are you sure? yes | no

František Šindelář wrote 03/17/2017 at 07:09 point

Thanks for the stuff on github! It saved me a lot of time! Although the schematic in Keyboard part 1 caused me a lot of head scratching :) Schematic on github seems to more or less work for me - some keys are swapped, but that might be problem on my side... 

  Are you sure? yes | no

RasmusB wrote 03/17/2017 at 15:00 point

Thank you! Yeah, the schematic in the project log is wrong... but I didn't realize until I got to the first proper prototype :) I think the schematic on github should be correct (at least row/column assigment). Shouldn't matter for the actual hardware, but it makes the software a lot easier to understand :) You can always double check the function with the scanning sketch (also on github).

  Are you sure? yes | no

Joao wrote 03/04/2017 at 18:57 point

hi Rasmus, any updates? Very anxious to hear how it's going!

  Are you sure? yes | no

Koen van Vliet wrote 03/04/2017 at 14:02 point

I used to have one of these, but unfortunately it died. It was a great little portable serial terminal! Nice to see you're upgrading these!

  Are you sure? yes | no

Joao wrote 02/28/2017 at 21:28 point

Joined hackaday just for this project, so thank you for posting it! I'm pretty anxious to find out how it's going, any updates? :)

  Are you sure? yes | no

RasmusB wrote 03/04/2017 at 14:09 point


It's moving along, but slowly :) I had a lot of interest in the keyboard adapter, so I'll start selling those soon on Tindie. I'm currently waiting for the final prototype for that.

  Are you sure? yes | no

Koen van Vliet wrote 03/04/2017 at 14:19 point

I still have my keyboard. Where can we find you on tindie?

  Are you sure? yes | no

RasmusB wrote 03/04/2017 at 16:25 point

I'll post a link as soon as I get the product listing finalized. I have to build the final prototypes and take proper product photos as per the Tindie guidelines.

  Are you sure? yes | no

Adam Hammerton wrote 03/09/2017 at 23:27 point

Really glad to hear that the keyboard adapter isn't too far away.

Have you seen the Gemini PDA campaign on Indiegogo? Not that I think it should discourage your project (where's the fun in just buying something that anyone can get!) but they seem to have sourced an 18:9 screen that looks like it could fit your project quite well.

  Are you sure? yes | no

Paul wrote 05/29/2016 at 01:01 point
Add your commentfeeling a bit silly now, a month ago I had a big cleanup of old tech and threw out my WinCE2 PDA that I had been saving. Eventually realizing that it was too underpowered for practically anything , out it went. If only I had seen this inspirational project before .Touchscreen too.

  Are you sure? yes | no

mclien wrote 05/03/2016 at 12:48 point

Hi RasmusB, interesting thing is, I thought about quite the same, but using the old Palm III. But the main reason for my post is, that there might be a nice shortcut and synergy project to consider:

The project is at the corner from prototype to serial production and is completely open (hardware design source will be released with first production run). the modular design of the Pyra will give you a designed ready CPU board with all information of the design and a very vivid community. i have quite a short connection to the head of the project and he completely liked the idea of having the same CPU board running in one of those old PDAs by just designing a new carrierboard for that.

  Are you sure? yes | no

RasmusB wrote 05/03/2016 at 13:04 point

That is a really interesting suggestion! I've been looking at the BeagleCore which also provides a modular CPU board. Do you think you could get me some preliminary data on the CPU module? I'm especially interested in what interface they are using for the LCD.

  Are you sure? yes | no

mclien wrote 05/03/2016 at 14:18 point

As the first information it's an OMAP5432 CPU and it is yet to decide, if it will get 4 or 2GB of RAM or if both modules will be available. but I'll ask for some more information (there was some special hardware to get the portrait LCD displaying landscape, but that's quite not my knowledge). Maybe I'll hint you to the important threads in the forum. Or you can use the forum yourself, too. It's english anyway.


I opened a thread the interface questions:

"MIDI DSI and HDMI are available, most probably one of each" was the first reply. feel free to join.

  Are you sure? yes | no

Daniel Roseman wrote 05/02/2016 at 20:45 point

If contrast was your only concern, you could always opt for epaper. I am not sure if anything on the market matches the size requirements you are looking for but it fits all of your requirements. Low power, high contrast, low refresh speed. Some are even capable of low frame rate video. Just a thought.

  Are you sure? yes | no

Similar Projects

Does this project spark your interest?

Become a member to follow this project and never miss any updates