Joel Bodenmann

Hello and welcome to the community! There is no such thing as an 'ECOS package'. The ECOS support is built-in into the library. All you have to do is setting GFX_USE_OS_ECOS to TRUE in your configuration file. About the master-slave: I'm not sure if I understand you correctly. When you want to have your GUI running on the master and the slave is just a passive terminal (the actual screen with touchscreen), this can be done easily. uGFX supports remote displays through the uGFXnet driver. ~ Tectu

Where does the Delay() function come from? Can you show us it's implementation? I haven't worked with the stdperiph library for a long time. ~ Tectu

So this issue is actually resolved now?

This means that solijoli should use the master branch in that case. @steved: I will let you know once I ported the driver. But days are currently very busy. Don't expect anything within the next 8 days please. ~ Tectu

Oh... I remember that there was something... Did you port the driver to the new driver structure from the newmouse branch? We'd be more than happy to add your driver to the repository ASAP then Otherwise I'll port it myself if you (re)provide us with your driver that works with the current master branch. However, I'll need you to test and probably debug it. ~ Tectu

Hello solijoli and welcome to the community! First of all, please note that the tutorial that you are refering to uses a rather old version of uGFX. Many things changed (to the better) by now. We are close to release the new drivers interface that makes it A LOT easier to write new drivers. Therefore, I'd recommend you to check out the newmouse branch of the uGFX repository in order to implement a driver that will be compatible with all the new upcoming uGFX versions. But sadly we don't have any available documentation to that yet. However, the already ported drivers should be more than enough to see how you have to implement a driver. And if you ever hit any problem, the forum is always there for you! A general advice: When starting to implement uGFX into your project, it is strongly recommended to start off just with the GDISP module enabled. Using this minimal configuration it is a lot easier getting your project set up and compiling. You should even start by taking the empty board template for your GDISP driver (in your case it is /drivers/gdisp/SSD1963/board_SSD1963_template.h) and try to compile with that one first. Edit: As I just see, steved seems to help you out with this one As far as I know he already uses the new driver structure as well! Let us know when you have any questions. ~ Tectu

Glad to hear that it compiles Just use the systick API from the standard peripheral library to implement these two functions. ~ Tectu

That is "just" the compiler (and linker) and so on. Make is not part of that package. I agree - I've had the very same experience. Let's see if he can successfully build the unmodified ChibiOS/RT demo first. ~ Tectu

As he uses ChibiStudio, he's quite certainly using Windowsindeed. However, I think that ChibiStudio comes with its own tool. There should not be a make related issue unless he installed a custom toolchain. @electrotehnik: Can you please try to compile an unmodified ChibiOS/RT demo project? (like the /demos/ARMCM3-STM32F103) ~ Tectu

Hi, Can you please specify which version of ChibiOS/RT you are using? I don't think that this is an uGFX related problem. I just compiled a project with ChibiOS/RT 2.6.6 and an STM32F103 as well. It worked without any problems. Please make sure that you always use the ChibiOS/RT provided Makefile and just modify it as described in the wiki as they change sometimes. ~ Tectu

This is definitely not an uGFX related problem. Please open a new thread whenever you hit a new problem. This way we keep the forum clean and it is easier for people to find answers using the forum search. I can try to compile it as well and point you to the actual problem then. ~ Tectu

It is recommended to copy the /drivers/gdisp/ILI9325/board_ILI9325_template.h file to your project and keep it's routines empty so you can see if everything compiles successfully first. This will save you a lot of trouble. From there you just have to use the STM stdperiph library functions to control your microcontrollers peripheral. There is sadly no example/template available for this setup. ~ Tectu

Can you please post the full compiler log? I will try to test it tonight but I cannot promise you anything. ~ Tectu

You're welcome. Feel free to open a new thread if you hit any problem / having a specific question. ~ Tectu

No problem. Feel free to start a new thread when you have any problems. ~ Tectu

This thread / the post containing the link is over one year old. It is not possible to update every outdated link on the forum. If you are searching for the current guide, you can find it here: http://wiki.ugfx.org/index.php?title=Getting_Started ~ Tectu

Hello Roman and welcome to the uGFX community! 1. Sadly we are not able to create a ready-to-use project for you as it takes a lot of time. However, the wiki is very detailed on what you need to do in order to get uGFX running. The forum is always there to ask specific questions. If you are a commercial customers please contact us through the mail address that can be found here: http://ugfx.org/imprint 2. You do not have to use ChibiOS/RT when you want to use uGFX. There are many other already supported underlying systems such as FreeRTOS. However, you can really use it with any system. You can either use the raw32 port to use it bare metal (= without any operating system) or you can easily implement a new operating system port following our wiki guide. ~ Tectu

I like what I see so far Keep it up! ~ Tectu

Glad to hear! Once "completed" we can put it on the official website if you like ~ Tectu

inmarket, either you or I have misunderstood his post. From what I got he will use uGFX and he's trying to put together a good project structure and he's asking us for advice. ~ Tectu

Hello LeMoussel and welcome to the community! It looks like you are spending a lot of time and effort into this. So far it looks good. Is this going to become a tutorial-like guide? Feel free to ask whenever you have any questions about the uGFX project. ~ Tectu

I can only confirm that there are huge quality differences in the TFT modules available. However, at the end you get what you pay for It is also correct that µGFX does currently not support any image or shape rotation. However, this should indeed be added at some point in the nearer future. Feel free to share your implementation with us and the community in case of you're going to implement it yourself. ~ Tectu

Hello juppeck I agree with your statement that a homogene IDE such as Keil is a lot easier for beginners. I don't use Eclipse myself and I never understood why especially all the beginner tutorials seem to use it as it is rather difficult to set up. However, Keil and other proprietary IDEs are not popular with beginners and DIY people as they have either a built-in size limit or are expensive (usually both). And when working with a graphics library such as µGFX, 32kB binary size really is not much. Note that µGFX itself has no such thing as 'prefered Compiler' or 'prefered IDE'. We spend a lot of time and effort into keeping uGFX free from any IDE or compiler bindings. In fact, that seems to be one of the reasons why µGFX is so popular with commercial and DIY users. It is true that most of our DIY users are using GCC but this is simply due to the fact that it is free to use without any restrictions. Some of those users are either using the Makefile based system, Eclipse or CoIDE, now Em::Blocks seems to become popular as well. Commercial users on the other hand seem to usually use either Keil or IAR, both of which work just fine with uGFX as well. Same as above: uGFX is held generic. It is not bounded to any underlying library. Therefore you can use whatever you like. It is true that most of the example board files are ChibiOS/RT specific. The FSMC line that you posted comes from a ChibiOS/RT usage examples from quite a long time ago. Replacing it with your suggestion (which is indeed more readable) would force the user to include the Std-Library in the ChibiOS/RT settings which adds a huge overhead. As a summary: You can use whatever you want and we don't expect you to face any issue. If you are having difficulties using a specific IDE or compiler, please let us know as we are interested in removing these kinds of boundaries ~ Tectu

Usually there is nothing to do but optimizing the FSMC timings in the board file to archive a reasonable performance. This is pretty much the same with uGFX. Benchmarks show that around 32 FPS are doable with this setup. ~ Tectu

Sorry for the late reply. I hit the post "Submit" button whilst being in the train it seems like I lost the signal there... Apologies. I confirm that there is a problem with the defines (the warnings that you see). I will try to fix this tonight. However, you are still able to create a successful build. Does it work for you? If not, can you describe the symptoms? (eg. does mounting work and just read() or open() fails etc). ~ Tectu