Most desired upgrades and enhancements for MikroE compilers

[pavel]

Hi,
The function on your list "TFT Get Pixel routine in the TFT library" is really my MOST wanted one for a long time. A picture redrawing would be so easy... ME team on Forum announced that this function is on the wish list a long time ago. But no implementation yet. Hope, will be added soon. Thank you. Good luck with compiler enhancements/upgrades to ME team!

Best regards,
Pavel

[feuerwolf]

Support for RTOS in mikroC PRO for PIC32
DMA library
I2C timeout

I desperately would like the IDEs to be able to view more than one File at the same time. Being able to open and view two or three file/windows in a split screen would be a huge workflow improvement.

[tm01]

Hi
Since VisualTFT will go into the compiler, I think that my requested feature should stand on this list:

Since a few years I am waiting for 16Bit support of SSD1963 Displays with 800x480 resolution. There are many posts in the forum about that. mE announced that feature years ago. Since Jan 2015 a 7" tft with that controller and that resolution is in the mE shop. I hoped the VisualTFT update would come soon. But it didn't. I think that I'm not the only person who need that feature.

[dibor]

COFF file compatible with Proteus and Atmel AVR Studio for AVR's.

[qwepoi]

90% of updates are about PIC's . If you follow my posts you know there is a deal between mikroelektronika and microchip.
for example look at the AVR compiler or ARM stuff .... how many proposal do you see ? . zero .... ????

[sshahryiar]

I have a number of suggestions for MikroE compiler updates although I voted my favourite three already and some are not even listed here. Thus I'm enlisting my wishes for compiler improvements here:

1. Complete DMA library for ARM, ATXMega and other MCUs that have it.
2. FSMC library.
3. I2S library.
4. Analog comparator library.
5. Watchdog library.
6. Capacitive touch library.
7. GPIO library for setting pin/port states and receiving pin/port logic states. (not GPIO pin configuration library)
8. IR communication library for MCUs with IR receiving units.
9. RTC library for MCUs with built-in RTC modules.
10. CRC, AES and DES libraries.
11. Display controller libraries for MCUs with built-in display controllers like STM32F429.
12. USB library improvements as to support USB OTG and CDC classes.
13. USB library for ATXMega and AVR MCUs that have built-in USB hardware.
14. Timer library as such that the user can configure input capture mode, cascading, etc other than time base generation and PWM.
15. Advanced ADC functions for dsPIC, ATXMega and ARM.
16. I2C timeout functionality for I2C library.
17. RTOS support for ARM, AVR and PIC32.
18. Integration of STM32CubeMX with MikroC for ARM.
19. Graphical clock configuration tool for ARM, ATXMega and other chips that have multiple clock sources.
20. Easy built-in functions for printing numerical values, e.g. variables.
21. Improvements of ethernet and storage libraries with more simple examples.
22. Examples of RS485 and CAN like MODBUS and J1939 CAN protocol.
23. Examples for making video and music players.
24. Correction of library examples and documents.
25. Support for TFT and OLED controllers like ST7735, ILI9325, SSD1306, etc.
26. Support for STC microcontrollers in MikroC for 8051.

I know it’s easy to make a long wish list and not always easy for developers but I believe these additions will surely improve MikroE compilers a lot. Best wished for the developers.

[fred85]

90% of updates are about PIC's . If you follow my posts you know there is a deal between mikroelektronika and microchip.
for example look at the AVR compiler or ARM stuff .... how many proposal do you see ? . zero .... ????

You're kidding right? Some PIC compilers haven't been updated in years. The last 8b one was just a licensing update the one before that wasn't really meaningful and was buggy as hell.

They probally have deals with all the ARM manufactuers to. AVR was bought by Microchip.

[p.erasmus]

90% of updates are about PIC's . If you follow my posts you know there is a deal between mikroelektronika and microchip.
for example look at the AVR compiler or ARM stuff .... how many proposal do you see ? . zero .... ????

You seem to be blind and can not read there are a few ARM related provements

To your Comment
(1) dePIC compilers did not get an update nearly 2.7 year while the ARM Compilers had 3- 4 updates including addition of New Families of microcontrollers
(2) the PIC 32 compiler has seen 1 update againt ARM compilers
(3) PIC compiler has seen 1 update more that 1 year ago

get your fact right before you post false infomation

[SimonD]

My first wish (i would say demand) is an EQUAL SUPPORT for LIBRARIES, DRIVERS and EXAMPLES for other compilers such as BASIC and PASCAL. Please don't forget that we have pay .. equal ...
Maybe your problem is the human resources, but this is your problem ... and this is not excuse for your customers ...
If i can propose something else in your list this is a library (and not only for C) for the most popular Touch Controller in the market at this moment, the XPT2046.
Thanks again

[ilferrari]

My first wish (i would say demand) is an EQUAL SUPPORT for LIBRARIES, DRIVERS and EXAMPLES for other compilers such as BASIC and PASCAL. Please don't forget that we have pay .. equal ...

Totally agree, each compiler costs the same, so they should get the same support and features. You should make a tool to convert code and projects between languages.

One feature I would like to add to this list is struct pointers for MB (-> in C).

[ilferrari]

I desperately would like the IDEs to be able to view more than one File at the same time. Being able to open and view two or three file/windows in a split screen would be a huge workflow improvement.

You can already do that. Click on the file tab and drag across the screen.

[arco]

Timeout for i2c routines would be nice. Also as mentioned before, fixing the IDE would be.
I mentioned numerous very annoying flaws over the last 5(!) years of which none has been addressed regrettably...

[Kalain]

Hi,

The most important thing before to add new features is to fix all known bugs.

[janni]

The most important thing before to add new features is to fix all known bugs.

This, unfortunately, never seems to be a priority . Fixing bugs is much more demanding than writing a library or two (or promising to do that ).

On the other hand, one doesn't have to be a marketing guru to see the difference in appeal between 'many new features!' and 'many bugs fixed!' .

[Toley]

The most important thing before to add new features is to fix all known bugs.

This, unfortunately, never seems to be a priority . Fixing bugs is much more demanding than writing a library or two (or promising to do that ).

On the other hand, one doesn't have to be a marketing guru to see the difference in appeal between 'many new features!' and 'many bugs fixed!' .

I completely agree, fixing existing bugs should be the priority. But to do that they should list the bugs first. Everytime someone report an old bug on the forum, they act like it's the first time they heard about it.