[Project&Inquiry] Framework 2-in-1

I’m planning to rework the Framework Laptop 13 into a 2-in-1 device for my undergrad engineering capstone project next year. Machining the parts and creating the device shouldn’t be too difficult, but the big issue is sourcing a panel. My current plan is to reach out to popular MPP display OEMs to see if they’d send me an eval board, but not sure how that will pan out. Anyone have experience sourcing displays? It seems especially the MPP ones are hard to come by, and I don’t want to strip one out of a device with proprietary UEFI/ACPI stuff and deal with all that, plus most seem to use SPI instead of the I2C mapped over the 13 mainboard’s eDP connector.


I am doing the same thing and I imagine you have seen my topic Connecting a Wacom I2C touchscreen to the Framework 13 motherboard (prototype). I can elaborate on why I ultimately chose the display I did so you can at least some some research time. For a DIY 2 in 1, there are 2 types of viable displays.

A usb drawing tablet is probably the simplest choice as it only needs 1 usb c cable to work and you do not need to interface with the eDP connector. The down side is that it will take up 1/4 of the IO and you would have to disassemble it to make it fit in the display. I was looking into the Asus ProArt Display PA169CDV before I decided that it was not the right option for me.

The other option is a display form a 2 in 1 laptop. This has the benefit of being able to interface with the eDP connector at the cost of additional work. As for as i know there are no 2 in 1 devices with stylus support that have a touch controller that connect over usb. I looked at displays primarily from Microsoft, Dell, and Lenovo laptops, as they all made a range of laptops with 4k displays with stylus support. I know that, despite using MPP, both the dell that i was looking at uses I2C for the touchscreen and older surface devices use I2C and newer ones uses “a rather special system”. Levovo devices also use I2C of course. In my research I never found a display that used SPI.

I ended up going with a display from a lenovo yoga 720-15ikb because I needed all 4 usb c ports on the motherboard, I already had the laptop, I can buy another off of ebay for the final device when i need (the dell display especially were very hard to come by for sale), and because i am already invested in the wacom AES ecosystem.

I think that a disassembled usb tablet may make the most sense for your project. First of all, if you do get a SPI display, i do not know of any easy way to get the OS to recognize it. The drivers designed for it will almost certainly not interact with a usb-spi bridge and there are no SPI exposed pins on the motherboard to connect it to. An I2C display will come with the same requirement of modifying the ACPI table to get it to work so, if that is a no go, i think a usb tablet is the only option remaining.

One thing you may be able to do is to disassemble the usb tablet and then disconnect its display from the controller pcb and then connect it to the eDP connector directly. This may then allow you to connect the tablets controller to one of the frameworks internal usb 2 ports (ether on the eDP connector [no idea if it works], webcam connector, or trackpad connector), allowing you too still use all 4 usb c ports on the motherboard. I was never able to find tear down photos of drawing tablets so I have no idea if the displays could be connected to the eDP connector and I have no idea if the controllers in the displays would work if only connected to usb 2 without a display signal, but it may be something to look into.

Whatever you do, keep posting updates as i would love to see what path you choose and how the project turns out!

I had not actually seen that thread and am very pleased that some precedent exists for this. I agree I2C is the way to go given the I2C that’s there because I do plan to go down the eDP route given I’d like to produce a pretty usable “final product” and don’t want to lose ports.

RE: ACPI I was hoping that Framework had an EDK2 port somewhere so I could go that route for adding an I2C display via ACPI, but I see you have some of that in a DSDT patch. I’m more experienced in DTS than ACPI so I’m happy to see I’ll have something to start from.

RE: display choice, I totally agree. I in fact have a Surface myself with the “special system” you mention–as a matter of fact, it’s one of the newer ones with the ITHC. I did some research into that route, but it seems that the ITHC is just a PCH-exposed SPI controller that abstracts away some of the stupid pen stuff. Unless Framework mapped these pins to test pads and didn’t label them on the schematic, I think that that (and SPI in general as you also found) is a no-go.

I will do one of three things:

  1. I have emailed (with low expectations) Wacom, and will also contact other vendors to see if I can source an eval board or something the “proper” way
  2. I will try to disassemble and map the eDP stuff for a USB pen tablet of the right size
  3. I will try to find a specific non-SPI display (like the Dell and Lenovo ones you mentioned and used)

Luckily for me, I have access to material stock and machining power at school, so the chassis isn’t a big limiter–If no display exactly matches my proper size, I can machine a new frame etc.
Thank you for the help and I will assuredly keep this thread updated!

1 Like