Post navigation

McuOnEclipse Components: 1-Apr-2018 Release

It’s April Fool’s Day, but be assured this is not a joke ;-): I’m pleased to announce that a new release of the McuOnEclipse components is available in SourceForge. This release includes several smaller bug fixes and components have been upgraded for FreeRTOS V10.0.1.

Thank you, for the new components. Recently I have got PCAL6524 IO expansion chip sample from NXP. Chip has has useful debounce filter for use with push buttons on our joysticks. Now, I am trying to make component PCAL6524 similar to PCA9554 existing in PE component. Is it possible to be added to Component Libraries?

Hi Marceli,
I have not used that PCAL6524, but it looks like an interesting device. I won’t have the bandwidth to create a driver for it, but I’m sure you would be able to create such a component yourself?

No, there is no such template. Things are pretty much in normal C language with some extensions (special keywords starting with % character). The framework is called CDE (Component Development Environment).

To be honest, I tried that CDE inside Eclipse, but it had too many issues and bugs. So I sticked with the ‘classic’ Bean Wizard from CodeWarrior (which is only available in the Pro edition).
So if you do a component with the Eclipse based CDE, it won’t be backwards compatible with the BeanWizard, so it would be rather hard for me if you want to add it to the McuOnEclipse library because I won’t be able to maintain it.
But this does not stop you from doing your own thing.
As for copy: you can ‘clone’ or copy an existing component, maybe this is the way to go for you? Other than that: the CDE files are text files, in many cases I use a normal text editor to edit them.

I use the SSD1306 Drive Display. I’m having trouble refreshing the screen by the Clear () method of component SSD1306. Every time I use the Clear () method and then write on the display again, it is possible to notice the screen being erased and written. I wish this was not remarkable. how to solve this?

The reason is that Clear() does UpdateFull() att he end.
You can use the GDisplay component which has a higher level interface to the display.
In that component there is a Clear() method too, but the display is only affected after to call its UpdateFull() method().
So I recommend you use the GDisplay component for the SSD1306.
But I could add a ClearBuffer() method to the component too?

I checked GitHub, but it looks I have not published any example about it :-(.
I see that I can publish one. Until then, here is an example:
static void Demo3(void) {
PIMAGE image = ImageWait_GetImage();
FDisp1_PixelDim x, y, xCursor;

Hi Erich,
I am trying to use the SEGGER_RTT module from the McuOnEclipseLibrary repo.
Can you tell me why the McuLib.h file is included in the SEGGER_RTT_Config.h file ?
It did not seem to be included in previous versions of the files (before 1st april update).
I would like to avoid including any file outside of the SEGGER ones.

Hi Nathan,
It is used because some ‘global’ settings from McuLib.h/McuLibConfig.h are used, for example McuLib_CONFIG_SDK_USE_FREERTOS.
That’s currently the only setting (so you could hardcode that one), but in the future other settings might be added.
I hope this helps,
Erich

There is no technical limiation for a larger font size, but the ones I have implemented are going up to 24 pixels. I had no need for larger fonts.
But you certainly can create your own and larger font.