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 ... 21
1
Discussion - EVE / Re: EVE Asset Builder
« on: March 05, 2021, 02:33:05 PM »
Hello Rudolph,

Thank you for your detailed analysis of this issue, I have passed this onto the development team for investigation.

Best Regards,
BRT Community.

2
Discussion - EVE / Re: EVE Asset Builder
« on: March 02, 2021, 04:05:13 PM »
Hello,

I’ve had some clarification from the developers regarding Unicode font conversions:
  • Only the font metrics table covers the maximum code point of the input characters.
  • For the .glyph data,  only the input characters are converted. The characters whose code point are not present are not
    converted.


Then, number of characters is determined by: (max code point + 128 ) & ~ 127. For example if one input character set includes a character whos max code point is 382 (ž), then the .xfont will list 384 characters:

(382 + 128) & ~127 = 384

If another input character set in used which include for example the trademark symbol (™), its max code point would be 8482, and the .xfont would list 8576 characters:

(8482 + 128) & ~127 = 8576


The metric table (.xfont) will include the number relating to the max code point, and will include padding to the relevant code points for a characters width data.
However only the characters included in the input character set will be converted to the .glyph data.

I will need to investigate why you are seeing such large .glyph files when converting these fonts with differing character sets. Could you provide the input char set and font file you are using during conversion?

Best Regards,
BRT Community

3
Discussion - EVE / Re: displaying compressed png
« on: February 26, 2021, 05:04:32 PM »
Hi,

It may depend on which version of the library you use but the GD2 library has a function to call the calibrate command,

void GDClass::self_calibrate(void) {
cmd_dlstart();
Clear();
cmd_text(w / 2, h / 2, 30, OPT_CENTER, "please tap on the dot");
cmd_calibrate();
finish();
cmd_loadidentity();
cmd_dlstart();
GDTR.flush();
}

Best Regards, BRT Community

4
Discussion - EVE / Re: Display a loading page with ESD
« on: February 25, 2021, 01:19:09 PM »
Hello,

The code below is an example of writing a file to a flash IC connected to EVE:
Code: [Select]
int Utils_Write_File_To_Flash(uchar8_t *fileName, uint32_t addr, uint32_t tmp_ram_addr)
{
FILE *fp;
uint32_t fileLen, ret, progress = 0;
uint8_t pBuff[(1024 * 32)];
fp = fopen(fileName, "rb+");

if (fp) {

fseek(fp, 0, SEEK_END);
ret = fileLen = ftell(fp);

fseek(fp, 0, SEEK_SET);
while (fileLen > 0)
{
progress = (ret - fileLen) * 100 / ret;
fprintf(stderr, "Progress PROG %d\n", progress);
fflush(stderr);
int32_t ramlen = 0;
tmp_ram_addr = 0;
while ((ramlen < (1024 * 1024)) && (fileLen > 0))
{
uint32_t blocklen = fileLen > (1024 * 32) ? (1024 * 32) : fileLen;
fread(pBuff, 1, blocklen, fp);
fileLen -= blocklen;
Gpu_Hal_WrMem(phost, tmp_ram_addr, pBuff, blocklen); //write data to RAM_G
tmp_ram_addr += blocklen;
ramlen += blocklen;
}
ramlen = (ramlen + 4095) & (~4095);//to ensure 4KB alignment

Gpu_CoCmd_FlashHelper_Update(phost, addr, 0, ramlen); // CMD_FLASHUPDATE
addr += ramlen;
}
fclose(fp);
}
else {
printf("Unable to open file: %s\n", fileName);
}
return ret; /* File size */
}

Please note, this is from our EAB flash programming utility which requires a USB connection to a module. However the same steps will work when updating a flash IC from an MCU. Unfortunately however you may be required to expand the storage of your MCU if the flash file is significantly larger than the storage available, adding an SD card to your configuration may be a suitable solution.

Best Regards,
BRT Community

5
Discussion - EVE / Re: Display a loading page with ESD
« on: February 24, 2021, 04:31:07 PM »
Hello,

Please have a look at the Ft_Esd_ProgressBar Widget included in ESD for producing a progress bar for a loading screen.

As for verifying the contents of flash after an ESD restart, unfortunately this is not currently a supported feature. But I will contact the development team to see if they can add this in future versions of ESD.

Best Regards,
BRT Community

6
Discussion - EVE / Re: BT81X Bilinear filtering make dark border on bitmaps
« on: February 24, 2021, 12:38:09 PM »
Hello,

The developers have noted that every bitmap in BORDER mode has a black border. It's not normally visible, but in bilinear at the edges, the black border pixels get sampled and used. We are looking into modes for future revisions of EVE to mitigate this behaviour, but currently there is the expected behaviour for EVE.

Best Regards,
BRT Community

7
Discussion - EVE / Re: ESD 4.10 display instabilities
« on: February 24, 2021, 12:20:14 PM »
Hello,

Glad you have resolved the issue.

Best Regards,
BRT Community.

8
Discussion - EVE / Re: BT81X Bilinear filtering make dark border on bitmaps
« on: February 22, 2021, 04:30:12 PM »
Hello,

Thank you for the details.
I'm glad you work around is producing much better results currently, I am in discussion with the development team to see if they have any other suggestions for mitigating this behaviour.

Best Regards,
BRT Community

9
Discussion - EVE / Re: displaying compressed png
« on: February 22, 2021, 03:33:02 PM »
Hi,

Yes there is normally an index and a look up table file for paletted 8. I'm not sure how the GD library displays these and what underlying code it has but you need some additional blending too in order to display paletted 8. Please see section 4.7 in the programmers guide.
https://brtchip.com/wp-content/uploads/Support/Documentation/Programming_Guides/ICs/EVE/FT81X_Series_Programmer_Guide.pdf

Due to the 1M of RAM, you may be able to use smaller types of image (such as L1 or L2) to avoid loading them on the fly. But these would make black and white or grayscale characters rather than your more complex ones. You can make them a colour though the COLOR_RGB command and maybe even add some extra effects using the graphics features of EVE however.

Best Regards,
BRT Community

10
Discussion - EVE / Re: BT81X Bilinear filtering make dark border on bitmaps
« on: February 19, 2021, 04:10:48 PM »
Hello,

Thank you for your question.
Could you give me details on how you have converted the bitmaps you are using with Bilinear filtering, so I can investigate this issue further?

Best Regards,
BRT Community

11
Discussion - EVE / Re: ESD 4.10 display instabilities
« on: February 17, 2021, 02:54:46 PM »
Hello,

Thank you for the update.
Yes it is possible that a slight hardware issue with the SPI signals may be causing the issue with the co-processor.
Please let us know if you have any further issues.

Best Regards,
BRT Community

12
Discussion - EVE / Re: ESD 4.10 display instabilities
« on: February 15, 2021, 01:38:20 PM »
Hello

Would it be possible for you to share your project with us so we can investigate this issue further?
Can you also give me details on your hardware setup, i.e which MCU are you using?

Best Regards,
BRT Community

13
Discussion - EVE / Re: ESD 4.10 display instabilities
« on: February 10, 2021, 02:50:16 PM »
Hello,

Thank you for your question.

Please see section 5.7 of the programmers guide:
https://brtchip.com/wp-content/uploads/Support/Documentation/Programming_Guides/ICs/EVE/BRT_AN_033_BT81X_Series_Programming_Guide.pdf

This covers how to read co-processor faults, which would help use determine if this is the cause of the screen issues you are seeing. It also includes the recommended recovery procedure  for when a fault is detected.

Best Regards,
BRT Community

14
Discussion - EVE / Re: ST7789V and FT81x - startup
« on: February 01, 2021, 02:22:00 PM »
Hi,

We have not used that configuration but we're not aware of any issue with using the MCU to do the reset so long as you provide the same sequence to reset the LCD controller on start-up. As you mentioned, we allow for both on the ME810A-HV35R via the OR gate. We normally leave the MCU input unused and use the DISP line from the FT810 when using this module but it should also work if using the MCU only. We're not sure about the timing needed for the ST7789 but you could even use a solder jumper in place of the OR gate to select one source or the other for initial testing.

Best Regards,
BRT Community

15
Discussion - EVE / Re: ST7789V and FT81x - startup
« on: January 29, 2021, 10:39:01 AM »
Hi,

We have not tried this particular one but we have used a similar technique with the ILI9488 in our ME810A-HV35R displays. In that case we use the same lines for SCK/MOSI/MISO for the display and for EVE but we have a second chip select and a DCX line for command/data selection for the display.

You can get an example of the hardware in the ME810A-HV35R datasheet.
https://brtchip.com/wp-content/uploads/Support/Documentation/Datasheets/ICs/EVE/DS_ME810A_HV35R.pdf

We also have a draft of an example which configures it, if you would like a copy then please email us at support.emea@brtchip.com and we can send you a beta copy,

The actual commands and values needed over this interface may vary between displays but the manufacturer will often be able to recommend a command sequence to set it in RGB mode etc.

Best Regards, BRT Community

Pages: [1] 2 3 ... 21