Changes between Initial Version and Version 1 of ventana/errata


Ignore:
Timestamp:
10/22/2017 05:28:45 AM (2 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ventana/errata

    v1 v1  
     1{{{#!html
     2          <div id="wikipage" class="trac-content"><p>
     3</p><div class="wiki-toc">
     4<ol>
     5  <li>
     6    <a href="#VentanaErrata">Ventana Errata</a>
     7    <ol>
     8      <li>
     9        <a href="#HW1GW54xx-BAnalogVideoInputnonfunctional">HW1 GW54xx-B Analog Video Input non functional</a>
     10      </li>
     11      <li>
     12        <a href="#HW2GW54xx-BGPSAntennaShortProtectionNotOperational">HW2 GW54xx-B GPS Antenna Short Protection Not Operational</a>
     13      </li>
     14      <li>
     15        <a href="#HW4Tamperswitchnon-functional">HW4 Tamper switch non-functional</a>
     16      </li>
     17      <li>
     18        <a href="#HW5GW52xx-AUSBOTGroutingselectthroughmuxinverted">HW5 GW52xx-A USB OTG routing select through mux inverted</a>
     19      </li>
     20      <li>
     21        <a href="#HW6GW53xx-AB5Vinsufficientformaximumperipheralexpansion">HW6 GW53xx-A/B 5V insufficient for maximum peripheral expansion</a>
     22      </li>
     23      <li>
     24        <a href="#HW7GW51xx-ABpre-matureWatchdogresets">HW7 GW51xx-A/B pre-mature Watchdog resets</a>
     25      </li>
     26      <li>
     27        <a href="#HW8PowerbackfeedwhenboardpowereddownwhileOTGconnectedtoPChost">HW8 Power backfeed when board powered down while OTG connected to PC host</a>
     28      </li>
     29      <li>
     30        <a href="#HW9GW551x-AYUV422semi-planarcapturenotsupporteddoesnotsupport1080p60Hz">HW9 GW551x-A YUV422 semi-planar capture not supported (does not support …</a>
     31      </li>
     32      <li>
     33        <a href="#HW10GW551x-AUSBOTGDeviceModenon-functional">HW10 GW551x-A USB OTG Device Mode non-functional</a>
     34      </li>
     35      <li>
     36        <a href="#HW11GW16111-AI2Cbufferisnotenabled">HW11 GW16111-A I2C buffer is not enabled</a>
     37      </li>
     38      <li>
     39        <a href="#HW12IMXWatchdogresetcanresultinaboardhangwithIMX6Q">HW12 IMX Watchdog reset can result in a board hang with IMX6Q</a>
     40      </li>
     41      <li>
     42        <a href="#HW13PCIebuserrors">HW13 PCIe bus errors</a>
     43      </li>
     44      <li>
     45        <a href="#HW14PCIeGen2complianceenhancement">HW14 PCIe Gen2 compliance (enhancement)</a>
     46      </li>
     47      <li>
     48        <a href="#HW16:micro-SDUHS-Ienhancedclocksupportenhancement">HW16: micro-SD UHS-I enhanced clock support (enhancement)</a>
     49      </li>
     50      <li>
     51        <a href="#HW17GW520x-CUSBroutingtominiPCIeJ7socket">HW17 GW520x-C USB routing to miniPCIe J7 socket</a>
     52      </li>
     53      <li>
     54        <a href="#HW18GW53xx-CDE5Vinrushcurrentlimitedat100mA">HW18 GW53xx-C/D/E 5V inrush current limited at 100mA</a>
     55      </li>
     56      <li>
     57        <a href="#HW19:GW16082irqmapping">HW19: GW16082 irq mapping</a>
     58      </li>
     59    </ol>
     60  </li>
     61</ol>
     62</div><p>
     63</p>
     64<h1 id="VentanaErrata">Ventana Errata</h1>
     65<p>
     66The below errata only affects certain models and certain revisions.
     67</p>
     68<p>
     69Please contact support@… with any questions.
     70</p>
     71<p>
     72<span class="wikianchor" id="hw1"></span>
     73</p>
     74<h2 id="HW1GW54xx-BAnalogVideoInputnonfunctional">HW1 GW54xx-B Analog Video Input non functional</h2>
     75<p>
     76Issue:
     77</p>
     78<ul><li>The three analog video inputs available at connector J27 are not functional on GW54xx products with PCB 02210121-01 (rev B product) because of a pixel bus swap between the video decoder and the i.MX6 processor.
     79</li></ul><p>
     80Resolution:
     81</p>
     82<ul><li>This is resolved on PCB 02210121-02 (rev C)
     83</li></ul><p>
     84Affected Product:
     85</p>
     86<ul><li>GW54xx-B (PCB 02210121-01)
     87</li></ul><p>
     88<span class="wikianchor" id="hw2"></span>
     89</p>
     90<h2 id="HW2GW54xx-BGPSAntennaShortProtectionNotOperational">HW2 GW54xx-B GPS Antenna Short Protection Not Operational</h2>
     91<p>
     92Issue:
     93</p>
     94<ul><li>The GPS antenna short protection circuit is bypassed on the GW54xx products with PCB 02210121-01 (rev B product ). Active antennas are fully functional but not protected against a short circuit.
     95</li></ul><p>
     96Resolution:
     97</p>
     98<ul><li>This is resolved on PCB 02210121-02 (rev C)
     99</li></ul><p>
     100Affected Product:
     101</p>
     102<ul><li>GW54xx-B (PCB 02210121-01) products with GPS loaded
     103</li></ul><p>
     104<span class="wikianchor" id="hw4"></span>
     105</p>
     106<h2 id="HW4Tamperswitchnon-functional">HW4 Tamper switch non-functional</h2>
     107<p>
     108Issue:
     109</p>
     110<ul><li>Early revision GW54xx/GW53xx/GW52xx boards have a capacitor loaded on the tamper circuit which makes it un-usable for the GSC tamper feature (Note that it still works as a GSC GPIO).
     111</li></ul><p>
     112Resolution:
     113</p>
     114<ul><li>GW52xx: remove C68
     115</li><li>GW53xx: remove C110
     116</li><li>GW54xx: remove C473
     117</li></ul><p>
     118Fixed in:
     119</p>
     120<ul><li>GW52xx-C (PCB 02210119-02)
     121</li><li>GW53xx-C (PCB 02210120-02)
     122</li><li>GW54xx-E (PCB 02210121-04)
     123</li></ul><p>
     124Affected Products:
     125</p>
     126<ul><li>GW52xx-A/B (PCB 02210119-00, 02210119-01)
     127</li><li>GW53xx-A/B (PCB 02210120-00, 02210120-01)
     128</li><li>GW54xx-A/B/C/D (PCB 02210121-00, 02210121-01, 02210121-02, 02210121-03)
     129</li></ul><p>
     130<span class="wikianchor" id="hw5"></span>
     131</p>
     132<h2 id="HW5GW52xx-AUSBOTGroutingselectthroughmuxinverted">HW5 GW52xx-A USB OTG routing select through mux inverted</h2>
     133<p>
     134Issue:
     135</p>
     136<ul><li>The GW52xx uses a 1-to-2 mux to route USB OTG to either the front-panel micro-USB or to one of the PCI sockets (which the USB EHCI host routes to the other PCI socket). The initial revision of the GW52xx (GW52xx-A) defaulted this to route to the miniPCIe socket when the desire is to have it routed by default on power-up to the front panel connector.
     137</li></ul><p>
     138Resolution:
     139</p>
     140<ul><li>Ground OTG_ID via a buffer that is active-high enabled by the USBOTG_SKT GPIO so that when USBOTG_SKT GPIO is high to select PCI SKT, ID gets grounded and forces it to host mode
     141</li><li>Add a 1k pulldown to USBOTG_SKT which is stronger than the 100k pullup at powerup so that the power-on default is front-panel
     142</li></ul><p>
     143Work-around:
     144</p>
     145<ul><li>steer GPIO2 manually in software:
     146<pre class="wiki">echo 2 &gt; /sys/class/gpio/export
     147echo out &gt; /sys/class/gpio/gpio2/direction # will default to output low
     148</pre></li></ul><p>
     149Fixed in:
     150</p>
     151<ul><li>GW52xx-B (PCB 02210119-01)
     152</li></ul><p>
     153Affected Products:
     154</p>
     155<ul><li>GW52xx-A (PCB 02210119-00)
     156</li></ul><p>
     157<span class="wikianchor" id="hw6"></span>
     158</p>
     159<h2 id="HW6GW53xx-AB5Vinsufficientformaximumperipheralexpansion">HW6 GW53xx-A/B 5V insufficient for maximum peripheral expansion</h2>
     160<p>
     161Issue:
     162</p>
     163<ul><li>The 800mA 5V supply on the intial GW53xx revisions is not sufficient to power the variety of peripherals that are possible such as: two USB devices (potentially 500mA ea), CAN transceiver (70mA max), LVDS connector (varies per display but est 500mA), HDMI termination (50mA max)
     164</li></ul><p>
     165Work-around:
     166</p>
     167<ul><li>Limit peripheral expansion
     168</li></ul><p>
     169Fixed in:
     170</p>
     171<ul><li>GW53xx-C (PCB 02210120-02) - 5V supply replaced with 1.5A supply. Each USB port can supply a max of 500mA each and the additional peripherals have 500mA allocated for them to share (typically most of this is optional for an LVDS display device).
     172</li></ul><p>
     173Affected Products:
     174</p>
     175<ul><li>GW53xx-A/B (PCB 02210120-00, PCB 02210120-01)
     176</li></ul><p>
     177<span class="wikianchor" id="hw7"></span>
     178</p>
     179<h2 id="HW7GW51xx-ABpre-matureWatchdogresets">HW7 GW51xx-A/B pre-mature Watchdog resets</h2>
     180<p>
     181Issue:
     182</p>
     183<ul><li>The GW51xx-A and GW51xx-B is susceptible to pre-mature IMX6 CPU watchdog timeouts due to the RTC XTAL input not being grounded. Noise on this signal which can occur at higher temperatures can cause this to be used as the xtal source instead of the intended internal oscillator.
     184</li></ul><p>
     185Work-around:
     186</p>
     187<ul><li>Disable IMX6 CPU watchdog (this is done in the current Ventana bootloader by removing the device-node entry for the CPU watchdog).
     188</li><li>Use GSC CPU watchdog if a watchdog is necessary (this is available with GSC firmware v44)
     189</li></ul><p>
     190Fixed in:
     191</p>
     192<ul><li>GW51xx-C (PCB 02210118-02)
     193</li></ul><p>
     194Affected Products:
     195</p>
     196<ul><li>GW51xx-A/B (PCB 02210118-00, 02210118-01)
     197</li></ul><p>
     198<span class="wikianchor" id="hw8"></span>
     199</p>
     200<h2 id="HW8PowerbackfeedwhenboardpowereddownwhileOTGconnectedtoPChost">HW8 Power backfeed when board powered down while OTG connected to PC host</h2>
     201<p>
     202Issue:
     203</p>
     204<ul><li>When an affected board is connected to a powered PC Host over USB OTG and the board is powered down, an unusual amount of current is allowed to backfeed through the IMX6 CPU and can potentially cause the 3.3V primary supply to provide partial voltage affecting the 3.3V power LED.
     205</li></ul><p>
     206Work-around:
     207</p>
     208<ul><li>Remove OTG connection when powering down
     209</li></ul><p>
     210Fixed in:
     211</p>
     212<ul><li>GW51xx-C (PCB 02210118-02)
     213</li><li>GW52xx-B (PCB 02210119-01)
     214</li><li>GW53xx-C (PCB 02210120-02)
     215</li><li>GW54xx-E (PCB 02210121-04)
     216</li></ul><p>
     217Affected Products:
     218</p>
     219<ul><li>GW51xx-A/B (PCB 02210118-00, 02210118-01)
     220</li><li>GW52xx-A (PCB 02210119-00)
     221</li><li>GW53xx-A/B (PCB 02210120-00, PCB 02210120-01)
     222</li><li>GW54xx-A/B/C/D (PCB 02210121-00, PCB 02210121-01, PCB 02210121-02, PCB 02210121-03)
     223</li></ul><p>
     224<span class="wikianchor" id="hw9"></span>
     225</p>
     226<h2 id="HW9GW551x-AYUV422semi-planarcapturenotsupporteddoesnotsupport1080p60Hz">HW9 GW551x-A YUV422 semi-planar capture not supported (does not support 1080p@60Hz)</h2>
     227<p>
     228Issue:
     229</p>
     230<ul><li>The GW551x-A is missing some signals required for 'gated clock' capture mode and as such only YUV422 BT656 capture from the HDMI receiver is possible. In this mode any resolution over 1080p@30Hz is not supported. See <a class="wiki" href="/wiki/Yocto/Video_In#HardwareCapabilitiesandvideodatabasemode">here</a> for more info.
     231</li></ul><p>
     232Work-around:
     233</p>
     234<ul><li>Use default YUV422 BT656 capture mode (which will be the default when using the latest bootloader/kernel).
     235</li></ul><p>
     236Fixed in:
     237</p>
     238<ul><li>GW551x-B (PCB 02210161-01)
     239</li></ul><p>
     240Affected Products:
     241</p>
     242<ul><li>GW551x-A (PCB 02210161-00)
     243</li></ul><p>
     244<span class="wikianchor" id="hw10"></span>
     245</p>
     246<h2 id="HW10GW551x-AUSBOTGDeviceModenon-functional">HW10 GW551x-A USB OTG Device Mode non-functional</h2>
     247<p>
     248Issue:
     249</p>
     250<ul><li>The GW551x-A does not connect the USBOTG_VBUS signal which is needed by the USB OTG host controller in order to go into device mode. This also causes hot-swap events to not trigger a bus re-enumeration when a device is hot-swapped in host mode.
     251</li></ul><p>
     252Work-around:
     253</p>
     254<ul><li>Do not use USB OTG device mode
     255</li><li>Force a re-enumeration manually on a hot-swap event, or hot-swap at the microAB connector (thus causing ID to change state)
     256</li></ul><p>
     257Fixed in:
     258</p>
     259<ul><li>GW551x-B (PCB 02210161-01)
     260</li></ul><p>
     261Affected Products:
     262</p>
     263<ul><li>GW551x-A (PCB 02210161-00)
     264</li></ul><p>
     265<span class="wikianchor" id="hw11"></span>
     266</p>
     267<h2 id="HW11GW16111-AI2Cbufferisnotenabled">HW11 GW16111-A I2C buffer is not enabled</h2>
     268<p>
     269Issue:
     270</p>
     271<ul><li>The GW16111-A does not enable the I2C buffer properly making the 3pin I2C header non-functional
     272</li></ul><p>
     273Work-around:
     274</p>
     275<ul><li>None
     276</li></ul><p>
     277Fixed in:
     278</p>
     279<ul><li>GW16111-B (PCB 02210162-01)
     280</li></ul><p>
     281Affected Products:
     282</p>
     283<ul><li>GW16111-A (PCB 02210162-00)
     284</li></ul><p>
     285<span class="wikianchor" id="hw12"></span>
     286</p>
     287<h2 id="HW12IMXWatchdogresetcanresultinaboardhangwithIMX6Q">HW12 IMX Watchdog reset can result in a board hang with IMX6Q</h2>
     288<p>
     289Issue:
     290</p>
     291<ul><li>The Power Management IC (PMIC) on the Ventana boards does not get reset in the event of an IMX watchdog reset. This can cause a board hang under certain circumstances: If the processor was running at 400MHz at the time the reset occurred and a PMIC driver is being used for dynamic voltage scaling which has reduced the IMX voltage rails for 400MHz operation (referred to as ldo-bypass mode). In this specific case, the IMX will come out of reset at 800MHz (per OTP fuse configuration) and the voltage rails to the IMX will be insufficient for that frequency and the board will hang in the BOOT ROM. The voltage rail differential has been found to not cause an issue on IMX6S or IMX6DL cpus and it only causes an issue on the IMX6Q. Because this is an internal reset the GSC boot watchdog (not to be confused with the standard GSC watchdog) does not get enabled. Note that an IMX watchdog reset that can cause this occurs in the following situations: watchdog timeout when using the IMX watchdog (instead of the GSC watchdog), a kernel crash, a soft reboot.
     292</li></ul><p>
     293Work-arounds:
     294</p>
     295<ul><li>Use the GSC watchdog (which is a more robust means of watchdog protection as it power cycles the entire board) instead of the IMX watchdog. This means you would enable the GSC watchdog (see <a class="wiki" href="/wiki/gsc#watchdog">gsc</a>) as well as use the GSC to reboot the board (see <a class="wiki" href="/wiki/gscreboot">here</a>).
     296</li><li>Disable PMIC dynamic voltage scaling below the 800MHz operating point by either:
     297<ul><li>disabling Dyanmic Voltage and Scaling completely by disabling the cpufreq driver (voltage rails will always be at their maximum value)
     298</li><li>disabling the PMIC driver (voltage rails will always be at their maximum value but CPU frequency is allowed to shift)
     299</li><li>disable the 400MHz operating point (thus ensuring the PMIC voltage rails are always sufficient for powerup at 800MHz)
     300</li><li>adjusting the 400MHz operating point voltage rails up to the 800Mhz values
     301</li></ul></li></ul><p>
     302Resolution:
     303</p>
     304<ul><li>A change has been made at the PCB level to allow the IMX6 external watchdog reset signal to reset the PMIC. This requires a kernel update (pending) as well as a bootloader update: <a class="ext-link" href="https://github.com/Gateworks/u-boot-imx6/commit/cf7e51ea03ad68a86a77c5764c8712942867bcfb"><span class="icon">​</span>cf7e51ea</a>
     305</li><li>All Ventana BSP's are now using ldo-enabled mode which means the PMIC rails are always set at a safe-maximum and the internal IMX6 LDO further regulates the voltage as needed. This avoids the potential issue of the PMIC rails being too low at reset time.
     306</li></ul><p>
     307Fixed in:
     308</p>
     309<ul><li>GW51xx*-E (PCB 02210118-04)
     310</li><li>GW520x*-D (PCB 02210119-03)
     311</li><li>GW5220*-B (PCB 02210166-01)
     312</li><li>GW53xx*-E (PCB 02210120-04)
     313</li><li>GW54xx*-D (PCB 02210121-03)
     314</li><li>GW551x*-C (PCB 02210161-02)
     315</li><li>GW552x*-C (PCB 02210147-02)
     316</li></ul><p>
     317<span class="wikianchor" id="hw13"></span>
     318</p>
     319<h2 id="HW13PCIebuserrors">HW13 PCIe bus errors</h2>
     320<p>
     321Issue:
     322</p>
     323<ul><li>An out-of-spec DC bias of the clock output on the IMX6 to the PCI clock buffer input can result in noise from the processor being coupled to the PCIe clock ultimately causing PCIe bus errors. This can result in hangs during PCI enumeration and PCI device configuration as well as unexpected errors during device operation. It has been found that this occurs on newer silicon IMX6S/IMX6DL <a class="changeset" href="/changeset/1" title="Initial Import">r1</a>.2 and IMX6Q <a class="changeset" href="/changeset/1" title="Initial Import">r1</a>.3 (reported as <a class="changeset" href="/changeset/1" title="Initial Import">r1</a>.5 by the bootloader which is technically the ROM version) and has not been found on earlier silicon revisions.
     324</li></ul><p>
     325Work-arounds:
     326</p>
     327<ul><li>a board-level rework adding a 100ohm resistor across the CLK-/+ inputs to the clock buffer eliminates the issue.
     328</li></ul><p>
     329Affected Products:
     330</p>
     331<ul><li>Boards using PCIe bridge and clock buffer:
     332<ul><li>GW52xx:
     333</li><li>GW53xx
     334</li><li>GW552x 
     335</li></ul></li></ul><p>
     336Resolution:
     337</p>
     338<ul><li>Next revision product will incorporate clock generators in order to fully support PCIe Gen2 which will also resolve this clock coupling issue.
     339</li><li>Current product will be bumped to a new BOM level (dot level) that adds the 100ohm resistor across the CLK-/+ inputs.
     340</li></ul><p>
     341Fixed in:
     342</p>
     343<ul><li>GW51xx*-E (PCB 02210118-04)
     344</li><li>GW52xx:
     345<ul><li>GW520x*-D (PCB 02210119-03)
     346</li><li>GW5200-C.2 (PCB 02210119-02)
     347</li><li>GW5201-B.2 (PCB 02210119-01)
     348</li><li>GW5204-C.1 (PCB 02210119-02)
     349</li></ul></li><li>GW522x:
     350<ul><li>GW5220*-C (PCB 02210166-02)
     351</li><li>GW5220-B.1 (PCB 02210166-01)
     352</li></ul></li><li>GW53xx:
     353<ul><li>GW53xx*-E (PCB 02210120-04)
     354</li><li>GW5300-C.1 (PCB 02210120-02)
     355</li><li>GW5301-B.1 (PCB 02210120-01)
     356</li><li>GW5304-C.2 (PCB 02210120-02)
     357</li><li>GW5304-D.2 (PCB 02210120-04)
     358</li><li>GW5310-D.1 (PCB 02210120-04)
     359</li><li>GW5311-B.1 (PCB 02210120-01)
     360</li></ul></li><li>GW551x*-C (PCB 02210161-02)
     361</li><li>GW552x*-C (PCB 02210147-02)
     362</li></ul><p>
     363<span class="wikianchor" id="hw14"></span>
     364</p>
     365<h2 id="HW14PCIeGen2complianceenhancement">HW14 PCIe Gen2 compliance (enhancement)</h2>
     366<p>
     367Issue:
     368</p>
     369<ul><li>The IMX6 LVDS clock commonly used as a PCIe clock does not meet the clock jitter requirements of PCIe Gen2. Note that Gen2 link training is currently disabled in the Gateworks BSP's so that we are within spec.
     370</li></ul><p>
     371Work-around:
     372</p>
     373<ul><li>Disable Gen2 PCIe link in the kernel. Note that this has been done in the Gateworks <a class="wiki" href="/wiki/OpenWrt">OpenWrt</a> 14.08 and Yocto v1.6-v1.8 kernels.
     374</li></ul><p>
     375Enhancement:
     376</p>
     377<ul><li>Next revision product will incorporate clock generators in addition to providing the IMX6 with a clock input from the generator.
     378</li><li>A software update will be required to configure PCIe clock input on the IMX6 and re-enable Gen2 link training. Without the software update older software will keep Gen2 disabled without any adverse affects.
     379</li></ul><p>
     380Added in:
     381</p>
     382<ul><li>GW51xx*-E (PCB 02210118-04)
     383</li><li>GW520x*-D (PCB 02210119-03)
     384</li><li>GW5220*-C (PCB 02210166-02)
     385</li><li>GW53xx*-E (PCB 02210120-04)
     386</li><li>GW54xx*-E (PCB 02210121-03)
     387</li><li>GW551x*-C (PCB 02210161-02)
     388</li><li>GW552x*-C (PCB 02210147-02)
     389</li></ul><p>
     390<span class="wikianchor" id="hw16"></span>
     391</p>
     392<h2 id="HW16:micro-SDUHS-Ienhancedclocksupportenhancement">HW16: micro-SD UHS-I enhanced clock support (enhancement)</h2>
     393<p>
     394Issue:
     395</p>
     396<ul><li>micro-SD UHS-I compliant cards allow for clock frequencies above the 50MHz High Speed (HS) standard resulting in improved bus bandwidth. This requires the I/O rail to be switched from 3.3V to 1.8V.
     397</li><li>Note that both card and controller (IMX6) need to support this switchable I/O rail in order for cards to be used with the higher clock. If both do not support UHS-I then traditional HS clock is used and you gain no performance advantage.
     398</li><li>Note that a software update may be required for board revisions that incorporate UHS-I support for microSD to work at all as one of the unused NAND chip-select signals is routed to the microSD host controller voltage select. Older Gateworks kernels pinmuxed this signal to a 2nd NAND chip-select which puts the microSD voltage select in an invalid state.
     399</li></ul><p>
     400Change:
     401</p>
     402<ul><li>A switchable I/O rail has been added to baseboard products that support micro-SD card slots.
     403</li></ul><p>
     404Added in:
     405</p>
     406<ul><li>GW520x*-D (PCB 02210119-03)
     407</li><li>GW5220*-B (PCB 02210166-01)
     408</li><li>GW53xx*-E (PCB 02210120-04)
     409</li><li>GW54xx*-E (PCB 02210121-03)
     410</li></ul><p>
     411<span class="wikianchor" id="hw17"></span>
     412</p>
     413<h2 id="HW17GW520x-CUSBroutingtominiPCIeJ7socket">HW17 GW520x-C USB routing to miniPCIe J7 socket</h2>
     414<p>
     415Issue:
     416</p>
     417<ul><li>The USB sideband signals on Mini-PCIe site J7 are non-functional.
     418</li></ul><p>
     419Work-around:
     420</p>
     421<ul><li>Use J8 USB: Note the J8 site must be configured in software to support USB since it shares the signals with the front panel OTG port. See:
     422<ul><li><a class="ext-link" href="http://trac.gateworks.com/wiki/ventana/bootloader#USBFront-panelvsPCIesocketrouting"><span class="icon">​</span>bootloader USB routing config</a>
     423</li><li><a class="ext-link" href="http://trac.gateworks.com/wiki/ventana/gw5200usb"><span class="icon">​</span>GW5200 USB</a>
     424</li></ul></li><li>If USB signaling is required on both sites, a wire-mod can be performed to the board by the factory. Contact support@… for more information.
     425</li></ul><p>
     426Affected Product:
     427</p>
     428<ul><li>GW520x-C (PCB 02210119-02)
     429</li></ul><p>
     430Fixed in:
     431</p>
     432<ul><li>GW520x-D (PCB 02210119-03)
     433</li></ul><p>
     434<span class="wikianchor" id="hw18"></span>
     435</p>
     436<h2 id="HW18GW53xx-CDE5Vinrushcurrentlimitedat100mA">HW18 GW53xx-C/D/E 5V inrush current limited at 100mA</h2>
     437<p>
     438Issue:
     439</p>
     440<ul><li>In order to address <a class="wiki" href="/wiki/ventana/errata#hw6">HW6</a>, the 5V boost was updated to allow a max current of 1.5A. This new device was found to have an inrush current limitation of around 100mA which causes the device to go into a current limit fault condition when exceeded. Devices, such as LVDS displays, that pull more than this on power on will not reliably power on.
     441</li></ul><p>
     442Work-around:
     443</p>
     444<ul><li>Isolate the 5V from the LVDS cable and wire it to VUSB from the front-panel USB connector. In the bootloader you need to execute <tt>usb start</tt> in order to turn on VUSB but this is not needed once the kernel boots.
     445</li></ul><p>
     446Affected Product:
     447</p>
     448<ul><li>GW53xx-C (PCB 02210120-02)
     449</li><li>GW53xx-D (PCB 02210120-03)
     450</li><li>GW53xx-E (PCB 02210120-04)
     451</li></ul><p>
     452Fixed in:
     453</p>
     454<ul><li>GW53xx-F (PCB 02210120-05) - New 5V supply added for CAN transceiver, HDMI DDC, and LVDS.
     455</li></ul><p>
     456<span class="wikianchor" id="hw19"></span>
     457</p>
     458<h2 id="HW19:GW16082irqmapping">HW19: GW16082 irq mapping</h2>
     459<p>
     460Issue:
     461</p>
     462<ul><li>The TI XIO2001 PCIe-to-PCI bridge on the GW16082 has its interrupt mapping reversed with
     463regards to the PCI specification:
     464</li></ul><table class="wiki">
     465<tr><th> Slot </th><th> proper pin1 irq </th><th> GW16082 pin1 irq
     466</th></tr><tr><td> 12     </td><td> INTA              </td><td> INTD
     467</td></tr><tr><td> 13     </td><td> INTA              </td><td> INTC
     468</td></tr><tr><td> 14     </td><td> INTA              </td><td> INTB
     469</td></tr><tr><td> 15     </td><td> INTA              </td><td> INTA
     470</td></tr></table>
     471<p>
     472Work-around:
     473</p>
     474<ul><li>for kernels that obtain irqs through device-tree mapping, a device-tree fixup can be implemented in the bootloader that provides the actual irq mapping for the XIO2001 bridge. This fixup is present in Gateworks bootloader intended for kernels based on Linux 3.18+ (PCI needs to be enabled in the bootloader for this fixup: <tt>setenv pcidisable; saveenv</tt>
     475</li><li>for kernels that do not obtain irqs through device-tree mapping, a custom swizzle function can be implemented in the kernel for use when mapping interrupts to devices downstream from the XIO2001 bridge. This fixup is present in Gateworks downstream vendor kernels based on Linux 3.10 and 3.14.
     476</li></ul><p>
     477Affected Product:
     478</p>
     479<ul><li>GW16082-A (PCB 02210130-00)
     480</li><li>GW16082-B (PCB 02210130-01)
     481</li></ul
     482}}}