ronan_rt

@inmarket can you share this code with me too? Im experiencing some textedit bugs. I made the keyboard appear UP and DOWN. For example: if the textedit is located at the top of the screen, the keyboard appear at the bottom. If the textedit is located at the bottom o the screen, keyboard appears at the top. WHen I am typing into a TOP (for example) textedit, close the keyboard (by clicking outside of the textedit, my routine), and click on a BOTTOM textedit, the keyboard opens and the LAST textedit FOCUS in front of my keyboard. This happen always when I have a previous textedit focused. How can I take this focus away?

@inmarket, maybe the threat was my post..If wasnt, please point me the post. But anyway, about the memory: I tried to change the values of HEAP_SIZE like a lot! Nothing happened, still bug. I do think its a memory problem, but I couldnt find yet. This infos help you to solve my case?

Yes. In fact, when I increase the size, dumb chars appears. For example: I wanna type 1.456, when I type '6', chars like 'p?' apear. Its randomly apearing into any textedit. Lots of textedits of my program are making this.

Hello! Couldnt you open my video with the bug??

@Joel Bodenmann? @inmarket?

Hello again! My textedit are randomly printing some bad characteres..some are, some are not..why This is happening? I tried to increase and decrease heap tô Max and min value possible, but nothing happened Cheers!! VID_20170707_101651.mp4

Quick question @inmarket and @Joel Bodenmann: Do you recomend using an OS to work with uGFX? In my case, Im only using RAW32. Whats the difference between a simple raw32 and a OS like CHIMBIOS or KEIL_RTX?

Very nice!! I will see if this will work. Unfortunatelly I will have to scratch all my pcb. Thanks my friend! Almost reaching to the end of the project

Maybe the BTE software acceleration of RA8875 will resolve this? What do you think?? Cos im seeing here: not every Stm32 have this FMSC. In fact, stm32F103 have!! But only the high density ones! (above 100-144 pins)

I think cubeMX have this feature. Look at this: I The problem is that maybe stm32f105 doesnt have this feature

Well, Im screwed! Ive already printed my board with separated Pins. Is there any chance that I can use a regular pin to make this happen faster?? I mean: do I have to change my hardware or I can set any regula I/O FSMC??

Thats the video. Im even using a better uC: stm32F105 now. I am pasting the write index and write cmd just in case static GFXINLINE void write_index(GDisplay *g, uint16_t index) { (void) g; (void) index; // HAL_GPIO_WritePin(E_RD_GPIO_Port, E_RD_Pin, GPIO_PIN_SET); HAL_GPIO_WritePin(CS_GPIO_Port, CS_Pin, GPIO_PIN_RESET); HAL_GPIO_WritePin(RS_GPIO_Port, RS_Pin, GPIO_PIN_SET); if(index & 0x80) HAL_GPIO_WritePin(D7_GPIO_Port, D7_Pin, GPIO_PIN_SET); else HAL_GPIO_WritePin(D7_GPIO_Port, D7_Pin, GPIO_PIN_RESET); if(index & 0x40) HAL_GPIO_WritePin(D6_GPIO_Port, D6_Pin, GPIO_PIN_SET); else HAL_GPIO_WritePin(D6_GPIO_Port, D6_Pin, GPIO_PIN_RESET); if(index & 0x20) HAL_GPIO_WritePin(D5_GPIO_Port, D5_Pin, GPIO_PIN_SET); else HAL_GPIO_WritePin(D5_GPIO_Port, D5_Pin, GPIO_PIN_RESET); if(index & 0x10) HAL_GPIO_WritePin(D4_GPIO_Port, D4_Pin, GPIO_PIN_SET); else HAL_GPIO_WritePin(D4_GPIO_Port, D4_Pin, GPIO_PIN_RESET); if(index & 0x08) HAL_GPIO_WritePin(D3_GPIO_Port, D3_Pin, GPIO_PIN_SET); else HAL_GPIO_WritePin(D3_GPIO_Port, D3_Pin, GPIO_PIN_RESET); if(index & 0x04) HAL_GPIO_WritePin(D2_GPIO_Port, D2_Pin, GPIO_PIN_SET); else HAL_GPIO_WritePin(D2_GPIO_Port, D2_Pin, GPIO_PIN_RESET); if(index & 0x02) HAL_GPIO_WritePin(D1_GPIO_Port, D1_Pin, GPIO_PIN_SET); else HAL_GPIO_WritePin(D1_GPIO_Port, D1_Pin, GPIO_PIN_RESET); if(index & 0x01) HAL_GPIO_WritePin(D0_GPIO_Port, D0_Pin, GPIO_PIN_SET); else HAL_GPIO_WritePin(D0_GPIO_Port, D0_Pin, GPIO_PIN_RESET); //index write HAL_GPIO_WritePin(R_WR_GPIO_Port, R_WR_Pin, GPIO_PIN_RESET); HAL_GPIO_WritePin(R_WR_GPIO_Port, R_WR_Pin, GPIO_PIN_SET); HAL_GPIO_WritePin(CS_GPIO_Port, CS_Pin, GPIO_PIN_SET); //release_bus(g); HAL_GPIO_WritePin(RS_GPIO_Port, RS_Pin, GPIO_PIN_RESET); } static GFXINLINE void write_data(GDisplay *g, uint16_t data) { (void) g; (void) data; //HAL_GPIO_WritePin(E_RD_GPIO_Port, E_RD_Pin, GPIO_PIN_SET); HAL_GPIO_WritePin(CS_GPIO_Port, CS_Pin, GPIO_PIN_RESET); HAL_GPIO_WritePin(RS_GPIO_Port, RS_Pin, GPIO_PIN_RESET); if(data & 0x80) HAL_GPIO_WritePin(D7_GPIO_Port, D7_Pin, GPIO_PIN_SET); else HAL_GPIO_WritePin(D7_GPIO_Port, D7_Pin, GPIO_PIN_RESET); if(data & 0x40) HAL_GPIO_WritePin(D6_GPIO_Port, D6_Pin, GPIO_PIN_SET); else HAL_GPIO_WritePin(D6_GPIO_Port, D6_Pin, GPIO_PIN_RESET); if(data & 0x20) HAL_GPIO_WritePin(D5_GPIO_Port, D5_Pin, GPIO_PIN_SET); else HAL_GPIO_WritePin(D5_GPIO_Port, D5_Pin, GPIO_PIN_RESET); if(data & 0x10) HAL_GPIO_WritePin(D4_GPIO_Port, D4_Pin, GPIO_PIN_SET); else HAL_GPIO_WritePin(D4_GPIO_Port, D4_Pin, GPIO_PIN_RESET); if(data & 0x08) HAL_GPIO_WritePin(D3_GPIO_Port, D3_Pin, GPIO_PIN_SET); else HAL_GPIO_WritePin(D3_GPIO_Port, D3_Pin, GPIO_PIN_RESET); if(data & 0x04) HAL_GPIO_WritePin(D2_GPIO_Port, D2_Pin, GPIO_PIN_SET); else HAL_GPIO_WritePin(D2_GPIO_Port, D2_Pin, GPIO_PIN_RESET); if(data & 0x02) HAL_GPIO_WritePin(D1_GPIO_Port, D1_Pin, GPIO_PIN_SET); else HAL_GPIO_WritePin(D1_GPIO_Port, D1_Pin, GPIO_PIN_RESET); if(data & 0x01) HAL_GPIO_WritePin(D0_GPIO_Port, D0_Pin, GPIO_PIN_SET); else HAL_GPIO_WritePin(D0_GPIO_Port, D0_Pin, GPIO_PIN_RESET); HAL_GPIO_WritePin(R_WR_GPIO_Port, R_WR_Pin, GPIO_PIN_RESET); HAL_GPIO_WritePin(R_WR_GPIO_Port, R_WR_Pin, GPIO_PIN_SET); HAL_GPIO_WritePin(CS_GPIO_Port, CS_Pin, GPIO_PIN_SET); //release_bus(g); HAL_GPIO_WritePin(RS_GPIO_Port, RS_Pin, GPIO_PIN_SET); } VID_20170405_121654538.mp4

Hello folks! I was working with SPI communication. As we already talked, the change of the screens and buttons was too slow. Due this reasons and other reasons, We decided to change our hardware to parallel communication with the RA8875 driver. As a matter of fact, the change of the screen speed improved, but still very poor. Is there any chance of getting rid of the white clear screen every time we change our screen???

Ill try to do it all, thanks. About the item number 3. , If I lower the heap, some widget does not appear in my screen. I thought it was my firmware, than after running some tests, I discovered that if I type the wrong Heap, some widget doesnt show. Is that correct?

Im using exactly raw32 and heaping 13800, wich is my limit. The popping letters are caused by this memory fault too?