Changes between Version 1 and Version 2 of jtag_instructions


Ignore:
Timestamp:
10/21/2017 11:08:20 PM (3 months ago)
Author:
Chris Lang
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • jtag_instructions

    v1 v2  
    108108
    109109You can either use 'sudo jtag_usbv4' or 'sudo chmod 666' on the particular directory for the device however its likely that you want to install a udev rule to change the device permissions of this particular device every time its enumerated on the bus. You can do this by adding a udev rule that identifies the VendorID and ProductID of the Gateworks JTAG-USB Programmer and executes a chmod on it:
    110 {{{
    111 sudo cat <<EOF > /etc/udev/rules.d/51-gateworks-jtag-ftdi.rules
    112 # Gateworks USB-JTAG Programmer for normal users (FTDI 2232C Dual USB-ART/FIFO IC)
    113 SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", SYSFS{idVendor}=="0403", SYSFS{idProduct}=="6010", MODE="0666", NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}", RUN+="/bin/chmod 0666 %c"
     110
     111{{{#!bash
     112cat << EOF > 51-gateworks-jtag-ftdi.rules
     113# GW16060 Dongle
     114SUBSYSTEM=="usb",ATTR{idVendor}=="0403",ATTR{idProduct}=="6010",MODE="0666",GROUP="users"
     115# GW16061 Gang adapter
     116SUBSYSTEM=="usb",ATTR{idVendor}=="0403",ATTR{idProduct}=="6011",MODE="0666",GROUP="users"
    114117EOF
    115 sudo udevadm control --reload-rules # reload udev rules
    116 }}}
    117  * following this unplug the Gateworks JTAG-USB Programmer and re-connect to re-enumerate the bus and invoke this new rule.
     118sudo mv 51-gateworks-jtag-ftdi.rules /etc/udev/rules.d
     119sudo chmod 655 /etc/udev/rules.d/51-gateworks-jtag-ftdi.rules
     120# cause rules to be re-read and processed (or reboot)
     121sudo udevadm control --reload-rules
     122sudo service udev restart
     123sudo udevadm trigger
     124}}}
    118125
    119126The above udev configuration works for Ubuntu, however this configuration may vary on other Linux distro's that use something other than udev.
     
    138145./jtag_usbv4 –p <filename> –u <filename> –v <filename>
    139146}}}
    140 
     147 * '''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]
    141148If you encounter any errors see the [#Troubleshooting Troubleshooting] section below
    142149
     
    192199 *  Flashing a invalid image. There are times when downloading files that the html version was downloaded rather than the file itself.  Check the file extension and file size to be sure you have the correct file.
    193200 *  While programming, if it gets stuck at "Load Debugger: fS3' or fS2, this may mean there are issues with the GSC.  Please re-flash the GSC firmware as demonstrated here: http://trac.gateworks.com/wiki/gsc#GSCUpdates
     201 * Error message: "libgcc_s.so.1 must be installed for pthread_cancel to work”. Try to install gcc-multilib.
    194202
    195203
     
    235243screen /dev/ttyUSB1 115200,cs8
    236244}}}
     245 * You may need to use the sudo command in front of the screen command
    237246 * Typically /dev/tty* nodes are owned by root.dialout which means you need to be root or a member of the dialout group. If this is the case you will get a permissions error and you can either run the command with a 'sudo' in front of it, or add your user to the dialout group
    238247
     
    283292
    2842934. Click on Open next to the Program File field and select the file location of a binary image.
     294 * '''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]
    285295
    2862965. If desired, select a verify file or click on "Set Verify to Program File."