I have been waiting for this for quite some time as well. It would appear that the board has evolved to the proper point to where switching to tristate DIP switches would be elementary. It might cost a bit more, bit I think people will be able to stomach the extra $5-10 for tristate switches. The on...

Blast it, I just knew I was one bit off somewhere. I must have skimmed over that box on the datasheet. Thanks, xor.

Ah, maybe I should have been more clear. That code is debug code I am running on a dev board, not the original board. There is no hardware connection between the pins on my dev board.

The code is supposed to read PORTC and write it to LATB. All of the pins transfer properly except RC3 (which doesn't exist), RC4, and RC5. I've been twiddling pins in PORTC externally to see what shows up on PORTB. EDIT: Btw, this problem is very specific to the PIC18F2550 and PIC18F2455. If you are...

Writing to LATB does the same thing as writing to PORTB. I've just gotten into the habit of writing outputs to the latch directly since read-modify-writes of the port can change bits unintentionally because they can sometimes be read wrong depending on the setup of the circuit. Writing to LATB is no...

Any ideas on this?

This has been driving me crazy. I need to read the state of RC4 and/or RC5 at one point in the initialization of my program (there are two versions of the board that the chip is on, on the older one RC4:5 are tied to RA4:5 and I need to detect this to fix another miswire on that board). However, the...

Any idea when that might be? The current version is about seven months old and there have been about fifty bug fixes for the next release.

I am running Windows Vista Home Premium and the latest (though dated) version of mikroC (6.2.1.0). One particular project causes mikroC to produce an access violation: Access violation at address 0040653C in module 'mikroC.exe'. Read of address 00000078. Restarting the computer and mikroC didn't hel...

try /r/n.

Any news on this? It seems like this should be a very simple thing to add.

Do you mean a logic analyzer trace?

Are the device and clock speed #defined globally so they can be used for conditional compilation? If not, then they really should be. There are clock_khz and clock_mhz functions, but these are not exactly what I am looking for... BTW, you guys almost always answer that things will be implemented in ...

Is this going to be implemented at some point in the near future?

Can you please be more specific?