Hello,

Glad to hear you have managed to mitigate the issue, please let us know if it happens again or you run into any more issues.

Best Regards,
BRT Community

Hello,

Thank you for the update.

Can I clarify if you are trying to use CMD_ROTATE or CMD_SETROTATE? the function name provided below implies the former, but the definition for the later appears to have been utilised.

There is no reason that the CMD_ROTATE or CMD_SETROTATE command would cause the co-processor to hang (REG_CMD_READ =/= REG_CMD_WRITE) in normal operation. but it would help to understand when you are trying to call this command and what you are trying to achieve by calling it. i.e. are you trying to rotate an image and inadvertently using SETROTATE or are you intending on rotating the full screen?

In any case a a co-processor hang can also be caused by a poorly formed SPI transaction being received by EVE, in this case it may still be worth checking the integrity of the QSPI signals to the BT81x. Could also confirm if you are still seeing intermittent rendering fails, and if these are mitigated by removing the call to TFT_qspi_cmd_rotate?

Best Regards,
BRT Community

Hello,

Thank you for the update.

Can if there is any correlation between the instances of the flash attach error and display issue, i.e. do these both happen at the same time and does they always happen together?

Could I also ask what is contained within the TFT_init_flash() function? and whether the CMD_FLASHATTACH or presumably the CMD_FLASHFAST command is failing? if it is the latter what is the error code returned?

Thank you also for update regarding co-processor error checking, it is interesting that there is no error reported back from the co-processor, can I ask if the REG_CMD_WRITE and REG_CMD_READ pointers become equal when you observe the issue with the display?

Best Regards,
BRT Community

Hello,

Thank you for the update.

I note from your initialization code that you are indeed using a System Clock of 72Mhz, but that you are using a REG_PCLK = 2, this would clock the LCD displays pixel clock at 36MHz.
Please refer to Table 4-11 in the BT815 datasheet for the available Pixel clock rates.

Do you have access to the datasheet for the LCD panel that you are using in your application?
This should list a min/typ/max PCLK values for the panel, as a first test i think we should try reducing the PCLK for the display to the datasheets typical value, as this will give EVE more time to render assets which are stored in flash during a screen refresh cycle. If you do not have the datasheet to hand you can incrementally increase the REG_PCLK value until the screen stops rendering data (for example, try: 3, 4, 5, 6, 7, etc).

Best Regards,
BRT Community

Hello,

Thank you for your post.

Could I ask what Display settings you are utilising for your LCD panel? and what system clock you have the BT815 running at?

Best Regards,
BRT Community

Hi Rudolph,

Yes you are correct, CMD_SYNC is available in FT81x and BT88x.

It must have been an oversight but our BRT_AN_088 covers both FT81x and BT88x from now on, to replace the FT81x programmers guide.

Best Regards, BRT Community

Hi Everyone,

We've just released our latest update for our EVE Screen Editor utility (ESE).

ESE makes it even easier to design and lay out your user interface for EVE via the user friendly drag-and-drop interface. You can preview on a real EVE module connected over USB (see the user guide for supported modules). It's also great for learning about, and experimenting with, different EVE features and graphics techniques.

You can download version 4.11 now from this link:
https://brtchip.com/ese-2/

Here are some of the new features added:

• Make the dock widgets movable and floatable.
• Add feature: Move widgets to back/front.
• Remove nested BEGIN() and END() when the user drags and drops Primitives.
• When the user holds "CTRL" and drags a widget, clone that widget.
• When the user selects a widget on the emulator by clicking on it, pressing the arrow key will move the widget.
• CMD_FLASHPROGRAM/WRITE is supported.
• Support programming blank flash in the device manager.
• Update the DXT1_L2_RGB565 example.

This version also resolves some issues, including an issue with custom fonts when the device type selected is BT88x, and where REG_PLAY_CONTROL was not updating in the Inspector window.

We hope you find the new features helpful but let us know here if you have any feedback or questions...

Best Regards, BRT Community

Hi,

Could you advise which code you use to load your images and we can see if we can make any suggestions,

Best Regards, BRT Community