PIC compilers are very important to us, Next one for update is dsPIC, our developers are working on it. Are you guys at mE not ashamed to tell lies so bluntly in the forum ,this exact words we saw 2 years ago ,then 1 year ago and now it is almost 3 years since the last update We are aware we had ne...

Well yes that is one of the old quirks of mE libraries they are not very useful and that is true the mE library only supports 8 bit resolution but that is not the case
of the chip itself

I have realised that in the 2520 the PWM resolution is only 8 bits and the lower 2x bits are not implemented. T Where did you see this ,I never saw only 8 bit resolution on a PIC they are standard 10 bits for PIC18 and higher for PIC24/dsPIC33 I found this in the PIC18F2520 datasheet would be nice ...

Happy to give my opinion

Have good one

Oh... hang on.... so what would be wrong with say TRISC.B4 ? (other than it goes against the MCHP standard). Would this work in a structure and avoid duplication of information? Nothing is wrong with that ,if you only use the mE compiler but the MCP way will ensure you can use it in multiple compil...

[ Disagree that it makes sense, as it says the same thing twice. What would be wrong with maybe, just TRISC4? Well you are entitled to your opinion just a question how would you pack TRISC4 in a structure and have a structure name and the B4 as a member which is the standard way in C to process Dat...

This is the standard Microchip syntax
which makes a lot of sense

In the data sheet of the device which you down load from the Microchip web

Here is the Microchip free boot loader for dsPIC33E and PIC24E devices supports UART and some other means

http://www.microchip.com/SWLibraryWeb/p ... Bootloader

You will wait a long time for mE to do this ,a serial bootloader was asked already 5 years ago with the release of the very first dsPIC30 devices
it still remains a promise use this
http://picbootloader.com/

Hi Your syntax is correct that is also the standard way for the MCHP compiler syntax I would advise you to
make bug report at mE help desk
as a work around use the mE style
TRISA1_bit that compiles correctly as you can see from my screen print

Agreed then it is a compiler issue or a definition that not in the header files

Hi
Did you include the peripheral pin select in the library manager ?

I think the simulation and real hardware work fine but the problem and issue when generate the new Hex file! even though, the MikroC was compiled successfully without any error!! In my opinion the compiler does not generate the correct hex file (1) are you using a licensed version or a cracked vers...

I would suggest that you first move your project to Real hard ,Simulation is exactly what it says simulation and No guarantee included with that Use your generated hex file on real hardware to test ,unfortunately I do not have USB simulation with my Proteus , I used hardware The problem you have her...