I have a ticked logged for this, but I was wondering if anyone else is seeing 7.1.0 builds either ending with "Finished with errors" without any errors in the code, or displaying that message just after building the delays library. We usually find that it will build fine the first time, maybe the fi...

Hi, Yes, I agree with you. Just one note, Brown-out Reset Enable bit is in CONFIG1H<0> ,page 555: http://www.mouser.com/ds/2/268/30575A-243037.pdf Maybe your problem is because that CONFIG1L<0> is U-1 (not writable bit). Kind regards, Aleksandar Yes, posting problems on the forums is like going to ...

So I make some progress by getting the address' correct becomes Now it works once. ie the config1 is programmed, then it hangs....
Hmm, maybe I need to do a page write after all..

PK

So the "Brownout reset" config setting for an 18F67J94 in MikroC V6.6.2 has it's logic inverted, ie "enabled" actually disables BOR. It was an easy mistake to make, CONFIG1L<0> == 0 to enable is a bit counter intuitive, and I've logged a ticket. So now I have a bunch of product in the wild that I'd ...

OK, a big +1 for the case sensitivity in libraries problem. We have production code that won't build in 6.6.0. and that means we are close to dead in the water.
Please post rollback instructions.....
PK

Hi, I believe that I answered you via support desk. Best regards, Marina :-) Great, but if you had copy/pasted your response here, then I wouldn't have had to raise the same question as a support ticket. The problem gets much worse if you open C-PIC16 and C-PIC32 at the same time. With a single IDE...

filip wrote:Hi,

Please, could you disconnect all external circuitry, program the MCU with the bootloader, and try to upload the HEX files several times and see if you can recreate this issue ?

Regards,
Filip.

Sure, I'll give this a go in the morning. Thanks

PK

Hello, This happened during the normal work or during the reprogramming? Additional custom circuit is used with board? Best regards, Peter Peter it happened during the reprogramming. There is a circuit connected to this board and it is driving a stepper motor. But it fell over about 25% of the way ...

I have been developing some code on a Mikromedia 18F87J50 board for a few days. Everything was working fine. Then a bootload failed and the device is no longer detected by the windows HID bootload software. OK, these things happen.. So I connect a programmer and reflash the bootloader. Verify it, bu...

Thanks heaps for the response, I'll check the RP46 issue and try out your tool.

I do now have RP39 mapped to the EUSART and sending data. Yay!
The last piece of the puzzle was figuring out I had set TXSTA2 wrong....Doh!
Making progress now..
PK

Inching forward.. Gotta turn off the LCD driver, and IOLOCK is in OSCCON2 not OSCCON1 (the datasheet has a typo in section 11.15.5.1) I'm now at: void main() { TRISC.B3=0; ANCON1=0; ANCON2=0; ANCON3=0; LCDCON=0; LCDSE0=0; LCDSE1=0; LCDSE2=0; LCDSE3=0; LCDSE4=0; LCDSE5=0; LCDSE6=0; LCDSE7=0; LCDREG=0...

Impressive work! There's a great Calvin Coolidge quote. http://www.quotationspage.com/quote/2771.html very applicable here. So I'm now looking to migrate our products to this chip.. 4 UARTS and a built in RTCC with battery backup! Wooo hoo. I have a definition file from the MikroElectronica guys. No...

pk7639 wrote:OK, same (FAT-16 library using) code, 18F67J10
MikroC 5.01 RAM: 2911 ROM: 47567
MikroC 5.2 RAM: 3632 ROM: 49952

Looks suspiciously like there's an extra 512byte buffer in there!.....
PK

MikroC 5.3 (still using the new FAT16 library, not the legacy one) RAM: 3630 ROM: 46217

PK

Anyone tried 5.3 yet?

PK

Most compilers for more powerful packages come with a bounds checking library you can link in when debugging. I'm currently casting a suspicions eye over some of my sprintx code..... I don't know of any other tool for the PIC or AVR that does it, but it'd be really nice to have. It'd also set MikroC...