Search found 9075 matches

re: Any other protection

Not really 'protection' but if you sand off the PIC's model number and date code it'll slow down someone from reading what you have.......1st they have to figure out WHAT t ...

I've always thought of USB as an interface between TWO devices( say PC and mouse) and wonder just how much code is required to have a PC correctly communicate with two mouses ( mice ) on the same USB ...

Are you 100% sure it's the code controlling the Spansion xxx part that 'locks up the PIC' ??
Have you bypassed all access to it to confirm it IS the source of the 'lock up' ??
If not,add code like ...

Well according to one source, the 'start' and 'end' time needs to be 3.5T or greater.
I'll assume the 'start' is 10x longer to allow for hardware to stabilize before the actual frame of data is sent ...

'timing' is all based upon the actual clock used so to get the best most accurate 'timings', you need to use quality crystal and 2 caps. For the ultimate timing, use an external canned oscillator tha ...

OK, I'm curious..... why the need to embed at the beginning ?

Great, now you know why the dinosaur likes 'super simple'. You've proved it's NOT a 'clock' issue, that the hardware attached to the PIC works and the compiler is 'happy' with your code......

Since ...

by simple 1Hz LED program
I mean,something like this....

main()
do
output_toggle(LED);
delay_ms(500);
while(true)

...
it should flash the LED at 1Hz rate, forever.

I 'think' both you ...

From the PIC18F46K22 datasheet, way in the back, of course, but I remembered where...

24.6 ID Locations
Eight memory locations (200000h-200007h) are
designated as ID locations, where the user can ...

hmm, ceramic resonator is not the same as a crystal with 2 caps. That may be your problem. You'll need to read the mfr spec for how to get it working with the PIC.

Just cut SIMPLE code ,like the 1H ...

my 'gut' is telling me the new PIC's clock(4MHz) may not be running so it's using the 'secondary' RC clock( low speed)

You should cut a '1Hz LED' program and confirm the new PIC is operational.

...

re: Compiler: 5.026 (very very old)

I guess that's why I'm a 'dinosaur'.....My first PCM was 2.534

Thanks for making an old guy ,feel even older Sad

Jay

As a followup comment...
It'd be nice to have separate LEDs for status.
That way you know WHICH serial port has sent the commands.....

yes......
You have to remember PICs, like 99.44% of all micros can only do ONE operation at a time...ask it to do too much and oopsy....
Some (most ? ) EEPROMs have a faster method, usually a 'block ...

hmm, you've got me confused....
Maybe I'm reading it wrong ??

data from the 2nd UART gets stored in the buf array while data from 1st UART gets stored in the buf2 array.

I'd like to see better ...