Most of the functions declared by <string.h> are missing const qualifiers. For instance, void *memcmp(void *s1, void *s2, int n); should be void *memcmp(const void *s1, const void *s2, int n) Note that "const" on the arguments does not imply that the strings are in ROM or will never change, it means...

Is there any sample code to determine max stack usage for Mikroe projects? (ARM)

I try to compile the source code of the Mikromedia plus for STM32F7 but I get this error: "207 438 Call signature does not match the function definition signature 'Mmc_Multi_Read_Sector' __Lib_FAT32_Driver_STM32.c" I installed the FAT32 library "1461660309_fat32_library_mikroc_arm.mpkg" and use the...

Hi Look here https://libstock.mikroe.com/projects/view/108/fat32-library I am using this library for a Mikromedia Plus for STM32: https://libstock.mikroe.com/projects/download/108/4804/1483702589_fat32_library_mikroc_arm.mpkg It does compile. I have successfully written a file -- once! -- but I am ...

Now that MicroC Pro version 5.0.0 is out, I tried what was suggested before -- run the installer as Admin -- i.e., right-click, then "run as administrator". No problem installing, but when I start the compiler as a regular user, I still see the same dialogs. So basically, installing as administrator...

Any ideas how I can diagnose this? It just happened after a minor edit and undoing the changes does not help When I compile, I get the dreaded final error notice, but no other error messages. Every file compiles successfully, and there are no messages about memory usage. 0 102 Finished (with errors)...

When I am in the debugger, it would be incredibly useful to be able to see where you are in the calling tree. A separate stack window that I could bring up from View> would be perfect.

Of course, you won't want to do that if you are using the Mikroe libraries.

I found a bug in MikroC Pro with large arrays, i.e. any array with more than 65536 entries -- and it actually looks like it's a problem for any array with over 65536 bytes. I don't know the actual limits here, just that I got burned. I haven't found any relevant advice in the forum although it does ...

When I am in the debugger, it would be incredibly useful to be able to see where you are in the calling tree. A separate stack window that I could bring up from View> would be perfect.

It would be great to one for the "mikromedia plus for STM32F7", too.

(Same STM32F746ZG, but a 4.3-inch display instead of 7-inch)

I was able to hack up mikromedia 7 code to work, but it would be nice to have it work for this board out-of-the-box.

Now that I understand it, I can live with the current behavior.

I'd just like to see it fixed in a future version. Thanks.

I don't really understand the original post, but you should be aware that testing floating point for equality against a constant is usually a bad idea. The reason is that floating point is only an approximation for most fractional values you can write. For example, you cannot represent 0.1 exactly i...

I would like the "find" dialog to be persistent, at least on Windows. Explanation: While examining code, I often look for text in the same file -- Edit>Find, or ctrl-F. Enter the search-for text, then click "OK". This works fine ... except that the dialog disappears. To search for the same text agai...

Are you looking for the compiler to automatically use DMA for (large) memory operations? DMA is hardware -- well, strictly speaking, a feature of some hardware devices. For example, Analog-to-Digital converters are typically connected through DMA so you can collect many samples without polling. I wo...