BRT Community

Please login or register.

Login with username, password and session length
Advanced search  

News:

Welcome to the Bridgetek Community!

Please read our Welcome Note

Technical Support enquires
please contact the team
@ Bridgetek Support

Please refer to our website for detailed information on all our products - Bridgetek - Bridging Technology

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - BRT Community

Pages: [1] 2 3 ... 51
1
Discussion - EVE / Re: PNG issue with EAB
« on: June 11, 2024, 03:32:50 PM »
Hello Rudolph,

Thank you for your work in investigating this issue, we have run some EAB conversions on the PNG files and are seeing similar results.
Currently we are discussing this issue with the R&D teams and hope to have an update soon.

Best Regards,
BRT community

2
Discussion - EVE / Re: PNG issue with EAB
« on: June 06, 2024, 04:49:18 PM »
Hi Rudolph,
We're just trying it out here too and will update you with our results and we'll also look into why it happens,
Best Regards, BRT Community

3
Hello,

Thank you for your post.

Unfortunately we do not have any Modbus specific examples available, but hopefully one of the community members may be able to provide some insight.

In general you will be able to utilise the UART interface, with an appropriate line driver for the RS485 signal levels to implement your Modbus interface.

Please let us know if you have any specific questions. 

Best Regards,
BRT Community

4
Discussion - EVE / Re: Screen rotation issue with BT817 on 1280x800
« on: May 06, 2024, 09:54:38 AM »
Hi Rudolph,

Are you seeing REG_UNDERRUN count up in the cases where you see the issue?

Best Regards, BRT Community

5
Discussion - EVE / Re: Eve3 built-in fontset
« on: May 01, 2024, 02:49:22 PM »
Hello,

I'm just double checking what the exact font size conversions are for the inbuilt fonts with the development team.

But the difference between the fonts relates to when the conversion was done, as you have alluded too. The ROM fonts in all versions of EVE are the same, and the same data is used to render these fonts from EVE to EVE4, as such this conversion was performed during the initial EVE release with an older version of the font converter. Since this time there have been several updates to the font conversion utility and its aliasing settings which accounts for the changes you have noted between these versions of the font in ESE.

Best Regards,
BRT Community

6
Discussion - EVE / Re: Modularly load ASTC images
« on: April 30, 2024, 09:45:10 PM »
Hi,

No problem, we'll post an MCU to RAM_G example first and then provide a flash one too,

Best Regards, BRT Community

7
Discussion - EVE / Re: Modularly load ASTC images
« on: April 26, 2024, 02:57:29 PM »
Hi,
Yes we can post an example,
Are we correct that you want 2 or more ASTC images in Flash which are then copied to RAM_G and displayed simultaneously on the screen?
Best Regards, BRT Community


8
Discussion - EVE / Re: Long text on BT 815
« on: April 24, 2024, 10:21:58 AM »
Hi,

In addition to a few instructions for the actual setup of the font bitmap properties, each character will require at least a Vertex command.

For characters which are beyond the reach of VERTEX2II (e.g. more than 511) there is also a CELL() instruction since EVE needs to use VERTEX2F and that needs a preceding command to set which cell/character.

Therefore, you should budget at least 4 bytes per character and 8 bytes in some cases.

if the text is fixed, you may be able to write it to a bitmap or display it and take a snapshot after start-up and that would save some DL space by displaying the sentence as a bitmap.

Best Regards, BRT Community



9
Discussion - EVE / Re: Long text on BT 815
« on: April 23, 2024, 08:53:00 AM »
Hi,

Could you advise what lengths of strings you were needing to use?

Best Regards, BRT Community

10
Test and Review Area / Re: EVE Asset Builder 2.10.2
« on: April 19, 2024, 09:40:37 AM »
Hi Rudolph,

Yes, 2.11.0 is now out,

We were not able to make some other changes in time for this one but rest assured your suggestions are with the R&D team for future consideration,

Best Regards, BRT Community

11
Discussion - EVE / Re: EAB problem with astcenc.exe
« on: April 17, 2024, 03:36:24 PM »
Hello,

Thank you for the update, I'm glad to hear you can resolve the astcenc.exe issue.

Would you be able to provide the Conversion settings utilised in your testing? Along with the image dimensions for the needle image?

Best Regards,
BRT Community

12
Discussion - EVE / Re: EAB problem with astcenc.exe
« on: April 10, 2024, 03:39:55 PM »
Hello

Thank you for your post.

There are different versions of the astcenc.exe file available, some versions including the version distributed with EVE Asset Builder require AVX2 support in your CPUs instruction set.

Could you take a screen of the CPU-Z output for your machine?
Could you also attach the .bmp file that you were trying to convert so that we can test this?

Best Regards,
BRT Community

13
Discussion - EVE / Re: How often and when read REG_TOUCH_TAG
« on: April 04, 2024, 11:58:19 AM »
Hello,

EVE renders the screen from the contents in RAM_DL, however RAM_DL is actually double buffered meaning there is an active RAM_DL which EVE parses and uses to render the screen for every screen refresh. There is also a passive version of RAM_DL, this is the one you write to when you are issuing a display list or command list to EVE, this is swapped into the active buffer when the SWAP() command is issued.

The intention being that you only write a new display/command list to EVE when require the screen to be updated (say when a button is touched and you wish to enact a 3D effect to make this apparent), otherwise you can let the active display list continue to render the screen in the background and reduce the number of SPI transactions you send to EVE.

I note you mention you are scanning and re-issuing your Display() function every 100ms, but can I ask if this is irrespective of a touch detection?
It would not be necessary to re-issue the Display() call if you do not need to update any of the items on the screen.

Generally there are two approach's to dealing with touch on EVE, in either case we would recommend to initially issue your display list (call Display()):

  • Polling - Call Display(), then utilise another routine to periodically poll the appropriate touch registers to detect a touch (for example REG_TOUCH_TAG) 
    • If a touch is detected then you can re-issue a new display list with the appropriate updates (call Display() to update the screen) if required
  • Interrupts - Configure the touch interrupt, Call Display(), then wait for the interrupt pin to trigger and process this interrupt on your MCU (read the appropriate touch registers)
    • If an item has been touched which requires the screen to be updated then issue Display() accordingly with the required updates

Both approaches should reduce the number of times you call Display() the idea being that you would only need to update RAM_DL when something has to be changed on the screen. i.e. you shouldn't need to worry about an interrupt being triggered half way through your Display() routine because you are not continuously writing this data to EVE. If you structure your code in am manner that calls Display() and then only calls it again once a touch has been detected you should avoid any interrupted Display() calls. However it is possible that for example two interrupts would be trigged very close to each other, in this case you can utilise the recovery routine detailed in section 5.7 of the Programmers Guide and then re-issue the Display() command. As EVE will be rendering from the active versions of RAM_DL is a write to EVE is interrupted half way through a Display() command then the screen contents wont be affected.

Best Regards,
BRT Community

14
Discussion - EVE / Re: How often and when read REG_TOUCH_TAG
« on: April 03, 2024, 12:05:24 PM »
Hello,

Without knowing your exact display settings I would suggest an average configuration 1024*600 display would be running at roughly 50Fps (20ms a frame).

Therefore the 29ms you are seeing for frame rendering doesn't sound too unusual for a display of the resolution you are utilising. The CMD_SWAP command will also wait until the current screen refresh has completed to rendering a new display list, depending on when the list is issued this will add a small delay into the execution time also.

You can work out your display refresh rate in the following manner:
Code: [Select]
Fps = (System Clock/REG_PCLK) / (VCYCL * HCYCLE)

In short yes, the size of your screen is the limiting factor in this instance, I would suggest looking into utilising EVEs touch interrupts if possible.

Best Regards,


15
Discussion - EVE / Re: Picture transparency on another picture
« on: April 03, 2024, 10:11:21 AM »
Hello,

Unfortunately it is not possible to achieve this with a JPEG as these are loaded into EVE as RGB565 bitmaps (or  L8) which do not include an alpha layer (transparency), this is required to make sections of images transparent.

As you have noted using a command such as blend, this effects the whole image because it cannot determine which sections are the background in a JPEG. It may be possible to utilise a second masking image to mask off the background in your JPEG and then use the STENCIL operation to only draw the section of the image that isn't masked, but this would require an image such as a PNG which utilises an alpha layer to be used as the mask. In this case it may be simpler to modify your original JPEG image in a image processor to include a transparent background and save this accordingly.

Best Regards,
BRT Community

Pages: [1] 2 3 ... 51