 | Discussion Forum |  |
|
|
Cypress EZUSB-FX USB disconnect and uVision2 DebuggerNext Thread | Thread List | Previous Thread Start a Thread | Settings | Details | Message |
|---|
Read-Only Author
Dave Fords Posted
8-Sep-2004 18:03 GMT Toolset
C51 |  Cypress EZUSB-FX USB disconnect and uVision2 Debugger Dave Fords I just purchased the C51 development kit, with uVision V4.20a. I had an older version that came with the Cypress EZUSB-FX development kit.
The following code, which disconnects and then reconnects from the USB, used to work with the old debugger.
USBCS |= bmDISCON;
EZUSB_Delay(1000);
USBCS &= ~bmDISCON;
With the new development system, when the line
USBCS &= ~bmDISCON;
executes, my program somehow breaks and the PC gets set to 0x8000. There are no breakpoints set. My code resides at 0x2000-0x4FFF. The interrupts begin at 0 and CODE 0x0000 is a LJMP 0x3B27, which is the address of the startup code. This used to work fine. What has changed? Why is the PC being set to 0x8000, there are no custom STARTUP.A51 or .INI files in this project. | | Read-Only Author
erik malund Posted
8-Sep-2004 19:01 GMT Toolset
C51 | RE: Cypress EZUSB-FX USB disconnect and uVision2 Debugger erik malund Why is the PC being set to 0x8000,
That is how the EVAL works.
Erik | | Read-Only Author
Dave Fords Posted
8-Sep-2004 19:20 GMT Toolset
C51 | RE: Cypress EZUSB-FX USB disconnect and uVision2 Debugger Dave Fords I guess the new dubugger is responding to a INT2 interrupt that apparently is being caused by the USB connect. The interrupt vector at 0x0043 is a LJMP 0x8000. Me thinks I have to dissable INT2 before, then clear the USB core after reconnection, then re-enable INT2 right? | |
Next Thread | Thread List | Previous Thread Start a Thread | Settings |
|
