How to proceed without a device definition
-
- Posts: 64
- Joined: 01 Mar 2016 15:39
How to proceed without a device definition
I need to write code for the new PC16LF18323, but the device definition is missing. It would appear mikroC Pro isn't usable without the right definition. What do I do now?
Re: How to proceed without a device definition
Either find another chip that is supported by the compiller or use another compiller. The PIC compillers are not kept up to date and in some cases are lagging by years. Mplab is free.
see
http://forum.mikroe.com/viewtopic.php?f ... 4&start=30
Basically if you buy a PIC compiller or any of their PIC hardware all the proceeds go to their ARM or FTDI compillers.
Its been over a year since a meaningful update was done on their 8b compiller so I wouldn't hold my breath. There is also a matter of this bug
http://forum.mikroe.com/viewtopic.php?f=88&t=65692
see
http://forum.mikroe.com/viewtopic.php?f ... 4&start=30
Basically if you buy a PIC compiller or any of their PIC hardware all the proceeds go to their ARM or FTDI compillers.
Its been over a year since a meaningful update was done on their 8b compiller so I wouldn't hold my breath. There is also a matter of this bug
http://forum.mikroe.com/viewtopic.php?f=88&t=65692
Re: How to proceed without a device definition
you can wait for the standard reply of: `unfortunately it is not supported yet, will forward/suggest to developers, will be fixed in a later update.`
come back in 3 more years to find nothing has been done assuming mikroC is still around and being supported... if you consider what they have been updating as support, next update will only include vtft and maybe some minor bug fixes.
or do as fred85 suggests, your chances of it being fixed are zero to none.
come back in 3 more years to find nothing has been done assuming mikroC is still around and being supported... if you consider what they have been updating as support, next update will only include vtft and maybe some minor bug fixes.
or do as fred85 suggests, your chances of it being fixed are zero to none.
Re: How to proceed without a device definition
Thats what you will hear from mE.checker wrote:you can wait for the standard reply of: `unfortunately it is not supported yet, will forward/suggest to developers, will be fixed in a later update.`
unfortunately this is truecome back in 3 more years to find nothing has been done
This is also trueyour chances of it being fixed are zero to none.
mikroC once was a great tool for PIC however that has changed since they added the ARM compilers they have abandoned the PIC compilers although thy try to say otherwise in the Forum but thats all just lies to keep on selling PIC compilers that the revenue can support the ARM development they day will come when they are honest and say that they discontinue PIC move on while you have the chance
P.Erasmus
Saratov,Russia
--------------------------------------------------------------
Saratov,Russia
--------------------------------------------------------------
- biljana.nedeljkovic
- mikroElektronika team
- Posts: 1043
- Joined: 30 Jun 2015 15:15
Re: How to proceed without a device definition
Hello,
We appreciate any kind of feedback.
If we decide to ever abandon any of our compiler lines, we will announce it.
I assure you PIC compilers are still active and we have on our schedule to have an update for it.
This MCU will be supported.
Best regards,
Biljana
We appreciate any kind of feedback.
If we decide to ever abandon any of our compiler lines, we will announce it.
I assure you PIC compilers are still active and we have on our schedule to have an update for it.
This MCU will be supported.
Best regards,
Biljana