Skip to main content

Topics

This section allows you to view all Topics made by this member. Note that you can only see Topics made in areas you currently have access to.

Topics - paulreimer

1
Breakout boards / FT2232H Breakout Board for SWD / ARM Programming
I would like to use the FT2232H breakout board to program the LPC1114FN28 ARM DIP MCU.
Please raise your hand if you have done this! What protocol did you use (I think only SWD is supported), which programming software did you use, and did you need to add any hardware components (e.g. buffers, pull-ups) between the breakout board and the MCU?

In a recent topic I was able to use the FT2232H breakout to talk JTAG to my STM32F4 Discovery board (using *mostly* the SWD header pins on the Discovery board, with the DI pin on separate header).
viewtopic.php?f=50&t=4532
It was left unclear to me what the buffers on typical FT2232H-based JTAG programmers are for. Why are they needed, and why are they different for each programmer emulation? If buffers *need* to be added for SWD communication, I would prefer to take a Bus Blaster v1 approach and purchase the needed buffers only for SWD@3.3v. How do I spec those and/or will any of the buffers used in the Bus Blaster v1 BOM work for this?

Thanks!
2
Breakout boards / Using FT2232H Breakout Board with JTAG/OpenOCD
Hi all,

I am trying to use OpenOCD to program/flash my STM32F4 Discovery board. Instead of using the ST-LINK interface, I would like to confirm JTAG/SWD programming for this board, before moving on to JTAG programming of LPC1114 ARM DIP chips. I have many FT2232H breakout boards on-hand, which I already use with AVRdude to program my AVR chips (SPI/ISP).

My question is: how can I configure the FT2232H breakout board with openocd, and what pinout should I use for JTAG programming over the SWD debug bus? Is the Bus Blaster really required for this, and the FT2232H breakout is not enough to do this?

I have started followed a guide so far:
http://dangerousprototypes.com/2011/11/ ... s-blaster/

, which uses the Bus Blaster, and openocd configuration files to match the default Bus Blaster buffer configuration (which I understand to be the JTAGkey layout?) Why are the programmable CPLD buffers needed on the Bus Blaster, and would I need to add similar (or more basic) components in order to talk JTAG to the Discovery?

Thanks for the help,
Paul

( ! ) Fatal error: Uncaught exception 'Elk_Exception' with message 'Please try again. If you come back to this error screen, report the error to an administrator.' in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
( ! ) Elk_Exception: Please try again. If you come back to this error screen, report the error to an administrator. in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
Call Stack
#TimeMemoryFunctionLocation
10.01202281592session_write_close ( )...(null):0
20.01232413184ElkArte\sources\subs\SessionHandler\DatabaseHandler->write( )...(null):0
30.01232413960Database_MySQL->query( ).../DatabaseHandler.php:119
40.05562552696Database_MySQL->error( ).../Db-mysql.class.php:273