MikroElektronika Forum

For years now, flaws and errors in the IDE have been posted. None of them are addressed.
It is very annoying to see that nothing is done to resolve those problems.
I think that all problems probably could be handled in a few days if somebody actually cared...
(this goes for PIC, PIC24, and PIC32 IDE's)

hello

(this goes also for ARM IDE's and VTFT)

wolfgang sachs

arco wrote:For years now, flaws and errors in the IDE have been posted. None of them are addressed.
It is very annoying to see that nothing is done to resolve those problems.
I think that all problems probably could be handled in a few days if somebody actually cared...
(this goes for PIC, PIC24, and PIC32 IDE's)

+1

On the other hand............ I have been using MikroBasic since V4 (about 2006).

I paid (from memory) $149 for the full compiler. I have since had 12 years of free updates.

If this was Mickeysoft it would have cost at least the original price annually, possibly with a "0" on the end.

Maybe there should be an annual subscription to help fund compiler enhancements.

Probably not a popular thought but in these times it may be necessary.

hello

But a few more information than there:
"Have it reported to our developers"
Would cost in the roadmap nothing

wolfgang sachs

True.

Bugs can be already be notified but maybe get ignored, or have to wait for spare capacity with the development team.

Roadmap also seems to have been abandoned. Last update is from 2016...
A crappy IDE (and helpfile) or failing support for new devices is also bad for selling new compilers.
(At the moment I'm hesitant to recommend them to collegues for the lack of support, a pity)

The very long time before new devices are supported is also a downer. We can never use
recent devices, because they are not supported.
(Most devices are years old before the are supported. I had to turn down a few jobs because
the device a client wanted was not supported)

Hello

The fact for me is that the IDE appeals to me from the operation!
But €390 to "turn on and off an LED" show too expensive for me.........
For large projects I failed with VTFT (build and rebuild time)
!! Until today, 1/2jahr later, I do not know if this is changed by the "Men's developers", have for the moment all activities (except request to support...) Stopped!!

A very disappointed customer Wolfgang Sachs

dangerous wrote:True.

Bugs can be already be notified but maybe get ignored, or have to wait for spare capacity with the development team.

bug are notified and confirmed .. some since several years ( !! )
and the answer is always "we forward the bug to the team .. be patient" ..
actually i open a ticket for a serious bug (confirmed by the team) .. this bug prevents me from finishing my job and deliver the job to my customer ..
and the answer since 1 month is "be patient" ...or "if we can solve it, i will inform you asap !!" ...

Team ! stop to ask what enhancement you can do .. simply solve the bugs then we can speak after about enhancement !

regards

Toley wrote:Hi mikroe Team, something very important is missing in that list. A tool to generate defs files for new MCU. This has been requested many times. Then we don't have to wait 2 years or more to use new devices.

I understand files generated with such a tool cannot be supported by mikroe, but once it can generate all the registers and be recognized by the compiler it will be enough to start a project.

Another thing that would be useful is the capability to set fuses by code.

YES!!

Mikroe Team, please take notice, this is definitely Number One on my list!!

Dear Mikroe Team,


Life time upgrades for the compilers sounds great,
but only until there is no money left to add new MCUs and fix bugs.

And we need to get new MCUs added and to get bugs fixed.

How about making a Subscription Service for all your compilers,
where customers can vote to get their MCUs added, hotfixes, or other things prioritized?

If you get 15-20 USD per customer, every year, across all compilers,
there should be enough to get things flowing.

Anyone?

I have Mini M4 tiva board and when I make hex record in Keil I can exchange archive to board with your Bootloader application, I really love this sheets.

arco wrote:For years now, flaws and errors in the IDE have been posted. None of them are addressed.
It is very annoying to see that nothing is done to resolve those problems.
I think that all problems probably could be handled in a few days if somebody actually cared...
(this goes for PIC, PIC24, and PIC32 IDE's)

+1

brelstad wrote:Dear Mikroe Team,


Life time upgrades for the compilers sounds great,
but only until there is no money left to add new MCUs and fix bugs.

And we need to get new MCUs added and to get bugs fixed.

How about making a Subscription Service for all your compilers,
where customers can vote to get their MCUs added, hotfixes, or other things prioritized?

If you get 15-20 USD per customer, every year, across all compilers,
there should be enough to get things flowing.

Anyone?

I think it's more likely the biz plan is as follows: offer the platform at dirt-cheap rate, then make profit off ancillary offerings, like all those breakouts, and such. What seems to be lacking, is the discipline to fold back resources on shoring up the unprofitable IDE. Why should they, we suckers are already biting, so what's the added value?

Hopefully my cynicism is unfounded .

I am not sure how to vote so I will put my vote.

A 1,000,000 million votes for better documentation. With that you will get less questions and a more more sales. Right now it is hard to start a project and to use the parts. The documentation is all over and a lot of missing or very vague.

Example. I2C is advertise on the HMI displays as having 2. However there is no documentation on how to use either, just the routine calls. Are both available or is only 1 available? Same with UART Terminal on the IDE. Nobody can answer the question of how to use this within the program and the IDE other then using the breakout board.