View previous topic :: View next topic |
Author |
Message |
ratgod
Joined: 27 Jan 2006 Posts: 69 Location: Manchester, England
|
PIC18F4550 code disabling interupts!?!? |
Posted: Fri Aug 03, 2007 12:01 am |
|
|
Hi there,
I have been playing with USB Pics but when I compile the examples I keep getting these messages:
this is with ex_usb_kbmouse2.c but its the same with the other examples.
Code: | >>> Warning 216 "ex_usb_kbmouse2.c" Line 313(0,1); Interrupts disabled during call to prevent re-entrancyl (usb_token_reset)
>>> Warning 216 "ex_usb_kbmouse2.c" Line 313(0,1); Interrupts disabled during call to prevent re-entrancyl (usb_flush_int)
>>> Warning 216 "ex_usb_kbmouse2.c" Line 313(0,1); Interrupts disabled during call to prevent re-entrancyl (usb_flush_out) |
I have not tampered with the example code in any way.
I am told that I have version 4013
I had a 4550 going on a breadboard with an altered version of the ex_usb_serial.c where I piped the virtual com port data back. then I tried to get the same code working with the 2550. but now it seems that any of the examples I compile have them warning and I don't seem to be having luck with the circuits. the PC finds the device then it says it cant initialise. I assume this is because the PIC is not being interupted properly.
anyone have any idea? |
|
|
PCM programmer
Joined: 06 Sep 2003 Posts: 21708
|
|
|
ratgod
Joined: 27 Jan 2006 Posts: 69 Location: Manchester, England
|
|
Posted: Fri Aug 03, 2007 11:40 pm |
|
|
Many thanks for the response,
So I am I right in thinking that I should just ignore the warnings concerning the USB intrupts? |
|
|
PCM programmer
Joined: 06 Sep 2003 Posts: 21708
|
|
Posted: Sat Aug 04, 2007 12:02 pm |
|
|
To answer your question, I would have to go study the whole USB driver again. I don't want to take the time to do that. I think Darren writes
the USB drivers and examples at CCS. I assume that he tested this
driver and found that it works, even though interrupts will be disabled for
some period of time within the main(), when a certain routine is called.
If you're worried about it, I think you should email CCS support. I'm
just trying to politely say that I don't have the time to analyze this one. |
|
|
|