pwdixon wrote:I want to make some changes to a standard library is there a way to do this in ME?

You would practically have to hack the library (object) file directly...

Is it possible to use the library for the T6963C from the dsPIC C compiler with standard PICs? No, it is compiled for dsPIC, whose core is totally different. Don't worry, next (service) release of mikroC for PIC is couple of weeks away, and it will have this library included, together with the Bitm...

You'll have to update the driver first. In the dsPICFLASH folder you have folder for the WinNT driver. Update the existing driver from there. I spoke too soon. You seem to have the version with USB1.1 driver, right? If so, under <Tools..Options..Tools>, under "PIC Flash Programmer Settings", select...

You'll have to update the driver first. In the dsPICFLASH folder you have folder for the WinNT driver. Update the existing driver from there.

Your existing activation key should work on the ghost'ed disk, too.

You can either use bit fields or good ol' masks.

It's a bug that has been discovered after the latest mikroC release (5003). The flash_write() in Bootloader(s) works OK, but this one doesn't. Anyway, the error has been corrected and updated library will bi available with the next maintenance release, which should now be couple of weeks away. If yo...

I'm using the bootloader code on an 18F8520. When the new program hex file has completed transfer the PIC remains in a loop waiting for more data and the user must cycle the power on the PIC to start the new program. Is there any way a timeout could be applied or the number of hex bytes be counted ...

Current (the only one) bootloader for PIC16s works only for those with 8K program words, such as 16F877A. Besides, I think 16F628A is not self-programmable anyway.

You can put interrupt() function anywhere you wish, and you don't have to declare it (at all), .... it will be linked properly.

ivan1979 wrote:I have some problem with terminal communication tools intergated in MikroC. I can't connect to COM at 115200 Baudrate, but I can at all Baudrate <115200.

This is a known bug. Please take a look at http://www.mikroe.com/forum/viewtopic.php?t=1839

ascomm wrote:Yes, but nothing happens. The serial connection is working as I can send and receive data with same pic programmed with other serial comms programs.

I tried the bootloader on 18F252 @20MHz, with SPBRG = 129, it works.

sevanjam wrote:thanx for your help, but i read from one of the posts that i need to add an empty line at the end of my code , and that solved the problem...

This has been solved starting from version 5.0.0.0.

After you press reset, you have about 3-5 seconds to click the <Connect>button on the mikroBootloader tool. If all goes OK, you'll have the "Waiting for response...Connected" message, otherwise it will be "Waiting for response...Disconnected".

Dear beta testers, Fresh beta build of mikroC for dsPIC is available for download. The location is: http://www.mikroe.com/zip/mikroc_dspic/mikroc_for_dspic_1002_beta.zip . Please upgrade your installations on this. You can read about the new features in the "Whats New.txt" file. Installation is abou...