Firstly thank you for this library, it has solved my issue exactly. I have however noticed something that I'm confused about. I have run both the 'Small" and "Fast" AES demo projects against a 18F2680 and got the following build sizes; Small = 5812 bytes Fast = 5468 bytes So it looks like the small ...

I would like to suggest two improvements for the PIC MicroBasic (and possibly other) compilers. I would like to add a right click menu option when clicking on a function in the code explorer to take you to the function implementation. I am aware that you can double click on the function and it does ...

Thanks, just what I was looking for.

Rohan

I have been writing code for my product for over a year now, and it is working very well. However I am starting to run out of space in my PIC and I wanted to try and optimise the code to save space. I have found a couple of odd things by experimenting, such as moving repeated code into a subroutine ...

Is there (or has anybody developed) an industry standard encryption library of some sort, that can be used for the exchange of information between 2 systems? I'm thinking of something like AES or triple DES or whatever? I want to be able to send an encrypted sign on sequence between 2 devices, one w...

Has the situation regarding the need to manually copy files between versions when upgrading to V6?

I notice the V6 installer still wants me to uninstall the previous version before installing the new, thus losing all my custom settings.

Regards

Rohan

I understand that there are differences in the actual MCU, but from what I can see that is all taken care of at compile time. When I look at the hex output file it contains intel hex encoded data that has the target address built in to the encoding. All the boot loader appears to do is decode the in...

I am writing my own front end to communicate with the example PIC bootloader code. It all looks pretty straight forward, but one thing I notice on the mikroBootloader is the MCU selection which toggles between PIC16 & PIC18. Can you tell me what difference it makes when choosing one MCU over another...

I found what I needed here http://www.mikroe.com/forum/viewtopic.p ... 4&p=191515

And from that topic I have deduced that it is the bootloaders settings that ultimately are used.

If I'm wrong, then let me know.

Rohan

I am trying to understand how the configuration bits are set when using the MikroBootloader. I have a board with a pic18f2680 that I have loaded the correct bootloader onto and then used it to load the actual program hex file. However in the real application I have the watchdog set, but in the bootl...

Thanks for your help Robert. I had considered your method, but unfortunately in my case, I need to read the external uart inside the ISR or I risk a buffer overflow. Setting a bit and waiting for the main loop to check it is too slow, as some of the main loop routines can take longer than it takes f...

Thanks Janni.

The example looks clear and straight forward.

I also like your article on reenterency.

Thanks for your help.

Regards

Rohan

There is a method to call same procedures from two threads if one takes care there's no real reentrancy, but I wonder why don't you perform all I2C communication in ISR? If necessary, you may even force interrupts from main code, which is equivalent to calling from main. That is the lateral thinkin...

The problem is not how to make interrupts work or how the ISR works, but the fact that you cant call the same i2c routines from within the ISR and the main loop. This is a limitation of the compiler. It places this restriction on the code to protect the programmer from unknowingly corrupting the sta...

The question is more generic than that. What I want is an example of how to do anything with i2c inside the ISR when the same i2c routines are in the main loop. In fact it is not even restricted to i2c, it could be anything that requires communication with an external chip, SPI, UART, ect. Any exter...