summaryrefslogtreecommitdiff
path: root/tools/xsvf_tools/svf2xsvf.py
diff options
context:
space:
mode:
authorntfreak <ntfreak@b42882b7-edfa-0310-969c-e2dbd0fdcd60>2009-08-18 14:41:58 +0000
committerntfreak <ntfreak@b42882b7-edfa-0310-969c-e2dbd0fdcd60>2009-08-18 14:41:58 +0000
commita634b5d52e9a818f7dea91958df7d8a0cd1c1d04 (patch)
tree4eec5fa23f7dbb8346e5483f99ce7e0376305352 /tools/xsvf_tools/svf2xsvf.py
parentbb5086b83e098ea9839c4d44b486dacdd11da8d3 (diff)
downloadopenocd+libswd-a634b5d52e9a818f7dea91958df7d8a0cd1c1d04.tar.gz
openocd+libswd-a634b5d52e9a818f7dea91958df7d8a0cd1c1d04.tar.bz2
openocd+libswd-a634b5d52e9a818f7dea91958df7d8a0cd1c1d04.tar.xz
openocd+libswd-a634b5d52e9a818f7dea91958df7d8a0cd1c1d04.zip
Jonas Horberg [jhorberg@sauer-danfoss.com]
https://lists.berlios.de/pipermail/openocd-development/2009-August/009939.html 1. It can only be built with the FTD2XX driver. libftdi supports FT2232H/FT4232H since version 0.16 2. A speed value of 0 is used as a RTCK request indicator. This clashes with the valid clock division value 0 that provide the highest fixed clock frequency. 3. The ft2232_speed_div function return the maximum selectable frequency (30MHz) when RTCK is activated. It should return 0. 4. The ft2232_khz function return ERROR_OK when RTCK is requested even for devices lacking RTCK support. It should return ERROR_FAIL so the upper driver layers can detect this and try to fallback to a fixed frequency. 5. FT2232H/FT4232H have a backward compatibility function that divide the clock by 5 to get the same frequency range as FT2232D. There is no code that disable this functionality. I can not find anything about if this is enabled or disabled by default. I think it is safest to actively disable it. git-svn-id: svn://svn.berlios.de/openocd/trunk@2591 b42882b7-edfa-0310-969c-e2dbd0fdcd60
Diffstat (limited to 'tools/xsvf_tools/svf2xsvf.py')
0 files changed, 0 insertions, 0 deletions