Changes between Version 19 and Version 20 of jtag_instructions


Ignore:
Timestamp:
01/24/2019 03:04:39 PM (4 weeks ago)
Author:
Tim Harvey
Comment:

update URL for jtag programming utility and remove Windows JTAG programming tool references

Legend:

Unmodified
Added
Removed
Modified
  • jtag_instructions

    v19 v20  
    66The device is primarily used used to access Gateworks devices for debugging and developing purposes.
    77
    8 Gateworks provides a software utility application with support for both [#Linux Linux] and [#Windows Windows] operating systems (Note that for the Ventana product family, you must use the Linux tool). In order to use the windows utility please install the drivers which are also available at the link below (CDM20814_Setup.exe).
     8Gateworks provides a software utility application supporting x86 [#Linux Linux]. While JTAG programming is not supported for [#Windows Windows] operating systems you can use the JTAG dongle as a serial console.
    99
    1010[[Image(wiki:jtag_instructions:gw16042.JPG,200px)]]
     
    3535
    3636
    37 = Instructions =
    38 [#Linux Linux Instructions]
    39 
    40 [#Windows Windows Instructions]
    41 
     37= Instructions
    4238
    4339[=#linux-jtag]
    44 == Linux ==
    45 
    46 [https://youtu.be/i3G8sQlwzcU Click here for instructional video baised on this section, mkimage and jtag_usbv4 are demonstrated]
    47 
    48 The Gateworks '''jtag_usb''' utility supports x86 32bit and 64bit Linux systems. Ubuntu is supported, however most x86 Linux distros should work as well.
    49 
    50  * ''' Note virtual machines are NOT recommended'''
    51 
     40== Linux
     41
     42[https://youtu.be/i3G8sQlwzcU Click here for instructional video based on this section, mkimage and jtag_usbv4 are demonstrated]
     43
     44The Gateworks {{{jtag_usb}}} utility supports x86 32bit and 64bit Linux systems. Ubuntu is supported, however most x86 Linux distros should work as well.
     45 * Virtual Machines should work fine as long as they allow access to USB devices (ie Virtualbox has been known to work well)
    5246 * If using a 64-bit system, the following is recommended to support the 32-bit binary:
    53 {{{
     47{{{#!bash
    5448sudo dpkg --add-architecture i386
    5549apt-get update
     
    5953 * Please email support @ gateworks.com with any other questions
    6054
    61 The most recent version '''jtag_usbv4''' supports all Gateworks product families and can be downloaded [http://dev.gateworks.com/jtag/ here]
     55The most recent version {{{jtag_usbv4}}} supports all Gateworks product families and can be downloaded [http://dev.gateworks.com/jtag/ here]
    6256
    6357The GW16042 JTAG dongle uses a FTDI FT2232C Dual USB-UART/FIFO chip and when enumerated on the USB bus will show as:
    64 {{{
     58{{{#!bash
    6559lsusb | grep 0403:6010
    6660Bus 001 Device 007: ID 0403:6010 Future Technology Devices International, Ltd FT2232C Dual USB-UART/FIFO IC
    6761}}}
    6862
    69 With the Linux kernel '''ftdi-sio''' driver installed this will expose two USB serial devices:
    70 {{{
     63With the Linux kernel {{{ftdi-sio}}} driver installed this will expose two USB serial devices:
     64{{{#!bash
    7165ls -l /dev/ttyUSB*
    7266crw-rw---- 1 root dialout 188, 0 Apr  2 07:04 /dev/ttyUSB0
     
    8074
    8175References:
    82  * Latest Linux x86 jtag_usb download: http://dev.gateworks.com/jtag/linux/x86/
    83 
    84 
    85 === Conflict with ftdi-sio driver ===
    86 The jtag_usb application requires that the Linux ftdi_sio kernel module not be loaded to run. You can temporarily unload it, then reload it (ie by hotplugging the jtag dongle) when done if you require it:
     76 * Latest Linux x86 jtag_usb download: http://dev.gateworks.com/jtag/
     77
     78
     79=== Conflict with ftdi-sio driver
     80The {{{jtag_usb}}} application requires that the Linux {{{ftdi_sio}}} kernel module not be loaded to run. You can temporarily unload it, then reload it (ie by hotplugging the jtag dongle) when done if you require it:
    8781{{{
    8882sudo rmmod ftdi_sio
     
    10094
    10195
    102 === Linux permissions on USB device ===
     96=== Linux permissions on USB device
    10397If you encounter permission errors when running jtag_usb it is likely that you require root privileges to access the USB device via libusb:
    10498{{{
     
    133127
    134128[=#linux-jtag-flashing]
    135 === Using jtag_usb to read/write Firmware, Programming Software ===
     129=== Using jtag_usb to read/write Firmware, Programming Software
    136130Please see above for the download link to the latest jtag_usb executable. Note that an update may be required for new board models or memory configurations.
    137131
     
    189183==== Troubleshooting ====
    190184
    191  * ''' Note virtual machines are NOT recommended'''
    192185 * Permission denied: '''libusb couldn't open USB device''' - [#LinuxpermissionsonUSBdevice see above] regarding Linux permissions
    193186 * fOP: '''USB Open Rev  fOP''' - failure to open the USB device via libusb - you likely have the ftdi_sio serial driver loaded - [#conflictwithftdi-siodriver see above]
     
    246239
    247240[=#linux-serial]
    248 === Serial Console Access on Linux ===
     241=== Serial Console Access on Linux
    249242
    250243[https://youtu.be/9LKgHiAq-BM Establishing a serial console in Linux instructional video]
     
    276269
    277270[=#windows]
    278 
    279  
    280 
    281 == Windows ==
    282 
    283 ** Please note **
    284 Gateworks no longer maintains the Windows JTAG software and thus it is not recommended. Gateworks recommends using the provided Linux JTAG software as found on this page.
    285 
    286 ***WARNING*** This software is incapable of programming GSC firmware, your board will be bricked by doing so.   
    287 
    288 [[CollapsibleStart(Windows Programming Software - No Longer Maintained)]]
    289 
    290 
    291 === Installing the Drivers for Windows ===
    292 
    293 1. Download and run the file CDM20814_Setup.exe on to your windows machine ([http://dev.gateworks.com/jtag/ Download JTAG Executables]). A window should open and close on its own:
    294 
    295 [[Image(wiki:jtag_instructions:winjtag.JPG)]]
    296 
    297 2. Once that is finished running, download and install winjtagsetup_0_1_5.msi
    298 
    299 [[Image(wiki:jtag_instructions:winjtag2.JPG)]]
    300 
    301 3. Choose a location to install the Gateworks Win JTAG.
    302 
    303 [[Image(wiki:jtag_instructions:winjtag3.JPG)]]
    304 
    305 {{{
    306 #!html
    307 <h3 style="color:red">NOTE:  There have been reports of an error regarding a missing DLL file.  If this error is seen, please try to find the DLL on the system, and copy it into the same directory as the executable.</h3>
    308 }}}
    309 
    310 
    311 [=#windows-jtag]
    312 === Operating Instructions For Programming ===
    313 ''' Please note, Windows Programming is not supported for Ventana'''
    314 
    315 1. Connect the Gateworks JTAG-USB Programmer to the JTAG header on the board using the attached ribbon cable.
    316 
    317 2. Power on the board and connect the Gateworks JTAG-USB Programmer to a Windows PC using the supplied USB cable.
    318 
    319 3. Run the Gateworks !WinJTAG program.
    320 
    321 4. Click on Open next to the Program File field and select the file location of a binary image.
    322  * '''Note''' - For Laguna boards, please do not flash a squashfs file to the board. A proper JTAG binary must be created with instructions [wiki:OpenWrt/building#BuildingJTAGBinaryFile here]
    323 
    324 5. If desired, select a verify file or click on "Set Verify to Program File."
    325 
    326 [[Image(wiki:jtag_instructions:winjtag4.JPG)]]
    327 
    328 6. Click on Go and wait for the programming to be complete.
    329 
    330 [[CollapsibleEnd]]
    331 
     271== Windows
     272**Gateworks no longer maintains the Windows JTAG software and thus it is not recommended.**
     273
     274Gateworks recommends using the provided [#Linux Linux] JTAG software as found [#Linux above].
    332275
    333276[=#windows-terminal]
    334 === Windows Operating Instructions For Serial ===
    335 You can use a terminal program for windows such as [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty] / Hyperterminal to connect to the Gateworks board serially over the JTAG / or serial port.
    336 
    337 Connect the jtag programmer to the computer, or connect a serial cable from the Gateworks board to the computer (if serial is available)
    338 
    339 Please reference the device manager area on your windows computer to detect which 'COM' port the JTAG is connected on.
     277=== Windows Operating Instructions For Serial
     278You can use a terminal program for windows such as [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty] / Hyperterminal to connect to the Gateworks board serially over the JTAG / or serial port as long as the FTDI Virtual COM port drivers are installed on your system:
     279 * https://www.ftdichip.com/Drivers/VCP.htm - Downloads for x86 (32bit) and x64 (64bit) Windows drivers
     280
     281To see if you have the proper drivers installed simply connect the Gateworks JTAG dongle to your Windows PC and look in the 'Device Manager' application under 'COM Ports' to see if a new serial device was added.
    340282
    341283Then, start a standard serial connection on that port.  Configure the terminal program for 115,200 baud, 8 data bits, 1
     
    349291
    350292
    351 = General Troubleshooting =
    352 
     293= General Troubleshooting
    353294 1. If while programming a board it gets stuck an invalid image may have locked up the board or the board is not powered on. Please try powering on the board. 
    354295 2. JTAG utility stuck at '''Core 0 DRAM 00%''' while programming a Laguna family board - A lockup may have occurred in which a detailed fix may be available.  Please contact Gateworks support at support@gateworks.com.
     
    360301
    361302
    362 = OpenOCD =
     303= OpenOCD
    363304Please see out JTAG hardware page here: [wiki:jtag#OpenOCD JTAG OCD]
    364305
    365306
    366 = JTAG Programmer Hardware =
     307= JTAG Programmer Hardware
    367308Please see out JTAG hardware page here: [wiki:jtag JTAG Hardware PAGE]