Search found 62 matches

I need to respond to interrupts very fast (as close to realtime as possible) for both polarities. It's likely that I will bypass CCS's interrupt handling entirely, and write the whole thing in ASM. ...

I'm writing code for a PIC18F46K20.

The datasheet indicates that I have hardware interrupt pins for INT0, INT1, and INT2. To set the edge polarity of these interrupts, there are INTEDGx bits in ...

Thanks, jeremiah.

I fully agree with you; in another instance I would be the guy saying the same thing in a reply.

I've already gone down the road you suggest, checking and watching the hardwa ...

Sorry, the i2c address is being set near the beginning of Main. Here are some additional code snippets to eliminate ambiguity:

unsigned int8 i2cAddr = 0xa8;

I2C_SlaveAddr(sI2C,i2cAd ...

I'm using a dsPIC33FJ128MC804 as an i2c slave. To test it, I'm using a pickit serial analyzer. The application is simple, it emulates eeprom: write a 16-bit address, read as many bytes back as neede ...

I'm using a PIC33FJ128GP804 with a standard 2-line LCD and the CCS lcd.c driver. It has been working fine during initial code setup/test/development, there are no hardware issues.

As I add code to ...

In the past I've used portable programmers from Kanda.com, which were problematic for various reasons but generally ended up working when I needed them.

more recently I've been using the Microchip ...

Hi everyone. I'm embarrassed to have to ask this, but...

What is a Trap Conflict Reset?

I've been developing an application on the DSPIC33FJ128MC804 using CCS C 4.103. A Trap Conflict Reset ...

For now, I've written a function with the same syntax as set_pwm_duty(), and used switch to call set_pwm_duty() with the required constant inserted. Perhaps this is the best workaround?

Jim

Using PCD compiler version 4.101, target dsPIC33.

I have written a fairly complex function utilizing set_pwm-duty(). It was my hope to use this function for 4 different pwm outputs using a variabl ...

Even more strange:

I can debug successfully with an ICD2. So the problem seems to rest with the ICD3.

This one has me stumped. I have code that works when programmed into the dsPIC33 with an ICD3. But the same code does not work when trying to debug using the ICD3. The environment is MPLAB 8.40, an ...

Spectacular! Creating an include file of registers and bits is easy. :)

Thank you, ckielstra. Very very very much appreciated!

Jim

I'm running the most current versions of everything for the dsPIC33. Compiler/IDE version 4.101. Also have the most recent release of Microchip stuff: MPLAB 8.40, and ICD firmware bundled with that ...

I have the CCS IDE, and will look closer at the device editor. I didn't realize it would be helpful in this case. Can you elaborate just a bit more?

Unfortunately, though, debugging stopped worki ...