Have you fixed your alignment? The flash destination address that you posted in the other thread was not a multiple of 4096.
- May 07, 2024, 04:36:01 PM
- Welcome, Guest
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
91
on: February 20, 2024, 03:44:06 PM
|
||
Started by rascalito - Last post by Rudolph | ||
92
General Category / Discussion - EVE / Re: BT817 Calibration has strange matrix, sometimes don't work.
on: February 20, 2024, 03:11:02 PM
|
||
Started by KarolBob - Last post by BRT Community | ||
Hello,
Thank you for the clarifications, I think in the case that both the older version of the same display and the fact that rerunning the calibration routine results in the display working as expected means we can rule out an issue with the I2C data coming from the touch controller. And similarly it would rule out a hardware issue such as the CTP connector being misaligned. I would be interested to know if the saved matrix values that you are noting are captured before you write them into the EERPOM or afterwards? This, as you have noted, may be related to an overflow issue or potentially an endianness issue. Best Regards, BRT Community |
93
on: February 20, 2024, 10:47:20 AM
|
||
Started by rascalito - Last post by HEYYA | ||
I am trying to update my flash using cmd_flashupdate. But flash doesn't get updated, unless I erase the whole flash memory.
|
94
on: February 19, 2024, 08:12:11 PM
|
||
Started by Rad - Last post by KarolBob | ||
Hi there.
I've been recently testing the method with interrupt handling from the touch panel. Thanks to this, it's possible to practically not send anything to FT/BT81x for most of the time. When an interrupt occurs, only then do I read the TAG. Here's the interrupt configuration: Code: [Select] void EVE_INT_config(void) Then, in loop functions: Code: [Select] if(is_set(FLAGS,_f_tp_irq)) Also IRQ from pin change:Code: [Select] ISR(INT7_vect) |
95
General Category / Discussion - EVE / Re: BT817 Calibration has strange matrix, sometimes don't work.
on: February 19, 2024, 07:59:44 PM
|
||
Started by KarolBob - Last post by KarolBob | ||
Thank you for your response to my questions.
I note you mention an older screen does not present this issue, are both of these screens the same RVT101HVBNWC00-B model? It turned out that the issue also occurs on the older/newer RVT101HVBNWC00-B panel. Currently, I am working on the project, and every time I power it on and restore the saved calibration matrix from EEPROM, I still have to perform calibration. I trigger the calibration with a button on the PCB. On the occasion of the issue occurring does a re-run of the calibration routine result in accurate matrix values, or for example do you need to power cycle the board?Running the calibration function solves the problem with the touchscreen panel. It seems like I mostly have to do this almost every time I power it on. Have you noted any issues around the CTP connector to the displays main PCB?I haven't noticed any problems with the CTP connector. When I used 7" panels with CTP before, everything worked fine. I'll add that I have the screen rotated 180 degrees, but that shouldn't be an issue. PS. Perhaps the problem lies elsewhere, for example, I might be experiencing buffer overflow - I need to carefully check the source code again. Regards, Karol |
96
General Category / Discussion - EVE / Re: BT817 Calibration has strange matrix, sometimes don't work.
on: February 19, 2024, 03:48:01 PM
|
||
Started by KarolBob - Last post by BRT Community | ||
Hello,
Thank you for your post. I note you mention an older screen does not present this issue, are both of these screens the same RVT101HVBNWC00-B model? On the occasion of the issue occurring does a re-run of the calibration routine result in accurate matrix values, or for example do you need to power cycle the board? Have you noted any issues around the CTP connector to the displays main PCB? Best Regards, BRT Community |
97
on: February 16, 2024, 12:30:17 PM
|
||
Started by KarolBob - Last post by KarolBob | ||
Hi there.
This is my first post on this forum, so I would like to say hello to everyone. Also, I want to express my gratitude to Rudolph for his amazing work. Big thanks for that! I'm using RVT101HVBNWC00-B with BT817Q: Sometimes i have strange calibration matrix value, only with 0 or 65535 values: Quote TransMatrix1 = 65536;Sometimes it works well, other times it doesn't. This is my source code: Code: [Select] void restore_calibrate_matrix(void) In the main function, I simply call the 'restore_calibrate_matrix' function. This function reads the calibration matrix from EEPROM. If EEPROM is empty (i.e., it has a value of 0xFFFFFFFF), I invoke the screen calibration and then save the new calibration matrix values to EEPROM. However, if EEPROM contains any saved values, it reads the consecutive 'TransMatrix[n]' and then saves them to 'REG_TOUCH_TRANSFORM_n'.I feel that one panel, the older one, works perfectly fine while the newer one has the problems described above. Regards Karol |
98
on: February 15, 2024, 03:07:53 PM
|
||
Started by karst.drenth - Last post by karst.drenth | ||
Hi,
For some projects, I need to have the Text property of an ESD_TextBox to be editable ( I need it a.o. for a OS_Keyboard ) I looked in the Keyboard example and saw the use of "cstring" there. As I wanted so be sure that each instance has it's own storage, I checked the generated code. To my asthonisment, I saw that in the EVE_Header files "cstring" is just a typedef of "const char*" which in turn means, that I will be writing directly in "some" memory where the default value is kept Is there anybody out there who can wake me up from this bad dream I am probably missing something, but can't figure out what. Greets and already thanks for an answer, Karst |
99
on: February 10, 2024, 09:48:08 PM
|
||
Started by Rad - Last post by Rudolph | ||
My code usually checks for touch events every 5ms and that function does three reads now.
Reading REG_CMDB_SPACE to check if EVE is still busy from the display refresh or if there was a co-processor fault. Reading REG_CMD_DL as a debug measure to get the size of the last generated display-list. Reading REG_TOUCH_TAG. I just did an experiment with a Teensy 4.1 under Arduino as this was wired up to the logic analyzer. The SPI clock is 16MHz. I moved out the function call to check for touch events that I placed in the loop() function to outside the code that checks that 5ms passed. And all that happens is that I can see with the logic analyzer that the SPI is flooded. The REG_TOUCH_TAG is read every 12µs. Now I commented out the reading of REG_CMD_DL which means that REG_TOUCH_TAG is read every 8µs. Ok, I can get away with not reading REG_CMDB_SPACE since I have an internal flag for the DMA transfer of the display update. And reading REG_TOUCH_TAG does not interfere with the co-processor. Now the logic-analyzer traces shows reads of REG_TOUCH_TAG about every 3.6µs. And the EVE3-50G module which has a BT815 and a GT911 is just fine. No crash and the touch still works fine. So no, there does not appear to be a limit on how often REG_TOUCH_TAG can be read. My display update is every 20ms though, so it really does not help to read the register >5400 times in between. :-) My main loop does this now, 5ms per step: read read read display read read read display And there probably would not be a noticeable difference if I changed that to >read / display< with 10ms steps. Hmm, I wonder now how long touch events actually are, or rather how short these can get. I went back to reading REG_TOUCH_TAG every 12µs and added a counter that is set to 1 on registering the touch of a button and gets increased as long as the button is touched. And I can not get this time realiably below 3000. Right now the number is 1142 which meant I managed to touch the button for only 13ms. 2161 - 28ms 976 - 12ms 2138 3298 4417 3275 3304 2156 Going back to 5ms timeslots I can not get the counter lower than 3. And not trying to touch as fast as possible I get closer to 20. So I guess it is ok to assume that the duration of touch events is at least 10ms. |
100
on: February 09, 2024, 08:55:59 AM
|
||
Started by Juanj - Last post by BRT Community | ||
Hi,
Yes, nice work and a very interesting project, thanks for sharing and let us know how it is going as you add the new features, Best Regards, BRT Community |