Actually, I did not know that jalv2 was a compiler (IDE) as robust.
It has modern libraries (i2c, usb, uart, glcd ...), runs on linux / windows (tested on Windows 98SE), works with the best bootloaders (tinybootloader and picdemusb) and that just as the ladder compiler LDmicro does, he already automatically inserts the magic line 020000040000FA in the code first, then we need not worry about the reset vector.
Moreover, its language is very simple, it is 'like Easter', which makes it, in my opinion, simpler than the own C. Even if there was some difficulty, the examples provided with the compiler has been widely commented, and there a free book on the website.
We can still say that there is a great and gentle community working quite the compiler jalv2. Support is wonderful! And it's free!
I think there is no better tool for PIC's the microchip.
At the moment, I continue using the compilers of MIKROE for 3 reasons:
1) I'm passionate about the BASIC language (use the mikroBasic);
2) Have a lot of friends who use, or ask me, C programs (conversion between MIKROE compilers is very easy because the syntax is similar). This makes it easy to share codes.
3) Recently, I had to help a friend in 8051 and atmel AVR. I started with BASCOM 8051 and BASCOM AVR. However, because the teacher asked programs written in C, did not think twice to use the mikroC PRO for AVR. That is, to change the microcontroller was also easy.
I have read in this forum complaints and suggestions on MIKROE tools in Linux. In my opinion, much more important than that are the drivers.
For example, using the wine, I found some complaints like 'the toolbar buttons do not appear' -clicando twice, they appeared. Or 'text area disappeared' - opening a new project, decided also. Yet seen 'on the wine the system is slow' -I also thought fastest compiler in windows, after the system was designed for windows, but can work well in the wine. All compilers MIKROE I used in Linux ran well on the wine.
My complaint is still on the drivers. For example, I use to uart bootloaders, the Pic-Ready Bootloader v1.00, with FTDI chip. It was very easy to record my pic's (16f877a and 18f4520). Perhaps the MIKROE has not developed more tools for Linux because they do not know if anyone uses ... So I'm saying I USE! lol
Also tested the mikroHIDbootloader with the PIC18F4550 in windows7. It was great! Too bad there is no official HID bootloader version MIKROE under linux.
See the microchip left the MAL (microchip aplication lybraries) available for Linux, and using the piklab can upload codes in picdemusb. I think the MIKROE should do AT LEAST something.
We can in linux use MIKROE compilers, and even upload the code to use UART bootloader. Does not give at all is to use the HID bootloader. For use with the boot of picdemusb, need to change the code of the reset vector (with instruction org), or change the start of the hex file (with the 020000040000FA line) -that wisely jalv2 does automatically.
You could not do only Mikrobootloader HID for linux, for it to be as easy as you would on windows?
Even in MIKROE tools (picflash, avrflash, MikroProg) I see a lot of people asking for drivers ...
Anyone who wants to comment, welcome! Thank for still studying it! The jalv2 support really has been the best!
Anyone who wants to comment, welcome! Thank for still studying it! The jalv2 support really has been the best!
Thank you!