The Keil ULINK family of USB-JTAG Adapters connect your PC's USB port to your target system (via JTAG, SWD, or OCDS) and allow you to debug embedded programs running on target hardware The ULINK2 USB-JTAG Adapter offers all the features of the original ULINK USB-JTAG Adapter plus:. Works with standard Windows USB drivers,. 10MHz JTAG clock,. RTCK support,. Serial Wire Debug (SWD) support,.
Serial Wire Viewer (Trace) support,. and a real-time agent. ULINK2 Features:.
The ULINK2 USB-JTAG/SWD Adapter section displays driver, device and firmware information about your ULINK2 adapter. The Serial No: displays the serial number of a ULINK2 adapter. When more than one ULINK2 adapter is connected, use the drop-down list to select the ULINK2 adapter. KEIL ULINK DRIVER DOWNLOAD - By continuing to use our site, you consent to our cookies. To download drivers for free. After 4 years his blog became the best blog.
Plug-and-Play installation using standard Windows USB drivers,. Serial Wire Debug (SWD) support for ARM Cortex-M3 based devices,. Real-Time Trace for Cortex-M3 using Serial Wire Viewer (SWV),. Real-Time Agent with memory R/W during execution, terminal emulation, and serial debug output,. 10-pin and 20-pin connector support. ULINK2 may be used for:.
On-chip Debugging (using on-chip JTAG, SWD, or SWV),. Flash Memory Programming (using user-configurable Flash programming algorithms). Using the Keil µVision IDE/Debugger with the ULINK2 adapter, you can easily create, download, and test embedded applications on actual target hardware. Note that the original ULINK has been replaced by ULINK2.
1 Running the Oracle Java ME Embedded Software on the Keil MCBSTM32F200 Board The Keil MCBSTM32F200 board is the reference device of the Oracle Java ME Embedded software. This chapter documents how to install the Java ME Embedded software with RTX binary onto the Keil MCBSTM32F200 board, configuring the Java ME Embedded system, connecting to the command-line and logging interfaces, and installing and running a Java ME Embedded 'IMlet' application. The following items are required for developing on the Keil MCBSTM32F200 board:. The Oracle Java ME Embedded RTX Software Distribution, Version 3.3.1. A desktop computer running Windows XP or later with two USB ports.
A Keil MCBSTM32F200 Cortex Board. A hardware debugger, such as the ULINK-ME or ULINK 2.
A MicroSD card (with an SD adapter, if necessary for connecting to the desktop computer). A networking LAN cable with RJ-45 interface. A terminal emulation program, such as PuTTY. Downloading and Installing the MDK-ARM Lite Development Kit To install the Oracle Java ME Embedded software on the reference board, first download and install version 4.54, 4.6, or 4.7 of the MDK-ARM development kit.
The MDK-ARM development kit can be obtained from the following site: Be sure the download completes successfully: for example, the file size for the MDK-ARM Lite version is approximately 500 MB. Once downloaded, install the MDK-ARM tool by double-clicking on the executable.
After the tool install finishes, verify the installation by double-clicking on the Keil µVision 4 IDE executable. Connecting the Keil MCBSTM32F200 Board to the Computer The Keil MCBSTM32F200 board comes with two USB cables. Both cables must be connected to the desktop computer.
The first USB cable attaches to the USBHS connector, and provides power to the board, as shown in. The other connects to the hardware debugging unit, such as the ULINK-ME, which in turn connects to a compatible debugging port on the evaluation board. See the instructions that come with your specific hardware debugging unit for more information. After the USB cables are connected, ensure that the board and the debugger are receiving power by verifying that the LEDs on both the board near the USB connection and the hardware debugger are lit. The LED near the USB connection should be lit green. With the Keil MCBSTM32F200, the backlight of the touchscreen display also lights up, even though it might not be displaying any information. Figure 1-2 Windows Formatter Settings.
Once the formatting completes, copy all the files inside the directory sdcard/ in the Oracle Java ME Embedded distribution to the root directory of the SD card. Edit the file rtcupd.cfg on the root directory of the SD card. (This can be done by opening the file with a standard text editor.) Edit the current time and date that the device should use, in the format YYYY/MM/DD HH:MM:SS Zone. For example, the file rtcupd.cfg could contain the following: 2012/11/22 18:46:00 GMT Next, rename the file rtcupd.cfg to rtc.cfg. Open the file platform.cfg on the root directory of the SD card to specify the appropriate networking information for the device. Edit the MAC address if you have more than one board in your local network or if you think that there is a MAC address conflict.
The following is an example of a MAC address: #- # MAC Address # - It should be unique value in the same LAN #- mac.addr= 00:0A:0C:0E:07:0A. Note: The MAC address must comply with the IEEE 802.3 standard.
If your network uses dynamic IP addresses, uncomment the DHCP line under Dynamic IP Address and comment the lines under Static IP Address. If your network uses static IP addresses, uncomment and edit the lines under Static IP Address and comment the line under Dynamic IP Address. Installing the Firmware on the Evaluation Board The Java ME Embedded distribution contains a utility that uses the MDK-ARM software to erase and flash the Oracle Java ME Embedded binary onto the evaluation board.
Use the following procedure to prepare the SD card and install the firmware:. Use the Safely Remove Hardware function on the Windows desktop to remove the SD card from the computer. (In Windows XP, for example, the Safely Remove Hardware tool is present in the lower right system tray near the clock.) Alternatively, you can select the SD card in the My Computer window, right click and select Eject. If necessary, remove the MicroSD card from the SD card housing.
Be sure that the board is not powered up by temporarily disconnecting the USB cables. Insert the MicroSD card into the SD card slot on the board. Switch the 'BAT/3V3' jumper near the RS-232C connection on the board to the left (BAT) position, outlined in.
Epson Drivers For Mac
Connect the board to the Windows desktop computer as you did previously, including the network cable, the USB power cable, and the debugger with its USB cable. The board should now be receiving power. On the desktop, check the file flash.bat inside the directory flash/ in the Oracle Java ME Embedded software. Ensure that this file contains the correct path to the MDK-ARM tool binary. For example: C: Keil UV4 UV4.exe -f jmee.uvproj -o output.txt.
Keil Uvision3
With the board connected, run the batch file flash.bat to download the distribution to the evaluation board. The MDK-ARM tool notifies you when the download has completed. If the MDK-ARM tool requires a Flash Upgrade of the debugger, press OK to allow this, then restart the flash.bat when completed. Once completed, push the Reset button on the board to start the Java ME Embedded native platform. The runtime will then use the configuration files on the MicroSD card to initialize itself.
If successful, the touchscreen on the device should look similar to. Note that after the time clock has been initialized, the runtime will rename the rtc.cfg file on the MicroSD card back to rtcupd.cfg and ask you to reset the board to activate the clock's settings. Table 1-1 Ports Used by the Embedded Board Port Description 65000 Logging / Java VM System Output 65002 Command-line interface The window that outputs data from port 65000 provides logging and standard output information from the device.
This is useful when determining if a Java ME embedded program ran successfully on the board. The window from port 65002 provides a command-line interface (CLI). Both the CLI and logging windows are shown in. The logging port is defined in the jwcprop.ini properties file using value assigned to the log.tcp.port property. Table 1-2 AMS CLI Commands Syntax Description ams-list INDEX or NAME VENDOR List all installed IMlet suites and their statuses or show the detail of a single suite ams-install username:password Install an IMlet using the specified JAR or JAD file, specified as a URL. An optional username and password can be supplied for login information as well.
Ams-update Update the installed IMlet ams-remove Remove an installed IMlet ams-run IMLETID -debug Execute the specified IMlet or the default if none is specified. An optional debug parameter can be specified to run the IMlet in debug mode. Table 1-3 Additional System Commands Available in the AMS CLI Syntax Description setprop Sets a property identified by with the value getprop Returns a property identified by odd on off Explicitly sets the on-device debugging (ODD) property to on or off. If no parameters are passed, returns the current ODD value. Shutdown -r Perform either a shutdown of the board, or a reboot if the -r parameter has been passed. Note that the watchdog should be enabled in the platform.cfg file to successfull reboot.
(See ) Here is a typical example of using the Application Management System (AMS) to install, list, run, and remove a Java ME Embedded application on the Cortex board. Note: Note that the AMS syntax and output may change in future Oracle Java ME Embedded releases. First, install the application using the ams-install command, specifying its location either on the MicroSD card (using the Memorycard directory, which maps to memcard on the filesystem) or across a network using a URL.
Oracle ams-install file:///Memorycard/hello.jar ams-install ams-install ams-list ams-remove 0 ams-list ams-run 1 ams-list. Additional Methods of Obtaining Logging Information There are several additional ways to connect to the embedded board and obtain logging output. These include the following:. UART - Through RS232 To utilize this method, connect to the board using an RS232 serial cable and use a tool such as PuTTY to create a serial connection from a terminal on the Windows desktop using the following options: Baud rate: 115200 Data bits: 8 Stop bits: 1 Parity: None Flow control: XON/XOFF Also, ensure that the log.method property from the jwcprop.ini file contains the value UART in its list. USB/COM - Through a USB COM port and an appropriate driver In order to use this method, connect a USB cable from your desktop to the Keil board. A USB to COM driver must also be installed on your Windows desktop machine. Drivers' installers and installation instructions can be found in the driver directory of the Keil bundle.
Finally, ensure that the log.method property from the jwcprop.ini file contains the value USBCOM in its list. Then, create a serial connection from your terminal with the following options: Baud rate: 115200 Data bits: 8 Stop bits: 1 Parity: None Flow control: XON/XOFF.
ITM - Through ITM trace supported by MCU An instrumentation trace can be used as supported by the ARM microcontroller. See the embedded board documentation for more information on this method.
Also, ensure that the log.method property from the jwcprop.ini file contains the value ITM in its list.