BramPeeters Beginner

  • Member since Feb 3rd 2017
Last Activity

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • BramPeeters -

    Replied to the thread Hardfault when calling GUI_Clear, thread related ?.

    Post
    So it is as I expected. If I use the 16 bit interface I get the memdev memory area directy in the low level functions without swapping. And I can transmit the bytes in the order so that my raw images have the right colors, but then any drawing actions I…
  • BramPeeters -

    Replied to the thread Hardfault when calling GUI_Clear, thread related ?.

    Post
    Small update: If I use GUIDRV_FLEXCOLOR_M16C0B16 I get pointers directly inside the memdev region so that is nice. There is a lot of tricky stuff going on though to get it right. Eg to set CASET values of the controller in 8 bit mode the following values…
  • BramPeeters -

    Replied to the thread Hardfault when calling GUI_Clear, thread related ?.

    Post
    Quote from Sven: “Actually, I'm the one [img]https://forum.segger.com/wcf/images/smilies/wink.png[/img] I will add a note to the manual. ” Haha, of course, there can be only one. Thanks :P Now looking at the buffers for my little color problem I see 2…
  • BramPeeters -

    Replied to the thread Hardfault when calling GUI_Clear, thread related ?.

    Post
    I assume in your Task2 if you would have wanted the 1. GUI_GotoXY(0, 0); 2. GUI_DispString("Task2"); to be run on the memdev and not directly on the screen that you would have put a GUI_MEMDEV_Select(hMem); / GUI_MEMDEV_Select(0); around it right ? I…
  • BramPeeters -

    Replied to the thread Hardfault when calling GUI_Clear, thread related ?.

    Post
    Quote from Sven: “Did you unselect the memory device after GUI_Clear() ” Aha, no I did not ! What I do now is : m_hMemDev = GUI_MEMDEV_CreateEx(0,0,DISPLAY_WIDTH_PIXELS,DISPLAY_HEIGHT_PIXELS, GUI_MEMDEV_NOTRANS) GUI_MEMDEV_Select(m_hMemDev); from…
  • BramPeeters -

    Replied to the thread Hardfault when calling GUI_Clear, thread related ?.

    Post
    Hi Sven, GUI_OS is set to 1. GUI_MAXTASK is not defined. Manual says the default is 4. I have more tasks in my system but I am only calling it from 2 tasks now. The * GUI_X_GetTime() * GUI_X_Delay(int) * GUI_X_InitOS() * GUI_X_GetTaskId() *…
  • BramPeeters -

    Posted the thread Hardfault when calling GUI_Clear, thread related ?.

    Thread
    Hi, Based on the discussion in Direct framebuffer access, I started using memdevs. But now I run into an exception during when calling GUI_Clear() when the memdev is active (though it might not be memdev related, so i created new topic). Background: I…
  • BramPeeters -

    Replied to the thread Direct framebuffer access.

    Post
    Hi, Quote: “Unfortunately, not. the hardware routines called by emWin only receive the pure data. ” Yes, but as far as I understand emwin transfers that data to the LCD controller using the GUI_PORT_API.pfWriteM8_A1 function. This function takes a…
  • BramPeeters -

    Replied to the thread Direct framebuffer access.

    Post
    And another realisation: If emwin does now work with a framebuffer, does this mean then when working with a memdev and caching not enabled, a GUI_MEMDEV_CopyToLCD command will do a direct write from the memdev memory area to the display (so no…
  • BramPeeters -

    Replied to the thread Direct framebuffer access.

    Post
    And thinking around the box about my getting to my 'ideal' scenario a bit more: does emwin 'leak' the cache location towards the lower level functions ? Eg if i would trigger a write of the entire screen by filling it with a color will he pass a buffer…
  • BramPeeters -

    Replied to the thread Direct framebuffer access.

    Post
    Hi, Ok, thanks for the super clear & spot on explanation. It even answers one of the questions i had not asked yet, what is the advantage of using the cache :). My ideal scenario would be then to have a cache I can write into but sadly that is not…
  • BramPeeters -

    Replied to the thread Direct framebuffer access.

    Post
    Hi Sven, Ok that is super interesting to know :), thank you. So that means Emwin is not 'aware' of what is currently visible on the screen ? And if i write eg some text on the screen, it will *only* transfer the pixels of the text ? I would have…
  • BramPeeters -

    Posted the thread Direct framebuffer access.

    Thread
    Hi, I already posted a similar question to the stemwin forum but so far without result. I have a board with an external controller connected via an 8bit bus to my cpu, and my pixels are 16bit 565 format. Relevant calls setting this…