Changes between Version 49 and Version 50 of jtag_instructions

Timestamp:

02/28/2024 11:10:46 PM (9 months ago)

Author:

Ryan Erbstoesser

Comment:

add note about i.mx8m plus som and usb required

jtag_instructions

@@ -117 +117 @@
 Please 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.
 
-1. Connect the JTAG-USB Programmer to the JTAG header on a Gateworks Single Board Computer using the attached ribbon cable.
-
-2. Connect the JTAG-USB Programmer to a PC USB port using the supplied USB cable.
-
-3. Verify FTDI module is not loaded.
+1. With the SBC powered off, connect the JTAG-USB Programmer to the JTAG header on a Gateworks Single Board Computer (SBC) using the attached ribbon cable.
+
+1. Connect the JTAG-USB Programmer to a PC USB port using the supplied USB cable.
+
+1. If using a SBC with a i.MX8M Plus CPU (Venice GW7xxx-2x or GW74xx), attach a USB cable from the USB port on the SBC to the the desktop/laptop host PC. 
+
+1. Verify FTDI module is not loaded.
  * {{{ sudo rmmod ftdi_sio }}}
 
-4. Apply power to the Gateworks board.
-
-5. Run the JTAG program (jtag_usbv4) with the syntax shown below to program a .bin file to the boards flash:
+1. Apply power to the Gateworks board.
+
+1. Run the JTAG program (jtag_usbv4) with the syntax shown below to program a .bin file to the boards flash:
 {{{
 ./jtag_usbv4 –p <filename> 
@@ -135 +137 @@
   * If you encounter any errors see the [#Troubleshooting Troubleshooting] section below.
 
-jtag_usbv4 options:
+'''jtag_usbv4 options:'''
 ||= Option =||= Operation =||= Notes =||
 ||-p        ||Program Flash device using specified filename|| ||
@@ -145 +147 @@
 
 ==== Examples ====
-programming a firmware image:
+Programming a firmware image:
 {{{#!bash
 ./jtag_usbv4 -p venice-imx8mm_u-boot_spl.bin
@@ -170 +172 @@
 ==== Troubleshooting ====
 
+ * If using a SBC with a i.MX8M Plus CPU (Venice GW7xxx-2x or GW74xx), additionally attach a USB cable from the USB port on the SBC to the the desktop/laptop host PC. 
  * Permission denied: '''libusb couldn't open USB device''' - [#LinuxpermissionsonUSBdevice see above] regarding Linux permissions
  * 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]