I am trying to use Teraterm rs232 comport. when I am running MDK Arm Software to download the program or in debug mode. The problem I see is that the ULINK2 can not be accessed when I set TeraTerm to the comport where I have a USB adapter to RS232 interface.
As soon as I close Teraterm the ULINK2 can be accessed.
This problem started occurring when I had to reinstall the MDK ARM software because I tried to install the free STM Lo version. and lost the MDKLite license. So I just uninstalled the MDK version and reinstalled it again to get back the MDK Lite license.
What error message are you getting when you try to access ULINK2?
Did you check the driver status using the Device Manager? See http://www.keil.com/support/docs/3266.htm
If I start the ULINK2 and Board in Debug mode, Then start up teraterm to add a serial port rs232 adapter.
then try to stop the project from running I get a pop up.
ULINK - ARM Error
X Could not stop ARM device! Please check the JTAG cable
If I select ok
Debug mode went away I did not select any menu item. the software program just seemed to stop debug on its own.
So then I go ahead to try to enter debug again then I get the pop up:
X No JTAG Devices Found
Under Control Panel -> Hardware and Sound -> Devices and Printers
I See Keil ULINK2 CMSIS-DAP
Double click on ICON see Pop Up
-------------------------------------------------------
HID-compliant device
No driver files are required or have been loaded for this device.
------------------------------------------------------
If I choose driver -> driver details the pop up will come back
saying no driver files are required.
as soon as I turn teraterm off. then MDK-software will find the ULINK2 and will work as I would expect. Unfortunatly, I have no access to serial port then.
Looking at the device manager. Am not seeing anywhere the ULINK2 name associated with the HID devices.
The issue could be a windows issue, a ULINK2 issue, or a communication with the board issue.
It looks like windows sees the ULINK2 device OK.
From the Project pull-down menu, select Options For Target... to open the target options dialog. on the debug tab (2nd to last tab) on the right of the dialog, select "settings"
www.keil.com/.../ulink2_ctx_debugdrivercfg.htm
On the top right of the "Cortex M driver setup" dialog, can you see the ULINK Serial number, and driver version? Then the ULINK2 is working correctly.
On the right of the screen, in the SW device section, can you see the Cortex CPU ID listed? If so then the ULINK can talk the Cortex's coresight debugger.
If you can't debug at this point, perhaps hooking up a serial port is causing the cortex's built in bootloader to jump to a different memory location. I know some NXP chips would do that unless a port pin was also held low.
Check your devices datasheet to see what the device will do if a serial port is connected to it at power up.
Hi Ron,
Thanks for the response. I took a look at the webpage. And I should tell you I am using a MCB2300 board right now. I think it has a LPC2368 processor ARM7.
Teraterm terminal NOT running When I go to options for target -> Debug and the Teraterm RS232 Terminal is not running It can see the JTAG Chain (No Problem)
Teraterm terminal running When I go to options for target -> Debug and the Teraterm RS232 Terminal IS running It can NOT see the JTAG Chain (Problem)
Error message JTAG Communication Failure.
I am going to Teraterm long after the board has powered up.
I also have other boards I can try including Cortex M3.
This board use to work without any problems before I reinstalled the MDK software again.
Thank you Ron
I was running out of Ideas. So I reinstalled the Keil software to a second place on my hard drive. Then It was also behaving the same. Then I Just removed the cable from the board while leaving the keil program running. then Keil was responsive. I guess that the RS232 cable was driving the two pins and affecting the board. then I just removed the RS232 adapter from the PC and put back in the PC. Then Keil ULINK2 was still responsive after that. So It looks like that the RS232 Adapter had been affecting the board and stopping debug operation when Tera Term was running. But now after the rs232 adapter went through a reset everything is operating as expected.
the serial cable may be causing the lpc2300 to enter ISP mode
www.compuphase.com/lpc2100_isp.htm
Thank You, Ron. I think it is a good idea to make a special rs232 cable to with only the rx and tx wires hooked up. So that the other pins are floating.