Hi,
It seems that the MikroProg can program PIC18F55K42 and PIC18F65J94 but I can't use it as an ICD.
I'm using MikroBasic Pro V7.2.0 and MikroProg V2.80.
Are you going to add ICD support for these, and when might I expect to be able to use it.
Regards,
Alex

Hi Uros,

I meant it is not the same as a relative search path for the project.

Alex

Hi Uros,

That is useful to know, but it is not quite the same as a relative search path.

Alex

Thanks Janni

Alex

In this program snippet, I want the ToggleLatchB() procedure to be built and linked The mikrobasic compiler detects that it is never called, so doesn't link it Is there a way to force it to be linked without putting a call to ToggleLatchB() in the main program thing sub procedure ToggleLatchB() org ...

In the Help file for Mikrobasic v6.6.3 under Tutorials>Managing Project>Managing Source Files there is a section which says Paths for Source Files (.mbas) You can specify either absolute or relative path to the source file. However, I cannot figure out how to specify relative serach paths. Any ideas...

Yes, thanks for digging a little deeper, Janni
Cheers

Alex

Hi Filip, here is what I get for 512, which is the number I actually found a problem with. Don't know why I left this one out. program modulus_bug main: dim uwCount as word uwCount = 510 while true uwCount = (uwCount + 1) mod 512 PORTA = lo(uwCount) PORTB = hi(uwCount) wend end. and the ASM _main: ;...

Hi Filip,

Not sure what means

Can I see the ASM produced from that in 6.6.3.

Thanks

Alex

Hi Checker, The code I presented is to show what the compiler produces. The bug is not is my code, but in the resulting ASM produced by the compiler. It is the minimum example to demonstrate the bug. For example these leins arte there to make sure the compiler doesn't optimise the problem away PORTA...

Hi Chaps, Here is the code, compiled for a PIC18F25K22 using Mb 6.5.0, wherin I try to increment a counter and find the modulus uising three different values It produces incorrect but mostly working code for 128, correct (I think) code for 129 and totally wrong and non working code for 256. :shock: ...

I gather what you want now is to be safe while using a potentially dangerous directive. No, I'm asking for a warning so that a tool which saves me time can save me even more time. As I said, in near future you may regret that compiler does not offer even more freedom than it does. I won't regret it...

And some programmers routinely and purposefully intrude on compiler's internal variables Doesn't sound like a recipe for success. the warning you request would cause a multiple of unappreciated warnings in such cases. Those warnings would be appreciated by me and anyone else who hate having to trac...

Now I'll have multiple warnings for every program I write :( . No, I'm not talking about every overlapping memory absolution, just the ones which Mikrobasic uses and are in libraries which I have no control over. For example, program trash ' compile for PIC16F1829 ' Declarations section dim thing a...

I'm using a PIC16F1829, which has common ram in locations 0x70 to 0x7F These are also mapped directly to 0xF0 to 0xFF, 0x170 to 0x17F etc. Mikrobasic uses these locations as working registers When I allocate a variable to a specific location eg. const MEM_BASEADDR = 0x120 ' bottom of bank 2 const BU...