# LCD Display Driver Issue: "AttributeError" when using attribute 'QVGA'

**URL:** <https://forums.openmv.io/t/lcd-display-driver-issue-attributeerror-when-using-attribute-qvga/5566>\
**Category:** OpenMV Boards\
**Created:** [March 16, 2021, 10:30pm UTC](https://forums.openmv.io/t/lcd-display-driver-issue-attributeerror-when-using-attribute-qvga/5566 "2021-03-16T22:30:45Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![CRMANN](https://yyz1.discourse-cdn.com/flex029/user_avatar/forums.openmv.io/crmann/32/58_2.png) [@CRMANN](https://forums.openmv.io/u/CRMANN)\
**Post date:** [March 16, 2021, 10:30pm UTC](https://forums.openmv.io/t/lcd-display-driver-issue-attributeerror-when-using-attribute-qvga/5566/1 "2021-03-16T22:30:45Z")

</div>

I recently upgraded to the latest OpenMV IDE and firmware for my H7 Plus (as of the date of this post). I am now receiving the following error when attempting to run a program that is verified functional with the 2.6.8 IDE & its bundled H7+ firmware:

**AttributeError: ‘module’ object has no attribute ‘QVGA’**

The line:

```auto
lcd.init(type=lcd.LCD_SHIELD, width=320, height=240,framesize=lcd.QVGA,refresh=60, triple_buffer=False, bgr=False)*

```

…is highlighted as being problematic with the new firmware. I looked over the LCD driver docs and the example templates and I really don’t see a change since I last looked at this, but clearly something is different.

FYI: I am using the code here, when I was developing the driver (last post where I finished the driver):

[Can no longer drive ST7789V SPI TFT w/ firmware 3.8.0 (works for \<= 3.6.7) - OpenMV Products - OpenMV Forums](https://forums.openmv.io/t/can-no-longer-drive-st7789v-spi-tft-w-firmware-3-8-0-works-for-3-6-7/2068/5)

Thanks for any guidance…

---

<div class="post-metadata">

**Author:** ![iabdalkader](https://yyz1.discourse-cdn.com/flex029/user_avatar/forums.openmv.io/iabdalkader/32/1169_2.png) [@iabdalkader](https://forums.openmv.io/u/iabdalkader)\
**Post date:** [March 16, 2021, 10:44pm UTC](https://forums.openmv.io/t/lcd-display-driver-issue-attributeerror-when-using-attribute-qvga/5566/2 "2021-03-16T22:44:28Z")

</div>

You don’t need `framesize=lcd.QVGA` anymore as far as I can see from the code.

---

<div class="post-metadata">

**Author:** ![kwagyeman](https://yyz1.discourse-cdn.com/flex029/user_avatar/forums.openmv.io/kwagyeman/32/4_2.png) [@kwagyeman](https://forums.openmv.io/u/kwagyeman)\
**Post date:** [March 16, 2021, 11:56pm UTC](https://forums.openmv.io/t/lcd-display-driver-issue-attributeerror-when-using-attribute-qvga/5566/3 "2021-03-16T23:56:30Z")

</div>

That’s for driving an external HDMI display as mentioned in the docs. It doesn’t have anything to do with the LCD code.

---

<div class="post-metadata">

**Author:** ![kwagyeman](https://yyz1.discourse-cdn.com/flex029/user_avatar/forums.openmv.io/kwagyeman/32/4_2.png) [@kwagyeman](https://forums.openmv.io/u/kwagyeman)\
**Post date:** [March 16, 2021, 11:57pm UTC](https://forums.openmv.io/t/lcd-display-driver-issue-attributeerror-when-using-attribute-qvga/5566/4 "2021-03-16T23:57:07Z")

</div>

Given that, the strings are missing in the firmware for boards that can’t drive an external display. Only the Pure Thermal and Portenta will be able to do this.

---

<div class="post-metadata">

**Author:** ![CRMANN](https://yyz1.discourse-cdn.com/flex029/user_avatar/forums.openmv.io/crmann/32/58_2.png) [@CRMANN](https://forums.openmv.io/u/CRMANN)\
**Post date:** [March 18, 2021, 8:43pm UTC](https://forums.openmv.io/t/lcd-display-driver-issue-attributeerror-when-using-attribute-qvga/5566/5 "2021-03-18T20:43:55Z")

</div>

Thanks for the clarification, I’ve modified my program accordingly and the error is no longer present. I really appreciate the help!