Migration from mikroC for PIC
Posted: 16 Apr 2020 18:39
Hi, there are several questions that I couldn't find an answer, so I hope someone from ME could offer clarification.
1. CODEGRIP debugger hardware for PIC isn't available yet. When it will be available?
2. Would there be 3 different CODEGRIP versions (PIC, dsPIC, PIC32), or just 1 covering all PIC architectures?
3. Can we **finally** define config fuses and oscillator frequency in code? This is my biggest hurdle with MikroC compilers. Change the chip, have to MANUALLY set everything all over again. Compiling firmware for 3 or 4 different chips at once is a nightmare!
5. Will mikroProg programmer/debugger firmware continue to be updated with new chips?
6. Does Necto PIC compiler supports extended instruction set in some PIC18 families (PIC18 K22, Q42, etc.)?
EDIT:
7. Do we lose rights to our MikroC for PIC license when upgrading to Necto Studio?
1. CODEGRIP debugger hardware for PIC isn't available yet. When it will be available?
2. Would there be 3 different CODEGRIP versions (PIC, dsPIC, PIC32), or just 1 covering all PIC architectures?
3. Can we **finally** define config fuses and oscillator frequency in code? This is my biggest hurdle with MikroC compilers. Change the chip, have to MANUALLY set everything all over again. Compiling firmware for 3 or 4 different chips at once is a nightmare!
5. Will mikroProg programmer/debugger firmware continue to be updated with new chips?
6. Does Necto PIC compiler supports extended instruction set in some PIC18 families (PIC18 K22, Q42, etc.)?
EDIT:
7. Do we lose rights to our MikroC for PIC license when upgrading to Necto Studio?