Thanks, but I do understand why there is a requirement for VBus monitoring and realise that one could implement an interrupt routine manually to ensure USBFS_Stop is called if the VBus drops.
What I don't understand is the practical difference between the "Internal VBus" and "External VBus" options in the USBFS component.
Not sure if this will help –
Also in the basic ap note (AN57294) a discussion on VBUS monitoring -
http://www.cypress.com/?rID=70131 AN82072 - PSoC® 3 and PSoC 5LP USB General Data Transfer with Standard HID Drivers
http://www.cypress.com/?rID=39553 AN56377 - PSoC® 3 and PSoC 5LP - Introduction to Implementing USB Data Transfers
http://www.cypress.com/?rID=39404 AN57473 - USB HID Basics with PSoC® 3 and PSoC 5LP
http://www.cypress.com/?rID=39327 AN57294 - USB 101: An Introduction to Universal Serial Bus 2.0
http://www.cypress.com/?rID=40103 AN58726 - PSoC® 3 / PSoC 5LP USB HID Intermediate (with Keyboard and Composite Device)
Thanks Dana but I'm still no closer to answering my actual question.
Perhaps a direct question would serve me better:
If I am using the USBFS "Internal VBus" monitoring option, do I connect the associated USBFS:VBus pin directly to the USB VBus or do I have to connect it through the RC configuration shown in the USBFS datasheet under the heading "Enable VBUS Monitoring"?
Sorry to keep getting back to you.
I did read that and it is similar to what's in the current datasheet. However, it seems from that paragraph that you do the same wiring for the Internal and External options so. The current USBFS datasheet words it slightly differently and makes it a bit ambiguous as to whether that circuit is for both Internal and External options or just for the External option. Perhaps I'm being over-cautious and pedantic, but after all I am an engineer :)
If they both require the same circuit, then what's the difference between the two options? (as you answered the first question you don't have to answer that one!)
Fo External VBUS monitoring there will be a pin on the component which you need to route to GPIO in which ever way you like.On the other case the pin will be available automatically in the Pin Editor section