>> I am using the dsPIC30F2010 28 pin dip package. In previous posts
>> I had problems with getting external interrupt INT0 to work. Resolved by
>> declaring _INT0Interrupt as global. Now I have problems with INT1 and
>> INT2.
>> I am using Visual Device Initializer to set up INT0, 1, and 2. VDI shows
>> pin conflicts
>> on pins 14 and 15 (INT2 and INT1 respectively). It says that they are
>> already claimed by
>> EMUD2 and EMUC2. Before I configure INT1 and INT2 these pins show up in
>> grey (Unclaimed).
>> Does anyone have any suggestions?
>>
>> --
>> Regards,
>> Stephen D. Barnes
>>     
>
>
> I haven't yet used the dsPIC30, but have used the similar PIC24H. On the
> 24H, config bits set which debug port will be used. Perhaps these config
> bits conflict with your pin assignments.
>
> How do you like the Visual Device Initializer? It seems to generate a
> whole lot of code to do very little. I've just written my own
> initialization and pin selection stuff in C. That way I have code I can
> understand when I'm debugging.
>
> Harold
>
>
>
>   
No, on this chip the debug port is PGC and PGD. I have tested the 
configuration even though
VDI says there is a pin conflict and it actually works. This is a hobby 
project, not professional,
so I'm not concerned at this point in my development.

VDI is not too bad if you set it up correctly, ie;
I only check the box in code generation options for generate code only 
for features/options on package.
Then I delete the code that's commented out from the file.
I find it quick and it's teaching me how to configure the chip on my own 
too. This chip is a big leap
from the earlier 16F parts. I've done a little with a couple of the 18F 
parts like the 452 and the 4450.
Thanks for the reply Harold!

-- 
Regards,
Stephen D. Barnes

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist