# Framework 16 Screen Compatability

**URL:** <https://community.frame.work/t/framework-16-screen-compatability/69385>\
**Category:** Creators & Developers\
**Created:** [May 18, 2025, 4:11pm UTC](https://community.frame.work/t/framework-16-screen-compatability/69385 "2025-05-18T16:11:14Z")\
**Posts on this page:** 1\
**Showing post:** 45

<div class="post-metadata">

**Author:** ![Xavier\_Jiang](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/xavier_jiang/32/2793_2.png) [@Xavier\_Jiang](https://community.frame.work/u/Xavier_Jiang)\
**Post date:** [August 6, 2025, 6:29am UTC](https://community.frame.work/t/framework-16-screen-compatability/69385/45 "2025-08-06T06:29:25Z")

</div>

well this is anticlimatic.

I have the cable. I have the screen. The pinout is correct (ripped apart both the framework and custom cables tape for analysis)

Hooked up to the main board, and uh … _nothing_

No spark, no like, magic smoke or whatsnot. Just nothing. Laptop works, post to external display.

And if I swap back the NV160QDM, the laptop works.

So uh. No $1000 mistake. $100 mistake. Big deal. At least I cannot destroy the main board. Mostly.

I can probe the screen for power, but I might also just short something in the process. I can, however, continuity check the voltage pins and ground pins to see if I messed up the cabling.

 ![IMG_8979](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/3X/c/b/cb289fdab9c94914cb043ed438046fb0e2963e86.jpeg)

 ![IMG_8980](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/3X/9/f/9f4d24539e77387328e1c08d537b3b47f35bf13e.jpeg)

I heard someone have modified EC code that support debugging, I might need some of that.

(makes spark with multimeter)  
Ooo! But like, I am in voltage measurement mode?  
Probably contacted the back, lets try that again. yeah it reads … 15? Sounds about right.

I have some POST code. Let’s read those!  
1st code:  
WGGGGGRGGGGGGOBBBGGBGG

2nd code (no display connected):

WGGGGGRGGGGGROGGGGBBGG

3rd code (UAK01.5 connected):  
WGGGGGRGGGGGROGGGGBBGG

I dont think I even need to look them up. The internal display bit is failing, and the code is exactly the same.

What even handles link training? bios? ec?

---

_[View the full topic](https://community.frame.work/t/framework-16-screen-compatability/69385)._