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 - exatech

Pages: [1]
1
Discussion - EVE / fading screen flicker
« on: October 05, 2019, 04:54:26 PM »
Hi,
on a 800*480 display, driven by BT815, I made a background image and 20 icons of 100x100 pixels. All images are converted to 8x8 ASTC and reside in flash.

When this screen activates, all images are show up OK, but the screen flickers quite annoyingly. This slowly disappears: after about 15 seconds the screen is stable and I can switch between screens without any flicker.

If I start the display without the icons, but just the background, it shows up almost stable, but activating the icons in the first 15 seconds causes visible fading flicker. Using less compression for the background, and so more data, makes the flicker heavier and longer.

I just cannot grasp what is wrong with it. If the graphic engine is overloaded, how come the flicker disappears? Anyone any ideas?
thx.
Henk

2
Hi,
my board with BT815 is controlling a 7" PowerTip display that has a HY4635 capacitive touch controller. The display is OK, but the touch info is not.
I checked the I2C lines with an oscilloscope. The CTC issues an interrupt when touched, and the I2C lines show 1 byte with the address (0x38) and then halve a byte: after 4 clock pulses the clock remains low. Only when a new touch is made, the clock goes high again for the address byte.

Does anyone have experience with this CTC? Is it compatible with BT815?
thanks,
Henk

3
Discussion - EVE / Re: unified blob in BT815
« on: August 23, 2019, 03:59:58 PM »
Hi Rudolph,
you may want to check CMD_FLASHFAST: in my case it returned error 0xE002 (no header detected).

I do not know what info is in the blob: I read somewhere that it may have to be adopted for different memory sizes, but I cannot find that comment anymore. It would be interesting to know what is exactly in the blob. Have you checked REG_FLASH_SIZE? Does it tell you the correct size of your flash chip?

My approach in these cases is usually to steer clear of wonky tools, and go straight for SPI from my own processor to the chip: that allows deep debugging with the actual chip: make some small tools to read and write to the eeprom through BT815, and get the FlashUpdate command working because it is a lot easier and faster than chip erase: it also leaves your sector 1 intact.
success, Henk. 

4
Discussion - EVE / Re: unified blob in BT815
« on: August 14, 2019, 04:00:48 PM »
OK, found it: I wrote the blob to FLASH address = 0x800000, and was able to read it back because the flash is 16MB. But the destination should have been relative to the flash address, so 0x00000000:

  tft_start_write(RAM_G);   // dump blob into RAM-G
  sz = sizeof(unifiedblob);
  for (i = 0; i < sz; i++) spi_tx_8(unifiedblob);
  tft_stop();
   
    tft_cmds[0] = CMD_FLASHUPDATE;       // write to flash, erase sector if necessary
    tft_cmds[1] = 0;                                  // destination in flash
    tft_cmds[2] = RAM_G;                          // source in RAM-G
    tft_cmds[3] = sz;                                 // size
    tft_write_fifo((uint8_t*)tft_cmds, 16);


Bridgetek: a bit more documentation could have saved me a lot of time: the unified blob is nowhere to be found in your datasheet of user manual. Please do not mention errors like "Is it blank" without telling how to fix it.
Henk

5
Discussion - EVE / Re: unified blob in BT815
« on: August 14, 2019, 03:03:48 PM »
Hi darkjezter,

So it is possible? I tried, but did not succeed. Can you please share the info? What blob file you use, where you have written it to?
Adding the blob to the MCU firmware is no problem for me: plenty of memory available.

thanks,
Henk

6
Discussion - EVE / Re: unified blob in BT815
« on: August 07, 2019, 12:54:19 PM »
Hi Rudolph,
I have no problem writing to the flash. First I copied the data to RAM-G and then issued CMD_FLASHUPDATE with parameters FLASH, RAM_G and 4096. After this, I verified by cycling the power supply, and then reading back 4096 bytes to RAM-G. This verified OK.

The part is indeed new, and the error 0xE002 means: "no header detected in sector 0 – is flash blank?". Yes it is blank, so what to do next? The manuals do not tell me how to "unblank" it.

My board has a CAN interface only (plus an SD-card to transfer the images to the flash once after production), and I cannot see how the Asset Builder would succeed in getting the unified.blob and other files into the device using CAN.

7
Discussion - EVE / Re: unified blob in BT815
« on: August 05, 2019, 04:15:51 PM »
Thanks,
but as I mentioned: the asset builder cannot connect to my board. So, I need my host processor to install the blob. How can I do that?
best regards,
Henk

8
Discussion - EVE / unified blob in BT815
« on: July 31, 2019, 07:30:02 PM »
Hi,
I am testing a newly developed board with BT815 and external flash (W25Q128JVSIQ). It is a bare metal board without any link to the "EVE asset builder" utilities.

The display is functioning OK, and I can write text and images from RAM_G. Next step is to show ASTC images from flash, but I cannot get the flash into fast mode. After initialization, REG_FLASH_STATUS = 2 (FLASH_STATUS_BASIC) and CMD_FLASHFAST returns error 0xE002 (no header detected).
I then tried to write the unified.blob file from the "EVE asset builder" directory into the flash using CMD_FLASHUPDATE, dest = 0x800000, src = 0, num=4096 and this returns OK, and I can even read the blob data back from flash, but still CMD_FLASHFAST returns 0xE002.

Does anyone know how to do this? Is there any detailed information about this unified.blob and how to install it? I cannot find it anywhere.
Help is much appreciated,
Thanks, Henk

Pages: [1]