Changes between Version 1 and Version 2 of jtag_instructions

Timestamp:

10/22/2017 06:08:20 AM (7 years ago)

Author:

Chris Lang

Comment:

--

jtag_instructions

@@ -108 +108 @@
 
 You 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:
-{{{
-sudo cat <<EOF > /etc/udev/rules.d/51-gateworks-jtag-ftdi.rules 
-# Gateworks USB-JTAG Programmer for normal users (FTDI 2232C Dual USB-ART/FIFO IC)
-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"
+
+{{{#!bash
+cat << EOF > 51-gateworks-jtag-ftdi.rules 
+# GW16060 Dongle 
+SUBSYSTEM=="usb",ATTR{idVendor}=="0403",ATTR{idProduct}=="6010",MODE="0666",GROUP="users" 
+# GW16061 Gang adapter
+SUBSYSTEM=="usb",ATTR{idVendor}=="0403",ATTR{idProduct}=="6011",MODE="0666",GROUP="users"
 EOF
-sudo udevadm control --reload-rules # reload udev rules
-}}}
- * following this unplug the Gateworks JTAG-USB Programmer and re-connect to re-enumerate the bus and invoke this new rule.
+sudo mv 51-gateworks-jtag-ftdi.rules /etc/udev/rules.d
+sudo chmod 655 /etc/udev/rules.d/51-gateworks-jtag-ftdi.rules
+# cause rules to be re-read and processed (or reboot)
+sudo udevadm control --reload-rules
+sudo service udev restart
+sudo udevadm trigger
+}}} 
 
 The above udev configuration works for Ubuntu, however this configuration may vary on other Linux distro's that use something other than udev.
@@ -138 +145 @@
 ./jtag_usbv4 –p <filename> –u <filename> –v <filename>
 }}}
-
+ * '''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]
 If you encounter any errors see the [#Troubleshooting Troubleshooting] section below
 
@@ -192 +199 @@
  *  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.
  *  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
+ * Error message: "libgcc_s.so.1 must be installed for pthread_cancel to work”. Try to install gcc-multilib.
 
 
@@ -235 +243 @@
 screen /dev/ttyUSB1 115200,cs8
 }}}
+ * You may need to use the sudo command in front of the screen command
  * 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
 
@@ -283 +292 @@
 
 4. Click on Open next to the Program File field and select the file location of a binary image.
+ * '''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]
 
 5. If desired, select a verify file or click on "Set Verify to Program File."