All Activity

This stream auto-updates   

  1. Today
  2. Dr

    Hi, I have just cloned uGFX from https://git.ugfx.io/ugfx/ugfx.git I wanted to test it on a 429 Disco board I have. I was expecting to find something buildable I could just flash to the board to get an idea and verify whether I can work with the tools I have set up: arm-none-eabi and st-flash on Linux. The demo directory readme says nothing buildable, which seems an odd philosophy for "demos". The I looked at ugfx/boards/base/STM32F429i-Discovery/example_chibios_3.x There is a Makefile but again nothing that seems ready to run. I can build and run the chibios demos for this board, so where do I find what I need to test uGFX ? Thanks.
  3. Yesterday
  4. Last week
  5. Thanks!
  6. This is not at all related to your initial problem / the topic of this forum thread. We're happy to help wherever we can but please at least try to figure out what the problem is. Googling the error(s) you're getting would instantly give you results. Furthermore, the demo you're trying to compile even comes with a readme file that explains what to do: In order to run this demo you will have to link against the math libs. You can do this by adding -lm to the LIBS variable in your Makefile: LIBS = -lm
  7. Ok, thanks, I've just launched mandelbrot example, and it works fine. But now I trying another example(bubbles), and I have this message: Linking .build/hello_world /tmp/cci1nNng.ltrans0.ltrans.o: In function `initialize': <artificial>:(.text+0x1b64): undefined reference to `sinf' /tmp/cci1nNng.ltrans0.ltrans.o: In function `matrix': <artificial>:(.text+0x1c22): undefined reference to `sqrt' collect2: error: ld returned 1 exit status ../resources/ugfx/tools/gmake_scripts/compiler_gcc.mk:282: recipe for target '.build/hello_world' failed make: *** [.build/hello_world] Error 1
  8. Here: http://api.ugfx.io/group___colors.html You can add your own color format if you need something specialized. Eg. some people on this forum added color formats with an alpha channel.
  9. So where I can find list of all supported color systems?
  10. Although not specified above i am guessing that you are using the linux framebuffer. If so what that message is saying is that GDISP_PIXEL_FORMAT does not match the capabilities of the framebuffer linux driver for your machine. Try changing that macro in your gfxconf.h to match the hardware capabilities.
  11. You need to get someone who can understand English better to help you with the instructions above. The instructions above have been clear and simple. We speak a limited range of languages and we run this forum in English. We do our best to help but we can't help where our words are not understood.
  12. my main.c Nothing extra is defined,and nothing code.only demo code. Could it be wrong to dial.h? How can it be. main.c.txt
  13. It's part of the board file of the framebuffer. Have a look at the board file template that you can find in the driver directory (/drivers/gdisp/framebuffer/board_framebuffer_template.h). You might want to get the latest master branch of the µGFX repository to get all the latest framebuffer driver goodness:
  14. Note that this is not about #defines. This is about function definitions (the C functions). There must only ever be one function named main in the entire program/application. The project you're having has two: One in main.c and one in gui.c. Simply remove the one in main.c (because the one in gui.c is the one from the demo that does everything you want) and you can continue to compile. Then you'll hit the next problem as described above.
  15. Hello everybody, where i can set framebuffer bitness? I got this error: GDISP Framebuffer: The display is 8 not 32 bits per pixel
  16. I looked at the link below. He was talking about the error you said. But there is nothing defined in my main.c file. Could you edit the example of the dial widget for the keil. So it could be a good example for everyone. I guess I do not understand :-) http://www.keil.com/support/docs/3724.htm
  17. This is the error when just building the project you attached without any modifications: compiler_output.txt These are the two only errors: .\Objects\Widge_Create_Ugfx.axf: Error: L6200E: Symbol __ARM_use_no_argv multiply defined (by gui.o and main.o). .\Objects\Widge_Create_Ugfx.axf: Error: L6200E: Symbol main multiply defined (by gui.o and main.o). It tells you exactly what your problem is: You have multiple definitions of the main() function. It even tells you where they are. So currently your problem is that you have your own main.c() and the one that comes as part of the demo. Simply commenting out your own main() function allows you to get rid of that problem. Then, you'll hit the next problem: .\Objects\Widge_Create_Ugfx.axf: Error: L6218E: Undefined symbol dialGCreate (referred from gui.o). .\Objects\Widge_Create_Ugfx.axf: Error: L6218E: Undefined symbol dialGetAngle (referred from gui.o). .\Objects\Widge_Create_Ugfx.axf: Error: L6218E: Undefined symbol dialSetAngle (referred from gui.o). .\Objects\Widge_Create_Ugfx.axf: Error: L6218E: Undefined symbol assert (referred from gfx_mk.o). You haven't added the other source files that came as part of the demo/widget to the project (you're missing dial.c and probably dial.h is not in the include path, but I haven't checked that).
  18. This appears to be related to a miss match of the floating point flags.
  19. It looks like a problem with your cross compiler. The compiled code seems to be using a different c calling convention to the c library. Run some test cross compiles with simple hello world programs first to make sure your cross compiler is working. Also try it using the same compiler flags uGFX uses (that's why each uGFX compile prints the options first). You can also try compiling uGFX for your host machine. That will at least demonstrate that uGFX works. Note it is very important to do a "make clean" between each change in platform or options.
  20. I fixed this with simple rebuild.... Try make clean, maybe it will help
  21. I sent you the error. I still get the same error .
  22. Hi All, Maybe I should start the new topic but ma setup is very similar and I have a building problem as well. I'm trying to make the first step and familiarize myself with uGFX but I can't build the basics demo without errors. My Host OS is Ubuntu 16.4 and target is OPOS6UL board (ARM Cortex-A9). Please find attached building log and makefile. Would be great if somebody could help me in this case so I can make a progress. Thanks in advance, building log.odt Makefile
  23. I just had the time to download and try building the project. Did you even read the error message that you're getting? It tells you exactly what the issue is.
  24. The µGFX library currently doesn't come with a built-in driver for the ILI9327 so you'd have to write your own GDISP driver. This should be very straight forward as everything is well documented and as there are literally dozens of examples (existing drivers). I assume that you can just copy the existing ILI9325 or ILI9320 driver and modify it to work for the ILI9327 display controller.
  25. Hello. How to use ILI9327 chip ?
  26. Have a look at the GDISP driver / GDisplay documentation. It tells you the function signature (the function name is gdisp_lld_fill() or something like that, that the linker will try to link against). If you implemented the hardware filling functionality into your driver correctly then it should just work. Maybe you forgot to set the corresponding define in the driver configuration file. You might want to have a look at some of the other drivers that implement hardware acceleration.
  27. Usually you'd want your event loop to run in its own thread so you'd use TIME_INFINITE as the timeout parameter of geventEventWait(). This solves all your problems. Keep in mind that you have to use gfxSleepMilliseconds() instead of HAL_Delay() in any case as pointed out by @inmarket.
  28. I inserted HAL_Delay as a way to simulate a large blocking event. I set the timeout 0 wanting to avoid spending the timeout value waiting for an event. What I did was follow your instructions from 2, inserting a check for NULL, as in the code below, and seems the issue is gone while (1) { /* USER CODE END WHILE */ // HAL_Delay(50); gfxYield(); // Get an event pe = geventEventWait(&glistener,0); if (pe != NULL){ switch (pe->type) { case GEVENT_GWIN_BUTTON: if (((GEventGWinButton*)pe)->gwin == ghButton1) { guiShowPage(1); } if (((GEventGWinButton*)pe)->gwin == ghButton2) { guiShowPage(0); } break; default: break; }} /* USER CODE BEGIN 3 */ }
  1. Load more activity