ec297e4bf1
Most of this patch updates documentation and comments for various Luminary boards, supporting two bug fixes by helping to make sense of the current mess: - Recent rev C lm3s811 eval boards didn't work. They must use the ICDI layout, which sets up some signals that the older boards didn't need. This is actually safe and appropriate for *all* recent boards ... so just make "luminary.cfg" use the ICDI layout. - "luminary-lm3s811.cfg", was previously unusable! No VID/PID; and the wrong vendor string. Make it work, but reserve it for older boards where the ICDI layout is wrong. - Default the LM3748 eval board to "luminary.cfg", like the other boards. If someone uses an external JTAG adapter, all boards will use the same workaround (override that default). The difference between the two FT2232 layouts is that eventually the EVB layout will fail cleanly when asked to enable SWO trace, but the ICDI layout will as cleanly be able to enable it. Folk using "luminary.cfg" with Rev B boards won't see anything going wrong until SWO support is (someday) added. Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
19 lines
578 B
INI
19 lines
578 B
INI
#
|
|
# Luminary Micro Stellaris LM3S811 Evaluation Kit
|
|
#
|
|
# http://www.luminarymicro.com/products/stellaris_811_evaluation_kits.html
|
|
#
|
|
# NOTE: this is only for boards *before* Rev C, which adds support
|
|
# for SWO tracing with ADBUS_6 DBG_ENn and BDBUS_4 SWO_EN signals.
|
|
# The "evb_lm3s811" layout doesn't set up those signals.
|
|
#
|
|
# Rev C boards work more like the other Stellaris eval boards. They
|
|
# need to use the "luminary_icdi" layout to work correctly.
|
|
#
|
|
|
|
interface ft2232
|
|
ft2232_device_desc "Stellaris Evaluation Board"
|
|
ft2232_layout evb_lm3s811
|
|
ft2232_vid_pid 0x0403 0xbcd9
|
|
|