> 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



-- 
FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
opportunities available!
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist