Search found 13 matches

Yeah, I know I wasn't fooling the processor... Fortunately for me, there is only one SPI device in this project, and thanks to the kind folks in this forum, I'm actually writing and reading the chip o ...

Ttelmah - I anticipate read/write tests today.

PCMProgrammer - I am not in the habit of combining all of the files into one - I was just following the suggestions of the compiler vendor. By putting ...

I'm not sure about mode=3. In fact, after changing to mode 0, I seem to be getting data back from the MAX30003.

I am sure about the connections, which are correct. I have an EE to beat up on for th ...

Indeed - I took out the set_tris_c() statement altogether, and I get the same results - still get chip select and clock, data out to the slave looks good, but the slave returns only 1's, which, like s ...

Thanks to you both. I'm closer now.

Yeah, the set_tris_c() was kind of dumb on my part. I assumed that the #use SPI statement would initialize things. I was wrong!

Now I get proper chip select w ...

I am trying to talk to a MAX30003 ECG chip via the SPI but the MAX30003 has a 32bit SPI read/write cycle. The 16F1513 seems rather intent on an 8bit cycle, but I may just be ignorant of a way around t ...

They're not identical. You have two different PICs specified.

1. 16LF15313

2. 16LF1513

Boy, do I feel dumb ! I even had another guy look it over to make sure.

PCM Programmer - thank yo ...

So would I, Jay. So would I.

To add additional spice, I can't reproduce the problem any more, so the problem is likely some failure on my part to do operations in the proper order.

Does anybody have a particular "dance&q ...

I have a sample program I built using the Project Wizard - it's the LED blinking example. Mostly it works, so I use it as a baseline - add stuff until it breaks, then I know the last thing I added is ...

I contacted CCS Tech Support about the issue. After a few days of head-scratching, they came back with a suggestion that I not use the dreaded Multiple Compilation Units. I used an #include directive ...

We have tried using the MACHX to supply power. Same behavior. The other chip on the board consumes (at 3.6V - we're running at 2.0) 1.6uA max. The PIC consumes something on the order of 30uA. The supp ...

I'm new to PIC (well, I did use one 5-6 years ago), and I'm having issues with the MACHX debugger. When I connect to the PIC, the CCSLoad program can program the device. If I go to the Diagnostics par ...