Search found 137 matches

I believe I've fixed the program with my program. In my case it seems like maybe I had messed up some coding by accidentally doing some unsafe things in an interrupt handler and also by accidentally m ...

Slight follow up: I looked at the ASM list and traced down what it was doing. Upon doing so it became apparent that it really does basically list the actual value of RCON. And, so, I see that a value ...

I am getting the above reset cause in a project of mine. The name of this reset cause seems to be total nonsense. The chip I am using (PIC18F25J11) does not reset because of a WDT while sleeping - it ...

Man, my transition back to PIC programming has been off to a rocky restart. Two dumb errors in two days... This one was caused by accidentally defining millis as an int. I'm use to 32bit MCU programmi ...

Oh, sorry, yes I suppose that would have been useful info.

PIC18F25J11 is the processor and 4.129 as the compiler version.

calc = (int32)((int32)250ul * (int32)millis);
#ifdef DEBUG
fprintf(pc, "calc: %Lu", calc);
#endif

I'm trying to use a 32 bit value ...

Aaaand, yeah, I should have known. At least being forced to produce an example program made me test my theory. It is true that the reason it messes up is that it was sending characters when it went in ...

This isn't perhaps the smallest program ever but it faithfully reproduces the environment that the actual project is running. It strikes me that it perhaps is because I go to sleep before the serial i ...

I'm using the 4.129 version of the compiler with the above chip. I have used the peripheral select instructions to turn a set of pins into the second UART. This works fine and the UART will send sane ...

If it's working then I wouldn't complain. ;-)

Your calculations do seem correct as far as the canbus timing goes.

One thing though: That's 1 TQ for the start quanta. It's always 1 TQ for start t ...

And, just to complete this whole discussion: What they mean is: it takes 4 clocks per instruction so one instruction takes 0.2uS at 20MHz. 36uS is thus 180 instruction times not 2880. You were only of ...

Yes, of course you can.

You can verify this by trying it yourself and/or looking at the documentation of the PIC chip you plan to use.

You have it trimmed down pretty far. There are only a few things I can think of that would speed it up:

1. If you can, up the clock speed

2. Switch to directly setting the port with constant val ...

It seems like some of your pins are configured oddly. SDI should be PIN_D1 and SDO should be PIN_D4 not the other way around like you have it. The usual hardware select pin for SPI2 is PIN_D3 but I su ...

A global variable will work fine for that. You can even change it while the system is running to debug on the fly if you want.

I'd also like to suggest that you invest in a cheap logic analyzer suc ...